Pay by bank payments in ecommerce: readiness checklist for 2026

Pay by bank is having a naming moment, and that matters because confusion slows adoption. In the same category you will hear open banking payments, bank to bank, account to account, and pay by bank. The common thread is simple: the money moves from a customer’s bank account to a merchant’s bank account without card rails in the middle.

In the latest episode of Behind the Checkout, John Lunn (Gr4vy) and Alexandre Gonthier (Trustly) walk through what is driving momentum, what is holding it back, and what merchants should do next. One line from Alexandre is the clearest way to frame the method:

“It works from bank account to bank account directly with no third party network in the middle.”

If you sell online in 2026, the question is not “will pay by bank exist?” It already does. The question is whether your checkout, risk controls, and operations are ready to support it without hurting conversion or increasing fraud exposure.

Here’s the full episode:

What pay by bank is (and what it is not)

Pay by bank is not the same as “enter your routing and account number” experiences from the early days of ecommerce. Alexandre calls out why that older model never worked at scale:

• The underlying rails were often batch-oriented and slow
• The user experience was poor because people do not know their account details
• Settlement timing created risk for merchants that needed to ship fast

Pay by bank, as discussed in the episode, is essentially a modern user experience layered on top of bank rails. The customer authenticates with their bank using familiar behaviors (often Face ID or a banking login), similar to how a user signs in to a wallet.

Alexandre describes the UX shift this way:

“You move from having to fill out the form with information you don’t know to simply doing a Face ID or signing in to your bank.”

That is the first readiness theme for 2026: pay by bank succeeds when it feels as easy as a card or wallet.

Why 2026 is a turning point

Two forces are converging:

1) Real-time rails improve the experience

John frames the big change as near real-time confirmation. Historically, merchants avoided bank transfers in ecommerce because the payment might not confirm for days. In the episode, Alexandre explains how real-time networks change that and why they reduce a specific risk:

“With real time you eliminate that problem because you grab the funds in real time.”

Even when funds do not move instantly to the merchant, the merchant can receive confirmation in real time, or a guarantee, which enables shipping and fulfillment decisions.

2) Merchants are more motivated than consumers

Consumers already have a payment method that works. Cards and wallets are familiar, ubiquitous, and often rewarded. Alexandre makes the economic reality blunt:

“Merchants pay a lot for that product… interchange… it doesn’t go down… it goes up.”

In other words, the stakeholder with the strongest incentive to change behavior is the merchant. That affects how you design your pay by bank rollout. You cannot assume consumers will demand it on their own. You need to present it well and justify it clearly.

What holds pay by bank back in ecommerce

This is the part merchants underestimate. Pay by bank can be technically available and still fail commercially if the rollout ignores three adoption blockers.

Branding confusion at checkout

John points out a common conversion issue: customers may want to pay from their bank, but they see an unfamiliar brand in the flow and hesitate. Alexandre agrees that leading with an unknown processor brand can curb conversion:

“No one is going to use something they don’t know when it comes to their money.”

This is a readiness issue, not a philosophical one. Your checkout presentation should emphasize “pay by bank” and the customer’s own bank. Any intermediary branding needs to be placed carefully and explained simply.

Incentives and habit inertia

A strong quote from Alexandre should be printed and put on a slide for any ecommerce leadership team:

“If you don’t put an incentive structure in place why would consumers walk away from something that works?”

Cards win on rewards, habit, and familiarity. Pay by bank needs a value exchange for mainstream ecommerce adoption. In some verticals, adoption is already natural. In general retail, it often is not.

Risk and non-repudiation

Real-time payments can behave more like cash. Alexandre describes the trade-off clearly: instant movement plus limited reversibility means liability questions matter.

He notes that regulators and banks often respond with velocity limits, and those limits reduce usable ecommerce cases. If you want pay by bank to work for meaningful order values, you need a risk strategy that is more nuanced than “cap everything.”

Readiness checklist for 2026

This checklist is designed for ecommerce teams that want to launch, expand, or optimize pay by bank without guessing. Use it as a working document across product, payments, fraud, finance, and support.

1) Checkout and UX readiness

Goal: make pay by bank feel as fast and familiar as a wallet.

• Confirm that your pay by bank flow supports mobile-first authentication, including bank app authentication when available.
• Reduce steps. Treat every extra screen as lost conversion.
• Use clear language: “Pay by bank” plus a short explanation like “Pay directly from your bank account.”
• Test the branding layout. Customers should recognize their bank before they are asked to trust anything else.
• Ensure error handling is specific. “Payment failed” is not good enough. You need guidance that helps users recover.

A practical benchmark: if your pay by bank flow takes noticeably longer than a wallet sign-in, conversion will suffer unless you compensate with incentives or strong messaging.

2) Funds confirmation and fulfillment readiness

Goal: know when you can safely ship.

In the episode, Alexandre explains two approaches when underlying rails are not fully real-time:

• Use risk signals to provide a real-time “funds are good” guarantee
• Use real-time rails where available to move funds immediately

Your readiness actions:

• Decide what “confirmed” means for each market you sell in.
• Define fulfillment rules for pay by bank orders. For example, ship immediately only if confirmation type is real-time settlement or guaranteed funds.
• Train operations teams on exceptions. If confirmation arrives but settlement timing differs, your reconciliation and support need to understand that nuance.

3) Fraud and risk readiness

Goal: prevent “instant loss” scenarios.

Alexandre gives a concrete scenario where criminals exploit timing and move money out quickly:

“We have seen and blocked… they put money in the bank account… within minutes… they use Zelle to move the money out.”

What to do in 2026:

• Treat pay by bank as its own risk category. Do not copy-paste card rules.
• Add velocity controls that reflect your product and ticket size, not generic bank limits.
• Build a playbook for mule activity and organized fraud patterns, not just account takeover.
• Monitor pay by bank fraud separately in reporting so you can detect pattern shifts quickly.
• Align liability expectations across teams. If a payment is non-revocable, customer support scripts must change.

4) Incentive and messaging readiness

Goal: give customers a reason to choose it.

Alexandre offers two important adoption examples:

• In bill pay, pay by bank can be a dominant method
• In donations, messaging shifted adoption dramatically when framed as “more of your donation goes to the cause”

For ecommerce, you need a similar “why.”

Options that work without sounding gimmicky:

• Small discount for pay by bank
• Loyalty points that are exclusive to pay by bank
• Free shipping thresholds tied to pay by bank
• Faster refunds via pay by bank in markets where it is feasible

Your readiness actions:

• Choose one incentive that is easy to explain and easy to measure.
• A/B test placement. Pre-selecting can lift adoption but must be handled carefully to avoid customer frustration.
• Align messaging with the incentive. If you offer a discount, say it plainly and show it early.

5) Refunds and customer support readiness

Goal: avoid the “refund frustration” trap.

John highlights a truth every shopper recognizes: cards feel instant for payment, slow for refunds. Real-time rails can change that expectation, but only if your operations and provider setup can support it consistently.

Readiness actions:

• Define refund timelines by method and market, and surface them in customer support tools.
• Update customer comms to reflect what is actually possible.
• Build a dispute handling process that fits pay by bank, especially where chargeback-like mechanisms differ from card processes.

6) Reporting and reconciliation readiness

Goal: make pay by bank measurable and finance-friendly.

If you cannot measure performance, you cannot scale adoption responsibly.

Readiness actions:

• Track share of checkout for pay by bank by country, device, and customer segment.
• Track approval and completion rates separately from card approvals.
• Track time-to-confirmation and time-to-settlement.
• Track refund time and support contact rate for pay by bank orders.
• Create a single view across providers so finance does not reconcile five dashboards manually.

7) Orchestration readiness

Goal: avoid a new set of payment silos.

John and Alexandre touch on a structural problem: pay by bank systems vary by country and do not behave like a single global network yet. If you operate globally, you will likely need multiple pay by bank providers depending on region, rails, and bank coverage.

That creates complexity fast. Orchestration is what prevents it from becoming a messy set of one-off integrations.

If you want Gr4vy’s perspective on how orchestration fits into emerging payment models, you can reference: payment orchestration for agentic commerce

Even though agentic commerce is a different topic, the core principle carries over: merchants need control across payment mechanisms without lock-in.

What “good” looks like by the end of 2026

If your pay by bank rollout is working, you should see these outcomes:

• Adoption grows in the segments where the value is obvious (high AOV, recurring-like use cases, cost-sensitive categories)
• Conversion stays stable because the flow is familiar and the messaging is clear
• Fraud remains controlled because risk rules are pay-by-bank specific, not generic
• Refund and support experiences improve, or at least do not deteriorate
• Finance teams trust the reporting and reconciliation

If adoption is flat, the usual causes are predictable: unclear value for the customer, too much friction, confusing branding, or conservative limits that make the method unusable for meaningful order values.

FAQ

What are pay by bank payments in ecommerce?

Pay by bank payments let customers pay directly from their bank account using bank rails rather than card networks. The user experience is typically powered by online banking or open banking authentication.

Are pay by bank payments the same as open banking payments?

In practice, the terms are often used interchangeably. “Pay by bank” is commonly used as the consumer-facing label, while “open banking payments” describes the enabling mechanism.

Why is pay by bank growing in 2026?

Two drivers are increasing adoption: improved user experience through bank authentication and the spread of real-time rails that reduce settlement delays and uncertainty.

What is the biggest barrier to pay by bank adoption in retail ecommerce?

Habit and incentives. Cards work well for consumers and often offer rewards. Many customers need a reason to switch, such as discounts, loyalty benefits, or better refund experiences.

What are the main fraud risks with pay by bank?

Fraud can include account takeover, mule activity, and social engineering. Faster settlement and limited reversibility can increase loss severity if controls are weak.

Do real-time payment limits affect ecommerce use cases?

Yes. Velocity limits can make some order values impractical. Merchants need a risk strategy that supports legitimate transactions while limiting fraud exposure.

Can pay by bank replace cards by 2026?

In some verticals, it can be the primary method. In general ecommerce, it is more likely to grow alongside cards, especially in markets where real-time rails and incentives align.

Pay by bank in ecommerce is not a single integration you “turn on.” It is a combination of user experience, risk strategy, operations, and incentives. Merchants that treat it as a checkbox will see low adoption or increased fraud. Merchants that prepare properly can reduce costs, improve payment resilience, and offer customers a faster, more direct way to pay.

Contact Gr4vy to learn how payment orchestration can help you launch and scale pay by bank payments in ecommerce for 2026.