Pay by Bank
Pay by Bank checkouts require precise device detection and accurate app redirection to prevent conversion drop-off. Cardflo provides the orchestration layer to present these interfaces correctly, ensuring high completion rates across both mobile and desktop payment environments.
- Category
- Methods
- Capabilities
- 6
- Available on
- All plans
Consumer checkout interfaces often suffer from high drop-off rates when shoppers are forced to manually enter account details or face poorly formatted authentication screens. Conversion specialists must design interfaces that automatically detect the user device and format the banking application trigger correctly, whether the buyer is browsing on a mobile browser or scanning from a desktop monitor.
Cardflo orchestrates the user interface components necessary for a direct pay by bank checkout experience. The gateway determines the correct presentation method based on the operating system, triggering deep links on smartphones or generating dynamic QR codes for desktop displays. This logic ensures the consumer reaches their banking environment without unnecessary clicks.
Implementing Pay by Bank options through Cardflo’s multi-acquirer network lowers processing overheads and virtually eliminates chargeback risk. Merchants benefit from instant, secure bank transfers, enhancing financial stability and reducing operational burdens.
Pay by Bank overview
Designing an effective interface for bank application redirection requires specific attention to the consumer checkout journey. While the underlying API architecture is handled via open banking payments and corporate B2B flows belong within account-to-account payments, this presentation layer governs how the shopper interacts with the payment prompt itself.
Cardflo provides the orchestration necessary to render device-appropriate prompts at the exact moment of purchase. Conversion specialists use this capability to format mobile deep links that launch banking applications instantly, or generate QR codes that allow desktop users to authorise a transaction via their smartphone.
By managing the visual and technical transition from the merchant site to the banking environment, operators reduce the cognitive load on buyers. The resulting interface minimises data entry errors, keeps the purchase intent high, and channels the user efficiently back to the merchant confirmation page upon successful biometric approval.
How pay by Bank works
Device detection and presentation logic
The orchestration layer identifies the consumer device and browser environment when the checkout loads. For mobile users, the interface prepares a deep link formatted for iOS or Android banking applications. Desktop shoppers receive a dynamically generated QR code that links to the exact transaction payload, ensuring the visual presentation matches the technical limitations of the hardware being used.
Bank selection and application routing
The consumer interacts with a formatted list or search field to choose their financial institution. Cardflo uses this selection to execute the correct redirection sequence. Mobile devices invoke the specific Uniform Resource Identifier for the chosen bank, forcing the native application to open on top of the merchant site while keeping the original browser session active in the background.
Authentication and return path handling
The shopper authenticates the transaction using facial recognition or fingerprint scanning inside their banking application. Once the institution approves the transfer, the application triggers a return URL. The Cardflo gateway captures this redirection event, matches it against the original checkout session token, and automatically advances the merchant site to the final success screen without requiring manual page refreshes.
Why pay by Bank matters
Reducing biometric authentication drop-off
Conversion rates fall sharply when consumers must recall passwords or navigate poorly rendered bank portals in mobile browsers. By routing directly to the native banking application, merchants allow buyers to use saved biometric credentials. This shift removes data entry from the checkout sequence entirely, accelerating the time to purchase and preventing abandonment during the critical approval phase.
Bridging desktop and mobile contexts
Desktop shoppers frequently abandon transactions if forced to locate payment cards physically. Presenting a QR code at the desktop checkout allows the consumer to scan the screen with their smartphone, instantly migrating the payment approval to a mobile bank app payments flow. This cross-device capability captures impulse purchases that would otherwise be lost to friction in the desktop environment.
Regulatory notes for pay by Bank
Biometric authentication and strong customer authentication
Direct redirection to mobile banking applications fundamentally changes how merchants handle Strong Customer Authentication mandates under European and UK frameworks.
Because the consumer proves their identity using the facial recognition or fingerprint scanner built into their personal hardware, the checkout process inherits the bank's native security protocols automatically.
The orchestration layer must ensure that the transition between the merchant site and the banking environment clearly denotes where the authentication is taking place.
This separation ensures the merchant platform never touches sensitive credentials, limiting compliance scope while maintaining a fluid user interface throughout the biometric check.
Accessibility and screen presentation standards
When deploying a pay by bank checkout, interface designers must adhere to web accessibility guidelines regarding timeouts and screen readability.
The transition from a merchant application to a banking portal requires clear messaging, as sudden visual shifts can disorient consumers relying on screen readers or accessibility tools.
Cardflo provides the necessary state indicators and loading states to bridge this gap compliantly.
By implementing proper aria-labels on bank selection grids and maintaining session persistence during the redirection phase, operators ensure the payment interface remains legally accessible without sacrificing the speed of the mobile app transition.
Pay by Bank use cases
Bank app checkout for travellers
Mobile shoppers selecting pay by bank can abandon checkout when the redirect gives little warning, opens the wrong banking route or loses basket context. Cardflo helps merchants present clear bank selection, preserve order references and return customers to a confirmation screen after biometric authentication in their banking app.
Desktop checkout QR handoff
Desktop shoppers may prefer approving a bank payment on their phone rather than continuing through a browser-based authentication journey. Cardflo supports checkout flows that display a time-limited QR code, retain the basket on the original screen and update the order status once approval is completed in the banking app.
Direct bank payments for subscriptions
Consumers can hesitate when a checkout presents an unstructured list of banks, unfamiliar logos or no clear route for finding their provider. Cardflo helps merchants optimise bank search, ordering, mobile display and fallback messaging, while measuring selection drop-off separately from authentication and return-to-merchant completion.
Grocery basket total changes
Online grocery baskets can change after picking, creating confusion when substitutions or unavailable items alter the amount shown before bank approval. Cardflo helps supermarkets display the payable total clearly, align payment status with fulfilment updates and route customers back to an accurate order confirmation after banking app authentication.
Pay by Bank by the numbers
Merchants often observe these savings on high-value transactions by bypassing card network interchange fees and ad-valorem scheme charges.
In regions supported by instant payment rails like UK Faster Payments, this is the typical window for fund transfer confirmation.
This range reflects industry benchmarks for customers who successfully redirect to their banking app and complete biometric verification.
Methodology: these figures are illustrative ranges drawn from published industry data and observed merchant cohorts, not guarantees. Actual results depend on your risk profile, card mix, geography and acquiring setup, and are confirmed only in your own pricing and approval terms.
Related terms
Talk to our team about a live rollout across our acquirer partners' rails.
What you get with Pay by Bank
- Present dynamic QR codes on desktop screens to bridge the transition to mobile bank app payments
- Trigger device-specific deep links that automatically open banking applications during smartphone checkout sessions
- Implement branded loading screens during the bank redirection phase to maintain consumer confidence and context
- Retain checkout session data if the consumer cancels the bank authentication, preventing abandoned carts
- Format the bank selection interface to display the most relevant local institutions based on IP address
- Optimise pay by bank app integration flows for minimal clicks between cart confirmation and biometric approval
A short scoping call, then a written plan for your MIDs.
Questions about Pay by Bank
How do we handle return URLs for mobile bank app payments?
The integration requires a precise return URL configuration to ensure the banking application can send the consumer back to the correct checkout state. Cardflo orchestrates this by appending session-specific parameters to the redirect payload.
When the banking app concludes the biometric check, it uses this exact URI to reopen the merchant application or browser tab. The orchestration layer then intercepts this return event, validates the session integrity, and updates the consumer-facing interface to display the final payment confirmation screen.
How should pay by bank checkout status messages reduce consumer abandonment?
The interface should distinguish clearly between bank selection, authentication in progress, payment confirmation and a cancelled or timed-out journey. After consumers leave the merchant site for their banking app, the checkout should preserve the basket and display a concise waiting state on return.
Cardflo provides payment status data that merchants can map to accurate on-screen messages, avoiding premature success pages or vague errors that encourage duplicate payment attempts.
Can we embed the bank selection screen directly into our checkout?
Operators can host the bank selection interface natively using the Cardflo gateway orchestration tools.
Instead of redirecting the consumer to a third-party hosted page to pick their institution, the merchant checkout queries the available banks based on the user location and renders them as a native dropdown or grid.
Once the shopper selects an institution, the platform triggers the immediate app redirection. This embedded approach reduces total clicks and keeps the consumer within the merchant brand environment for longer.
How does a QR code payment work for desktop checkouts?
When the gateway detects a desktop or tablet browser without native banking applications, the orchestration layer generates a unique QR code tied to that specific transaction session. The consumer scans this code using their standard smartphone camera or banking app scanner.
The scan reads the embedded deep link, which launches the authentication flow on the mobile device. Meanwhile, the desktop checkout interface polls the gateway for status updates, automatically refreshing to a success screen as soon as the mobile approval completes.
Related features.
Related guides.
See how Cardflo compares.
Ready to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.