Pay by Bank · Mobile SDK

Testing

Complete a Pay by Bank payment in the MITE sandbox and verify the return link that brings the customer back to your app.

Before you test

  • Pay by Bank is enabled on your MITE account. It is not enabled by default, so contact us if it is missing.
  • Your return URL is deployed with its verification file, and the app is signed with a certificate listed in assetlinks.json - see Return URL setup.
  • The iOS app's provisioning profile includes the Associated Domains capability.
  • Use a physical device where you can. Universal Links are most easily verified from another app, and a reinstall is needed after an entitlement change.

Test the bank journey

MITE uses the Tink Demo Bank for Pay by Bank; that page has the test credentials and the confirm and cancel options. Start the payment from your app, then:

  1. Choose Tink Demo Bank in the bank selection sheet.
  2. Choose Handoff to open the bank in the external-app path, or Redirect to complete the journey in the in-app browser. The choice is only offered in the sandbox; testing both covers the two ways the SDK hands the customer off.
  3. Sign in with the test credentials, select the test account and confirm to simulate a successful payment - or cancel to simulate a declined one.
  4. The bank hands the customer back through your return URL. The SDK resumes the payment and delivers the outcome through the payment result callback.
The sandbox does not offer a test bank application, so the Handoff path opens the demo bank in a browser rather than a real banking app. The production hand-off to an installed bank app can only be verified against a live bank.
On a successful sandbox payment the result should be Success, but the transaction can still be PENDING while it settles. That is the same behaviour as the APIs and not a failure of the SDK - check the transaction by id, as described in Take a payment.

Android

Ask the system whether the link is verified for your package. verified is the state you want; a freshly installed app can take a moment to be checked.

Shell
adb shell pm get-app-links com.example.app
adb shell pm verify-app-links --re-verify com.example.app

Then open the return URL as the bank would. With the app installed and verified, it should come to the foreground instead of a browser.

Shell
adb shell am start -a android.intent.action.VIEW -c android.intent.category.BROWSABLE -d "https://pay.example.com/pay-by-bank/return"

If the app opens but a second copy of your entry screen stacks on top of the payment sheet, the link is being handled by the wrong activity - use the no-display trampoline described in Return URL setup.

iOS

Universal Links only open the app from another app; typing the URL into Safari does not. Open the return URL from Messages, Notes or a browser's address bar link, and check that the app comes to the foreground.

Apple caches the association file, so a change can take time to reach devices. You can check the copy Apple serves:

Shell
curl https://app-site-association.cdn-apple.com/a/v1/pay.example.com

If the app never opens, check the Team ID and bundle ID in the association file, that the entitlement uses the same host, and that the capability is in the provisioning profile. Reinstall the app after changing any of them.

What to expect

Action in the bankSDK result
Confirm the paymentSuccess once the authorisation is confirmed; the transaction may still be settling.
Cancel the paymentError for a declined authorisation, or Canceled if the customer leaves the sheet before authorising.
Leave the bank and return laterThe SDK resumes when the app comes to the foreground, then reports the outcome.

The transaction id callback fires before any of these results, as soon as the API accepts the payment - see Track the transaction id.