Dev48
Language
  • About
  • Services
  • Industries
  • Technologies
  • Articles
  • Contacts
Book a call
    Home/Articles/Real time rails are not a merchant payment product
Dev48
info@dev48.org+375 29 320-40-96WhatsApp@isky_by

© 2026 · All rights reserved.

Real-Time Rails Are Not a Merchant Payment Product

Source: Endava•November 18, 2026 at 10:41 PM

Real-Time Rails Are Not a Merchant Payment Product

Real-time rails move money fast. Explore the identity, fraud protection and checkout experience needed to make pay-by-bank work.

Real-time payment infrastructure in the United States has matured quickly.

FedNow and RTP have given financial institutions the ability to move money in seconds, around the clock – an important foundation that has allowed for material growth in instant payments over the past several years.

But infrastructure alone does not create a merchant payment product.

Sionic’s launch of Instant Bank Pay provides a useful illustration of the distinction. Its proposition is designed to use real-time bank-payment infrastructure while adding capabilities intended to make account-to-account payments practical in a commerce environment.

Today, the larger market question is becoming clear: What has to surround the rail before consumers and merchants will choose it at checkout?

  • 1. Moving money is only one part of the payment experience

1. Moving money is only one part of the payment experience

  • Cards have spent decades building an ecosystem around authorization and settlement.

Cards have spent decades building an ecosystem around authorization and settlement.

  • Consumers recognise the experience. Merchants know how to accept it. Issuers and networks manage fraud. Operating rules define responsibilities. Dispute processes provide recourse. Rewards create incentives to choose one credential over another. The surrounding infrastructure is crucial.

Consumers recognise the experience. Merchants know how to accept it. Issuers and networks manage fraud. Operating rules define responsibilities. Dispute processes provide recourse. Rewards create incentives to choose one credential over another. The surrounding infrastructure is crucial.

  • A real-time account-to-account transaction can move money efficiently, but mainstream commerce requires answers to a broader set of questions:

A real-time account-to-account transaction can move money efficiently, but mainstream commerce requires answers to a broader set of questions:

  • Who is the consumer?
  • How is the account authenticated?
  • Who absorbs fraud?
  • What happens when the purchase is disputed?
  • How does a refund work?
  • Why should the consumer change behavior?
  • Why should the merchant promote the option?

These are product questions, not rail questions.

  • 2. Pay-by-bank economics require an experience consumers will actually use

2. Pay-by-bank economics require an experience consumers will actually use

  • The proposition for merchants to adopt instant payments is compelling. Account-to-account payments can potentially reduce payment costs, provide faster access to funds and give merchants another routing option. But lower acceptance cost alone does not guarantee adoption.

The proposition for merchants to adopt instant payments is compelling. Account-to-account payments can potentially reduce payment costs, provide faster access to funds and give merchants another routing option. But lower acceptance cost alone does not guarantee adoption.

  • Consumers already understand cards and wallets. They value convenience, protection and increasingly the rewards attached to their payment choice.

Consumers already understand cards and wallets. They value convenience, protection and increasingly the rewards attached to their payment choice.

  • For pay-by-bank to gain meaningful commerce volume, providers need to create sufficient value on both sides of the transaction. That could include streamlined authentication, recognizable checkout experiences, fraud protection, dispute mechanisms, loyalty or merchant-funded incentives and simple refund handling.

For pay-by-bank to gain meaningful commerce volume, providers need to create sufficient value on both sides of the transaction. That could include streamlined authentication, recognizable checkout experiences, fraud protection, dispute mechanisms, loyalty or merchant-funded incentives and simple refund handling.

  • Sionic's proposition represents an effort to build more of that commerce layer around real-time bank payments rather than treating the rail itself as the finished product.

Sionic's proposition represents an effort to build more of that commerce layer around real-time bank payments rather than treating the rail itself as the finished product.

  • 3. Identity and orchestration become strategic capabilities

3. Identity and orchestration become strategic capabilities

  • Pay-by-bank also creates a broader architecture challenge. The experience can involve a consumer bank, merchant bank, real-time rail, identity provider, fraud controls, checkout platform and potentially incentive or loyalty services. Those capabilities have to operate together quickly enough that the customer experiences one payment, making orchestration increasingly important.

Pay-by-bank also creates a broader architecture challenge. The experience can involve a consumer bank, merchant bank, real-time rail, identity provider, fraud controls, checkout platform and potentially incentive or loyalty services. Those capabilities have to operate together quickly enough that the customer experiences one payment, making orchestration increasingly important.

  • Providers need to coordinate identity, authentication, payment initiation, risk decisions, transaction status, merchant data and exception handling across multiple participants. And for banks, this creates an important strategic choice.

Providers need to coordinate identity, authentication, payment initiation, risk decisions, transaction status, merchant data and exception handling across multiple participants. And for banks, this creates an important strategic choice.

  • The decision has two paths: They can remain the account providers behind someone else's payment experience, or they can participate more directly in the identity, authorization, incentives and customer engagement that surround the transaction.

The decision has two paths: They can remain the account providers behind someone else's payment experience, or they can participate more directly in the identity, authorization, incentives and customer engagement that surround the transaction.

Three implications for payments leaders

For payments leaders, there are three valuable implications to consider.

  • 1. Acquirers should model the impact of alternative routing

1. Acquirers should model the impact of alternative routing

  • Even modest pay-by-bank adoption in high-volume or cost-sensitive merchant segments could change payment mix, pricing and acquiring economics.

Even modest pay-by-bank adoption in high-volume or cost-sensitive merchant segments could change payment mix, pricing and acquiring economics.

  • 2. Banks should decide where they want to participate

2. Banks should decide where they want to participate

  • Deposits provide the funding source, but ownership of the account does not automatically create ownership of the payment experience. Banks need to determine whether pay-by-bank belongs inside their broader payments and digital engagement strategies.

Deposits provide the funding source, but ownership of the account does not automatically create ownership of the payment experience. Banks need to determine whether pay-by-bank belongs inside their broader payments and digital engagement strategies.

  • 3. Commerce platforms should be designed for multiple payment experiences

3. Commerce platforms should be designed for multiple payment experiences

  • Gateways and merchant platforms increasingly need architectures capable of orchestrating cards, wallets and account-to-account payments while applying consistent identity, risk and data capabilities across them.

Gateways and merchant platforms increasingly need architectures capable of orchestrating cards, wallets and account-to-account payments while applying consistent identity, risk and data capabilities across them.

The signal to watch

← All articles

What this article says

More in Software Development

All →
L3Harris Awarded Joint Capability Group Contract for Advanced Capability System Implementation
L3Harris

L3Harris Awarded Joint Capability Group Contract for Advanced Capability System Implementation

AI Governance for Financial Services Starts With the Workflow
Endava

AI Governance for Financial Services Starts With the Workflow

Payments Platforms Win by Expanding the Relationship
Endava

Payments Platforms Win by Expanding the Relationship

Payments at the Operating Core
Endava

Payments at the Operating Core

The Last Mile of B2B Payments Is an Adoption Problem
Endava

The Last Mile of B2B Payments Is an Adoption Problem

The Atlassian AI SDLC Index
Atlassian

The Atlassian AI SDLC Index

More from Endava

AI Governance for Financial Services Starts With the Workflow
Endava

AI Governance for Financial Services Starts With the Workflow

Payments Platforms Win by Expanding the Relationship
Endava

Payments Platforms Win by Expanding the Relationship

Payments at the Operating Core
Endava

Payments at the Operating Core

The Last Mile of B2B Payments Is an Adoption Problem
Endava

The Last Mile of B2B Payments Is an Adoption Problem

Payments Modernisation: Dealing With Complexity in Regulated Industries
Endava

Payments Modernisation: Dealing With Complexity in Regulated Industries

From AI Prototype to Production: Scaling AI in Payments
Endava

From AI Prototype to Production: Scaling AI in Payments