Yes: the account is issued in the company's own name by a provider's banking partner, so a foreign company can open a BRL account through an API with no company in Brazil. It creates a business customer that requests the account and passes business verification. Lumx offers this flow to companies incorporated outside Brazil.
Multi-currency accounts without a local entity are BRL, MXN or COP accounts that a provider's banking partners issue to a customer, so it needs no company registered in each country to receive local payments. They do not remove the customer's own tax, employment or licensing duties there. Those belong to the local entity decision and to local counsel. A named virtual account (a local account number issued in the customer's own name) is the account type underneath, and a pooled account is the alternative.
Can a foreign company open a BRL account in its own name through an API?
Yes, through a provider, not through a Brazilian bank directly. A provider replaces the local bank relationship, not the company's legal existence. The account holder is the company itself, verified through KYB (know your business, the verification of a company and its owners) with its own country and tax ID. What KYB is covers the process in general. Two things follow:
The company needs no subsidiary or branch to receive local account details.
Verification takes the place of local paperwork: incorporation documents, owners and directors, and a proof of address.
The direct route is different. Brazilian banks generally want a registered Brazilian company with a CNPJ (Brazil's corporate tax ID) and a legal representative who lives in Brazil. A non-resident account, the conta CDE, exists, but Brazilian accountants describe it as built for investment and foreign-exchange structures, not for routine vendor payments or payroll.
On Lumx, a foreign company holds BRL and MXN accounts without an entity in Brazil or Mexico, and a COP account is available to any customer. Through the API it is one request: a BUSINESS customer with BRL in the accounts array, then KYB. The BRL account is a named one, with agência and conta in the customer's name, and any bank can pay it. The Brazilian entity, Lumx SPSAV Ltda, does not touch foreign currency: money in and out of it is BRL or stablecoin, and the only account it offers is a named one in BRL. The customer of record is the company, with its own country and tax ID, and the supported countries page lists the tiers: Supported, High-Risk (EDD Required) and Restricted.
Which accounts can a foreign company hold in BRL, MXN and COP?
One account per currency, each on the rail of its country. Brazil runs on Pix (Brazil's instant payment system, run by the Central Bank). Mexico runs on SPEI (Mexico's interbank transfer system, run by Banxico), and the payer sends to a CLABE (the 18-digit Mexican bank account number). Colombia collects over Bre-B (Colombia's instant payment system) and PSE (Colombia's online bank-transfer network).
What each account gives the payer, and whose name it carries
Currency | The payer sends to | Rail | Name on the account | Ready after approval |
BRL | The customer's agência and conta, or a Pix code, static or for one amount | Pix | The customer | Right after the customer is approved |
MXN | A CLABE, with a memo carrying the reference | SPEI | The customer | Right after the customer is approved |
COP | The Bre-B key of the COP account, or a PSE payment | Bre-B, PSE | The customer if it is Colombian, the banking partner for every other customer | Right after the customer is approved |
BRL runs over Pix only. The same request can add USD, EUR or GBP accounts too.
The COP row is the one to explain to payers. A COP account is available to any customer, but only a Colombian customer gets a named one. For everyone else the holder the payer sees is the banking partner, so say so in your payment instructions before the first transfer. A payer who sees a bank's name instead of the customer's often stops the transfer to ask finance.
Collections have a ceiling too. The 1,000 UVB cap on Bre-B payouts also applies to a payer's Bre-B transfer into the account, so a larger invoice needs PSE or a smaller transfer.
On Lumx, the currencies go in the accounts array of the customer request, each one enters verification alongside the customer, and the BRL and MXN accounts are active right after approval (per the Lumx docs, read November 1, 2026).
Step by step, from the customer request to the first deposit
The six steps and the signal behind each
Step | What happens | Call or event |
1. Create the customer | Send the company's details and the currencies it needs |
|
2. Accept the terms | The company opens a terms page, which expires after 24 hours |
|
3. Verify the business | Send company details, upload documents, add owners |
|
4. Wait for each account | Each account moves through requested and provisioning to active |
|
5. Share deposit details | A rule or an on-ramp returns the Pix code or the CLABE |
|
6. The deposit lands | Converted and credited to the company's wallet |
|
Verification asks for four documents: the articles of incorporation, the shareholder registry, the directors registry and a proof of address issued in the last 90 days. It also needs at least one associated party in each of three roles: a UBO (ultimate beneficial owner, always an individual, with 25 to 100% ownership), a shareholder and a representative. One person can hold several roles. The company also states its activity, expected volume and source of funds.
Lumx targets one business day for KYB once everything is in. That is a target, not a promise. When compliance needs more, the customer or the account moves to an RFI (request for information, a compliance hold that asks for a document before a transaction clears), and the clock restarts when the answer arrives. A company based in Colombia always goes through enhanced due diligence, so plan for extra documents there.
If you would rather not build the form, share the verification link returned on the customer, and do not mix it with API submission for the same customer.
One account per end customer, never one shared by many
A platform whose users each need local details does not share one account among them. Each user becomes its own customer, with its own verification and its own accounts. Money that belongs to someone the provider has not onboarded is a pass-through.
Launching a dollar account app follows the same rule.
I recommend asking for only the currencies a customer will collect in on day one, and adding the next one when the first payer in that country shows up. Each requested account carries its own status and can stop in an RFI on its own, so three accounts at sign-up are three things for support to explain, and an unused one is still a screen someone has to watch. I would start a customer with the currency of its largest payer, add the others on request, and keep COP for customers who really have Colombian payers, because that is the account where the name the payer sees can differ.
On Lumx, accounts are never pooled: Lumx's nested payments rules require every end customer to be onboarded as its own customer, and a marketplace's sellers each hold their own account, with the platform's cut collected as a partner fee.
Where does the conversion happen, and how does a deposit find its customer?
At the deposit. The local currency lands in the account, converts to a stablecoin, and the stablecoin is credited to the customer's wallet. The balance is USDC or USDT, not reais or pesos, so any local figure next to it is an estimate. For Pix and SPEI, every account belongs to one customer, so attribution is built in, and matching a deposit to an invoice or a payer can run two ways. A COP account collects on the Bre-B key of the account or through PSE.
Two ways to take a deposit, as the Lumx docs describe them
Conversion per deposit | Standing rule | |
Set up | An on-ramp created for the exact amount | An autoconversion rule on the account |
What the payer gets | A Pix code or a CLABE for that amount | One static Pix code, or a CLABE with a memo, reused |
How it is matched | The deposit has to match the on-ramp | The Pix |
A late payment | Refunded to the sender on the same rail | Converts whenever it is paid through the rule |
Fits | A fixed invoice | Recurring or unknown amounts |
A floating on-ramp over Pix or SPEI expires after 1 day. A payment that arrives after that is not processed, and the money goes back to the sender on the same rail, so tell the payer that on the expired screen. Key your own ledger on the customer ID and the transaction ID, and let the events move the status until onramp.success, with onramp.expired and onramp.failed as the exits.
On Lumx, every account converts its deposits the same way, COP included, and a BRL or MXN account can carry several autoconversion rules, one per payer. Each rule picks the target asset and one of Ethereum, Polygon, Base, Tron or Stellar, subject to the pairs on the coverage page.
Who holds the money while it sits in the account
Two layers. The fiat sits in an account at a banking partner until it converts, and afterwards the stablecoin sits in a wallet. On Lumx, the virtual account is issued by a banking partner in the customer's name, and the stablecoin sits in a custodial wallet segregated per customer. Lumx is not a bank. Lumx US OP LLC is a FinCEN-registered Money Services Business, and regulated money transmission runs through licensed financial-institution partners. In Brazil, services are provided by Lumx Sociedade Prestadora de Serviços de Ativos Virtuais Ltda, which filed its SPSAV authorization request with the Central Bank on October 27, 2026, and operates under the Article 88 transition regime of Resolution 520/2025 until the Central Bank decides. If your own product looks like a bank, that is a separate question, covered in neobank licensing in Brazil.
Taking money out of the same accounts
The wallet that collects also pays, converting the stablecoin and sending local currency over the destination's rail. For a EUR account, see paying Latin American suppliers from Europe.
Withdraw by country
Country | Rail | What the destination needs | Corridor |
Brazil | Pix | The recipient's Pix key or bank details | |
Mexico | SPEI | The recipient's CLABE | |
Colombia | Bre-B or ACH Colombia | A Bre-B key, or the holder's details and bank account |
In Colombia the rail is fixed when the destination is registered. A Bre-B payout above 1,000 UVB per operation is refused and not split. The cap comes from section 3.2 of the Banco de la República's Circular Reglamentaria Externa DSP-465 of March 31, 2026, applies to every provider, and is COP 12,110,000 for 2026.
Default limits for a standard KYB customer are a per-transaction limit (see the transaction limits in the Lumx docs) and USD 100,000 per day and per month, and enhanced verification raises them.
On Lumx, no fee comes out of the amount that reaches the recipient on a Pix, SPEI or Bre-B payout, and on a Pix payout the recipient sees the customer as the payer. A company that wants the dollar side of the same wallet can read receiving USD as a Brazilian company.
When this setup is the wrong tool
The company has local employees, issues its own local tax invoices or carries out a regulated activity. Those push a company toward an entity, and an account changes none of them.
Local revenue is large and steady, and local costs are paid from it. Converting twice can cost more than an entity.
Users expect a bank deposit. A stablecoin balance is not one.
Money belongs to people the provider has not onboarded. That is a pass-through, which is refused.
What this looks like on 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 named virtual accounts page describes the account type, and the coverage page lists the live rails.
Run the six steps in the sandbox first, where COP works too and the last digit of the taxId sets the verification result. The sandbox quickstart takes an empty project to a converted deposit without a real bank transfer.
Methodology and sources
Every Lumx statement comes from the docs pages for opening a named BRL account for a business, accounts, customers, global accounts, business verification, identity verification, autoconversion rules, transactions, destinations, transaction limits, nested payments and coverage, read on November 1, 2026, except the named BRL account guide, read on November 18, 2026. The Bre-B cap comes from the Banco de la República circular linked above, and the peso figure from its "Conozca Bre-B" page. What a Brazilian bank asks of a foreign company comes from two public guides, one by an entity-management firm and one by a Brazilian accounting firm, read on November 18, 2026.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Ahmet Yüksek ✪ on Unsplash.
Can a company get multi-currency accounts without a local entity?
Yes, for receiving local payments. A provider's banking partners issue the account details after the company passes verification, so no subsidiary is needed to collect. Tax, employment and licensing duties stay with the company. On Lumx, a foreign company holds BRL and MXN accounts without an entity in Brazil or Mexico, and a COP account is available to any customer.
Whose name does the payer see on a BRL, MXN or COP account?
On BRL and MXN accounts the account is in the customer's own name. A COP account carries the customer's name only when the customer is Colombian, and the banking partner's name for every other customer, so tell payers what to expect. On Lumx, the BRL and MXN accounts are named, and COP follows that rule.
How long does it take to get the accounts?
Verification targets one business day once all documents are in, and an RFI restarts the clock. On Lumx, the BRL, MXN and COP accounts are active right after the customer is approved, and an account.active event says when to show the details.
Can a foreign company open a BRL account in its own name through an API?
Yes. Create a business customer that requests a BRL account, pass KYB, and a banking partner issues the account in the company's own name, with no entity in Brazil. On Lumx, the BRL account is active right after approval and carries agência and conta in the customer's name, so any bank can pay it. Lumx is not a bank, and its Brazilian entity, Lumx SPSAV Ltda, only offers a named account in BRL.
What do multi-currency accounts without a local entity cost?
Expect a fee to issue each account, a recurring fee to keep it open, and a fee to verify the company, plus the conversion and payout fees on money that moves. On Lumx, virtual accounts have issuance and monthly maintenance fees, differentiated for individual vs business, and KYC (know your customer) and KYB verification is a one-time fee per entity. There is no setup fee, and for rates you contact sales.





