How to Send a SWIFT Payout From USDC: USD Bank Details

A SWIFT payout from USDC is a US dollar wire funded from a USDC balance. The sender registers the beneficiary's bank details, declares why the money moves, converts the USDC to dollars and sends the wire to a bank account abroad. On Lumx the wire is in USD only and lands in 1 to 5 business days.

What happens between USDC and the beneficiary's bank?

The beneficiary receives an ordinary dollar wire and never touches a stablecoin. The conversion is in what a stablecoin off-ramp is, the asset in what USDC is.

The five stages of a SWIFT payout funded with USDC, who acts at each one, and the Lumx event that reports it.

Lumx treats the off-ramp as complete once funds leave its banking partner, so offramp.success does not mean the beneficiary's bank has credited the account. The tracking section below closes that gap.

On Lumx, the payout debits the custodial wallet of the customer that sends it, in USDC on Ethereum, Polygon or Base. A payout above the balance fails.

Which bank details does the beneficiary need to give you?

More than a domestic transfer needs, because the wire crosses banks that have never seen the account.

The fields of a SWIFT destination in USD, mapped to the Lumx API. All five address parts are required on both the bank and the holder.

Three details are easy to get wrong.

• Country is a three-letter ISO 3166-1 alpha-3 code (BRA, DEU, SGP), not the two-letter code most forms collect.

• The BIC belongs to the bank, not the beneficiary.

• The holder legal name must be the name on the account, and a trade name from the invoice is the usual mismatch.

Address limits to check before you submit a SWIFT destination.

• Street address, line 1 and line 2 together: 70 characters at most.

• City: 35 characters at most.

• State: exactly 2 letters.

• Postal code: 16 alphanumeric characters at most.

• The whole address: 140 characters at most, with no unsupported symbols.

The IBAN is optional. A beneficiary in a country without IBANs sends an account number and the bank's BIC. Which countries can you pay by SWIFT? The Lumx coverage page lists the rail as Global, and the jurisdictions where Lumx onboards customers are on the docs supported countries page.

I would take the beneficiary's details from a document their bank issued, such as a bank letter or the header of a statement, and never from an invoice footer, because the invoice is written by the supplier's accounting team and the letter by the bank that will receive the wire. I would also send a small first payment to any new beneficiary and wait for the supplier to confirm receipt before the invoice amount goes. That adds a day or two once per supplier, and it is cheaper than asking a correspondent bank to recall a wire.

On Lumx, a destination carries a verification status that you read back with GET /destinations, and webhooks report each outcome.

Why SWIFT payouts from USDC run in dollars

On Lumx, SWIFT is a USD rail. The currency on a SWIFT destination is USD, and the pair is USDC to USD. A beneficiary who wants euros or pounds is paid on a different rail, SEPA for euros and Faster Payments (the UK's real-time bank transfer network) for pounds, covered in the last section.

Dollars dominate: SWIFT data cited in the Federal Reserve's FEDS Note of March 30, 2026 puts more than 50 percent of international payments in US dollars. The currencies and rails involved are in what a stablecoin corridor is, and the pair is priced on the USDC to USD page.

On Lumx, USD is supported against USDC on Ethereum, Polygon and Base, and a locked rate for the conversion lasts 30 seconds, 1 minute or 5 minutes. The 30-second lock has no extra fee, and the longer ones include one.

Purpose and relationship: what the banks and compliance read

Two fields do the work an invoice does in a paper wire: the holder relationship says who the beneficiary is to you, and the purpose says why the money moves. Both feed screening and must match your paperwork.

The relationship comes from a closed list: your own account (SELF) or a third party such as a supplier, an employee or a subsidiary. The purpose is a closed list of nine values. A supplier invoice is TRADE_TRANSACTIONS, which the docs define as cross-border payments for goods or services, supplier invoices and import or export settlement. Consulting, legal or accounting fees are PROFESSIONAL_SERVICES, and PERSONAL_ACCOUNT is valid only for a SELF destination.

When the fields do not describe the real payment, the payout can be held. A held payout is a transaction RFI (request for information, a compliance hold that asks for a document). Compliance usually asks about the relationship, the purpose and the expected outcome. Keep the invoice or contract behind each payout within reach.

On Lumx, a transaction RFI is resolved with compliance over email or Slack, and a transaction that gets no answer within 24 hours may be refunded to the sender.

How long does a SWIFT payout take, and what does it cost?

The Lumx coverage page lists international SWIFT at 1 to 5 business days. The cut-off is 3:00 PM ET on US business days, and a request after it, on a weekend or on a bank holiday is processed the next business day. SWIFT follows US federal holidays, per the Federal Reserve's K.8 schedule.

The rule on a real calendar, counting from the day of processing:

A payout sent after the cut-off, November 2026. Veterans Day, November 11, is a Federal Reserve holiday and does not count.

These are processing targets, not commitments. A compliance hold, bank holidays, correspondent banks and the beneficiary's bank holding funds for its own review all stretch them.

On cost, Lumx does not let the customer choose between OUR, SHA and BEN: the wire fee is deducted from the sender. The minimum per SWIFT payout is USD 40. Correspondent banks on the route may still deduct fees in transit, so the credit can be lower than the amount sent, and quote a net figure only after a first payment to that bank has landed. What the three charge codes mean is covered in who pays which wire fee. The Lumx docs do not state a per-wire fee, so this post gives none. Wire against stablecoin on cost and speed is in stablecoins vs SWIFT, and other rails' cut-offs are in payout limits and cut-offs by rail.

On Lumx, pricing is a monthly platform fee plus usage-based per-transaction fees, transparent FX on locked quotes, no capital parked in settlement accounts beforehand; no published plans. The docs say intermediary deductions are outside Lumx's control.

How to track a SWIFT payout with UETR and MT103

Two references matter on a wire. The UETR (unique end-to-end transaction reference) is an identifier that every bank in the chain uses for the same payment, so any of them can trace it. The MT103 is the SWIFT message that carries the customer credit transfer, and its confirmation is the proof that the wire left.

When a supplier says the money has not arrived, the supplier gives the UETR to their bank, which can see where the payment sits. Status events cover the sender's side; the UETR covers the rest.

On Lumx, every SWIFT payout carries UETR and MT103 confirmations, every transfer carries a per-rail reference, and webhooks report each change from offramp.transferring_stablecoin to offramp.success or offramp.failed. On the beneficiary's statement the sender of record is the customer, the legal name registered at KYB (know your business, the verification of a company and its owners) or KYC (know your customer, the verification of an individual).

Why SWIFT payouts from USDC get stuck or rejected

These are the seven causes to check first, and the API names six of them by code. Match on the code, never on the message text.

Failure causes for a SWIFT payout, what you see and the fix.

Limits hit first on a large invoice. Default limits: a business at KYB Standard gets $50,000 per transaction and $100,000 a day and a month, and an individual at KYC Standard gets $7,500 per transaction and $15,000 a day and a month. They are global, whatever the customer's country.

The beneficiary's bank can also return a wire for a name mismatch or a closed account. More failures are in why stablecoin payouts get rejected.

When a SWIFT payout is the wrong rail

SWIFT is the reach option: use it when the beneficiary's country has no local rail you can pay into. A wire gives a 1 to 5 business day range where a local rail gives a number.

Local rails that can replace a wire include Pix (Brazil's instant payment system), SPEI (Mexico's interbank transfer system) and FEDWIRE (the Federal Reserve's same-day wire system).

Where a local rail replaces a SWIFT payout, with settlement times from the Lumx coverage page.

For a US beneficiary, a domestic rail beats a SWIFT wire into a US bank: see USDC to a US bank account. For euros, see USDC to euros over SEPA and the USDC to EUR page. For Brazil, the Pix rail has its own USDC-to-Brazil guide. To map each corridor to a rail, use the migrate SWIFT wires prompt.

On Lumx, the rail is chosen per destination, so a customer that pays suppliers in Brazil over Pix and in Singapore over SWIFT keeps one integration, one balance and one set of webhooks.

What a SWIFT payout looks like 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. SWIFT runs in USD only; the USD, EUR and GBP list applies to POBO and COBO.

The customer is approved first, and Lumx targets one business day for KYB, effective November 2026. USDC sits in the customer's custodial wallet, and the SWIFT rail is enabled by requesting the currency in the accounts array when the customer is created. The platform registers the beneficiary as a destination, then sends the off-ramp with a purpose and an idempotency key so a retry cannot pay twice. Rails and settlement times are on the Lumx coverage page, and the product behind the flow is global payments.

Methodology and sources

Product behavior was read from the Lumx docs on November 1, 2026: coverage, destinations, transactions, exchange rates, payment rail cut-off times, sender of record, purpose codes, transaction limits, Request for Information, webhooks, errors and the OpenAPI specification for the destination fields.

The dollar share is SWIFT data as cited in the Federal Reserve's FEDS Note of March 30, 2026, and the holidays are the Federal Reserve's K.8 schedule, both read on November 1, 2026. The cut-off example is computed from that calendar.

Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.

Cover photo: Franck V. on Unsplash.