Card, Apple Pay, and Google Pay payments in a Banxa Native integration are executed entirely inside your app via the React Native SDK. There are no Banxa-hosted screens, no redirects, and no webviews in the payment path. The customer selects a payment method, completes payment on a native sheet, and returns to your app — all without leaving your product.
Bank transfers are handled directly through the Native API and do not involve the SDK at all.
Before invoking any SDK payment flow, your backend must call the eligibility endpoint and confirm that paymentReady: true is returned.
{
"paymentReady": true,
"requirements": []
}paymentReady: false means there are outstanding KYC or compliance requirements. Collect the missing information, submit it to the identity endpoint, and re-check eligibility before attempting payment. Do not proceed to the SDK if paymentReady is false — the order creation will fail.
Once eligibility confirms the user is cleared, pass the same identityReference to the SDK as externalCustomerId and call createOrderAndShowPrimerCheckout. The SDK creates the order and presents the native payment sheet in a single call — there is no need to re-run eligibility client-side.
→ See Interpreting Eligibility for the full requirements dictionary and handling logic.
Card data, Apple Pay tokens, and Google Pay tokens are captured by Primer — PCI DSS Level 1 certified. Card numbers and wallet tokens never pass through your servers or Banxa's API.
Partners using the SDK for card and wallet payments do not need their own PCI compliance certification. Bank transfers bypass the SDK entirely — no card data is involved, so they run fully through the Native API.
| Method | UI | Card details entered? |
|---|---|---|
| Apple Pay | OS-native Apple Pay sheet | No — authenticates with Face ID or Touch ID |
| Google Pay | OS-native Google Pay sheet | No — authenticates with device PIN |
| Cards | Primer card input drawer | Yes — the only non-native screen in the integration |
The Primer card input drawer is a bottom sheet that overlays your app. It is not Banxa-branded — it is Primer's card capture component, styled to your configuration. After the customer submits, it dismisses and control returns to your app. Everything else in the flow is built and owned by your product.
The following screens show the native payment experience as it appears within a partner app. Select View interactive prototype to walk through the full flow.
The Apple Pay flow triggers the OS-native Apple Pay sheet. No card details are entered — the customer authenticates using a card already saved to their device.
The card flow presents the Primer card input drawer — a bottom sheet overlaying the partner app. The customer enters their card number, expiry, and CVV. This is the only non-native UI component in a Banxa Native integration.
The Google Pay flow triggers the OS-native Google Pay sheet on Android. Like Apple Pay, no card details are entered manually — the customer selects a saved payment method and authenticates.
- React Native SDK Reference —
createOrderAndShowPrimerCheckout, Primer theming, configuration options, and type definitions. - Integration Guide — full end-to-end walkthrough, including the SDK payment step in context.
- Interpreting Eligibility — requirements dictionary and the loop for satisfying outstanding checks.