Pay by Bank UX 2027: The Checkout Standard Cards Will Be Measured Against
Pay by bank has spent years as the cheaper option buried under the card form. In 2027 that excuse runs out. The rails are faster, the bank apps are better, and more of your customers have approved a payment in their banking app at least once. What still holds it back is the checkout design around it.
We audit payment flows for fintech, marketplaces, and B2B SaaS teams, and we see the same thing again and again. Teams wire up an open banking or account to account provider, drop a "Bank transfer" radio button under the card fields, and then conclude that customers prefer cards. The customers never had a fair choice. They were shown an unlabeled path into a redirect they did not expect, and they did what any careful person does with money. They backed out.
This is our standard for pay by bank UX in 2027. It is opinionated on purpose. If your checkout does not meet it, the conversion gap you see between bank and card is mostly a design gap.
The 2027 bar in one sentence
A first time payer should know, before they tap, exactly where they are going, what they will see there, what amount they are approving, and how they get back. A returning payer should get through in one confirmation.
Everything below serves those two sentences.
1. Name it like a payment method
"Bank transfer," "Open banking," "ACH," and "Instant EFT" are rail names. Customers do not shop for rails. Use "Pay by bank" and put it at the same visual weight as "Pay by card." When the two labels sit side by side, the choice reads as a choice.
Under the label, one line of plain copy does a lot of work: what it is, why it is safe, and what the customer gets. "Approve in your bank app. No card details shared." is enough. Skip anything that sounds like you are saving on fees, because customers can smell it and it does nothing for them.
2. Show their bank before they commit
The fastest trust signal in this flow costs nothing: logos of the banks you support, visible on the checkout screen itself. A customer is asking two questions at this moment. Is this real, and is my bank here? A short row of the most common banks for your market, with search behind it, answers both before the customer has spent any effort.
Keep the preview short. Five banks with a search field beats a wall of twenty. Order them by how common they are among your customers, using your own data once you have it.
3. Prime the redirect
The single biggest drop off point we see is the jump from the merchant page to the bank. To an unprepared customer, a sudden bank login looks like an error or a phishing attempt. Careful people have been trained for years never to log into their bank from a link on another site, and that training is good advice in every other context.
So tell them it is coming. A short screen or panel before the handoff should show:
- The amount and the merchant name exactly as the bank app will display them
- The bank they picked, by logo and name
- One sentence on what they will do there ("You will approve this payment in your Chase app")
- A button labeled with the destination, such as "Open Chase app," instead of a generic "Continue"
If the merchant name in the bank app will differ from your brand name, say so here. A mismatched name at the approval step is one of the quickest ways to lose a payment that was otherwise going to happen.
4. Deep link into the app, every time you can
On mobile, sending a customer to a mobile browser login when their banking app is installed is the 2027 version of asking for a fax. Customers expect the app to open, Face ID to fire, and the approval screen to be waiting. Work with your provider to prefer app to app handoff, test it on the top banks in your market on both iOS and Android, and treat a browser fallback as a defect to track.
5. Design the return trip as carefully as the departure
Most teams design the screens they own and forget that the customer has to come back. When they return from the bank app, they should land on a status page that answers one question immediately: did it work?
Plan for three outcomes, each with its own screen:
- Approved. Clear confirmation, the amount, a reference the customer can quote to support, and what happens next (shipping, account funded, invoice marked paid).
- Pending. Some bank payments do not confirm instantly. Say so in plain words, give an honest time expectation, and tell them you will notify them. Never show a spinner with no end.
- Failed or cancelled. Say it did not go through, say no money moved if that is true, and give one tap retry plus an easy switch to another bank or to card. A dead end here loses the sale and teaches the customer never to try bank payment again.
If the customer closes the bank app and never comes back, your order page and your emails need to reflect the true state. A "payment pending" order that quietly turns into a cancellation two days later is a support ticket you designed.
6. Make the second payment feel like a wallet
The first pay by bank payment is the expensive one, in effort. The second one should be nearly free. If your provider supports saved consents, recurring mandates, or variable recurring payments in your market, the returning experience should be a single confirmation, ideally backed by a passkey or device biometrics.
This is where pay by bank starts to beat cards on experience as well as cost. A returning customer who can approve with Face ID and never type a card number has a real reason to pick bank. Design the consent screens for that setup with the same care: what they are allowing, the limits, and exactly how to turn it off later in settings.
7. Offer it at the moment a card fails
A declined card is a dead end in most checkouts. It is also the moment a customer is most willing to try something else. When a card is declined, offer pay by bank right there as the way to finish the purchase, with the same primed redirect. Keep the message free of blame. "Your card did not go through. You can pay directly from your bank instead." is enough.
8. Be honest about what bank payments do differently
Customers know cards come with dispute rights. Many are unsure what happens with a bank payment if the order goes wrong. Regulated products in particular should state, in plain language near the payment option, how refunds and disputes work for bank payments in your product. Vague reassurance makes careful people more nervous. A short, specific line plus a link to the full policy calms them.
What we reject
These patterns fail our 2027 standard on sight:
- A pay by bank option hidden in a "More payment methods" dropdown
- Rail jargon as the only label (ACH, SEPA, RTP, EFT)
- A redirect with no warning and no destination on the button
- Bank login in a mobile browser when the bank app is installed
- An embedded iframe that asks for bank credentials with no clear sign of whose page it is
- A spinner with no timeout after the customer returns
- A failure screen with no retry and no alternative
- Copy that pitches the merchant's fee savings as the customer's benefit
- Different amounts or merchant names on the checkout and in the bank app
- Returning customers asked to pick their bank and log in again from scratch
How to check your own checkout this week
You do not need a research program to find the worst of this. Open your checkout on a phone, choose pay by bank, and pay yourself a small amount from two different banks. Write down every moment you hesitated or were unsure what would happen next. Then do the same thing and cancel inside the bank app, and see where you land.
For the page before the payment, run your checkout or pricing page through our free UX Scan. Scan your own page and you will get a quick read on clarity, trust signals, and friction before you ever reach the bank handoff.
Where we come in
We are a Bay Area boutique studio of senior designers working on complex and regulated products. For payment flows, we audit the full path across every bank your customers use, design the primed redirect, status, retry, and returning payer states, and ship them as working software alongside your engineers. We use AI to move fast on research and build, and senior people make every call that touches trust and money.
If pay by bank is on your 2027 roadmap, or it is already live and underperforming, book a discovery call or email ash@uxsignalstudio.com. Or start with the free UX Scan on your own checkout page today.