Embedded payment journeys are becoming a defining feature of modern platforms.
As app-to-app flows, deep linking and Pay by Bank mature, the structure of the transaction is changing. Customers are no longer consistently redirected into external checkout environments. Instead, more of the journey is being managed within the platform itself, with external systems providing authorisation rather than owning the experience.
This has practical consequences for how payment systems are designed and operated.
The shift from redirection to embedded journeys
Earlier open banking implementations relied heavily on redirection. A customer would leave the merchant or platform environment, select their bank, complete authentication and then return.
That model remains valid, but it introduces fragmentation. Each transition creates dependency on external behaviour, reduces visibility into what is happening during the journey and complicates recovery when something interrupts the flow.
Embedded journeys reduce that fragmentation. The platform maintains continuity across the transaction, passing the customer into authentication only when required and retaining control of the surrounding experience.
This changes the role of the platform from initiator to orchestrator.
Routing becomes a system decision
Bank selection has traditionally been treated as a user task.
In practice, it is a routing problem. The platform often has enough context to determine a likely or preferred path based on prior behaviour, device signals or stored preferences.
Handling that deterministically reduces unnecessary interaction at the point of payment and produces more consistent outcomes. Where confidence is lower, the system can fall back to explicit choice without disrupting the overall journey.
This approach requires careful design, particularly in how routing logic is separated from bank-specific behaviour and how decisions are recorded for later analysis.
Consent becomes a managed state
As payment journeys become more embedded, consent moves from a moment in the flow to a state that is maintained and referenced across interactions.
The platform needs to understand:
- whether consent has been granted for a specific transaction or relationship;
- how that consent is scoped in terms of value, frequency and merchant; and,
- how it can be verified, refreshed or revoked in a controlled way.
Managing consent in this way creates a more stable foundation for both single transactions and recurring payment models. It also introduces a requirement for consistent identifiers, durable records and clear linkage between consent events and subsequent payments.
At enterprise scale, performance is shaped by orchestration rather than individual API calls.
Routing, fallback behaviour, session continuity and return handling all influence how a journey performs under real conditions. Variability across banks adds another layer of complexity, making it important to manage the flow in a way that produces predictable outcomes.
This places greater emphasis on how systems are structured. Orchestration logic needs to be explicit, observable and resilient to interruption. It also needs to support consistent behaviour across both ideal and degraded paths.
Fallback becomes part of the core flow
Fallback is often treated as an exception.
In practice, it occurs frequently enough to be considered a standard path. Customers switch apps, sessions expire, network conditions vary and device behaviour introduces interruptions that cannot be fully controlled.
Handling fallback well depends on continuity of state. The platform needs to preserve context across transitions, support idempotent retries and provide clear signals to the customer about what has happened and what happens next.
Without that structure, support overhead increases and performance metrics become difficult to interpret.
Control brings responsibility
As platforms take on more of the payment journey, responsibility shifts with it.
Decisions about routing, consent handling, retry behaviour and error states affect not only conversion but also liability, compliance and operational clarity. The platform becomes the point at which behaviour is defined and explained.
Carmen James, Head of Operations, highlights how this plays out in practice:
“When the platform owns the journey, it also owns the outcome. Clear ownership makes issues easier to resolve, but it also means there is less room for ambiguity when something goes wrong.”
This reinforces the need for well-defined control points and consistent behaviour across different scenarios.
Observability supports accountability
With greater control comes a need for greater visibility.
Each stage of the journey should be instrumented in a way that allows teams to understand what happened, where and why. This includes initiation, consent, authentication, authorisation, return events and final confirmation.
Structured telemetry allows teams to separate bank-side latency from application-level issues and to prioritise improvements based on identifiable patterns rather than aggregate drop-off.
John Blackmore, Head of Technology, summarises the requirement:
“You need to be able to explain every step of the journey. If you cannot see it clearly, you cannot control it, and if you cannot control it, you cannot scale it.”
A more defined control layer
Embedded payments are establishing a clearer control layer within platforms.
That layer manages routing decisions, maintains consent state, coordinates fallback behaviour and exposes the data needed for operational and regulatory requirements. It also becomes the point at which consistency is enforced across different banks and user environments.
As adoption increases, the quality of that control layer will have a direct impact on performance, reliability and trust.
Structured progression
The movement toward embedded payment journeys is incremental.
Each improvement reduces fragmentation, increases visibility and strengthens control. Over time, these changes accumulate into a more stable and predictable system.
Platforms that invest in orchestration, observability and governance early tend to experience fewer disruptions as complexity increases. The structure they build becomes the mechanism through which both performance and accountability are maintained.
- Open Banking Limited, customer experience guidelines and app-to-app redirection standards. Link
- HM Treasury, National Payments Vision. Link
- Financial Conduct Authority, payments regulatory priorities and open banking direction. Link
