The best stablecoin pay-in API for Latin America in 2027 is the one that gives each payer a local account in their own country and turns what arrives into USDC without a manual match. On documentation checked through November 2026, Lumx, Bridge and Avenia document local collection in Brazil, Mexico and Colombia.
Quick answer:
Local collection in all three countries under one API: Lumx, Bridge and Avenia, with different account types.
Accounts in the customer's own name in both Brazil and Mexico: Lumx, with Trace Finance in Brazil and Rain in Mexico.
Dollar, euro and pound accounts for payers abroad: UnblockPay, BVNK and Circle, plus Lumx and Bridge.
Brazil over Pix: Lumx and Bridge, plus the Brazil specialists Trace Finance, Transfero and Bloquo.
Cards and wallets rather than bank-account collection: Crossmint, Rain and Velocity.
This post covers collection only. Payouts and off-ramps are in best stablecoin APIs for LATAM and Latin America payout rails compared, and who issues accounts is in virtual account providers.
What a pay-in API has to do in Latin America
A pay-in API belongs on this list if a payer can send a domestic transfer and your customer receives a stablecoin balance. Five tests separate the providers.
The first is the rail: Pix (Brazil's instant payment system, run by the Central Bank) in Brazil, SPEI (Mexico's interbank transfer system, run by Banxico) in Mexico, and Bre-B (Colombia's instant payment system, launched in 2025) and PSE (Colombia's online bank-transfer network) in Colombia.
The second is the account. A named virtual account (a local account number issued in the customer's own name) lets the payer pay what looks like a supplier, while a shared deposit instruction points everyone at the provider's account and asks for a reference. The difference is in named accounts versus one-time deposit instructions.
The third is conversion: whether each deposit becomes USDC or USDT on arrival, at what rate. The fourth is the bad day: a deposit that arrives late, short, from a third party or without its reference. The fifth is reconciliation through webhooks, so finance can close a payment without a bank statement.
Which providers collect in Brazil, Mexico and Colombia?
What each provider documents for collection, from the matching Lumx comparison page. Those pages were verified against each provider's own docs or site between September 16 and November 10, 2026. The Lumx row is Lumx's own statement of November 16, 2026.
Provider | Brazil (BRL) | Mexico (MXN) | Colombia (COP) | What the payer pays into |
Lumx | Named account with agência and conta, plus a Pix code | Named account, CLABE over SPEI | Bre-B key and PSE | Customer's name in BRL and MXN; in COP, the customer's name only for Colombian customers |
Bridge | Pix BR Code | CLABE over SPEI | Bre-B | BRL is a QR code, not agência and conta |
Avenia | Static BR code | CLABE per payment | PSE and Bre-B instructions | Per-payment instructions; subaccounts are a ledger |
Conduit | Pix and TED on a shared account with a payment reference | CLABE over SPEI | ACH Colombia, naming the collecting institution | Shared in BRL; no reference needed in COP |
Due | Pix, in Due's name | In Due's name | In Due's name | Named EUR, GBP, USD and AED; local ones are Due-named |
UnblockPay | Per-payment instruction | Per-payment instruction | None | Named accounts in USD and EUR |
BVNK | None | None | None | Named accounts in USD, EUR and GBP |
Bloquo | Pix QR deposits | None | None | Named BRL account marked coming soon |
Trace Finance | Pix, TED and boleto funding | None | None | BRL accounts, some in the owner's name |
Rain | None | CLABE over SPEI | None | Named USD and MXN accounts in the end user's name |
Lumx, Bridge and Avenia show a route in all three countries. Conduit documents deposit details in all three, on a shared account in Brazil, and Due's local accounts sit under Due's name. Circle, Crossmint and Velocity document no named local account.
The groups behind the table
The fourteen providers fall into four groups, and the group decides most of the choice.
Payments infrastructure with local collection: Lumx, Bridge and Avenia, with Conduit and Due as partial cases. These can put a Brazilian, Mexican or Colombian payer on a local rail, and differ on whether the payer sees your customer or the provider.
Dollar-account providers: UnblockPay, BVNK and Circle. A payer abroad can pay by ACH, wire or SEPA, and a payer in Latin America cannot pay locally. That suits payers in the United States or Europe, not a company that bills in reais.
Brazil specialists: Trace Finance, Transfero and Bloquo run Pix and BRL accounts as the core product, and some add TED or boleto (a Brazilian bank slip payable at any bank or app) funding. For Brazil-only questions, see stablecoin payment providers for Brazil.
Wallets, cards and checkout: Crossmint, Rain and Velocity collect from cards, wallet deposits or card-network flows, and none documents Pix or PSE collection. One-to-one views: Lumx versus Conduit and Lumx versus Bridge.
What changes for collections in 2027
Dated changes that reach collections, read in the primary text where reachable. Resolutions are the Central Bank of Brazil's (BCB).
Date | Country | Change |
December 14, 2026 | Mexico | Banxico Circular 9/2026: standard mobile transfer screens in SPEI apps; no new collection rule |
January 1, 2027 | Brazil | Resolution BCB 584: a 24-hour hold on some transfers of virtual assets to a self-custodied wallet or a foreign virtual asset firm |
February 1, 2027 | Brazil | Resolution BCB 587: hybrid charge (Pix Cobrança also payable by boleto) and fraud-suspicion marks in the Pix key directory |
May 31, 2027 | Brazil | Resolution BCB 561: eFX providers outside the listed institutions must request authorization, and eFX cannot settle with virtual assets |
During 2027 | Colombia | Bre-B to carry collections, payroll and supplier payments, with rules due by year-end |
Brazil: the 24-hour hold, the hybrid charge and May 31
Resolution BCB 584 (August 7, 2026) takes effect on January 1, 2027. Article 2-B says a provider of virtual asset services may execute a transfer order only 24 hours after the funds that fund it arrived in the wallet, in reais or as virtual assets, when the destination is a foreign virtual asset firm or a self-custodied wallet. The hold applies above US$10,000, per operation or as the customer's total that day, or when the provider's own risk policy asks for it. Stablecoins are named as covered, and providers in the Article 88 transition are included.
On a plain reading, the clock starts when the funds reach the wallet, so for a collection it starts when the Pix converts. A platform that forwards the balance the same day to its own exchange or a personal wallet above US$10,000 should expect a wait. A BRL payout, or a balance left in a custodial wallet, is not covered in the text. See Brazil's self-custody wallet rule.
Resolution BCB 587 (September 18, 2026) matters on February 1, 2027 for anyone who bills over Pix with a due date. A hybrid charge lets one invoice be paid by Pix or by boleto, and if the Pix settles after the boleto was paid, Article 41-A, paragraph 3 makes the collecting institution refund the payer in full from its own funds within 24 hours. Offering it is optional, and BRL collection on Lumx is Pix only today. On July 1, 2027, Pix Automático (recurring Pix) also reaches salary accounts.
Resolution BCB 561 (April 30, 2026) covers eFX, the international payment service. Article 56-B gives providers outside the listed institution types until May 31, 2027 to request authorization, and Article 50 bars virtual assets from the settlement with the foreign counterparty. A collection that reaches a foreign seller through eFX cannot settle in stablecoin.
Mexico: no dated SPEI collection rule in 2027
In the sources read, no Banxico or CNBV (Mexico's banking and securities regulator) rule changes how SPEI collection works in 2027. The dated item is Circular 9/2026, signed June 8, 2026, which gives SPEI participants until December 14, 2026 to standardize the mobile transfer experience. A CLABE (the 18-digit Mexican bank account number) still works the same way.
Colombia: Bre-B is due to reach companies
Bre-B today carries a cap per payment. Circular DSP-465, in its March 31, 2026 version, caps each payment at 1,000 UVB (Unidad de Valor Básico, the central bank's unit for the cap), which is COP 12,110,000 in 2026 at the UVB value of COP 12,110 set by Finance Ministry Resolution 3488 of 2025 (per a CER Latam summary of that resolution). The cap applies to every provider, and its peso value moves with the UVB each year; no 2027 value was out when this was written.
The 2027 change is reported by Portafolio on September 17, 2026, quoting Ana María Prieto, director of payment systems at the Banco de la República: the bank expects to close the year with regulation that lets Bre-B carry payroll, supplier payments and collections, with invoice number and billing period as extra fields, arriving during 2027 as each institution adapts. The bank's project pages blocked automated reading, so the rule text was not read.
Mismatched and third-party deposits
A collection API earns its place on the bad day. The table shows how Lumx handles three cases to ask every provider about.
How Lumx treats deposits that do not match the happy path, from Lumx's own statements of November 16, 2026.
Case | What Lumx does |
SPEI with no memo on an account that has several rules | The deposit lands and converts at the floating rate; the rule is not applied |
USD or EUR deposit with no rule or on-ramp active | The fiat stays in the account |
A payer who is not the customer (COBO) | Allowed when it fits the declared flow of funds; an unusual payer can trigger an RFI (a compliance hold that asks for a document), and a return can follow |
The other providers' pages read do not describe these cases, so none is compared; run them in a sandbox before signing. For a deposit that never arrived, start with the usual causes.
Which provider fits which collection use case
B2B collections where customers pay from local banks: a named account in each payer's country. Lumx names BRL and MXN accounts in the customer's name. See named virtual accounts for B2B collections.
A marketplace with sellers in several countries: each seller as its own customer with its own account, which Lumx and Bridge document in all three countries.
Dollar collection from payers in the United States or Europe: Lumx, UnblockPay, BVNK or Bridge.
Boleto or TED funding next to Pix, for a business that bills only in reais: Trace Finance.
I would not pick a collection provider from its rail list. I would ask each one to show, in the sandbox, what a payer's bank app displays as the beneficiary and what happens when the deposit arrives without its reference. Neither shows on a pricing page, and the second is where a finance team stops a payment.
When a stablecoin pay-in API is the wrong tool
A stablecoin pay-in is the wrong tool when your customers pay you in reais and you keep reais: a local bank account has fewer steps, and nothing is gained by converting on arrival.
It is also the wrong tool when one known counterparty pays once, since a single deposit instruction needs less setup, and when you would pool money from parties you have not onboarded. That is nesting, and Lumx's nested payments rules require written approval from compliance first.
What collection looks like with 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, 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.
The business requests currencies in the accounts array when it creates the customer, and BRL and MXN accounts are active right after approval. A standing autoconversion rule then returns the deposit details: a Pix code for BRL, or a CLABE with a memo for MXN. In COP, the payer sends to the Bre-B key of the account or pays by PSE (PSE is collection only; COP payouts go over Bre-B or ACH Colombia). Each matching deposit converts to USDC or USDT at the market rate, on Ethereum, Polygon, Base or Tron depending on the asset. A locked quote exists only on a single on-ramp, not on a rule.
Bre-B is enabled customer by customer, so confirm it for your account. The stablecoin reaches the wallet within about five minutes of a Pix or SPEI payment. The onramp.* webhooks follow each deposit from onramp.transferring_fiat to onramp.success, and the receipt carries amounts and rate, plus fees. Wallets are custodial, held by BitGo. Limits are on the Lumx limits page. The coverage page and the named virtual accounts page list the rails and account types, and on-ramping BRL, MXN and COP walks one deposit through.
Methodology and sources
Competitor rows come from the Lumx comparison page for each provider, verified against its own site and docs between September 16 and November 10, 2026. No pricing was compared, because few of the fourteen publish it.
The Lumx row comes from Lumx's own statements and the Lumx docs read on November 16, 2026: coverage, accounts, autoconversion rules and rail cut-off times. The Brazilian resolutions were read in the BCB's normative database on November 16, 2026: Resolution BCB 584, 587 and 561. Circular 9/2026 was read in the Diario Oficial de la Federación. Circular DSP-465 was read as the Banco de la República's PDF, and the 2026 UVB value is from the CER Latam summary of the Finance Ministry's resolution. The Colombian 2027 plan is from Portafolio, September 17, 2026. A cell that says none means the pages read did not document it.
Verified on November 16, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Wengang Zhai on Unsplash.
What is the best stablecoin pay-in API for Latin America?
It depends on the country and on what the payer sees. For local collection in Brazil, Mexico and Colombia, Lumx, Bridge and Avenia document a route in all three, with different account types. Lumx issues named accounts in BRL and MXN, collects in COP over Bre-B and PSE, and converts each deposit to USDC or USDT.
Which providers accept Pix, SPEI and Bre-B payments into a stablecoin balance?
On the comparison pages checked between September and November 2026, Lumx, Bridge and Avenia show all three, Conduit documents deposit details in all three, and Trace Finance, Transfero and Bloquo take Pix. Lumx converts each Pix or SPEI deposit through an autoconversion rule and credits the wallet within about five minutes.
What changes for stablecoin collections in Latin America in 2027?
From January 1, 2027, Brazil's Resolution BCB 584 holds some transfers to self-custodied wallets for 24 hours, and from February 1, 2027, Resolution BCB 587 adds the hybrid Pix and boleto charge. In Colombia, the central bank expects Bre-B rules for collections by the end of 2026. Lumx wallets are custodial, and a transfer that needs a hold goes through a transactional RFI (request for information, a compliance hold that asks for a document).
Can a third party pay into a collection account?
Usually for business payers, with limits that vary by provider and rail. On Lumx, a third-party payer is allowed when it fits the customer's declared flow of funds, and an unusual payer can trigger an RFI and a return. Pooling other parties' funds needs written approval from Lumx compliance.





