Key takeaways
- On mobile, Pay by Bank should hand over directly to the banking app.
- App-to-app flows replace passwords with biometrics and take only a few taps.
- The return journey matters as much as the redirect.
Most online shopping happens on phones, and most people manage their money in a banking app. That makes mobile the place where Pay by Bank feels most natural, as long as the handover between apps is smooth.
What an app-to-app flow looks like
- The customer chooses Pay by Bank in the merchant's app or mobile site.
- They pick their bank.
- The banking app opens directly, with the payment ready to approve.
- They approve with Face ID, a fingerprint or a PIN.
- The merchant's app or site opens again, showing the confirmation.
Done well, the whole journey takes a few seconds and feels like one continuous flow.
Details that keep it fast
- Use universal links and app links so the bank's app opens directly instead of a mobile web page.
- Remember the customer's bank, so returning customers can skip the bank selection step.
- Keep the bank list searchable and show recognisable logos.
- Make sure the return link brings the customer back to the right screen, even if their browser or app was closed in the background.
Every extra screen between the checkout and the banking app is a chance for the customer to give up.
Handling the edge cases
Not every customer has their bank's app installed, and some will switch apps and forget to come back. Plan for these cases: fall back to the bank's mobile website when the app isn't available, and check the payment status on your server rather than relying only on the customer returning.
Desktop to mobile
On desktop, many flows show a QR code that the customer scans with their phone to approve in the banking app. The desktop page then updates automatically once the payment is approved.