Banxa primary sources — 2026-04-30

Project status in this pass

• No canonical standalone whitepaper or litepaper surfaced.
• The clearest current source of truth is the official docs corpus, llms.txt, and API / integration materials.
• The main marketing site was behind a web challenge during this pass, so this review leaned on Banxa’s first-party documentation surface.

Primary-source snapshots

1) Docs overview / access and setup

• URL: https://docs.banxa.com/docs/overview
• Key excerpt:
  • Banxa says partners receive both a self-service Partner Dashboard and a sandbox environment before production approval.
  • The page frames two independent integration choices: checkout presentation (iFrame vs Redirect) and backend integration method (API integration vs Referral integration).
  • It also says dashboard changes such as webhooks, supported crypto/blockchains, and UI settings propagate into the integration.

2) Docs llms.txt

• URL: https://docs.banxa.com/llms.txt
• Notes:
  • Enumerates a large first-party surface spanning KYC token sharing, authentication, checkout visualization, API vs referral integration, mobile WebView guidance, onramp and offramp APIs, referral links, testing, webhooks, supported assets, payment methods, order status, dashboard configuration, and API reference endpoints.
  • Strong evidence Banxa should be treated as a broad integration platform rather than a one-page widget product.

3) Integration-method guide

• URL: https://docs.banxa.com/docs/integration-method
• Key excerpt:
  • Banxa distinguishes URL-based referral integration from full REST API integration.
  • Referral is positioned as the fastest path but without webhooks, in-app quote UI, or KYC sharing.
  • API integration is positioned as the higher-control path with quote retrieval, order creation, payment-method and currency control, webhook status updates, and KYC sharing.

4) Checkout-visualization guide

• URL: https://docs.banxa.com/docs/checkout-visualisation-iframe-vs-redirect
• Key excerpt:
  • Banxa describes checkout as a sequence covering identity verification, payment details, and order confirmation.
  • It explicitly compares redirect and embedded iframe / mobile WebView patterns, including tradeoffs around UX control, Apple Pay / Google Pay compatibility, and WebView configuration requirements.
  • This is useful evidence that Banxa operates as an embeddable checkout control plane, not just a hosted buy-crypto page.

5) On Ramp API guide

• URL: https://docs.banxa.com/docs/tutorial
• Key excerpt:
  • Banxa says the API route exposes JSON REST APIs for orders, prices, payment methods, countries, currencies, and customer-identity registration.
  • The docs say partners can pre-build a quote journey, then redirect or embed Banxa checkout, where Banxa handles KYC, payments, and liquidity.
  • The page also says Sumsub token sharing can let users skip repeated KYC friction in some flows.

6) Off Ramp API guide

• URL: https://docs.banxa.com/docs/off-ramp
• Key excerpt:
  • Banxa supports sell-side flows in which the partner facilitates the crypto transfer while Banxa collects KYC and fiat-payout details.
  • The docs describe a return URL that can be appended with the deposit address and related order details once payout details are submitted.
  • This shows Banxa is not only an onramp but also a partner-facing offramp platform.

7) Webhooks guide

• URL: https://docs.banxa.com/docs/webhooks
• Key excerpt:
  • Banxa says partners can configure separate sandbox and production webhook URLs.
  • Order status changes are sent via HTTP POST, and the docs recommend verifying authenticity with HMAC plus fetching the authoritative order record afterward.
  • This indicates Banxa supports production-style event-driven integration rather than only redirect handoffs.

8) Supported cryptocurrencies and blockchains

• URL: https://docs.banxa.com/docs/supported-cryptocurrencies-and-blockchains
• Key excerpt:
  • Banxa publishes a large matrix of supported assets, networks, buy/sell availability, and geography restrictions.
  • The breadth of this list supports classifying Banxa as a broad market-access layer and not a narrow single-jurisdiction checkout tool.

9) Create-a-buy-order API reference

• URL: https://docs.banxa.com/reference/create-a-buy-order
• Key excerpt:
  • The API reference says POST /v2/buy returns a unique checkout URL that expires after one minute if the customer is not redirected.
  • Required and optional request fields include partner code, payment method, fiat / crypto amounts, blockchain, wallet address, return URL, customer reference, external ID, promotions, and email prefill.

Working conclusion

Banxa is best cataloged as fiat-crypto ramp infrastructure with a partner dashboard, multiple integration modes, KYC-sharing capabilities, event-driven order tracking, and broad asset / geography coverage. The official docs make the operating model unusually explicit: partners can choose low-effort referral handoff or higher-control API integration, and separately choose hosted redirect or embedded checkout UX.