Funding a Latin American subsidiary with stablecoins means the parent sends dollars to an account that converts them to USDC, and the USDC is paid out as reais over Pix (Brazil's instant payment system) or pesos over SPEI (Mexico's interbank transfer system) into the subsidiary's bank account. Each transfer is papered as a loan, capital contribution or invoice.
The stablecoin is only the middle leg. The subsidiary never touches crypto, and the paper behind the money decides whether the transfer is clean.
How does a parent fund a Latin American subsidiary with stablecoins?
In four legs. The parent pays dollars into its own USD account, the dollars convert to USDC, the USDC waits in a custodial wallet (what a custodial wallet is), and a payout converts it to local currency and credits the subsidiary's bank account. Each pair of currencies and rails is a corridor (what a stablecoin corridor is).
The four legs of a transfer from a US parent to a subsidiary's local bank account
Leg | What happens | Rail | Settlement |
1. Dollars in | The parent pays its own USD account from its bank | ACH, FEDWIRE or SWIFT (USD) | ACH 1 to 2 business days, FEDWIRE same business day, SWIFT 1 to 5 business days |
2. Convert | The dollars become USDC (USD to USDC) | None | Follows the deposit |
3. Hold | The USDC sits in the parent's custodial wallet until the funding date | None | Until you pay |
4. Pay out | USDC becomes reais or pesos and lands in the subsidiary's bank (USDC to BRL, USDC to MXN) | Pix in Brazil, SPEI in Mexico | Instant on both, 24/7/365 |
In Colombia the last leg runs over Bre-B (the instant payment system), capped at COP 12,110,000 per payment in 2026, or over ACH Colombia for larger sums.
On Lumx, the parent is one customer with a USD account and a custodial wallet. Legs 1 and 2 run as an on-ramp transaction, or as an autoconversion rule that converts every matching deposit on its own, and leg 4 runs as an off-ramp transaction, all behind the same API and webhooks. Rails: global payments; countries on the coverage page.
One customer or two: how to model the group
Both models are valid on Lumx, and every entity that holds an account goes through KYB (know your business, the verification of a company and its owners).
Two ways to model a parent and its subsidiary on Lumx (Lumx docs, treasury management and destinations, read November 1, 2026)
Parent holds everything | Subsidiary is its own customer | |
Who is onboarded | The parent only | Parent and subsidiary |
Where the balance sits | The parent's wallet | Each entity's own wallet |
How the subsidiary is reached | A destination under the parent, with holder relationship SUBSIDIARY_COMPANY | A wallet-to-wallet transfer, then the subsidiary's own off-ramp to its own bank account |
Purpose code on the payout | LOAN for intercompany funding, a loan or a capital injection | The purpose that fits each payment the subsidiary makes; the wallet transfer between the two customers settles in seconds with no FX |
Best when | The subsidiary only needs its account credited | The subsidiary pays its own suppliers or staff |
A payment to a subsidiary is a third-party payment even when the parent owns all of it: the subsidiary is a separate legal entity with its own tax ID, a CNPJ (the Brazilian company taxpayer ID) in Brazil.
On Lumx, a destination for the subsidiary carries its legal name, tax ID and bank details and is verified before the first payout. A subsidiary onboarded as its own customer submits the usual business documents, including the ownership chart showing the parent as shareholder. Lumx targets one business day for KYB, and BRL and MXN accounts turn active once the customer is approved.
What paper sits behind each transfer
Every intercompany transfer needs a reason in writing before it needs a rail: the document tells the subsidiary's accountants how to book the money and is what a tax authority asks for later.
Intercompany flows, the document behind each and the Lumx purpose code that matches (Lumx docs, purpose codes, read November 1, 2026)
Flow | Document behind it | Purpose code | Destination relationship |
Loan to the subsidiary | Loan agreement with rate and repayment terms | LOAN | SUBSIDIARY_COMPANY |
Capital contribution | Board or shareholder resolution | LOAN, which the docs also use for inter-company capital injection | SUBSIDIARY_COMPANY |
Loan repayment back to the parent | Loan agreement and repayment schedule | LOAN | HOLDING_COMPANY |
Lumx maps intercompany funding to LOAN. An invoice for services is a different substance, so confirm the code with Lumx compliance before the first one. Pick the code for the economic substance. A mismatch between purpose and activity can trigger an RFI (request for information, a compliance hold that asks for a document before a transaction clears), and the Lumx docs say to pick the code for substance, not for the rail or the destination type.
On Lumx, a transaction flagged by monitoring is held, and the compliance team contacts the customer by email or Slack for the relationship between sender and receiver, the purpose and the expected outcome. A reply within 24 hours avoids a refund to the sender, so keep the loan agreement or resolution where treasury can send it the same day. RFIs that ask for documents already have webhooks in customer onboarding, while open questions about how the business works still go by email or Slack through operations@lumx.io. An API for transaction RFIs is expected between the end of 2026 and the first quarter of 2027.
What Brazil's foreign-capital rules ask of the subsidiary
Brazilian rules look at what the money is, a loan or an investment, not at the rail. The thresholds below come from BCB Resolution 278 of December 31, 2022, read on the Central Bank's site on November 1, 2026 in its English version updated to December 2024; the Portuguese original prevails.
Reporting triggers for money entering a Brazilian subsidiary (BCB Resolution 278 of December 31, 2022, English version read November 1, 2026)
Loan from the parent (external credit) | Equity from the parent (foreign direct investment) | |
Who reports | The debtor, the subsidiary (Article 17, first item) | The recipient, the subsidiary (Article 17, second item) |
What triggers it | A direct loan of USD 1,000,000 or more (Article 23, first item) | A transfer from the non-resident investor of USD 100,000 or more (Article 32, first item) |
Code on the transfer | SCE-Crédito on every financial transfer of an operation subject to reporting (Article 21, first item) | SCE-IED on transfers of USD 100,000 or more (Article 21, second item) |
If it is missed | Transfers tied to the operation can be barred until corrected (Article 22) | Same (Article 22) |
Whoever reports answers for the legality of the operation and the truth of the declarations (Article 18, paragraph 1) and keeps the supporting documents for ten years (Article 18, first item). That is where the loan agreement and board resolution stop being optional.
The Brazil regulation guide covers Resolution BCB 520 and Resolution BCB 521 of 2025, local entity in Brazil or Mexico whether you need an entity at all, and the Mexico regulation guide the Mexican side.
This section covers Brazil only. Mexican foreign-investment filings, Colombian exchange-regime filings, Brazilian transfer pricing (Law 14.596 of June 14, 2023) and the IOF tax stay with counsel, as does the choice between loan and capital.
Fund the subsidiary, then let it pay its own bills
The Lumx docs test is one question: whose money is it, and whose business does it pay for. A lease in the subsidiary's name paid from the parent's account names an entity other than the account holder, one of the nesting signals, and without written approval of the flow of funds the transaction can be delayed, rejected or reversed.
I recommend onboarding the subsidiary as its own customer before the first transfer, even if the parent could technically hold everything, because the first month is when the subsidiary's bills start and the parent's wallet is the easiest place to pay them from. I would keep the funding transfer and the subsidiary's spending in two separate records, so anyone reading the file sees a loan or a capital contribution going in and an operating company spending it.
The docs accept a customer that moves its own funds between its own accounts and pays its own vendors; a layered structure needs written approval from Lumx compliance first. Paying the subsidiary's vendors from the parent's wallet is allowed once compliance has approved that flow of funds in writing, and a third party can fund an on-ramp when it fits the expected flow of funds.
Moving money back to the parent
A subsidiary eventually sends value home, as a loan repayment or a distribution, and the route runs in reverse. It collects local currency on its BRL or MXN account, an autoconversion rule turns each deposit into USDC, and the USDC goes to the parent as a wallet transfer or a USD off-ramp, with the parent registered as HOLDING_COMPANY.
Brazilian reporting has its own clock on the way out. Under Resolution 278, payments on an external credit are declared in SCE-Crédito within 30 days (Article 31), and Article 36 gives 30 days for investment movements such as distribution of profits and dividends or return of capital when they are not carried out as Article 35 provides. Which article applies is a call for the subsidiary's accountants and counsel, made before the rail.
A BRL account on Lumx is a named virtual account, and a Pix payment into it converts to USDC on arrival.
How much, how fast, what it costs, and what the FX does in between
Lumx caps each customer per transaction, per day and per month by verification level. A business on KYB Standard has a per-transaction limit of $50,000 and a daily and monthly limit of $100,000, in every country. A $300,000 capital contribution is above both the per-transaction and the monthly limit on KYB Standard, so the group requests higher limits from Lumx compliance, which runs the Enhanced KYB review, before the transfer. Lumx targets one business day for that review, and the docs call it a target. A transaction over a limit is rejected before money moves.
The dollars leg sets the clock: ACH takes 1 to 2 business days (2:00 PM ET cut-off), FEDWIRE the same business day (3:00 PM ET cut-off) and SWIFT 1 to 5 business days. Pix and SPEI have no cut-off, so a transfer due on the 5th needs the dollars sent the business day before.
For the rate, a locked quote fixes the conversion for 30 seconds, 1 minute or 5 minutes, with the 30-second lock free and the longer ones carrying a fee. An autoconversion rule always converts at market, so a group that needs an exact local amount uses the per-transaction route. The natural FX hedge guide covers the case where local revenue offsets local costs.
The side-by-side with SWIFT is in stablecoins vs SWIFT.
Who charges what at each leg of a funding transfer (Lumx docs, exchange rates, read November 1, 2026)
Leg | Who charges | What |
Dollars in | The parent's bank | Its own wire or ACH fee |
Conversion | Lumx | Indicative rate: no fee. Locked quote: 30 seconds free, 1 minute and 5 minutes carry a fee |
Pay out | Lumx | Nothing taken from the amount that arrives on a Pix, SPEI or Bre-B payout |
Receiving | The subsidiary's bank | Whatever it charges for incoming credits |
Lumx pricing is a monthly platform fee plus usage-based per-transaction fees, transparent FX on locked quotes, no pre-funding; no published plans.
When funding a subsidiary with stablecoins is the wrong tool
When the group needs a rate fixed for months. A stablecoin route locks a rate for minutes, so a scheduled capital call at a pre-agreed rate belongs with the bank.
When the plan is to pay the subsidiary's suppliers from the parent's wallet without telling compliance. That is nesting, allowed only with the flow of funds approved in writing (compliance@lumx.io).
What this 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.
For a US parent and a Brazilian subsidiary, the order is this. The parent is a business customer with a USD account, active up to one business day after approval. The subsidiary is its own customer with a BRL account, active as soon as it is approved. The parent wires dollars, USDC lands in its wallet, and a transfer moves it to the subsidiary's wallet. The subsidiary then runs a Pix off-ramp to its own bank account, registered with relationship SELF, and offramp.success reports it.
When the parent pays a destination under its own customer instead, the Pix payout shows the parent's legal name as the payer, not Lumx, so the statement line matches the loan agreement.
Each receipt carries the amounts, rate, fees and transaction hash, and the webhooks onramp.success, transfer.success and offramp.success let the file build itself. The corporate treasury guide covers a group's own cash, the KYB explainer what the subsidiary submits, and what USDC is the asset between the legs.
Methodology and sources
Product statements come from the Lumx docs for treasury management, destinations, purpose codes, nested payments, transaction limits, accounts and cut-off times, read on November 1, 2026.
Brazilian reporting rules come from BCB Resolution 278 of December 31, 2022, Articles 17, 18, 21, 22, 23, 31, 32 and 36, in the BCB's English version updated to December 2024, read on November 1, 2026. The Bre-B cap is Circular Reglamentaria Externa DSP-465 of the Banco de la República.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Ries Bosch on Unsplash.
How do you fund a Latin American subsidiary?
The parent sends dollars to a USD account, they convert to USDC, and the USDC is paid out as reais over Pix or pesos over SPEI into the subsidiary's bank account, with a loan agreement, capital resolution or invoice behind each transfer. On Lumx, the parent is a customer with a USD account and a wallet, and the subsidiary is a registered destination or its own customer.
What documents and purpose code does an intercompany transfer need?
The document that says why the money moves: a loan agreement, a capital resolution, a services invoice or an expense statement. In Brazil, a loan of USD 1,000,000 or more and equity transfers of USD 100,000 or more bring reporting duties under BCB Resolution 278. On Lumx, a loan or capital injection uses the purpose code LOAN, and misclassifying the purpose can trigger an RFI or a hold: compliance contacts you by email or Slack, and a reply within 24 hours avoids a refund to the sender.
Can the parent pay the subsidiary's suppliers directly?
It is nesting: the documents name the subsidiary while the payer is the parent. Fund the subsidiary and let it pay its own suppliers. On Lumx, paying another entity's vendors from the parent's wallet is allowed once compliance approves the flow of funds in writing; the cleaner route is to onboard the subsidiary as its own customer.
How fast and how much can a parent send to the subsidiary?
The Pix or SPEI leg is instant, any day; the dollars leg takes 1 to 2 business days by ACH, the same day by Fedwire or 1 to 5 by SWIFT. On Lumx, a business on KYB Standard can move $50,000 per transaction and $100,000 per day and per month, and an amount above that needs a limit increase approved by Lumx compliance before the transfer.
