Explaining a stablecoin payout to a recipient means telling them three things: they receive local currency, it lands in their own bank account, and it arrives on a stated date. The stablecoin is only how the payment travels, so it gets one plain sentence if they ask. The rest covers the details you need and your next update.
This post gives you four email templates, a table of what to ask for on each rail, and the announcement in Portuguese and Spanish. The rails it covers are Pix (Brazil's instant payment system, run by the Central Bank), SPEI (Mexico's interbank transfer system, run by Banxico) and Bre-B (Colombia's instant payment system), plus the CLABE (the 18-digit Mexican bank account number) that SPEI needs. It is written for the company doing the paying, writing to its own suppliers and contractors. If you still need to set up the payments, start with paying LATAM contractors in stablecoins.
What should you tell a recipient, and what should you leave out?
Tell them the amount, the currency, the account and the date. Leave out anything they would have to search for. A supplier in Recife or Guadalajara cares about reais or pesos landing on the day you named, and has no use for the network in between. The table swaps the phrases that cause questions for ones that do not.
Phrases that generate replies from recipients, and the wording that answers the question before it is asked.
Instead of | Write |
"We are paying you in crypto" | "You will receive Brazilian reais in your bank account" |
"Send us your wallet address" | "Send us your Pix key" (or your CLABE, IBAN or account number) |
"Instant payments" | "Usually within minutes on Pix. We will confirm when it is sent" |
"No fees" | "You receive the full invoice amount" (only if that is true on the rail) |
"Here is the transaction hash" | "Payment reference: [ID]" |
"Your funds are on the blockchain" | "Your payment is on its way" |
Keep one honest sentence for recipients who ask, and for their bank: "We send the payment as USDC, a dollar stablecoin, and our payment provider converts it to local currency." It is true and short. For more, see what USDC is.
On Lumx the recipient never touches the stablecoin. Your company funds a wallet, the off-ramp converts the balance and the money arrives as local currency in a bank account the recipient registered, so the message above is also an accurate description of the product. Pix payouts carry your company's name as the payer, not Lumx's, so the transfer shows up under a name the recipient knows.
Template 1: announce the change before the first payout
Send this two weeks before the first payment.
> Subject: How we will pay you from [month] > > Hi [name], > > From [date], we will pay your invoices through a new payment provider. > > What changes for you: > - You will receive [currency] directly in your bank account. > - Payments usually arrive [within minutes on Pix | within 1 to 2 business days]. > - You will get an email from us each time a payment is sent. > > What we need from you: the details in the next email, by [date]. You do not need a new account or an app. Reply to this email with any question. > > [Signature]
Protect the line "you do not need a new account or an app": most worry in a first announcement is the fear of opening something, and one sentence removes it.
What details does the recipient need to send, rail by rail?
Ask for the legal name of the account holder first, exactly as the bank spells it, and then the identifier the local rail uses. Name mismatches are the most common cause of a returned payment, which is why the template below says so in plain words. The table lists what to request, plus the published timing so you can fill the "when" line honestly.
What to ask each recipient for, by destination rail, with the settlement target Lumx publishes.
Destination | Rail | Ask the recipient for | Settlement target and cut-off |
Brazil | Pix | Pix key (CPF or CNPJ, phone, email or random key), legal name, CPF or CNPJ, email, address | Instant, 24/7, no cut-off |
Mexico | SPEI | CLABE, legal name, tax ID, email, address | Instant, 24/7, no cut-off |
Colombia | Bre-B or ACH Colombia | Bre-B key, or bank, account number and type, ID type and number, email | Bre-B is an instant rail; no settlement time published for ACH Colombia |
United States | ACH or FEDWIRE | Routing number, account number and type, bank name and address, legal name | ACH: 1 to 2 business days, 2:00 PM ET cut-off. FEDWIRE: same business day, 3:00 PM ET cut-off |
Eurozone | SEPA | IBAN, BIC, legal name, address | Instant, or same or next business day for SEPA Credit Transfer |
United Kingdom | Faster Payments | Account details, legal name, address | Instant, up to £1M per payment |
Elsewhere | SWIFT in USD | SWIFT/BIC, account number or IBAN, legal name, address | 1 to 5 business days, 3:00 PM ET cut-off |
The settlement column is a target, not a promise. Lumx's cut-off page says the timelines are processing targets, and that the receiving bank can hold funds for its own review. Write "usually" in your email, not "will".
On Lumx, each recipient becomes a destination under your customer record: the rail, the identifier and a holder block with name, tax ID and contact details (a birth date is optional for an individual), plus a holder relationship such as SUPPLIER or EMPLOYEE. That is why the request below asks for more than a key and a name. A destination must be approved before any payout can run. The check includes sanctions screening and a name check by the banking partners, and the SELF check covers the name. Collect the full set once and reuse the destination on every payout. The Pix guide shows the Brazilian version field by field, and cut-offs by rail covers the deadlines.
Template 2: ask for the account details
> Subject: Your payment details for [company] > > Hi [name], > > To pay you in [currency], please reply with: > > 1. The full legal name of the account holder, exactly as your bank shows it > 2. [Pix key | CLABE | Bre-B key | IBAN | account and routing number] > 3. [Tax ID | ID document type and number] and your email and address > > Please check the name twice. If it does not match your bank's records, the payment can be returned and delayed. > > [Signature]
Send one small payout to each new account before the first full run. The recipient confirms receipt, and any error in the details surfaces on a payment that costs little to repeat.
Templates 3 and 4: payment sent, payment delayed
Tie both emails to a status event, not to someone remembering. The sent notice goes out when the payout is created, with the exact amount the recipient will see.
> Subject: Payment sent: [currency amount] for invoice [number] > > Hi [name], > > We sent you [currency amount] for invoice [number]. It should arrive in the account ending in [last 4 digits] [usually within minutes | within 1 to 2 business days]. > > Payment reference: [ID] > > If it has not arrived by [date], reply to this email with the reference. > > [Signature]
The delay notice follows one structure: what happened, what you are doing, and when you will write again.
> Subject: Update on your payment for invoice [number] > > Hi [name], > > Your payment of [currency amount] is taking longer than usual. > > Reason: [a routine compliance review | a bank holiday in [country] | the account name did not match your bank's records] > > What we are doing: [we sent the documents requested | it will go out on [date] | please confirm your details below] > > We will update you by [date and time], even if nothing has changed. > > [Signature]
Promise the next update, not an arrival time. If the recipient asks why the amount differs from the invoice, do not guess. For the status each rail reports at each step, see payout statuses and tracking by rail.
On Lumx, an off-ramp moves through transferring stablecoin, trading and transferring fiat before it ends in success or failed, and each step fires a webhook your system can turn into an email. Success means the funds left Lumx's banking partner, so the receiving bank can still be the party holding a payment. A payout flagged by monitoring is held as an RFI (request for information, a compliance hold that asks for a document before a transaction clears), which is the "routine compliance review" in the template. Lumx does not send anything to your recipients: the notices are yours.
Who pays the fee to receive a payout?
Decide before the first email who covers the fees, and state the expected amount. On Pix, SPEI and Bre-B, Lumx does not deduct a fee from the amount that reaches the recipient. Only the recipient's own bank can charge them, so check what that bank charges before you promise "you receive the full invoice amount".
SWIFT is the exception. An international wire can cross correspondent banks, and each can deduct a fee outside anyone's control, so a USD payment needs different wording: "the invoice amount, less any fees your bank or intermediary banks deduct".
How do you say it in Portuguese and Spanish?
Send the announcement and the details request in the recipient's language. Below is the short version of Template 1 for the three corridors where Lumx pays out in local currency from USDC. USDC to BRL, USDC to MXN and USDC to COP have the corridor details.
Portuguese (Brazil), over Pix.
> Assunto: Como vamos pagar você a partir de [mês] > > Olá [nome], > > A partir de [data], vamos pagar suas faturas por um novo provedor. Você recebe em reais, direto na sua conta, via Pix. O pagamento costuma chegar em minutos, e você recebe um e-mail a cada pagamento enviado. > > Precisamos da sua chave Pix e do nome completo do titular da conta, exatamente como aparece no seu banco, até [data]. Você não precisa abrir conta nova nem instalar nenhum app.
Spanish (Mexico), over SPEI.
> Asunto: Cómo te pagaremos a partir de [mes] > > Hola [nombre], > > A partir del [fecha], pagaremos tus facturas a través de un nuevo proveedor. Recibes pesos mexicanos directamente en tu cuenta, por SPEI. El pago suele llegar en minutos y recibirás un correo con cada pago enviado. > > Necesitamos tu CLABE de 18 dígitos y el nombre completo del titular, tal como aparece en tu banco, antes del [fecha]. No necesitas abrir una cuenta nueva ni instalar ninguna app.
Spanish (Colombia), over Bre-B or ACH Colombia.
> Asunto: Cómo te pagaremos a partir de [mes] > > Hola [nombre], > > A partir del [fecha], pagaremos tus facturas a través de un nuevo proveedor. Recibes pesos colombianos directamente en tu cuenta bancaria. Recibirás un correo con cada pago enviado. > > Necesitamos el nombre completo del titular, tal como aparece en tu banco, y tu llave Bre-B. Si prefieres transferencia bancaria, envíanos banco, número y tipo de cuenta, y tipo y número de documento, antes del [fecha]. No necesitas abrir una cuenta nueva ni instalar ninguna app.
In Colombia the rail is fixed when the destination is registered: a destination registered for Bre-B pays over Bre-B, and one registered for ACH Colombia pays over ACH Colombia. Lumx will not move a payment to the other rail. Bre-B also caps a single payment at 1,000 UVB, about COP 12.1 million in 2026, so an invoice above that needs a destination registered for ACH Colombia, and the recipient should be asked for bank details up front.
I would not send the first full payment to any new recipient. I would send a small test payout first, tell the recipient it is a test, and wait for them to confirm it arrived before the real run. If the amount comes in short, why a recipient gets less has the causes. The recipient who confirms a test amount has also checked their own account details, and that confirmation is the last proof that the name and the key match, after the checks the platform runs. A rejected test of a few reais costs a reply email. A rejected invoice run costs a supplier cash flow.
When explaining stablecoins to a recipient is the wrong move
A template is the wrong tool in three cases. If the recipient's bank, accountant or tax authority asks how the money arrived, answer plainly and name the stablecoin: hiding the mechanism from someone who asked is worse than naming it. If you are changing payment terms, dates or currency, the contract is the document, and the email only announces it. And if a recipient lives somewhere stablecoin services are restricted, such as mainland China, pay in USD over SWIFT and do not mention stablecoins at all.
What a payout looks like to the recipient 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.
In practice the recipient sees three things. A local-currency credit in their own account, a payer name they recognize, and whatever reference their bank shows on the transfer. They do not see a wallet, a network or a token. The company that runs the payout is yours, and Lumx is not a bank and does not appear in the message you write: Lumx handles compliance and conversion inside the API, and your communication stays yours. A foreign company can hold a named account in BRL and MXN without a legal entity in Brazil or Mexico.
For where payouts land, see what a stablecoin corridor is, what an off-ramp does and the coverage page. The wider product is on global payments. For the sender side in Brazil, see paying contractors in Brazil.
Methodology and sources
Rail timings, cut-offs and destination fields were read on docs.lumx.io on November 1, 2026: Coverage, Payment rail cut-off times, Destinations, Payroll, Wallets, Transactions, Webhooks and Request for Information. The Colombian Bre-B limit is from Banco de la República's Circular Reglamentaria Externa DSP-465, Asunto 18, numeral 3.2, sheet of March 31, 2026, quoted by name and number because the page was not fetched for this post. The template wording is ours.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Haim Charbit on Unsplash.
How do you explain stablecoin payouts to recipients?
Tell them what changes for them, which is usually very little: they receive local currency in their own bank account, on a stated date. Mention the stablecoin once, in one plain sentence, only if asked. On Lumx the recipient is paid by an off-ramp in local currency, so the email can say reais, pesos or euros and nothing else about the mechanism.
What does a recipient need to receive a stablecoin payout?
A normal bank account and the details the local rail asks for, such as a Pix key in Brazil, a CLABE in Mexico or a Bre-B key in Colombia. No wallet and no crypto account. On Lumx, the payer registers those details as a destination with the holder's name, tax ID and contact details, and the recipient never handles the stablecoin.
Will the recipient see who sent the payment?
Yes, they see a payer name. On Lumx, a payout over Pix shows your company as the payer, not Lumx, and SPEI payouts also go out in your company's name. A COP payout from a non-Colombian customer shows the banking partner as sender. Tell recipients the name to expect so a transfer from an unfamiliar sender does not look like a scam.
What should I promise about when the money arrives?
Say "usually" and give the rail's typical timing, then promise the next update instead of an arrival time. Pix and SPEI run around the clock, while ACH and SWIFT follow business days and cut-offs. On Lumx, timelines are processing targets and not guarantees, and a payout held for an RFI waits for a document before it continues.
Does the recipient pay a fee to receive the payout?
The recipient's bank decides whether to charge for receiving. On Lumx, no fee is deducted from the amount that reaches the recipient on Pix, SPEI or Bre-B, and only the recipient's own bank can charge them. A USD payment over SWIFT can lose fees to intermediary banks, so state the expected amount in the first email.
