Checkout Visualisation

Redirect vs iFrame

The Banxa checkout is a sequence of screens that guides your customer through their crypto transaction — identity verification, payment details, and order confirmation. You choose how that checkout is presented to them.


Redirect

The customer is redirected to a Banxa-hosted checkout page, either in a new tab or the same window.

How it works:

  1. Your app generates a checkout URL (via Referral link or the checkoutUrl returned in an API order response).
  2. The customer is redirected to that URL.
  3. Banxa handles the entire checkout experience.
  4. On completion, the customer is redirected back to your redirectUrl.

Advantages:

  • Least integration effort — no embedding or WebView configuration required.
  • The checkout page can be co-branded with your logo and styling.
  • Fully compatible with all payment methods including Apple Pay and Google Pay.

Considerations:

  • The customer visibly leaves your application.
  • Less control over the in-app experience.

Embedded Checkout (iFrame)

The Banxa checkout is embedded inside your application using an iFrame (web) or WebView (mobile).

How it works:

  1. Your app generates a checkout URL.
  2. The URL is loaded inside an iFrame or WebView component in your UI.
  3. The customer completes the transaction without leaving your app.

Advantages:

  • Seamless experience — the customer stays within your product.
  • Greater control over layout and context around the checkout.

Considerations:

  • Requires additional WebView configuration on mobile (camera access, local storage, media playback).
  • Some payment methods (e.g., Google Pay on Android) require Custom Chrome Tabs rather than a standard WebView.
  • More integration effort than redirect.

Comparison

RedirectiFrame / WebView
Customer leaves your appYesNo
Integration effortLowMedium
Co-branding supportYesYes
Camera / KYC supportNative browserRequires WebView config
Apple PayYesNo
Google PayYesNo

Recommendation

  • Choose Redirect if you want the fastest integration or are building a mobile app where WebView complexity is a concern.
  • Choose iFrame / WebView if keeping the customer inside your product is a priority and you have the capacity to handle platform-specific WebView configuration.

Both options are compatible with both Referral and API integration methods.