Lumx vs Crossmint

Which should you choose, Lumx or Crossmint?

Choose Lumx if the deliverable is a bank account and a payout. A PSP settling Brazilian merchants needs a BRL account with agência and conta and a PIX payout today; Crossmint lists Pix for Q4 2026 and issues no named account. A payroll platform paying UK contractors needs Faster Payments in GBP; Crossmint lists it for Q4. A treasury team collecting from Mexican buyers needs a CLABE in the customer's name; Crossmint's onramp takes cards and Apple Pay, not bank collections. Lumx has each of these live, in one API, with a locked quote, purpose codes and KYB/KYC inside.

Choose Crossmint if the deliverable is a wallet. Embedded wallets your users own, treasury wallets your policies govern, agent wallets an AI system spends from with on-chain limits, all across 50-plus chains with gas paid in fiat, plus a card, Apple Pay and Google Pay onramp, token checkout and minting. Crossmint's offramp already covers USD, EUR, MXN and COP, so a wallet-first product in Mexico or Colombia can pay out without a second provider, and its Spanish MiCA CASP and PSD2 licences give EU flows a directly regulated home.

Teams that need both run Crossmint for the wallet layer and Lumx for the accounts and rails. When value in a Crossmint wallet needs to become reais, pounds or a named local account, Lumx is the leg that does it today.

What is Crossmint?

Crossmint is a stablecoin and wallet infrastructure platform with offices in New York, Miami and Madrid, founded by Rodrigo Fernández Touza and Alfonso Gómez-Jordana. It raised $23.6M led by Ribbit Capital in March 2025 and counts Circle Ventures as a strategic investor. Per docs.crossmint.com, its platform has three pillars: Wallets (embedded, treasury and agent smart-contract wallets with passkey, TEE, HSM or server-key signers, an on-chain policy engine and gas sponsorship, on more than 50 blockchains), Payments (a consumer onramp by card, Apple Pay and Google Pay; an offramp to ACH, Same-day ACH, RTP, Wire, SEPA, SEPA Instant, SPEI, Bre-B and COP bank transfer, with SWIFT, Faster Payments and Pix listed for Q4 2026; stablecoin orchestration with treasury wallets, pay-ins, payouts and swaps; token checkout; and agent cards) and Tokenization (NFTs, verifiable credentials and batch minting). It ships SDKs for React, React Native, Flutter, Swift and Kotlin, a CLI and an MCP server, and publishes self-serve pricing with a free wallet tier. Crossmint Europe, S.L. is authorised as a MiCA crypto-asset service provider by the CNMV and as a PSD2 payment institution by the Bank of Spain; Crossmint Financial Services US is a FinCEN-registered MSB; Crossmint Canada Ltd. is a FINTRAC MSB and a Bank of Canada payment service provider. Named customers include MoneyGram, Western Union, Robinhood, Wirex, Santander and Telefónica.

Crossmint is adjacent to Lumx, not a rival. Its core product is the wallet; local payout rails are a feature it is adding to that wallet. Lumx's core product is the account and the rail; the custodial wallet is the balance behind them.

What is Lumx?

Lumx is stablecoin payments infrastructure for businesses that move money between Latin America and the rest of the world: one API to collect, hold, convert, and pay out in BRL, MXN, COP, USD, EUR, and GBP or in USDC and USDT, over local rails such as PIX, SPEI, PSE, ACH, FEDWIRE, SEPA, and Faster Payments, with SWIFT and on-behalf-of payments and collections (POBO and COBO) in USD, EUR, and GBP, plus named virtual accounts, custodial wallets, and KYB/KYC built in.

Lumx was founded in 2022 in Rio de Janeiro and is backed by BTG Pactual, the largest investment bank in Latin America. Custodial wallets run in production, segregated per customer, on Ethereum, Polygon, Base and Tron, with Stellar for USDC on-ramps in BRL. In Brazil, Lumx SPSAV Ltda operates under Article 88 of Central Bank Resolution 520/2025; in the US, Lumx US OP LLC is a FinCEN-registered MSB (#31000316459619). Lumx processes more than $2B in annualized payment volume (as of September 2026). Customers include Nomad, Logcomex and Conta Simples.

How do Lumx and Crossmint compare?

Model. Lumx is corridor-first: a named account in each of six currencies, a local rail behind each, a locked quote between stablecoin and fiat, and KYB/KYC, purpose codes and holder relationships on every payment. Crossmint is wallet-first: a smart-contract wallet per user, treasury or agent, with policies enforced on-chain, and payments attached as modules. Its onramp is a consumer purchase flow by card, Apple Pay or Google Pay, not a business collection into a bank account, and it has no named-account product in any currency. Its offramp does reach bank rails, and the overlap with Lumx is real where it is live: ACH, RTP and Wire in USD, SEPA and SEPA Instant in EUR, SPEI in MXN, Bre-B and bank transfer in COP. For Brazil, the UK and SWIFT, Crossmint's docs list Pix, Faster Payments and SWIFT for Q4 2026; as of September 2026 those rails are not live, and this page says so rather than leaving them out. Lumx runs all nine of its rails and SWIFT in USD today.

Custody. The word means different things on each side. Lumx custodies USDC and USDT per customer on Ethereum, Polygon, Base and Tron, as the balance a business pays out from. Crossmint's wallets are smart contracts: non-custodial by default for embedded use, with custodial treasury and agent configurations, signers that can be passkeys, TEEs, HSMs or server keys, gas paid by Crossmint and billed in fiat, and a policy engine that enforces spending rules on-chain, across more than 50 chains with about 18 self-serve. A Lumx wallet is an operational balance; a Crossmint wallet is a product a business hands to its users or its agents. Neither replaces the other.

Pricing and compliance. Crossmint publishes self-serve pricing: a free tier of 1,000 monthly active wallets, then per-unit and per-transaction fees across wallets, ramps, checkout, orchestration and tokenization, with volume tiers and bundles. Lumx charges a monthly platform fee plus usage-based per-transaction and virtual account fees, with transparent FX on locked quotes and no pre-funding, and does not publish plans. On regulation there is a real asymmetry in the EU: Crossmint Europe, S.L. holds its own MiCA CASP authorisation from the CNMV and a PSD2 payment institution licence from the Bank of Spain, while Lumx has no EU licence and runs EUR and GBP through banking partners. Lumx operates under Article 88 of Central Bank Resolution 520/2025 while its VASP authorization is processed, and both Lumx and Crossmint hold FinCEN MSB registrations in the US. Both use Sumsub for KYC; Lumx adds token sharing for instant approvals and Chainalysis on-chain monitoring, while Crossmint's identity API covers individuals only, with KYB done once for production access, and its screening stack names TRM Labs, Elliptic, Unit21, Sardine and Notabene.

When is Lumx the better fit?

• Your customers need a bank account in their own name. BRL with agência and conta, MXN CLABE, COP, USD routing and account, EUR IBAN, GBP sort code and account. Crossmint has no named-account product. See USDC to BRL, USDC to MXN, USDC to COP and USDC to EUR.

• You pay into Brazil or the UK today. PIX and Faster Payments are live on Lumx; Crossmint lists Pix and Faster Payments for Q4 2026. See USDC to GBP.

• You need SWIFT. Lumx runs SWIFT in USD with UETR and MT103 on every payout; Crossmint lists SWIFT in EUR for Q4.

• You collect from businesses, not consumers. Lumx's named accounts receive bank transfers from any local bank; Crossmint's onramp takes cards, Apple Pay and Google Pay, with bank transfers "coming soon". See BRL to USDC.

• You need Brazilian compliance modeling and local reporting fields. Lumx models purpose codes and holder relationships on every payment, which Brazilian and LATAM reporting demand.

• You need KYB as a data model. Lumx runs KYB on business customers as part of the API; Crossmint's identity API verifies individuals, with KYB done once with its team for production access.

Where does Crossmint fit?

Crossmint does several things Lumx does not do, and this page should say so plainly.

• Programmable wallets. Embedded, treasury and agent smart-contract wallets with an on-chain policy engine, flexible signers, account recovery and gas sponsorship billed in fiat, across more than 50 chains. Lumx has no wallet product of this kind.

• Agent payments. Agent wallets, agent virtual cards, agent checkouts from any merchant URL, and support for x402, Google AP2 and Visa Intelligent Commerce.

• Consumer onramp and checkout. Card, Apple Pay and Google Pay purchases of stablecoins and tokens with light KYC at low amounts, and hosted or headless checkout for NFTs, fungible tokens and physical goods.

• Tokenization. Minting of NFTs and verifiable credentials at scale.

• Offramp breadth in the US, EU, Mexico and Colombia today. ACH, Same-day ACH, RTP, Wire, SEPA, SEPA Instant, SPEI, Bre-B and COP bank transfer, with mobile money and cash pickup on the marketing page, and Pix, Faster Payments and SWIFT scheduled for Q4 2026.

• Direct EU licensing. A MiCA CASP authorisation and a PSD2 payment institution licence held by Crossmint Europe, S.L., where Lumx works through banking partners.

• Developer surface. SDKs for React, React Native, Flutter, Swift and Kotlin, a CLI and an MCP server; Lumx ships an OpenAPI spec and an MCP server, no SDKs.

• Published pricing. A self-serve price list with a free tier; Lumx prices by contact.

Can you use Lumx and Crossmint together?

Yes, and the split follows the product boundary. Crossmint holds the wallet layer: the embedded, treasury or agent wallets your users and systems control, the onramp and checkout that fund them, and the offramp rails it runs today in the US, EU, Mexico and Colombia. Lumx holds the accounts and rails: named BRL, MXN, COP, USD, EUR and GBP accounts, PIX and Faster Payments today, SWIFT in USD, and the KYB, purpose codes and relationship types a business payout needs. Both settle USDC on Ethereum, Polygon and Base, so moving a balance from a Crossmint wallet to Lumx custody is an on-chain transfer, and both send webhooks on status changes, so the reconciliation model is the same on each side.

How do you migrate from Crossmint to Lumx?

Most teams do not migrate; they add Lumx for the account and rail leg and keep Crossmint for the wallet. The steps below cover moving a stablecoin-to-fiat payout flow onto Lumx.

1. Map Crossmint offramp recipients to Lumx customers and destinations. Lumx runs KYB for businesses and KYC for individuals, with Sumsub token sharing where a prior verification exists, and adds a holder relationship (SUPPLIER, EMPLOYEE, SUBSIDIARY and others) and a purpose code on each payment.

2. Open a sandbox at dashboard.lumx.io. New accounts start in a sandbox with mock banking partners; magic numbers on taxId force approved, rejected or pending verification.

3. Provision named accounts. BRL, MXN, COP, USD, EUR and GBP accounts in each customer's name, so collections arrive on local bank details instead of through a card onramp.

4. Fund Lumx wallets from Crossmint wallets. Transfer USDC on Ethereum, Polygon or Base from the Crossmint treasury or user wallet to the Lumx custodial wallet; Crossmint wallets stay in place for everything that is not a bank payout.

5. Swap saved bank accounts for destinations and add a locked quote. Crossmint payment methods become Lumx destinations. Request a quote (30 seconds free, one or five minutes for a fee), show it, confirm within the window.

6. Subscribe to webhooks and run parallel. Send Idempotency-Key on every mutation, reconcile both ledgers for one cycle, then move production traffic. Read the docs or talk to us.