Wirex BaaS

• Name: Wirex BaaS
• URL: https://www.wirexapp.com/developers
• Category: stablecoin card-and-wallet middleware / hosted account-and-card control plane
• Tags: ethereum-ecosystem
• Summary: Wirex BaaS is hosted card-and-wallet middleware. The real surface is onboarding, Base smart-wallet deployment, wrapped internal balances, card issuance, and prefunded authorization. Long menu, still middleware.
• What it does:
  • Onboards users into Wirex BaaS by authenticating them, deploying account-abstraction wallets on Base, registering them on-chain, and completing KYC flows
  • Normalizes balances into wrapped internal stable assets such as WUSD and WEUR so partners can manage chain-agnostic value instead of juggling chain-specific stablecoin formats
  • Accepts multichain stablecoin deposits through global addresses and routes them into Base-side smart wallets, where deposits are wrapped into unified balance assets
  • Lets users withdraw by unwrapping unified assets back into external stablecoins and sending them to outside wallets
  • Issues virtual and physical Visa cards linked to user wallets, with API controls for activation, limits, freeze/unfreeze, PAN retrieval, transaction visibility, and 3DS confirmation
  • Exposes webhooks for wallets, balances, cards, card limits, 3DS events, activities, recipients, and withdrawal workflows
  • Supports an External Authorization model where partners keep their own user ledger and settle transactions against a prefunded Wirex master account instead of deploying per-user onchain wallets
• Key claims:
  • The docs make the platform shape plain enough: onboarding, cards, global addresses, unified balance, withdrawals, external authorization, bank rails, and a long webhook surface all sit under one hosted operator stack
  • The onboarding flow says each user gets an AA wallet on Base, while KYC can run through Wirex-hosted, SumSub-shared, or reliance-style paths, which is where real admission power sits
  • Wirex turns supported stablecoins into internal wrapped balances such as WUSD and WEUR, then unwraps again on withdrawal, so the actual accounting rail is Wirex-managed balance logic on Base rather than a simple pass-through wallet
  • The card side is conventional operator middleware: Visa-linked virtual or physical cards, tokenized card-management flows, point-of-sale fiat conversion, and webhooks for card, balance, recipient, and 3DS state
  • External Authorization is the cleaner lower-tier contrast: partners can skip per-user smart wallets, keep their own ledgers, and settle against a prefunded master account while Wirex calls out for authorization
• Whitepaper: No canonical standalone Wirex BaaS whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official docs corpus, llms.txt, onboarding and balance docs, card and webhook docs, and the external-authorization docs; see ../whitepapers/wirex-baas-primary-sources-2026-04-30.md.
• Sources:
  • https://www.wirexapp.com/developers
  • https://docs.wirexapp.com/llms.txt
  • https://docs.wirexapp.com/docs/api-basics.md
  • https://docs.wirexapp.com/docs/dev-onboarding.md
  • https://docs.wirexapp.com/docs/unified-balance.md
  • https://docs.wirexapp.com/docs/crypto-assets.md
  • https://docs.wirexapp.com/docs/cards.md
  • https://docs.wirexapp.com/docs/webhooks.md
  • https://docs.wirexapp.com/docs/extauth-overview.md

Internal linkages

• Best upward reads: gnosis-pay and rain.

Control surface

• Practical authority sits in onboarding approval, Base smart-wallet deployment, wrapped-balance accounting, card issuance, withdrawal routing, and partner-prefunded authorization.

• Read Wirex BaaS as the hosted operator layer that keeps identity, balances, cards, and bank-rail state in sync, not as some novel wallet substrate.

• Last reviewed: 2026-06-18 UTC