Skip to main content
When a transaction redirects the user to an external destination. Another app, a wallet, a bank flow, or a hosted page. The user eventually returns to your app or site. The iOS and Android SDKs expose handleDeeplink so you can forward that incoming URL and let the SDK resume the transaction. The Web SDK has no handleDeeplink. When the shopper comes back to your return URL, the page loads fresh and the SDK keeps no state across the redirect. Read the checkout session you stored, or the one in your return URL, and call sdkPayments.transactionStatus({ checkoutSession, elementSelector }). The SDK renders the payment outcome for that session into elementSelector. Pass language and countryCode to match the original transaction. The screen is display-only, so confirm the result through webhooks or the payments API.

Behavior

handleDeeplink(url) accepts any URL. Decide when to call it based on the URL itself. For example, when it carries query parameters like customer or checkoutSession that identify it as belonging to a Yuno transaction. The method returns a boolean indicating whether the transaction could be continued. It does not reflect the final result of the transaction. The final status still arrives through onStatus. On iOS the same call also receives the return URL of a Revolut Pay payment when the Revolut Pay module is installed.

Where to call it

Call handleDeeplink from wherever your app receives an incoming URL.
Use AppDelegate if you use UIKit, or the SwiftUI lifecycle if your app is SwiftUI-based.UIKit (AppDelegate)
SwiftUI (onOpenURL)

Signature

  • Transactions. How a payment flows through Yuno.
  • onStatus. Receives the final status of the transaction.