--- title: "How to explain stablecoin payouts to recipients: email and FAQ templates for suppliers and contractors" seoTitle: "Explain stablecoin payouts to recipients: email templates" description: "Copy-ready emails and an FAQ for suppliers and contractors paid over stablecoin rails: what changes, which details to send, and what to say about delays." date: "2026-10-17" updated: "2026-10-17" category: "payments" author: "BlindPay Team" faq: - q: "Do I need to tell recipients that a payout uses stablecoins?" a: "Tell them what changes for them, which is usually very little: they receive local currency in their own bank account. Mentioning that the payment travels as a dollar stablecoin is honest and helps if their bank asks, but the email should lead with the amount, the date, and the account. Avoid crypto terms they would have to look up." - q: "Does the recipient need a crypto wallet to receive a stablecoin payout?" a: "No, when the provider converts the stablecoin and pays out over a local rail. The recipient gives the same details as for any domestic transfer: a Pix key in Brazil, a CLABE in Mexico, a CBU, CVU, or alias in Argentina, or bank account and ID details in Colombia. The money arrives as local currency." - q: "What details should I ask a recipient for?" a: "Ask for the account holder's legal name exactly as the bank has it, plus the identifier for the local rail: a Pix key or bank details in Brazil, an 18-digit CLABE in Mexico, a CBU, CVU, or alias in Argentina, or account number, bank, and ID document in Colombia. In Europe and the UK, ask for the IBAN or sort code and account number." - q: "What should I tell a recipient when a payout is delayed?" a: "Say what happened in plain words, what you are doing about it, and when you will update them next. Common causes are a compliance review, a bank cut-off or holiday, or a detail that doesn't match the bank's records. Never guess an arrival time you can't support. A dated next-update promise calms more people than a vague apology." - q: "Will the recipient pay a fee to receive the payout?" a: "On most local rails the recipient's bank charges nothing to receive, but this depends on the bank and the rail, and international wires can lose fees to intermediary banks. Decide before launch whether you or the recipient covers the payout fees, then state it in the first email so the recipient knows the exact amount to expect." --- Tell recipients three things: they will receive local currency in their own bank account, the details you need from them, and when the money will arrive. The stablecoin is how the payment travels, not what they receive. The templates below cover the announcement, the details request, payment notices, and delays, in English with Portuguese and Spanish versions. Under the hood, these payouts follow the [stablecoin sandwich](/resources/more/what-is-a-stablecoin-sandwich): dollars become a stablecoin, cross the border in minutes, and convert back to local currency at the edge. Your recipients only see the last step. **Key takeaways** - Lead with amount, date, and account. Mention stablecoins once, in plain words, if at all. - The recipient needs no wallet. They give normal local bank details. - Ask for the legal account-holder name exactly as the bank has it. Name mismatches cause most returns. - Decide who covers fees before the first email, and state the expected amount. - Never promise an arrival time the rail can't keep. Promise the next update instead. ## What should you avoid saying to recipients? Avoid words they would need to search for, and claims you can't keep. A supplier in Recife or Guadalajara cares about reais or pesos landing on time, not the network in between. | Instead of | Write | | --- | --- | | "We're paying you in crypto" | "You'll receive Brazilian reais in your bank account" | | "Send us your wallet address" | "Send us your Pix key" (or CLABE, CBU, IBAN) | | "Instant payments" | "Usually within minutes on Pix; we'll confirm when it's sent" | | "No fees" (unless true for every rail) | "You receive [amount]; fees are covered by us" | | "Blockchain transaction hash" | "Payment reference: [ID]" | | "Your funds are on-chain" | "Your payment is on its way" | Keep one honest line about the mechanism for recipients who ask, and for their bank: "We send the payment as USD Coin (USDC), a regulated dollar stablecoin, and our payment provider converts it to local currency." That sentence is true and short. ## Template 1: announcing the change Send this before the first payout. Keep it under 150 words. ```text Subject: How we'll pay you from [month] Hi [name], From [date], we'll pay your invoices through a new payment provider. What changes for you: - You'll receive [currency] directly in your bank account. - Payments usually arrive [within minutes on Pix / within 1 to 2 business days]. - You'll get an email from us each time a payment is sent. What we need from you: the details in the form below, by [date]. Nothing else changes. You don't need a new account or app. If you have questions, reply to this email. [Signature] ``` ## Template 2: asking for bank details Ask only for what the local rail needs, and ask for the legal name first. Here is what each country's rail uses: | Country | Rail | What to ask the recipient for | | --- | --- | --- | | Brazil | Pix | Pix key (CPF, CNPJ, phone, email, or random key), or bank code, branch, account, and CPF or CNPJ | | Mexico | SPEI | 18-digit CLABE and the account holder's name | | Argentina | Transfers 3.0 | CBU, CVU, or alias and the account holder's name | | Colombia | ACH Colombia | Bank, account number and type, ID document type and number, and email | | Eurozone | SEPA | IBAN, BIC, legal name, and address | | United Kingdom | Faster Payments | Sort code, 8-digit account number, legal name, and address | | Other countries | SWIFT | SWIFT/BIC, account number or IBAN, full name, and full address | [Pix](https://www.bcb.gov.br/en/financialstability/pix_en) runs 24/7 and is operated by the Banco Central do Brasil, and [SPEI](https://www.banxico.org.mx/services/interbanking-electronic-payme.html) is operated by Banco de México, so payouts on those rails can land outside banking hours. For the field-by-field detail in Brazil and Mexico, see [what details you need to pay someone in Brazil or Mexico](/resources/more/pix-key-cpf-clabe-payout-details), and for the region, the [Latin America payout cheat sheet](/resources/more/latin-america-payout-cheat-sheet). ```text Subject: Your payment details for [company] Hi [name], Please reply with the following so we can pay you in [currency]: 1. Full legal name of the account holder, exactly as your bank shows it 2. [Pix key | CLABE | CBU, CVU, or alias | IBAN | sort code and account number] 3. [Country-specific: CPF/CNPJ | ID document type and number | address] Please double-check the name. If it doesn't match your bank's records, the payment can be returned and delayed by several days. [Signature] ``` If you pay contractors from the US, your tax team may also need IRS [Form W-8BEN](https://www.irs.gov/forms-pubs/about-form-w-8-ben) from foreign individuals. Collect it in a separate step so the payment email stays short. ## Template 3: payment sent Send it when the payout is created, with the exact amount the recipient will receive. ```text Subject: Payment sent: [currency amount] for invoice [number] Hi [name], We've sent you [currency amount] for invoice [number]. It will arrive in the account ending in [last 4 digits] [usually within minutes / within 1 to 2 business days]. Payment reference: [ID] If it hasn't arrived by [date], reply to this email with the reference. [Signature] ``` Tie this email to a status event in your system, not to a person remembering. Send it when the payout is created, and send a second note if the status turns into a hold or a return. ## Template 4: payment delayed or held Say what happened, what you're doing, and when you'll write again. ```text 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 didn't match the bank's records]. What we're doing: [we've sent the documents requested | it will go out on [date] | please confirm your details below]. We'll update you by [date and time], even if nothing has changed. [Signature] ``` When the recipient asks why the amount is different from what they expected, the [payout amount support playbook](/resources/more/payout-amount-support-playbook) walks through the usual causes, and [who pays to receive a payout](/resources/more/recipient-fees-to-receive-local-payouts) covers bank-side fees. ## Template 5: the recipient FAQ Paste this block into your help center or the bottom of the announcement. ```text Do I need a crypto account or wallet? No. You receive [currency] in your normal bank account. Why did you change how you pay me? Our new provider pays you in [currency] over [Pix | SPEI] and lets us track each payment's status. Will I pay a fee? You receive [amount or "the full invoice amount"]. Your bank may have its own rules; most banks don't charge to receive a [Pix | SPEI] transfer. How do I know a payment was sent? You'll get an email with the amount and a payment reference. What if my bank details change? Email us before your next invoice. For your security, we confirm changes before paying a new account. ``` ## How do you say it in Portuguese and Spanish? Use the recipient's language for the announcement and the details request. Short versions of Template 1: **Português (Brasil)** ```text Assunto: Como vamos pagar você a partir de [mês] Olá [nome], A partir de [data], vamos pagar suas faturas por um novo provedor. O que muda para você: - Você recebe em reais, direto na sua conta, via Pix. - O pagamento costuma chegar em minutos. - Você recebe um e-mail nosso 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. ``` **Español (México)** ```text 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. Lo que cambia para ti: - Recibes pesos mexicanos directamente en tu cuenta, por SPEI. - El pago suele llegar en minutos. - Te enviaremos un correo cada vez que enviemos un pago. 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. ``` For Argentina, swap "CLABE de 18 dígitos" for "CBU, CVU o alias" and "pesos mexicanos" for "pesos argentinos". For Colombia, ask for "banco, número y tipo de cuenta, y tipo y número de documento". ## How does BlindPay handle the recipient side? On BlindPay, the recipient is a bank account you add with the fields its rail needs ([bank accounts](/docs/bank-accounts)), and the payout pays it in local currency over Pix, PIX Safe, TED, SPEI, Transfers 3.0, ACH Colombia, ACH, RTP, SEPA, Faster Payments, or SWIFT (POBO/COBO) with UETR tracking and MT103 confirmations. The quote shows the exact amount the recipient receives before you execute, and the `cover_fees` setting decides whether you or the recipient bears the payout fees ([payout quotes](/docs/payout-quotes)). Webhooks such as `payout.update` and `payout.complete` can trigger Templates 3 and 4 automatically. ## What to do next Pick your top corridor, translate Template 1 and Template 2 into the recipients' language, and send them two weeks before the first payout. Collect the details, then send one small payout to each new account before the full run.