Adding a pay-now button to an invoice removes the gap between a client deciding to pay you and actually doing it. That gap is where a great deal of late payment lives — not refusal, just the friction of logging into a banking portal and typing account details from a PDF.
The cost of removing that friction is a percentage of every payment. Whether that is a good trade depends almost entirely on your invoice sizes, and the answer flips as the amounts get larger.
How processing fees are structured
Almost every card processor charges the same shape of fee: a percentage of the transaction plus a small fixed amount. For domestic card payments the percentage commonly sits near 3% with a fixed component of roughly 20–30 cents, though published rates vary by provider, country and product, and change often enough that you should check current pricing rather than trusting a figure in an article.
That shape matters more than the exact numbers, because the two components dominate at opposite ends. On a small invoice the fixed fee is the painful part — 30 cents on a $10 payment is 3% again, doubling the effective rate. On a large invoice the fixed fee disappears and the percentage is everything: 3% of $10,000 is $300 to receive a payment a bank transfer would move for a fraction of that.
Several surcharges sit on top and catch people out. Manually keyed cards usually cost more than ones entered by the customer. International cards typically add a percentage. Currency conversion carries a spread that is often larger than the headline fee. And chargebacks generally attract a flat fee whether or not you ultimately win the dispute.
Matching the rail to the invoice size
The practical rule that follows: offer cards for convenience on smaller invoices, and offer a bank rail for larger ones.
Most processors support bank debits — ACH in the US, SEPA direct debit in the euro area, and equivalents elsewhere — at a much lower cost, frequently a small percentage capped at a few dollars. That cap is the whole point: it converts an unbounded percentage into a fixed maximum, which is what makes large invoices viable through a payment page at all.
A sensible default for most small businesses is to offer both on every invoice and let the client choose. Card payers get convenience, bank payers cost you almost nothing, and you are not making the decision on the client’s behalf. Where invoices are consistently large, it is entirely reasonable to offer the bank option only and treat cards as an exception.
| Invoice size | Reasonable default | Why |
|---|---|---|
| Under ~$100 | Card or wallet | Speed matters; the fixed fee is the main cost and it is small in absolute terms |
| ~$100 to ~$1,000 | Card and bank debit, client chooses | Percentage starts to bite but convenience still has real value |
| Over ~$1,000 | Bank debit or transfer, card on request | A capped bank fee saves substantially more than the convenience is worth |
| International | Compare landed amount, not headline fee | Conversion spread and cross-border surcharges usually exceed the stated rate |
Should you pass the fee on?
Surcharging — adding the processing cost to the customer’s bill — is tempting and legally constrained. Rules differ sharply by country and by card scheme: some jurisdictions prohibit card surcharges outright, some cap them at your actual cost, and card network rules impose their own conditions including advance disclosure. Consumer transactions are typically more restricted than business ones.
Because the rules are genuinely local, the safe sequence is to check your jurisdiction and your processor’s terms before adding any surcharge. Getting this wrong risks penalties from the card networks as well as regulators.
Two alternatives avoid the question. A discount for paying by bank transfer is often permitted where a card surcharge is not, and it presents better to customers. Or simply price the cost in: if a meaningful share of clients pay by card, building roughly 3% into your rates spreads the cost invisibly and avoids the awkward line item entirely.
Practical setup
A payment link on the invoice is the minimum useful implementation — a URL that opens a hosted payment page with the amount and reference pre-filled, so the client does not retype anything. Pre-filling the reference is what makes reconciliation automatic rather than manual detective work later.
A QR code alongside it costs nothing and helps whenever the invoice is being read on a screen other than the one that would make the payment, or on paper. It is a small addition that measurably reduces friction.
Two operational details are worth settling early. Payout timing means money reaching your processor is not money in your bank — expect a delay of a couple of business days, longer for new accounts, and plan cash flow against the payout date rather than the payment date. And reconciliation matters: a processor that deposits a weekly total net of fees leaves you unpicking which invoices it covered, so prefer per-transaction data or an accounting integration that records the gross amount and the fee separately.
Common Mistakes
Offering only card payment on large invoices
A percentage fee with no cap on a five-figure invoice is an expensive convenience. Offer a bank rail alongside it and let the client pick.
Surcharging without checking the rules
Card surcharges are restricted or banned in many jurisdictions and constrained by network rules even where permitted. Check before adding a line; consider a bank-transfer discount instead.
Treating the payment date as the payout date
Funds typically reach your bank a couple of business days after the customer pays, and longer on new accounts. Forecast against payouts, not payments.
Recording only the net deposit
Booking the amount that landed understates revenue and hides the fee as an expense you never see. Record gross revenue and the processing fee separately.
Frequently Asked Questions
Are online payment fees tax deductible?
In most jurisdictions payment processing fees are an ordinary business expense and deductible as such — which is another reason to record them separately rather than netting them off revenue. Confirm the treatment locally.
Do I need a merchant account?
Not usually. Modern payment providers aggregate merchants, so you can accept cards with an account you set up in an afternoon. Traditional merchant accounts can price better at high volume but involve more onboarding.
What happens if a client disputes a card payment?
The processor typically withdraws the funds pending investigation and charges a dispute fee, and you supply evidence that the work was delivered as agreed. Clear invoices, signed acceptance and delivery records are what win these — which is a practical reason to keep the document chain tidy.
Is it worth accepting cards if my invoices are large?
Often not as the default. At a few thousand and up, an uncapped percentage costs far more than the convenience is worth, and a capped bank debit does the same job. Offer cards on request rather than promoting them.
Sources & Further Reading
Ready to put this into practice?
Create a professional invoice in your browser — free, no sign-up, no watermark.
Open the Invoice Generator