Taking Card and ACH Payments as a Freelancer

Model the processor’s all-in cost at your normal invoice size

Processor pricing may include percentage fees, fixed transaction fees, instant-payout charges, international costs, and dispute fees. Model the all-in cost at your typical invoice size.

A paid screen is not the same as cash settled in your bank

Payout timing affects cash flow. A client can click 'paid' on Friday while the bank deposit arrives days later; milestone dates should leave room for settlement before you release irreversible deliverables.

Make the statement descriptor recognizable to the buyer

Statement descriptors should help clients recognize the charge. A cryptic legal-entity abbreviation can trigger avoidable disputes when the buyer remembers only your brand name.

Surcharges need both network-rule and state-law checks

Surcharges and convenience fees are regulated by card-network rules and state law. Do not add a surprise percentage to every invoice without checking the processor's current requirements and the client's jurisdiction.

Reduce checkout friction without weakening payment verification

A payment method is only useful if the client can complete it without an avoidable support loop. Put the amount, due date, accepted rails, and a working payment link or bank instruction in one place, and test the client view before sending the first large invoice. Convenience does not mean relaxing fraud controls: verify bank-detail changes out of band, keep processor authentication tools enabled where appropriate, and do not move a high-value payment to a new rail solely because an email asks you to.

Processing cost is only one line in the decision

Choose payment rails by ticket size, client behavior, speed, and dispute exposure—not by one advertised percentage. Cards are easy for clients and can reduce collection friction, but the processor may charge a percentage plus fixed fee and can impose reserves or holds. ACH is often cheaper for large B2B invoices, though bank-verification, return timing, fraud controls, and client convenience differ by provider. Compare the full fee schedule: standard processing, international cards, instant payout, refunds, disputes, and any monthly platform fee. On a $5,000 invoice, a 2.9% + $0.30 card price would be about $145.30 before other charges, which is large enough to justify comparing current ACH pricing.

Set up reconciliation before the first payment. Record the $5,000 gross charge as revenue and the processor fee separately rather than calling the lower bank deposit the sale. Do the same for refunds and chargebacks so year-end 1099-K totals can be tied back to the books. Use a statement descriptor the client will recognize, and do not add a card surcharge simply because the processor has a button for it. Card-network rules and state law can govern surcharges or convenience fees and can change; check the current processor and jurisdictional rules. For high-value invoices, offer more than one sensible option so payment convenience does not quietly erase margin.

Compare payment methods using the all-in economics of a typical invoice. For each processor or bank option, record card percentage and fixed fee, ACH fee or cap, monthly fee, payout timing, chargeback fee, reserve/hold policy, refund treatment, international/currency fees, and whether invoices automatically reconcile. On a $5,000 invoice, a 3% card cost is $150 before fixed fees, while an ACH option may be materially lower; the client convenience may still justify card acceptance for some services. Decide whether the business absorbs fees into pricing or uses a permitted surcharge/convenience-fee approach only after checking card-network rules and applicable state law. Do not add a surprise ‘3% processing fee’ at checkout if the contract and legal framework do not support it.

Build controls for payout and dispute risk. Use a statement descriptor customers will recognize, send a receipt, tie the payment to the contract/invoice, and get written acceptance for meaningful milestones. Reconcile gross customer payments to processor fees and net bank deposits so accounting and 1099-K reporting can be explained later. Keep enough working capital that a processor hold does not make payroll or taxes impossible; new accounts, unusual transaction size, high refund rates, or disputes can trigger reviews. For very large projects, consider whether bank transfer, ACH, or staged payments reduce card-dispute exposure while still giving the client a convenient method. The cheapest payment rail is not always best, but the business should know what it is paying for speed, convenience, and risk allocation.

Test one month of real transactions before choosing a default rail. Calculate the weighted fee across your actual invoice sizes, not the processor’s headline percentage alone. Ten $100 card payments and one $10,000 card payment can create very different fixed-fee economics and dispute exposure. Check whether ACH settlement is fast enough for your cash cycle and whether clients value card rewards enough to resist bank transfer. For international clients, include currency conversion and cross-border fees. Then write the preferred method into the proposal and invoice while still offering an approved alternative where useful. Payment choice should be intentional at sale time rather than negotiated after the invoice is already overdue.

Payment-rail setup before the first invoice link

1. Compare all-in fees at your normal invoice size.
2. Verify ACH instruction changes out of band.
3. Check surcharge rules before passing fees through.
4. Use a recognizable statement descriptor.
5. Reconcile gross payments to net deposits and fees.

Payment-method questions before you pass fees through