How to send a SWIFT payout from USDC: bank details, address format, and documents

To send a SWIFT payout from USDC, give a payout provider the beneficiary's SWIFT bank details, quote at least 100 USD, fund it with USDC or USDT, and attach an invoice or contract that links you to the recipient. The provider converts the stablecoins and sends a normal SWIFT wire. Most failures come from formatting, not money.

SWIFT is the reach option: it gets dollars to bank accounts in countries no local rail covers. This guide is the mechanics. For where SWIFT sits in a stablecoin flow, see what a stablecoin sandwich is.

Key takeaways

• A SWIFT payout from USDC is an off-ramp: stablecoins in, a USD SWIFT wire out.
• Format matters. Uppercase, no punctuation, an 11-character BIC, and a beneficiary address of 140 characters or fewer.
• Third-party payouts need a transaction document that shows the relationship between sender and recipient.
• The minimum is 100 USD on the requested amount. Expect up to 5 business days to land.
• Put the invoice number first in the description. Only 30 characters reach the beneficiary.

When should you use SWIFT instead of a local rail?

When the recipient's country has no local payout rail you can reach.

Local rails are faster and cheaper where they exist: Pix in Brazil, SPEI in Mexico, ACH Colombia, Transfers 3.0 in Argentina, and SEPA across Europe settle in minutes to about two business days. SWIFT covers the rest, from suppliers in Asia to contractors in Africa. It is also the default for larger B2B invoices in dollars, where the supplier expects a wire. Dollars dominate the network: SWIFT data cited in the Federal Reserve's March 30, 2026 FEDS Note puts more than 50 percent of international payments in US dollars.

The trade-off is time and paperwork. A SWIFT payment can pass through correspondent banks, and each one screens it. Why are cross-border payments slow? breaks down where the days go.

What bank details do you need for a SWIFT payout?

More than for a domestic transfer, and the extra fields are country-specific.

Business beneficiaries also need an industry code (NAICS). The full country lists are in the bank accounts docs. Asking for every field up front saves a second round with your supplier.

How do you format SWIFT details so the payment isn't rejected?

Write like a 1970s telex. SWIFT fields are short and strict.

1. Uppercase plain text only. No commas, periods, or special characters. JPMORGAN CHASE BANK NA SINGAPORE, not J.P. Morgan Chase Bank, N.A., Singapore.
2. Use an 11-character BIC. A BIC has a 4-letter bank code, a 2-letter country code, a 2-character location code, and an optional 3-character branch code. If you only have 8 characters, append XXX to route to the main office: CHASSGSG becomes CHASSGSGXXX.
3. Fit the address in 140 characters. Address lines 1 and 2 share 70 characters. City gets 35. State is exactly 2 characters; repeat the country code if the country has no states. Postal code is up to 16 alphanumeric characters. Country is the ISO two-letter code.
4. Abbreviate long addresses. "Building 12, Zone C, Longhua Science & Technology Industrial Park" becomes BLDG 12 ZONE C LONGHUA SCI-TECH IND PARK.
5. No P.O. boxes unless the receiving bank explicitly allows them.

The SWIFT deliverability guide has worked examples and a pre-submission checklist.

Which documents does a SWIFT payout need?

A document that proves why you are paying this person.

For any payout to a third party, the receiving side wants a transaction document that shows the relationship between the sender and the recipient. Accepted types:

• Invoice
• Purchase order
• Contract
• Delivery slip
• Customs declaration
• Bill of lading
• Other supporting documents

The key word is relationship. An invoice addressed to someone else, or a contract that doesn't name the sender, fails. Payouts to your own account are different: set recipient_relationship to first_party, and no document is needed as long as the beneficiary name matches the customer. First-party vs third-party payouts covers when each applies.

What does the beneficiary see on the payment?

The sender name and a short reference, so make the reference count.

The quote's description maps to MT103 field 70, the remittance information the beneficiary's bank shows as the payment reference. The field accepts 128 characters, but only the first 30 reach the beneficiary. Put the invoice number first: INV-2026-0418 survives, a sentence doesn't.

By default the sender name is the payment provider's. If you pay on behalf of a customer, a named account can show your customer's name instead. POBO vs COBO explains how that works and where it stops.

How do you send the payout, step by step?

Six steps from bank details to a tracked wire.

1. Create the bank account as international_swift with the formatted details and the right recipient_relationship.
2. Quote the payout. The requested amount must be at least 100 USD before fees, or the request fails with swift_minimum_is_100_usd. Pick the network and token you fund from. The quote locks the rate and fees for 5 minutes.
3. Execute before the quote expires, by approving or signing the token transfer from your wallet.
4. Submit the document. The payout starts on_hold with tracking_documents.status set to waiting_documents. Upload the invoice or contract through the document submission endpoint; status moves to compliance_reviewing.
5. Wait for approval. On approval the payout moves to processing and the fiat is sent. On rejection it returns to waiting_documents, and you submit a better document.
6. Track it. Once the wire is confirmed, the payout carries a provider_uetr, the unique end-to-end transaction reference every bank in the chain uses for the same payment.

The SWIFT statuses guide shows the webhook payloads for each stage.

Why do SWIFT payouts get delayed or returned?

Usually one of five reasons.

• A field that breaks the format: punctuation, lowercase, an address over 140 characters.
• A document that doesn't link sender and recipient.
• A missing country field: tax ID, phone number, or payment code.
• A sanctions or screening hit. Banks screen beneficiaries against lists such as OFAC's Specially Designated Nationals list, and a near match stops the payment until it's cleared.
• A beneficiary bank policy. Some banks decline payments not in the invoice party's name, and some countries restrict third-party payments.

Since Swift ended the coexistence of MT and ISO 20022 messages for cross-border instructions on 22 November 2025, payments carry structured data end to end. Clean, structured fields get through screening faster. Stablecoin payout mistakes lists the errors that hit every rail.

How does BlindPay handle SWIFT payouts?

BlindPay sends SWIFT (POBO/COBO) payouts funded with USDC or USDT, through tier 1 banks, with UETR tracking and MT103 confirmations. The international_swift bank account enforces the BIC and address format rules, and a missing SWIFT payment code fails at account creation, so most errors surface before any money moves. Document status shows on every payout response and webhook through tracking_documents. BlindPay operates as a non-custodial payment processor for payout flows from customer-controlled wallets: you authorize the exact amount and BlindPay executes that single transaction. If a payout cannot be delivered after the stablecoins are collected, BlindPay refunds them to the quote's refund wallet, or to the sending wallet when none is set; on Pix and other non-USD local rails the refund is automatic, while USD payouts and payouts whose review times out are refunded after an operator review. Optional BlindPay-managed wallets (beta) are custodial when you choose that path.

What to do next

Pick one supplier you pay by wire today and collect their details in the format above. Create the international_swift bank account on a development instance, quote 100 USD or more, and walk the payout through waiting_documents with a sample invoice. The payout quotes docs show the request.