Which should you choose, Lumx or BlindPay?
Choose Lumx if custody and local accounts are the product. A neobank whose users hold USDC needs a custodial wallet with an SLA, not a beta with production on request. An exporter in Mexico invoicing a US buyer needs a standing CLABE and a standing US account in their own name; BlindPay gives the US one and a per-payment CLABE. A payroll platform paying Colombians needs Bre-B; a UK corridor needs Faster Payments in GBP. Lumx has all of that live, with locked FX quotes and purpose codes on every payment.
Choose BlindPay if your stack is crypto-native or agent-native. Eight chains with Circle CCTP v2 between them, Argentina over Transfers 3.0, RTP and ACH Pull in the US, TED in Brazil, and an agent toolchain that goes past the MCP server both companies ship: Agent Skills, a CLI, published prompts and integration pages for Lovable, v0, Cursor and Claude Code. Payables lets a stablecoin balance pay a Brazilian boleto or invoice.
If you only need PIX, SPEI, ACH and SWIFT in USD with a US account, both work and the decision is price and support. Ask BlindPay which of its published plans applies to you, and ask Lumx for a quote on your corridor.
What is BlindPay?
BlindPay is a stablecoin payment API founded in 2024 in Delaware and backed by Y Combinator (W25), Bitso, 468 Capital and Circle Ventures. It provides fiat-to-stablecoin payins, stablecoin-to-fiat payouts, KYC/KYB, US virtual accounts, POBO and COBO over SWIFT, and, since 2026, custodial managed wallets (beta) and Payables for boletos and invoices. It supports USDC and USDT across eight blockchains (Ethereum, Polygon, Base, Arbitrum, Tempo, Solana, Stellar, Tron). Its published rail table lists 13 rails: ACH, ACH Pull, Domestic Wire, RTP and SWIFT (USD); Pix, PIX Safe and TED (BRL); SPEI (MXN); PSE receive and ACH Colombia send (COP); Transfers 3.0 (ARS); SEPA send (EUR). BlindPay is a FinCEN-registered MSB and runs regulated activity through licensed partners. It reports $2.5B in annualized transfer volume across a 100+ country network. Customers include Takenos and Ruvo.
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 BlindPay compare?
Model. Both sell one API for stablecoin payments over local rails with KYC/KYB inside. BlindPay's center of gravity is the US: a US virtual account, ACH, ACH Pull, RTP, Domestic Wire and SWIFT, with LATAM reached through per-payment instructions and Payables. Lumx's center of gravity is the corridor: a named account in each of six currencies, so a customer in Brazil, Mexico, Colombia, the US, the eurozone or the UK receives on local details in their own name. The rail lists overlap on PIX, SPEI, PSE, ACH, Wire, SEPA and SWIFT. BlindPay adds RTP, ACH Pull, PIX Safe, TED and Argentina. Lumx adds Bre-B, Faster Payments, FEDWIRE, SEPA collection and PSE send. Both lock a quote before execution: BlindPay for five minutes, Lumx for 30 seconds free or one or five minutes for a fee.
Custody. Until 2026 BlindPay described itself as non-custodial. Its docs now offer a managed wallet where "BlindPay generates the address, holds the keys", in beta, with production access on request, up to 10 wallets per customer, on Ethereum, Base, Polygon, Arbitrum, Solana and Tempo, and an optional Yield feature that lends idle USDC on Base or Polygon. Lumx has run custodial wallets in production since launch, segregated per customer, on Ethereum, Polygon, Base and Tron, with real-time USDC and USDT balances and payouts straight from those balances. For a product whose users hold a balance, that is the difference between a GA service and a beta.
Pricing and compliance. BlindPay publishes plans (Basic, Business+, Enterprise) on its pricing page while its billing docs describe no monthly minimum, free development instances and per-account virtual account fees; ask which applies to you. 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; plans are not published, so contact sales. Both are FinCEN-registered MSBs operating through licensed partners, and both run KYC/KYB with a KYT engine, so US registration and screening are a tie. Lumx supports Sumsub token sharing for instant approvals, monitors on-chain activity with Chainalysis, operates under Article 88 of Central Bank Resolution 520/2025 while its VASP authorization is processed, and models purpose codes and third-party relationship types that LATAM reporting demands.
When is Lumx the better fit?
Your users hold a balance today. Lumx custody is production, per customer, on four chains. BlindPay's managed wallets are beta with production on request.
Your customers invoice on local bank details. Six currencies with a named account: BRL (agência and conta), MXN (CLABE), COP, USD (routing and account), EUR (IBAN), GBP (sort code and account). BlindPay issues a named account in USD only. See USDC to BRL, USDC to MXN, USDC to USD and USDC to EUR.
You pay out in Colombia over Bre-B. Lumx runs PSE and Bre-B both ways behind a named COP account. BlindPay receives over PSE and pays over ACH Colombia.
You run the UK. Faster Payments with named GBP accounts and GBP POBO and COBO. BlindPay has no GBP rail; UK payouts go over SWIFT in USD.
You collect in Brazil into a named account. Lumx's BRL account carries agência and conta in the customer's name; BlindPay's Pix payins use per-payment instructions. See BRL to USDC.
You collect in EUR. Lumx's IBAN receives SEPA; BlindPay's SEPA is send-only.
Where does BlindPay fit?
Eight chains. Solana, Stellar, Arbitrum and Tempo on top of Ethereum, Polygon, Base and Tron, with Circle CCTP v2 for cross-chain USDC. Lumx settles on four chains plus Stellar for BRL on-ramps.
Argentina. Transfers 3.0 in ARS, receive and send, live today. Lumx has ARS announced for Q3/2026.
US and Brazil rails depth. RTP and ACH Pull in addition to ACH and Domestic Wire; TED and PIX Safe in Brazil.
Agent tooling beyond MCP. Both ship an MCP server, llms.txt and an OpenAPI spec, and neither ships SDKs. BlindPay adds Agent Skills, a CLI, published prompts and integration pages for Lovable, v0, Bolt, Replit, Cursor and Claude Code.
Payables. Pay Brazilian boletos and invoices from a stablecoin balance (August 2026).
Yield. Idle USDC in a managed wallet can earn a variable rate on Base or Polygon (beta).
Can you use Lumx and BlindPay together?
Yes. The natural split is BlindPay for Argentina, Solana or Stellar settlement and agent-driven workflows, and Lumx for production custody, named accounts outside the US, Bre-B and Faster Payments. Both settle USDC on Ethereum, Polygon, Base and USDT on Tron, so a balance moves between them on-chain. Both expose webhooks and lock FX quotes, so the operational model on each side is the same.
How do you migrate from BlindPay to Lumx?
Map BlindPay receivers to Lumx customers and destinations. Both run KYB for businesses and KYC for individuals. Lumx adds a holder relationship (SUPPLIER, EMPLOYEE, SUBSIDIARY and others) on third-party destinations and a purpose code on each payment.
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.
Replace the USD virtual account and add five more. Lumx issues named accounts in BRL, MXN, COP, USD, EUR and GBP. Customers who received Pix, SPEI or PSE on per-payment instructions get a standing account instead.
Move balances out of managed or external wallets. Lumx custodial wallets are provisioned per customer on Ethereum, Polygon, Base and Tron; fund them with an on-chain transfer of USDC or USDT.
Swap quote windows. BlindPay locks for five minutes; Lumx locks for 30 seconds free or one or five minutes for a fee. Confirm inside the window.
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.
Methodology and sources
This page reflects both companies' public documentation as of September 2026. BlindPay facts come from its homepage and pricing page; its API docs for payins, payouts, receivers and virtual accounts; and its payment methods, supported countries, supported chains, managed wallets, Yield, billing, llms.txt and changelog, all fetched on 16 September 2026. Lumx facts come from docs.lumx.io and the verified-facts register maintained by the Lumx team. Country counts use each company's published onboarding lists and the same rule on both sides: countries a business can onboard from, plus anywhere SWIFT reaches that is not prohibited. Where BlindPay does not document a capability, this page says so rather than claiming it does not exist. Where its pricing page and billing docs disagree, both are quoted. Spot an error? Tell us.
This page is general information, not legal, tax, or financial advice. BlindPay is a trademark of BlindPay, Inc.; Lumx is not affiliated with BlindPay.
Fique por dentro do que a Lumx está desenvolvendo.
BlindPay
FAQ
Is Lumx a replacement for BlindPay?
For most LATAM payment flows, yes. Lumx covers PIX, SPEI, PSE, ACH, Wire, SEPA and SWIFT in USD like BlindPay, and adds production custody, named accounts in six currencies, Bre-B and Faster Payments. It does not replace BlindPay for Argentina, TED, Solana or Stellar settlement, or Payables.
Can you use Lumx and BlindPay together?
Yes. Keep BlindPay for Argentina, the extra chains and its agent tooling; run Lumx for custody, named accounts outside the US and the Colombian, UK and Brazilian rails BlindPay lacks. Both settle USDC on Ethereum, Polygon and Base, so balances move between them on-chain.
Which is cheaper, Lumx or BlindPay?
BlindPay publishes plans (Basic, Business+, Enterprise) while its billing docs say no monthly minimum, free development instances and per-account virtual account fees; ask which applies to you. 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. Compare on your actual volume.
How long does it take to migrate from BlindPay to Lumx?
Integration starts the day you sign up: Lumx accounts open in a sandbox with mock partners and magic numbers. Production follows a call and KYB. The concepts map one-to-one (receivers to customers, bank accounts to destinations, quotes to quotes), and the main data-model work is adding purpose codes and relationship types.
Does BlindPay offer custodial wallets?
Yes, since 2026, as "managed wallets" in beta: BlindPay holds the keys, production access is on request, up to 10 per customer, on six chains, with optional Yield on USDC. Lumx has run custodial wallets in production since launch, segregated per customer, on Ethereum, Polygon, Base and Tron.
Does BlindPay have virtual accounts in Brazil or Mexico?
Not as of September 2026. BlindPay issues named virtual accounts in USD, and an IBAN and BIC for SWIFT COBO. Pix, SPEI and PSE payins use per-payment instructions, and its billing docs list a Brazil virtual account as "not yet published". Lumx issues named accounts in BRL, MXN, COP, USD, EUR and GBP.

