The best stablecoin infrastructure for neobanks in Latin America is the layer that issues local accounts in each customer's own name, holds the balance in custody and pays out over each country's own rail, delivered through one API. A neobank rents it instead of building it.
For most neobanks that means API infrastructure behind their own app, not a white-label product. Eleven providers are compared below, with the 2026 rules that change the choice in 2027. The country-by-country payout view is in best stablecoin APIs for Latin America.
The five jobs a neobank hands to its provider
A neobank's product is the app, the ledger and the customer relationship. Five jobs sit underneath:
Local accounts, so customers can be paid by local banks and payers.
Conversion between local currency and USDC stablecoin at the edges of the balance.
Custody of the balance between deposit and withdrawal.
Payouts to a bank in the customer's country, over that country's own rail.
Identity checks on every user, with a path when a document is missing.
Brazil runs on Pix (the Central Bank's instant payment system). Mexico runs on SPEI (the Banxico interbank system), paid to a CLABE (the 18-digit Mexican account number). Colombia runs on Bre-B (the instant payment system launched in 2025) and on PSE (an online bank-transfer network), which only collects. A provider that does the five jobs in one country has not done them in the other two, so the stablecoin corridor is the unit to check.
Why a neobank uses stablecoins is in what stablecoin banking is, the API layer in what a stablecoin API is, and the shortlist in embedded banking API with an on-ramp. On Lumx, the five jobs sit behind one API: create a customer with the currencies it needs, and the accounts, wallet and verification follow.
Which of eleven providers is the best stablecoin infrastructure for neobanks in Latin America?
Provider facts from Lumx's comparison pages verified on September 16 and 17, 2026, with the Conduit payouts API re-read on November 10; the Lumx row comes from Lumx's verified facts and docs.lumx.io, read on November 16.
Provider | Accounts for end customers | Payouts in Brazil, Mexico, Colombia | Custody | What it is built for |
Lumx | Named virtual accounts in BRL, MXN, USD, EUR and GBP; a COP account for any customer, named when the customer is Colombian | Pix, SPEI, Bre-B and ACH Colombia | Custodial, a wallet per customer on each supported blockchain | Neobanks whose users hold balances |
Bridge | Virtual accounts in USD, EUR, MXN, BRL, COP and GBP, BRL through a Pix code | Pix, SPEI, Bre-B and bank transfer | Custodial or external wallets, about 19 chains | Issuing a stablecoin, cards |
Due | Named accounts in EUR, GBP, USD and AED; BRL, MXN and COP accounts documented under Due's name | SPEI and Bre-B | Non-custodial vault | Self-custodied balances, many regions |
UnblockPay | Named USD and EUR accounts; Brazil and Mexico on per-payment instructions | Pix and SPEI | Custodial, one wallet per customer | White-label resale |
Avenia | A static Pix code, a per-payment CLABE and Bre-B instructions | Pix, SPEI and Bre-B | Balances in a main account and subaccounts | Products built on BRLA |
Trace Finance | BRL named accounts and virtual accounts | Pix | Accounts holding BRL, USDT and USDC | A Brazil-only product |
BVNK | Named USD, EUR and GBP accounts | No Brazilian, Mexican or Colombian rail | BVNK-custodied wallets | US, UK and EU enterprises |
Conduit | Named USD, EUR and GBP accounts | Pix, SPEI and ACH Colombia listed in its payouts API, with no availability by corridor published | Custodial balances, plus a non-custodial wallet | Multi-signer wallets |
Crossmint | No named local bank account | SPEI and Bre-B (as of September 2026) | Non-custodial by default for embedded wallets | Wallet-first apps |
Circle | No named local accounts | Through partner institutions on Circle Payments Network | Issuer reserves; wallets are a separate product | Minting and redeeming USDC |
Rain | End-user accounts in USD and MXN | None of the three documented | Custodial and non-custodial options | The card program |
Three of the eleven, Lumx, Bridge and Due, document standing accounts in all three local currencies, and only Lumx documents them in the customer's own name in Brazil and Mexico. Three document payouts in Brazil, Mexico and Colombia without a caveat: Lumx, Bridge and Avenia. The rest cover part of it, or publish no availability by corridor.
An account can exist without carrying the customer's name: some providers show a pooled recipient name in the payer's bank app. Check that line in every provider's documentation; what a named virtual account is explains why.
Bre-B is capped at 1,000 UVB per transaction (COP 12,110,000 in 2026) by section 3.2 of the Banco de la República's Circular Reglamentaria Externa DSP-465, re-read on November 16 (March 31, 2026) for every provider. On Lumx, a Bre-B payout above the cap is refused rather than split, and ACH Colombia has no per-payment limit, so it carries the larger invoice.
Does a Latin American neobank need white-label stablecoin infrastructure?
"White-label" covers two models. A white-label product hands over a ready dashboard under the buyer's brand, with a spread the buyer sets per quote; among the eleven, UnblockPay sells one to FX correspondents (Lumx's comparison page, verified in September 2026). API infrastructure runs the accounts and the payouts behind the neobank's own app, as the rest of the table does.
A neobank's product is the app, so it usually wants the API, and the brand that counts is the one on the money: the payer's bank shows the neobank's customer as the beneficiary, and the recipient's bank shows that customer as the sender.
On Lumx, the neobank builds on the API and its team uses the Lumx dashboard alongside it; Lumx does not sell a white-label app or dashboard. The neobank earns through a partner fee, set as a rate in basis points, a flat amount in dollars or both, separately for deposits and withdrawals. Lumx sends it to the wallet the neobank chooses. Lumx's own price is a monthly platform fee plus usage-based per-transaction fees, transparent FX on locked quotes, no pre-funding; no published plans. The standard agreement has a monthly minimum, waived during ramp-up. On a Pix, SPEI or Bre-B payout, no fee comes out of the amount that reaches the recipient, and only the recipient's bank can charge them.
What changes for Latin American neobanks in 2027
Dates from primary texts read on November 16, 2026: Res. BCB 520, 589 and 584, the GENIUS Act, the OCC bulletin and Portafolio
Date | Rule | What it means for a neobank |
November 6, 2026 | Brazil, Res. BCB 520 Art. 91, as amended by Res. 589 | Banks may not work with a virtual asset provider not authorised in Brazil, except as the resolution allows; ask each provider where it stands |
January 1, 2027 | Brazil, Res. BCB 584 | A Brazilian provider holds a transfer to a self-custodied wallet or foreign virtual asset firm for 24 hours above USD 10,000 per operation or per day |
January 18, 2027 | GENIUS Act and the OCC final rule take effect | Only a permitted issuer may issue a payment stablecoin in the United States; ask whose USDC backs the balance |
During 2027 | Colombia, Bre-B | The central bank expects rules for payroll, supplier payments and collections on Bre-B (Portafolio, September 17, 2026); no rule text yet |
On Lumx, each app user is one customer with its own wallet, and a transfer that needs a hold goes through a transactional RFI (request for information, a compliance hold that asks for a document). Since October 21, 2026, a SPEI destination also needs the holder's type, tax ID and name, so collect them in the neobank's payout form.
Where each alternative fits, and when the stablecoin layer is the wrong one
Bridge fits issuing a stablecoin or running cards from the same vendor, Rain a card-led product, Circle minting and redeeming USDC, Crossmint an app that starts from an embedded wallet, and Trace Finance a Brazil-only neobank.
One-to-one pages are on the compare hub; the method is in choosing an infrastructure provider. On Lumx, one contract covers accounts and payouts in Brazil, Mexico and Colombia, with custody and verification included.
None of the eleven fits a neobank with one country and one currency, which needs no stablecoin leg, or one that pools funds for users it never onboards: on Lumx, nested payments are not allowed, so each user needs an account and wallet. For a launch country outside Brazil, Mexico and Colombia, read the Lumx coverage page first.
How long does it take to go live, and which stablecoins do the wallets hold?
Wallets hold USDC and USDT, and the chain decides which a customer can use. On Lumx, USDC runs on Ethereum, Polygon and Base and USDT on Ethereum, Polygon and Tron.
On Lumx, an API integration takes 2 to 3 weeks to go live, and your team uses the Lumx dashboard alongside the API. BRL, MXN, EUR, GBP and COP accounts turn active right after the customer is approved, and the USD account takes up to one business day.
Who holds the money, who checks the customers, and where the card sits
Custody comes in three models: the provider holds the keys (custodial), the customer's own wallet signs (non-custodial), or an issuer holds reserves against a token. The practical question is who answers to the customer when a balance looks wrong.
Compliance has two halves: verification at onboarding, KYC (know your customer, for individuals) and KYB (know your business, for companies and their owners), and what happens afterwards. An RFI (request for information, a compliance hold that asks for a document before a transaction clears) should name the document and arrive as an event.
On Lumx, custody is with Lumx: each customer gets a wallet on each supported blockchain, created with the customer and enabled once approved. KYC runs through Sumsub, and monitoring through Chainalysis. KYB targets one business day once the documents are in. An RFI can sit on the customer, the account or a transaction, and it comes as an event naming the documents at issue. An individual already verified on the neobank's own Sumsub account can be imported with a share token, which saves the document upload and liveness check. Lumx has filed its SPSAV application and operates under the transition of Res. BCB 520 of 2025, Article 88; the COP leg runs under its banking partner's licence. A neobank that operates through a licensed partner can be a Lumx customer; the neobank licence guide covers authorization.
Cards sit beside the account, not inside it, under a separate contract with a card issuer. With Rain's real-time funding, described on its site, the cardholder connects a wallet and approves a spending limit, and each purchase commits only its own amount.
On Lumx, a card top-up is a deposit by Pix, SPEI or PSE that converts to stablecoin in the customer's wallet, and the withdrawal is an off-ramp started by the neobank's platform through the API. The off-ramp does not see open card authorizations, so capping a withdrawal at the balance minus the holds is the app's job. Rain stays the card issuer, under its own contract.
The order I would shortlist in
I would shortlist on the account question before price, speed or chain count. A deposit that shows the customer's own name is easier to explain than one that shows the provider's. I would ask next who holds the balance, and only then compare fees, because fees can be renegotiated and a custody model cannot be changed without a migration. And I would sign the card issuer separately, so replacing one vendor does not mean replacing both.
What this looks like on Lumx for a neobank
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, Bre-B, 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.
Day one: the platform creates the customer with the currencies it needs, the customer accepts the terms and completes verification, and each account turns active with an event.
Money comes in by an on-ramp for an exact amount, or by an autoconversion rule that converts every deposit to a standing Pix code or CLABE. Money goes out through a registered destination, a locked quote and an off-ramp. On a Pix or SPEI payout the recipient sees the customer as the sender, as the sender of record page lists. A named virtual account is the account type behind both, and global payments is the product page for the payout side.
A neobank that needs named BRL and MXN accounts, a COP account and custody under one provider should start with Lumx. One that decides on a card program or an issued stablecoin should weigh the issuers first. The operator map shows who operates where, and the supported countries page lists onboarding countries.
Methodology and sources
Providers were included if they publish an API and cover at least one of the five jobs in Brazil, Mexico or Colombia; Transfero and Bloquo cover neither Mexico nor Colombia. Facts for ten providers come from the comparison pages on lumx.io/compare, verified on September 16 or 17, 2026; Conduit's payouts API was re-read on November 10, and Due's Pix is left out because its docs changed after that verification.
Lumx facts come from docs.lumx.io pages read on November 16, 2026 and from Lumx's verified facts register, which takes precedence where the docs lag. Rain's real-time funding was read on rain.xyz the same day.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Al Ishrak Sunny on Unsplash.
What is the best stablecoin infrastructure for neobanks in Latin America in 2027?
The best fit gives each customer a local account in Brazil, Mexico and Colombia, holds the balance in custody and pays out over each country's own rail. Of eleven providers compared in 2026, three document standing accounts in all three local currencies, only Lumx in the customer's own name in Brazil and Mexico. Lumx issues named accounts in reais and Mexican pesos, a COP account for any customer, and pays out over Pix, SPEI, Bre-B and ACH Colombia.
Can a neobank give each customer a named account in Brazil, Mexico and Colombia?
In Brazil and Mexico, yes, with a provider that issues named virtual accounts. In Colombia the account is named only when the customer is Colombian, and some providers show a pooled recipient name, so check what the payer sees. On Lumx, a customer created with BRL, MXN or COP gets the account after approval, named in Brazil and Mexico; the COP account is open to any customer.
Who holds the money in a neobank's stablecoin balance?
Some providers hold the balance in custody and some let the customer's own wallet sign. The question is who answers to the customer when a balance looks wrong. On Lumx, custody is with Lumx, each customer has a wallet on each supported blockchain once approved, and the neobank reads balances through the API.
Can a neobank offer a card on top of the account?
Yes, as a separate contract with a card issuer such as Rain. The accounts provider handles deposit and withdrawal. On Lumx, the top-up is a Pix, SPEI or PSE deposit that converts to stablecoin in the customer's wallet, and the withdrawal is an off-ramp started through the API.
What is the best white-label stablecoin infrastructure for neobanks in Latin America?
For most neobanks it is API infrastructure behind their own app, not a white-label product, which suits FX correspondents that resell. Lumx does not sell a white-label app: a neobank builds on the Lumx API, with accounts in each customer's own name in Brazil and Mexico, a COP account, custody by Lumx and payouts over Pix, SPEI, Bre-B and ACH Colombia.





