Back to blog
Industry NewsSeptember 9, 20264 min read

Pay-by-bank is rewriting B2B invoicing: here is why

Pay-by-bank is moving from a consumer novelty to a serious B2B payment rail. Here is what the shift means for consultants invoicing large corporate clients.

By ZenPay Team

Share
Pay-by-bank is rewriting B2B invoicing: here is why
Photo by Atlantic Money on Unsplash

Your client's procurement team just told you they want to pay your $18k retainer by bank transfer "via their new payment portal." No card, no wire details hunted from a PDF. Just a link, a login, and funds in your account in hours. That is pay-by-bank, and it is quietly becoming the default rail for B2B invoicing.

What pay-by-bank actually is (and is not)

Pay-by-bank is account-to-account (A2A) payment initiated directly from the payer's bank account, usually triggered by a link or QR code. It is not a wire transfer, which requires manual IBAN entry and a SWIFT relay that can take 1-3 business days and cost $25-$45 per send. It is not a card payment, which costs the payee 1.5-3.5% in interchange. It is something in between: near-instant, low-cost, and increasingly supported by open banking infrastructure in the EU (through PSD2), the UK (Faster Payments), the US (RTP and FedNow), Brazil (PIX), and Singapore (PayNow).

For a consultant invoicing a $18k monthly retainer, a 2.5% card fee is $450 gone before you see the money. A wire costs your client friction and costs you waiting time. A pay-by-bank push takes seconds at the payer's end and clears in hours at yours.

The rails that are making this possible

The infrastructure shift is real. In the EU, open banking mandates require banks to expose payment APIs to licensed third parties. In Brazil, PIX processed over 42 billion transactions in 2024. In the US, FedNow launched in 2023 and now covers a growing share of financial institutions. These are not fringe experiments: they are regulated, settlement-guaranteed rails that corporate treasury teams are actively routing payments through to cut their own processing costs.

Why corporate clients are adopting it faster than freelancers expect

Large enterprises have strong incentives to move B2B payables off cards and wires. Cards carry interchange costs on the issuer side for corporate cards. Wires require treasury staff to manually batch and approve. Pay-by-bank fits neatly into AP automation stacks: the invoice arrives with a payment link, the AP system authenticates through the bank API, and the payment is pushed without human keying of bank details.

The consultant sitting across from that AP system benefits directly. Fewer manual errors on bank details. No "we sent it to the wrong IBAN" delays. No 3% card fee eroding margin on a high-value invoice.

The NET 60 problem does not disappear, but it shrinks

One honest caveat: pay-by-bank speeds up execution once a payment is approved. It does not change the approval cycle inside a slow-paying client. If procurement runs NET 60, you still wait 60 days for the approval trigger. What changes is the gap between approval and cleared funds: from 2-3 days for a wire to same-day or next-morning for A2A.

On a $25k project invoice, that 2-3 day wire lag at month end can push you into the next reporting period. Pay-by-bank removes that tail.

How to position your invoices to capture pay-by-bank payments today

The practical question is not whether this trend is real. It is whether your invoices are set up to receive payment this way.

How most consultants invoice today

  • Wire details typed into a PDF, easy to misread or miskey.
  • Client must log into their bank separately and manually enter IBAN/SWIFT.
  • No QR code: mobile approval requires zooming into a PDF to copy details.
  • Reminder to pay is a personal email you have to remember to send.
  • Revenue across USD, EUR, and GBP invoices reconciled manually at month end.

How ZenPay invoices are set up for pay-by-bank

  • Bank details (SEPA, ACH, PIX, wire) stored once and pulled onto every invoice automatically.
  • Shareable invoice link lets clients open a clean payment page without a portal account.
  • QR codes on every invoice support PIX, WeChat Pay, Alipay, and bank transfer in two taps.
  • Auto-reminders fire N days before or after due date in your name, with editable copy.
  • Multi-currency wallets aggregate USD, EUR, and GBP totals separately for clean reporting.

The QR code detail matters more than it sounds. A corporate approver reviewing invoices on a phone can tap a QR code and initiate a PIX or bank-linked payment in under 30 seconds. That removes a step that historically meant "I'll do it at my desk" and then did not happen.

What this means for your invoicing setup right now

Pay-by-bank will not replace every payment method overnight. Cards still dominate smaller B2C-style transactions. Wires still handle large cross-border payments where A2A rails are not yet connected. But for recurring B2B invoices in the $5k-$25k range, particularly with EU, UK, Brazilian, or Singapore-based counterparties, the switch is already happening whether you prompt it or not.

The practical upside for a consultant is real: lower cost of getting paid, faster clearing once approved, and fewer "did you get the right bank details?" exchanges. The risk of ignoring it is getting left on a slower, more expensive rail while your client's AP system is already wired for something better.

Set your bank details once, attach QR codes, and send links your clients can act on from their phone. The infrastructure is already there. The gap is usually just the invoice.