Card payments are genuinely convenient for the client, faster, no wire details to track down, and the processing fee is a real cost that doesn't disappear just because nobody explicitly discusses it. Absorbing it silently on every invoice adds up quietly across a year; passing it along without warning surprises a client who didn't expect an added line item.
The right answer isn't a blanket rule either way. It's a decided, stated policy the client understands before they choose how to pay.
The processing fee is real and has to land somewhere
Card processing typically runs a few percent, and that cost is real on every transaction, whether it's absorbed into your margin or passed to the client. Recognize it as an actual line item to decide on, not something to leave unexamined.
Decide the policy before a client asks, not case by case
Deciding whether to pass along the fee in the moment, for one specific client, produces an inconsistent policy across the business. Decide it in advance, as a standard practice, so every client is treated the same way.
In Stelaah, a payment method's processing fee can be reflected directly on the invoice, so the client sees the real cost breakdown rather than a surprise added charge. See how invoices works.
Present it as a real choice upfront, not a surprise added at checkout
If you do pass along the fee, present it clearly before the client commits to that payment method, not as a surprise line item they discover after choosing. A clear, upfront choice reads as transparent; a hidden fee reads as a bait and switch.
Weigh the convenience against the actual cost on this specific size of payment
The processing fee on a small invoice is negligible; on a large one, it's a real number worth actually weighing. Consider the transaction size when deciding whether to absorb it or pass it along, rather than applying one flat rule regardless of amount.
Check what your payment processor and local rules actually allow
Passing along a card surcharge is regulated differently depending on jurisdiction and processor agreement, and assuming it's simply allowed can create a real compliance problem. Confirm what's actually permitted before adopting a surcharge policy.
A simple checklist
If you do nothing else, do these five things:
- Decide the policy in advance, applied consistently to every client.
- Present any fee clearly before the client commits to that method.
- Weigh the actual cost against transaction size, not a flat rule.
- Confirm what your processor and local rules actually permit.
- Never let the fee show up as a surprise after the fact.
Do that, and card payment fees become a transparent, consistent policy, not an awkward surprise or a silently absorbed cost.
Run your client work in one place. Stelaah keeps projects, clients, contracts, and invoices together, with Aria for the busywork.
Start freeWe build Stelaah, the workspace for client work. We write about running teams, agencies, and venues without the busywork.
