Banxa

• Name: Banxa
• URL: https://banxa.com/
• Category: fiat-crypto onramp and offramp infrastructure / checkout and referral integration platform / KYC and payments control plane
• Summary: Banxa is an embedded ramp operator with a broad docs and integration surface. The substance is the hosted checkout and compliance layer — API versus referral flows, redirect versus iframe handoff, KYC sharing, dashboard controls, webhooks, and geography gating — not the buy-crypto marketing shell.
• What it does:
  • Lets partners embed crypto onramp and offramp flows using either URL-based referral links or server-to-server REST APIs
  • Supports both redirect-style hosted checkout and embedded iframe / mobile WebView checkout patterns
  • Returns partner-facing checkout URLs from order-creation APIs so applications can control quoting and pre-checkout UX before handing off payment and KYC flows
  • Provides buy and sell order APIs, quotes, payment-method lookup, country and currency lists, and order-history / order-status retrieval
  • Offers webhook notifications for order lifecycle changes and HMAC-based authentication for webhook verification
  • Supports customer-identity and KYC-sharing flows, including Sumsub token sharing, to reduce repeated onboarding friction
  • Publishes large first-party supported-asset and supported-network tables plus geography restrictions, showing Banxa operates as a broad distribution layer rather than a narrow single-market ramp
• Key claims:
  • The docs say partners receive both a dashboard and a sandbox environment, with separate sandbox and production credentials and dashboard-based control over webhooks, supported crypto / blockchain choices, and UI settings
  • Banxa’s integration docs explicitly separate two decision axes: checkout visualization (redirect vs iframe / WebView) and backend integration method (API vs referral)
  • The API integration guide says Banxa exposes JSON REST APIs for orders, prices, payment methods, countries, currencies, and customer identity registration / KYC sharing
  • The referral-link docs show that partners can pass detailed checkout parameters directly in URLs, including order type, fiat / coin types, blockchain, wallet address, callback URLs, and branding controls
  • The onramp docs say a successful buy-order API response includes a one-minute checkout URL, after which Banxa handles checkout, KYC, and payment flows
  • The offramp docs show Banxa also supports sell-side flows where the partner helps facilitate crypto transfer and Banxa handles fiat payout after KYC and payout details are collected
  • The webhook docs say Banxa sends order-status changes via HTTP POST and uses HMAC authentication, while recommending a follow-up Get Order call for trusted status retrieval
  • The llms.txt index exposes a large first-party docs surface spanning KYC token sharing, authentication, onramp/offramp APIs, referral links, mobile WebView guidance, webhooks, supported assets, payment methods, and API reference endpoints
• Whitepaper: No canonical Banxa whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official docs corpus, llms.txt, and API / integration materials; see ../whitepapers/banxa-primary-sources-2026-04-30.md.
• Sources:
  • https://banxa.com/
  • https://docs.banxa.com/docs/overview
  • https://docs.banxa.com/llms.txt
  • https://docs.banxa.com/docs/integration-method
  • https://docs.banxa.com/docs/checkout-visualisation-iframe-vs-redirect
  • https://docs.banxa.com/docs/tutorial
  • https://docs.banxa.com/docs/off-ramp
  • https://docs.banxa.com/docs/webhooks
  • https://docs.banxa.com/docs/supported-cryptocurrencies-and-blockchains
  • https://docs.banxa.com/reference/create-a-buy-order

Internal linkages

• Best upward reads for stronger embedded-ramp operators: transak and ramp-network.
• Best contrast for the routing layer above any single ramp: onramper.

Control surface

• Practical authority sits in supported geographies, KYC reuse policy, payment-method routing, order-state visibility, callback behavior, and which assets or chains Banxa makes easiest to reach for partners.

• This is operator-default risk disguised as onboarding UX.

• Last reviewed: 2026-05-25 UTC