The Card Reader Isn't the Only Way to Get Paid Anymore
If you've sent a client an invoice this year, you already know the ritual: they click "Pay Now," type in a card number, and three days later you watch a card-network fee quietly shave 3% off the top before the money even lands in your account. For a $5,000 invoice, that's $150 gone before you've bought a single stamp.
That math is exactly why Sage and GoCardless just made news by embedding "Pay by Bank" — an open banking payment button — directly into Sage's invoicing product for UK and Ireland customers. It's not a totally new idea (QuickBooks and Stripe have both been quietly building similar bank-payment rails), but the timing and the specific savings number attached to it are worth understanding, because the same account-to-account payment logic is spreading fast across every major accounting platform, US included.
What "Pay by Bank" Actually Is
Strip away the marketing language and the mechanism is simple. Instead of a customer typing in card details that get routed through Visa or Mastercard's network (with each intermediary — issuing bank, network, acquiring bank — taking a cut), the customer authorizes a direct transfer from their bank account to yours using open banking infrastructure.
In the Sage/GoCardless rollout, it works like this:
- A client opens an invoice and sees a "Pay by Bank" button alongside (or instead of) the card option.
- They select their bank, log in through their bank's own secure authentication, and approve the payment amount.
- Funds move directly, bank to bank — no card number, no card network, no expiration date to go stale.
- The payment status syncs back to the accounting software automatically, matching itself against the open invoice.
Sage and GoCardless say this cuts per-transaction costs by roughly 54% compared to card payments, and — just as important for anyone who has ever chased down a "your card was declined" email — it eliminates the entire category of failures caused by expired cards, wrong CVV digits, or insufficient card limits, since it's pulling straight from a bank balance instead.
Why This Matters Even If You've Never Heard of Sage
If you run a US-based small business, you're probably using QuickBooks, Xero, FreshBooks, or Stripe Invoicing rather than Sage. But the direction of travel is the same everywhere:
- QuickBooks Payments already offers bank-transfer payments on invoices at roughly 1% per transaction (with a $1–$10 cap), compared to 2.9% + $0.25 for card payments — a difference that adds up fast on larger invoices.
- Stripe processes ACH bank debits at around 0.8%, typically with a per-transaction cap, well under its card-processing rate.
- Traditional ACH transfers outside these platforms run $0.20–$1.50 per transaction flat, regardless of invoice size — which is where the real savings show up on high-ticket invoices (a $10,000 invoice at 2.9% card fees costs $290; the same invoice moved by ACH might cost a dollar or two).
The pattern across all of these: card fees scale with the size of the payment, bank-transfer fees mostly don't. If your average invoice is a few hundred dollars, the difference is nice but survivable. If you're a contractor, consultant, or B2B service business regularly invoicing four and five figures, switching your default collection method from card to bank transfer is one of the highest-leverage fee reductions available — with essentially no downside to the customer, who still just clicks a button and logs into their own bank.
The Reconciliation Win Is the Quieter Story
Fee savings get the headline, but the automatic reconciliation piece is arguably the bigger deal for anyone doing their own books. Historically, ACH and bank-transfer payments were the worst payment method for reconciliation — money would show up in your bank feed as an unlabeled deposit, and you'd have to manually match it to the right invoice, often days after the fact with three other deposits from the same week to sort through.
Pay-by-bank products close that gap by keeping the payment inside the accounting platform's own rails: the invoice, the payment authorization, and the bank settlement are all tracked by the same system, so the invoice marks itself paid the moment the transfer clears rather than waiting for you to eyeball a bank statement and guess. For a business owner already stretched across sales, delivery, and operations, that's hours per month you get back — the exact hours that usually get spent doing the bookkeeping equivalent of detective work.
Should You Turn This On?
A few practical considerations before you flip the switch on any pay-by-bank feature:
- Check the settlement speed. Open banking payments often settle faster than traditional ACH (sometimes same-day), but confirm your specific provider's timeline — cash flow planning depends on knowing when money actually lands, not just when a customer clicks "pay."
- Read the dispute/refund terms. Card payments come with well-established chargeback rights for both sides. Bank-transfer payments generally don't have the same reversal mechanics, so make sure your refund policy and provider's dispute process are clear before a customer expects a card-style chargeback and doesn't get one.
- Offer it as an option, not a mandate — at first. Customers who are used to typing in a card number may hesitate at an unfamiliar "log into your bank" flow. Keeping card payment available alongside pay-by-bank, and letting the fee savings speak for themselves over a few billing cycles, tends to convert better than forcing the switch.
- Watch the regulatory backdrop. In the US, the CFPB's broader open banking rulemaking (Section 1033) has been tied up in litigation and is currently being rewritten rather than enforced — it mostly concerns consumer data-sharing rights rather than the invoice-payment products described here, but it's a sign that the open banking plumbing underneath these features is still being formalized. The commercial products (QuickBooks bank payments, Stripe ACH, GoCardless) already work today regardless of that rulemaking's status.
Keep Your Books Clean However the Money Arrives
Whether a payment lands by card, ACH, or a new open banking rail, the bookkeeping fundamentals don't change: every dollar in needs to be categorized, matched to the right invoice, and reflected accurately in your records — including the processing fee itself, which is a real expense that should show up on your books, not just get netted away silently. Beancount.io's plain-text accounting keeps that trail fully transparent and version-controlled, so whether your revenue comes in through card networks, ACH, or a bank-to-bank transfer, you can see exactly what happened and when. Get started for free and keep your records as clear as the payment rails are getting.