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.
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: 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
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.
Send this before the first payout. Keep it under 150 words.
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 runs 24/7 and is operated by the Banco Central do Brasil, and SPEI 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, and for the region, the Latin America payout cheat sheet.
If you pay contractors from the US, your tax team may also need IRS Form W-8BEN from foreign individuals. Collect it in a separate step so the payment email stays short.
Send it when the payout is created, with the exact amount the recipient will receive.
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.
Say what happened, what you're doing, and when you'll write again.
When the recipient asks why the amount is different from what they expected, the payout amount support playbook walks through the usual causes, and who pays to receive a payout covers bank-side fees.
Paste this block into your help center or the bottom of the announcement.
Use the recipient's language for the announcement and the details request. Short versions of Template 1:
Português (Brasil)
Español (México)
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".
On BlindPay, the recipient is a bank account you add with the fields its rail needs (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). Webhooks such as payout.update and payout.complete can trigger Templates 3 and 4 automatically.
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.
Always cheaper? No intermediaries? Recipient needs a wallet? 10 common claims about cross-border stablecoin payments, checked against the Fed and the BIS.
Seven places blockchain payments beat bank rails: contractor payroll, remittances, B2B suppliers, marketplaces, 24/7 treasury, bill pay, and PSP payouts.
The dates that turned stablecoins from a trading tool into cross-border payment rails: USDC, Pix, MiCA, the GENIUS Act, ISO 20022, and Visa settlement.