[

Lumx payouts FAQ

]

Lumx payouts FAQ

How Lumx pays out USDC and USDT to local bank accounts: destinations, quotes, rails, cut-offs, tracking, sender name and what happens when a payout fails.

What is a stablecoin off-ramp?

A stablecoin off-ramp converts stablecoins such as USDC or USDT into local currency and delivers it to a bank account. In Lumx, one off-ramp request debits the customer's wallet (held by the custodian BitGo), converts at the quoted rate, and the banking partner sends the fiat over the destination's rail.

What do I need in place before the first payout?

You need an APPROVED customer, a stablecoin balance in that customer's wallet, and an APPROVED destination for the recipient. Request the payout currency in the accounts array when you create the customer, and pick a purpose code that matches what the money is for. Lumx rejects the payout if the customer is not approved, the destination is not approved or the balance is short.

How do I set up a destination for a recipient?

Register the recipient's bank details with POST /destinations: a Pix key, a CLABE for SPEI, or the details for another rail, plus the holder's data and relationship to your customer, such as SELF, SUPPLIER or EMPLOYEE. The destination fixes the rail and currency, so the payout request does not repeat them. Banking partners screen new destinations for sanctions and check the recipient's name, so a payout waits for the APPROVED status.

Which rails does Lumx pay out on, and how fast?

Lumx pays out over Pix in Brazil, SPEI in Mexico, Bre-B or ACH Colombia in Colombia (you choose when you register the destination), SEPA in Europe, Faster Payments in the UK, and ACH push, Fedwire or SWIFT in USD. Pix, SPEI, Bre-B, SEPA and Faster Payments are instant, ACH Colombia takes one business day, Fedwire the same business day, ACH one to two and SWIFT one to five. These are targets, not guarantees. SWIFT is USD only.

What are the cut-off times for payouts?

Pix, SPEI and Faster Payments run 24/7/365 with no cut-off. SEPA has none either, but payments of EUR 100k or more between 4:30 PM and 2:30 AM UK time route to SEPA Credit Transfer. For USD, the cut-off is 2:00 PM ET for ACH and 3:00 PM ET for Fedwire and SWIFT. Requests after a cut-off, on weekends or on bank holidays are processed the next business day.

How do I get a quote for a payout and lock the FX rate?

Call POST /exchange-rates with type LOCKED, the rail, the currencies and either the stablecoin amount to sell or the fiat amount the recipient must get. The response returns an id and an expiresAt. Pass the id as exchangeRateId on the off-ramp and the payout settles at that rate. Without a quote, the off-ramp converts at a floating rate, and a floating quote is only an estimate.

How long does a locked quote last, and what if it expires?

You choose a lock of 30 seconds, 1 minute or 5 minutes, and the clock starts when the quote is created. Each quote settles one payout. If you submit after expiresAt, Lumx rejects it with EXCHANGE_RATE_EXPIRED and converts nothing, so request a new quote and retry with a new Idempotency-Key. A locked quote fixes the price for that window only. It is not a hedge.

How do I track a payout?

A payout moves through TRANSFERRING_STABLECOIN, TRADING and TRANSFERRING_FIAT to SUCCESS, and each change sends an offramp webhook. Lumx signs every webhook, retries with exponential backoff if your endpoint does not return a 2xx, and GET /transactions/{id} returns the current state if you miss one. The success event carries the receipt with the final amounts, rate, fees and transaction hash.

What happens if a payout fails or is delayed?

A payout that cannot complete ends in FAILED, and Lumx also sends offramp.expired when one expires before completion. A transaction flagged by Lumx monitoring is held for a Request for Information (RFI), and a large one can get extra risk review, typically up to two business hours. Lumx counts the payout as complete when the funds leave its banking partner, and the recipient's bank can still hold them.

What happens if the recipient's bank returns a payout?

The money comes back to your customer. When a recipient's bank sends a completed payout back, Lumx notifies its banking partner and the returned amount is credited to the customer's virtual account, where you can pay it out again to corrected bank details or convert it. Check the destination details before resending, since most returns come from a closed account or a name that does not match.

Whose name appears on the recipient's bank statement?

The recipient sees your customer, using the legal name registered during KYC or KYB, as the sender on Pix, SPEI, ACH, Fedwire, SEPA, Faster Payments and SWIFT. The exception is COP: for a customer that is not Colombian, the recipient sees the banking partner that runs the Colombian leg as the sender.

How do I pay many recipients in one run?

Fund the customer's wallet once, then send one off-ramp request per recipient, each with its own destination and Idempotency-Key. If you lock rates, request one quote per payout. If a request times out, retry with the same Idempotency-Key and Lumx returns the original result instead of paying twice. Lumx publishes a copy-paste prompt for contractor payout runs.

Build your payment infrastructure with Lumx

Create an account to start exploring the platform, or schedule a call to discuss a custom integration for your business.

Start your integration

Begin your integration in minutes, scale as you go.

©2026. All rights reserved.

Lumx US OP LLC ("Lumx") is a financial technology and payments infrastructure company. Lumx US OP LLC is a Money Service Business (MSB) registered with the Financial Crimes Enforcement Network (FinCEN) (MSB #31000316459619). Lumx is not a state-licensed money transmitter and does not, in its own capacity, engage in the provision of regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial-institution partners.


Lumx is not a bank, financial institution, payment institution, or custodian of client funds. Certain services made available through the Platform may be provided by duly authorized and regulated third-party partners, in accordance with applicable laws and regulations.

Please refer to Lumx’s Terms of Use and Privacy Notice for further information regarding the conditions governing the use of the Platform and the processing of your personal data.