Best virtual account providers for Latin America (2026)

Virtual account providers for Latin America are API companies that issue local bank account details in Brazil, Mexico or Colombia to your customers, so payers can transfer domestically and the money lands as a stablecoin balance. They differ on countries covered, whether the account carries your customer's name, which payers it accepts and what the provider holds.

Quick answer by need, on documentation read on November 1, 2026:

• Local accounts in Brazil, Mexico and Colombia under one API: Lumx and Bridge.

• Brazil: Trace Finance, Transfero and Bloquo (Brazil only), plus Lumx and Bridge.

• US dollar accounts that settle to a wallet: Lumx, BlindPay, UnblockPay, Bridge, Due, Conduit and BVNK.

• No local account documented in Brazil, Mexico or Colombia: UnblockPay, Due, Conduit and BVNK.

The wider ranking of stablecoin APIs is in best stablecoin APIs for LATAM. This post ranks one thing, the account that a payer sends money to. A named virtual account (a local account number issued in the customer's own name) is defined in what a named virtual account is, and the difference from a pooled account is in named versus pooled accounts.

What a virtual account in Latin America has to do

A provider belongs on this list if a payer in Brazil, Mexico or Colombia can send a domestic transfer in local currency and your customer is credited without a manual match. A provider can pass one test below and fail the others.

The first is the currency: a payer in São Paulo with only a US dollar account to pay into still has to send a wire. A local account means a Pix (Brazil's instant payment system, run by the Central Bank) key or code, a CLABE (the 18-digit Mexican bank account number) for SPEI (Mexico's interbank transfer system, run by Banxico), or a Bre-B (Colombia's instant payment system) key, with PSE (Colombia's online bank-transfer network) as the other way in.

The second is the name. The payer's bank app shows a beneficiary, and on Pix or SPEI a payer's accounts-payable team that cannot match the beneficiary to a supplier record may hold the transfer for review, and the money does not reach your customer until someone clears it. Whether that name is your customer's or the provider's is the line between a named account and a pooled one.

The third is who can pay in. Some providers accept only the account holder's own transfers, others add third-party business payers, and each rail has its own limits.

On Lumx, each named virtual account is issued by a banking partner, one currency per account, and the rails follow the currency. In every currency except COP the account shows the name of the customer who holds it, and in COP it shows the banking partner.

Which providers issue local-currency virtual accounts in Latin America?

What each provider documents for Brazil, Mexico and Colombia, from its own docs or site on November 1, 2026. Transfero's row also leans on the matching Lumx comparison page of September 16, 2026, because its docs host did not resolve.

Only two providers on the list document a local account in all three countries, Lumx and Bridge. BlindPay's docs page now lists Mexican and Colombian account types, which its own September 30, 2026 comparison article does not, and it labels both as not named. Four of the eleven (UnblockPay, Due, Conduit and BVNK) document no local account in Brazil, Mexico or Colombia, only USD, EUR, GBP, AUD or AED accounts, which solves collection for a payer abroad and not for a payer in São Paulo.

On who holds the money: BlindPay settles each deposit to the wallet linked when the account is created, and Lumx keeps the stablecoin in a custodial wallet per customer. The other pages read do not say, so none is claimed here.

For a one-to-one view, see Lumx versus Avenia.

Brazil, Mexico and Colombia rail by rail

In Brazil the rail is Pix. It runs 24/7. The detail to check is the name: payers pay a Pix code and see the holder in their bank app, so a BRL account in the customer's name looks like a supplier, while a pooled one looks like an intermediary. Lumx issues BRL accounts as named accounts (the customer's name shows as holder), and a foreign company can hold a BRL account without a local entity in Brazil. For Brazilian payers see also stablecoin payment providers for Brazil.

In Mexico the rail is SPEI, and the account is a CLABE. Each CLABE is unique to one customer, so a deposit ties to that customer without a manual match. BlindPay's CLABE accounts are open to customers of any country, and Lumx's MXN accounts are named in the customer's name, also without a local entity. No Pix or SPEI per-deposit limit was found on the pages read, so none is quoted; Lumx's own floor, the autoconversion minimum, is in the Lumx section below.

In Colombia the rails are Bre-B, with a key, and PSE. Two rules shape the account. Bre-B has a regulatory cap of 1,000 UVB per transaction, set by the Banco de la República in Circular Reglamentaria Externa DSP-465, Asunto 18, numeral 3.2, which is COP 12,110,000 for 2026 per the central bank's own Bre-B page, and the cap applies to every provider. Second, the account holder depends on who the customer is. On Lumx, the Colombian peso leg runs on a banking partner's program, so a COP account is available to any customer and is named only when the customer is Colombian; for other customers the holder shown is the banking partner. BlindPay documents about COP 12,000,000 per Bre-B deposit and sends larger amounts to PSE. Lumx collects over the customer's Bre-B key or PSE.

How fast does a virtual account open, and what price is published?

Bridge's gate is KYC (know your customer, an individual check) or KYB (know your business, a company check) approval. Fees and documents by rail are covered in fees and KYB by rail.

Lumx creates accounts in the same POST /customers request as the customer, and they wait for the customer's verification. Once the customer is approved, BRL, MXN and COP accounts are active immediately and USD takes up to one business day. The status moves through REQUESTED, PROVISIONING and ACTIVE, with an RFI (request for information, a compliance hold that asks for a document before a transaction clears) as the pause state, and an account.active webhook marks the moment the account can receive funds. Lumx targets one business day for the KYB review itself.

Test the name before the currency list

I would not choose a provider by how many currencies its page lists. I would ask each one to show, for the corridor I care about, which beneficiary name the payer will see in their bank app, then create an account in the sandbox and read that field. A provider can list ten currencies and still make the payer's finance team stop at an unfamiliar name. I would run this check before any pricing conversation, because the price of an account the payer will not fund does not matter.

Which provider fits which use case

• B2B collections where suppliers or customers pay you from local banks: an account in your customer's name in the payer's country. Lumx names BRL and MXN accounts in the customer's name and activates them right after approval, with COP named for Colombian customers. How the pattern works end to end is in named virtual accounts for B2B collections.

• Marketplaces with sellers in several countries: each seller is its own customer with its own account. Lumx and Bridge both document accounts in all three countries; Lumx keeps each seller's funds in that seller's wallet, and Bridge fits if the platform also wants to issue its own stablecoin.

• Dollar collection from payers abroad, settling to a wallet your customer controls: BlindPay, which publishes $1.50 per month per US account, UnblockPay or Bridge.

• Euro and pound accounts for a European or British payer base: Lumx, Bridge, Due, Conduit or BVNK, each with different naming rules. Lumx's EUR and GBP accounts are named, collect from payers abroad and activate right after approval.

• A Brazil-only business that wants Pix-native checkout or an OTC desk next to the account: Transfero, or Trace Finance for BRL accounts in the company's name.

• A business whose payers in Brazil must see a company name they recognize, and that also pays in Mexico or Colombia: Lumx or Bridge, the two with all three countries in the table. Lumx names the BRL and MXN accounts in the customer's name, while Bridge's guide states the customer's name only for its USD accounts.

When a virtual account is the wrong tool

A virtual account is the wrong tool when a single known counterparty will pay once: a per-payment deposit instruction needs less setup.

It is also the wrong tool when the funds belong to someone you have not onboarded: Lumx's nested payments rules require the written approval of compliance at compliance@lumx.io for a nested structure. See supported countries.

If the payer is in the United States or Europe and the money never touches Latin America, a USD or EUR account from UnblockPay, Due or BVNK is enough.

What the account 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 the accounts it needs in the accounts array of POST /customers, and there is no separate call that creates an account on its own. The deposit details come from an autoconversion rule, which returns a Pix code (brCode) for BRL or a CLABE with a reference for MXN, or from a single on-ramp transaction for one expected deposit. With a rule in place every deposit is converted to stablecoin at the market rate and credited to the customer's wallet; a locked quote is available only on a one-off transaction. Each deposit must be worth at least 50 USD, whatever the rail, and smaller ones are not converted.

Brazilian payers see the customer's name as the holder. In COP, the same flow collects over the customer's Bre-B key or PSE. The accounts and wallets are custodial, one wallet per customer. The Lumx coverage page lists the rails and currencies by country.

Methodology and sources

The list covers Lumx and the ten providers it meets most often in the region, each checked on November 1, 2026 against what it publishes: Bridge's virtual accounts guide, BlindPay's virtual accounts docs and its September 30, 2026 comparison article, UnblockPay's virtual accounts page, Due's virtual accounts docs (updated October 28, 2026), Conduit's multicurrency virtual accounts announcement, the BVNK docs home, the Bloquo OpenAPI spec at docs.bloquo.io, the Trace Finance and Transfero sites, and the Lumx docs pages on accounts and coverage, plus the autoconversion rules guide.

The Avenia site, avenia.io, was read on November 1, 2026 and names Pix and SPEI as rails; its integration guide renders only in a browser, so the account model, the name and Colombia are marked not documented on the pages read. Transfero's docs host did not resolve, so its row combines the site read on November 1 with the Lumx comparison page verified on September 16, 2026. Bre-B's cap is from the Banco de la República's Circular Reglamentaria Externa DSP-465 of August 6, 2026, and the 2026 peso value from its Bre-B page. A cell that says none means the pages read did not document it.

Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.

Cover photo: Tim Wildsmith on Unsplash.