Comparisons

Best virtual account providers for Latin America in 2027

Ten virtual account providers for Brazil, Mexico and Colombia, with the 2026 rule changes and 2027 dates that affect the choice, and a pick for each use case.

Caio Barbosa

Founder & CO-CEO

Forbes Under 30. One of the leading voices in Fintech & Crypto in Brazil. Writes weekly about stablecoins, payments, and the future of financial infrastructure in Latin America.

Cover image for Lumx blog article: Best virtual account providers for Latin America (2026)
Cover image for Lumx blog article: 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 transfer domestically and the money lands as a stablecoin balance. In 2027 they differ on three checks: countries covered, whether the account carries your customer's name, and which institution issues it.

Quick answer by need, on documentation read on November 1, 2026 and the dated re-reads in the tables:

  • Local accounts in Brazil, Mexico and Colombia under one API: Lumx and Bridge. Conduit's API reference lists all three, on the collecting institution's name.

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

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

  • No local account in Brazil, Mexico or Colombia: UnblockPay 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.

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.

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. Dated rows come from later re-reads: Trace Finance, Avenia, UnblockPay and Due from September 16 and 17, Conduit from November 10. Transfero's row also leans on the Lumx comparison page of September 16, because its docs host did not resolve.

Provider

Brazil (BRL)

Mexico (MXN)

Colombia (COP)

Name on the account

Lumx

Named account, Pix code (brCode)

Named account, CLABE over SPEI

Bre-B key and PSE; account open to any customer

Customer's name in BRL and MXN; in COP, the customer's name for Colombian customers and the banking partner's name for others

Bridge

Pix code (first-party and third-party business payments only)

CLABE over SPEI

Bre-B key (first-party and third-party business payments only)

USD accounts "issued in your customer's name"; not stated for the others

UnblockPay

None

None

None

USD and EUR only, one account per customer and wallet

Due

Not covered here

SPEI, on an account in Due's own name

Bre-B, on an account in Due's own name

Named EUR, GBP, USD and AED; the local-currency accounts carry Due's name (Sep 17)

Conduit

Pix and TED details in the API reference, on a shared collecting account with a payment reference

CLABE over SPEI in the API reference

ACH Colombia in the API reference; no Bre-B or PSE

USD in the business's own name; BRL and COP show the collecting institution (Nov 10)

BVNK

None

None

None

USD, EUR and GBP accounts

Bloquo

Pix QR deposits; named BRL account marked "coming soon" in its spec

None

None

Named USD, EUR, GBP and BRL all marked "coming soon"

Trace Finance

BRL deposits and withdrawals through accounts in the company's name, over Pix

None

None

Company's own name

Avenia

Static Pix code, no named account

Per-payment CLABE

PSE and Bre-B payment instructions

No named accounts; subaccounts work as a ledger (Sep 16)

Transfero

BRL payment accounts and Pix QR deposits

None

None

Account at a payment institution authorized by the Central Bank

Three providers on the list document local accounts in all three countries: Lumx and Bridge, and Conduit in its API reference. What separates them is the name on the account, as the last column shows. UnblockPay and BVNK document no local account in Brazil, Mexico or Colombia, only USD or EUR ones, which solve collection for a payer abroad and not for a payer in São Paulo.

On who holds the money, Lumx keeps the stablecoin in a custodial wallet per customer. The pages read for the other providers 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, 24/7. Check 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. Lumx's MXN accounts are named in the customer's name, also without a local entity.

In Colombia the rails are Bre-B, with a key, and PSE. 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, which is COP 12,110,000 for 2026 per the central bank's Bre-B page, and the cap applies to every provider. On Lumx, the Colombian peso leg runs on a banking partner's program, so a COP account is open to any customer and is named only when the customer is Colombian; for others the holder shown is the banking partner. Lumx collects over the customer's Bre-B key or PSE.

What changes for virtual accounts in Latin America in 2027?

Dates come from the primary texts: the Central Bank of Brazil's Resolutions BCB 520 and 589, read on November 16, 2026, and the Banco de la República circular cited above.

Date

Rule

What it means when you pick a provider

October 30, 2026

Deadline under Article 88 of Resolution 520 for existing virtual asset providers in Brazil to file for authorization (270 days from February 2, 2026). Those that did not must stop within 30 days.

Ask which Brazilian entity filed, and whether it signs your contract.

November 6, 2026

Article 91, as amended by Resolution 589: banks and payment institutions may not enable virtual asset operations with a provider not authorized in Brazil, except in the forms the resolution expressly allows.

Ask which institution issues the BRL account and which entity is the virtual asset provider.

February 2, 2027

First 365-day stage of Article 89: virtual asset providers in Brazil set up the exchange of originator and beneficiary data between them. The rule binds from February 2, 2028.

Expect more payer and beneficiary questions at onboarding.

2027

The Bre-B cap is 1,000 UVB per transaction, COP 12,110,000 for 2026.

Check the central bank's peso value for 2027 before quoting a limit.

On Lumx, a banking partner issues the BRL account, and Lumx's Brazilian entity runs the stablecoin leg in the Article 88 transition. The regime is explained in Brazil's stablecoin regulation.

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

Provider

Activation after approval

Published price

Lumx

BRL, MXN and COP right after the customer is approved; USD up to one business day

Monthly platform fee plus usage-based per-transaction fees, transparent FX on locked quotes, no pre-funding; no published plans

Bridge

After the customer is approved

Not published on the pages read

The other eight

Not documented on the pages read

Not published on the pages read

Bridge's gate is KYC (an individual check) or KYB (a company check) approval. Fees and documents by rail are 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. An RFI (request for information, a compliance hold that asks for a document) can pause provisioning, 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.

  • Dollar collection from payers abroad, settling to a wallet your customer controls: 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.

  • Payers in Brazil who must see a company name they recognize, with payments also in Mexico or Colombia: 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 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 the minimum deposit in the Lumx docs, whatever the rail, and smaller ones are not converted.

Each named virtual account is issued by a banking partner, one currency per account, and wallets are custodial, one per customer. The Lumx coverage page lists the rails and currencies by country.

Methodology and sources

The list covers Lumx and the nine providers it meets most often in the region, each checked on November 1, 2026 against what it publishes: Bridge's virtual accounts guide, UnblockPay's virtual accounts page, Due's virtual accounts docs, Conduit's announcement, the BVNK docs home, the Bloquo OpenAPI spec, and the Trace Finance and Transfero sites. Where the Lumx comparison pages hold a later re-read (Sep 16 and 17, Nov 10), that row says so. Lumx facts come from the Lumx docs on accounts, coverage and autoconversion rules, read on November 16, 2026.

Avenia's row comes from its integration guide as read on September 16, 2026. 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. 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.

  • What are the best virtual account providers for Latin America in 2027?

    There is no single best provider, because the choice depends on the country and on the name the payer sees. For named local accounts in Brazil, Mexico and Colombia, Lumx and Bridge document all three, with different naming rules; Trace Finance, Transfero and Bloquo cover Brazil only. Lumx issues named accounts in BRL and MXN, and in COP for Colombian customers; other customers get a COP account that shows the banking partner as holder.

  • Whose name does the payer see on a Latin American virtual account?

    It depends on the provider and the currency. A named account shows your customer's name, while a pooled one shows the provider's. Lumx issues BRL and MXN accounts in the customer's name, and in COP the customer's name for Colombian customers and the banking partner's name for others.

  • How long does it take to open a virtual account in Brazil or Mexico?

    The account request is made with the customer, and it moves to active after the customer is approved. On the Lumx docs, BRL and MXN accounts become active immediately after approval, and USD takes up to one business day. Lumx sends an account.active webhook the moment an account can receive funds.

  • What does a virtual account cost in Latin America?

    Most providers do not publish prices. Lumx prices as a monthly platform fee plus usage-based per-transaction fees, with transparent FX on locked quotes and no pre-funding, and it publishes no plans.

  • Can a virtual account receive payments from third parties?

    Usually yes for business payers, with limits that vary by rail. Bridge accepts only first-party and third-party business payments on its Pix and Bre-B accounts. Lumx permits third-party collections (COBO) when they fit the flow of funds expected for the customer, and an unusual payer can trigger a compliance hold. Pooling other parties' funds is nesting, which needs written approval from compliance.

Stay up to date with what Lumx is developing.

Sign up to receive them by email.

Share on socials:

best-virtual-account-providers-latin-america-2026

A

best-virtual-account-providers-latin-america-2026

Best virtual account providers for Latin America in 2027

Copy link

Copied!

best-virtual-account-providers-latin-america-2026

TALK TO OUR TEAM

Ready to transform your business with stablecoins?

Discover how our infrastructure can seamlessly integrate stablecoins into your financial operations quickly, securely, and efficiently.

Comparisons

In this page

©2026. All rights reserved.

Lumx US OP LLC ("Lumx") is a financial technology and payments infrastructure company. Lumx US OP LLC is a Money Service Business (MSB) registered with the Financial Crimes Enforcement Network (FinCEN) (MSB #31000316459619). Lumx is not a state-licensed money transmitter and does not, in its own capacity, engage in the provision of regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial-institution partners.


Lumx is not a bank, financial institution, payment institution, or custodian of client funds. Certain services made available through the Platform may be provided by duly authorized and regulated third-party partners, in accordance with applicable laws and regulations.

Please refer to Lumx’s Terms of Use and Privacy Notice for further information regarding the conditions governing the use of the Platform and the processing of your personal data.