Baanx

• Name: Baanx
• URL: https://www.baanx.com/
• Category: wallet-and-card control plane / crypto-funded spending middleware / embedded card infrastructure
• Tags: ethereum-ecosystem solana-ecosystem
• Summary: Baanx is wallet-to-card middleware. The card is the wrapper. The useful part is custody-mode choice, delegated spend, wallet-priority routing, and the internal balance logic that decides what actually funds a purchase.
• What it does:
  • Provides a multi-tenant API platform for cryptocurrency wallets, card payments, and user onboarding flows
  • Supports both custodial wallet integrations and non-custodial delegation flows so partners can choose whether users keep keys or the platform manages them
  • Offers virtual-card ordering, card lifecycle management, PIN operations, transaction history, and downloadable statements
  • Lets custodial internal wallets be linked to cards so purchases automatically draw from prioritized wallet balances
  • Exposes delegation flows for EVM and Solana wallets so users can approve limited spending authority without surrendering custody
  • Maintains credit-wallet and reward-wallet balances with withdrawal and history endpoints, suggesting an internal ledger layer behind card-funded spending
  • Positions itself for neobanks, exchanges, wallet apps, DeFi platforms, and white-label financial applications rather than only direct retail distribution
• Key claims:
  • The homepage says Baanx enables self-custody transactions that let users “buy, spend, and borrow directly against digital assets” and separately highlights non-custodial debit cards, custodial debit cards, card acquiring, and borrowing products
  • The docs introduction describes Baanx API as a “multi-tenant gateway” that bridges cryptocurrency wallets with traditional card payments and explicitly supports both custodial and non-custodial wallet models
  • The docs position OAuth 2.0 + PKCE as the default authentication layer and present wallet custody as a separate design choice, which is a useful clue that Baanx is packaging a fairly complete partner platform rather than one narrow SDK
  • The card-operations guide says sensitive operations use tokenized access patterns and hosted pages so partners can manage card details and PIN flows without taking on direct PCI exposure
  • The wallet-to-card linking guide shows internal wallets can be linked to cards with a priority order, allowing the platform to try multiple wallets and currencies/networks when a card transaction occurs
  • The delegation guide says users with MetaMask-, WalletConnect-, Coinbase Wallet-, Phantom-, Solflare-, or Backpack-style wallets can grant limited onchain spending authority while retaining custody, and that Linea, Ethereum, and Solana are supported networks in the current docs set
  • The llms.txt index exposes a broad first-party API surface spanning auth, onboarding, consent, cards, delegation, internal/external/credit/reward wallets, statements, and transaction history, which is strong evidence that Baanx operates more like financial middleware than a single card product
  • The homepage includes partner testimonials from Visa, Mastercard, MetaMask, Ledger, Exodus, and 1inch, which at minimum signals active go-to-market emphasis around embedded crypto card programs and self-custody spending
• Whitepaper: No canonical standalone Baanx whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official API docs corpus, llms.txt, and the company site; see ../whitepapers/baanx-primary-sources-2026-04-30.md.
• Sources:
  • https://www.baanx.com/
  • https://docs.baanx.com/guides/introduction
  • https://docs.baanx.com/llms.txt
  • https://docs.baanx.com/guides/card/overview
  • https://docs.baanx.com/guides/wallet/custodial/card-linking
  • https://docs.baanx.com/guides/delegation/overview
  • https://docs.baanx.com/api-reference/wallet/credit

Internal linkages

• Keep the linkage budget short.
• Best upward reads: gnosis-pay, rain, and openpayd.

Control surface

• Practical authority sits in onboarding, custody-mode selection, delegated-spend setup, wallet-priority routing, card-program configuration, and the internal ledger logic that decides which balance actually gets hit.

• That is the whole point of the note. Baanx is not a payment rail. It is middleware stitching wallets, cards, compliance state, and partner policy into one operator stack.

• Last reviewed: 2026-06-04 UTC