What you get back if a stablecoin provider fails is set by which company failed and where your money sat. Stablecoins in a wallet you control are untouched. A balance the provider held for you depends on segregation, the contract and the insolvency regime. Fiat in transit depends on the bank behind the provider.
The answer sits in the contract and the account structure, so read both before the first deposit. This post covers the four failures worth planning for, a real collapse, recovery time, depegs, the rules, ten questions for a provider and the first day after one stops.
Four things can fail, and each costs you something different
A payment passes through the stablecoin issuer, the provider that moves it and the bank that holds the fiat. The fourth failure sits with you.
Four ways a stablecoin flow can fail, what is exposed and what protects you
Who fails | What is exposed | What protects you | The gap |
The stablecoin issuer | Every unit of that stablecoin | For a permitted US issuer, priority on the required reserves (GENIUS Act) | Other issuers, and redemption time |
The payment provider | Balances it holds and payments it is processing | Segregation, the contract, the insolvency law of its country | Balances pooled under terms that give the provider title |
The bank behind it | Fiat in transit or parked before a payout | The bank's regime and the account structure | Delay while a new bank is found |
You | A wallet whose keys you hold | Your own key management | A lost key cannot be recovered |
Stablecoins are not deposits. Section 4(e) of the GENIUS Act, the US statute on payment stablecoins, says they are not subject to FDIC deposit insurance or NCUA share insurance. What stablecoin banking is explains why a provider is not a bank.
Has a payments provider ever failed, and what did its customers get back?
Yes. The closest case with a court record is Synapse Financial Technologies, a banking-as-a-service middleman, not a stablecoin company. We found no stablecoin provider insolvency with a record we could read, so Synapse stands in for the structure that matters: customer money pooled at partner banks, with the provider keeping the ledger.
In May 2024 the partner banks reported about $219 million of Synapse end-user money frozen because the ledgers no longer reconciled. By the Chapter 11 trustee's report of February 6, 2025, the banks had paid the vast majority: AMG National Trust about 99% of $110.3 million, Lineage Bank about 95% of $62.1 million. The trustee also wrote that a shortfall appeared to predate the bankruptcy and that its size and source had not been established.
The money existed at the banks. The failure was the ledger that said whose it was. Customers were still appealing nine months on.
Where is your money at each stage of a payment?
The table maps each stage to the Lumx status that marks it and to who holds the money on Lumx, as the docs describe it. What a failure leaves you depends on the agreement and the partner's regime.
Where the money sits at each stage of an on-ramp and an off-ramp on Lumx, with the status that marks it
Stage | Lumx status | Where the money sits | What a failure leaves you |
Deposit not yet paid | On-ramp | The payer's bank | Nothing at risk. No money has left the payer's bank |
Fiat received, converting |
| The customer's account at the banking partner | Depends on the agreement and the partner's regime |
Stablecoin at rest | Wallet balance after | The customer's own wallet, custodied by BitGo | A segregated balance, never mixed with Lumx's own or other customers'; the contract sets the return sequence |
Payout started | Off-ramp | The stablecoin has left the wallet | A transfer that cannot be recalled |
Fiat sent | Off-ramp | The banking partner | Depends on the agreement and the partner's regime |
Payout complete | Off-ramp | The beneficiary bank | Nothing. The payment is done |
On Lumx the wallets are custodied by BitGo, which carries insurance, and the fiat sits in the banking partner's account. The balance is stablecoin, not a deposit, because Lumx is not a bank.
On Lumx, each transaction type has its own status progression and fires a webhook on each change, and a successful transaction carries a receipt with the amounts, the fees and the blockchain transaction hash. Lumx treats an off-ramp as complete once funds leave its banking partner, so a ledger needs a state for sent and not yet credited.
Segregated, omnibus or owned by the provider: the line that decides what comes back
A provider can give each client its own account or wallet address, which keeps assets identifiable and separate. It can pool clients in an omnibus account with a ledger line each, as strong as the ledger, which is the Synapse structure. Or it can keep one balance and record what it owes, which makes the client an unsecured creditor.
The GENIUS Act draws the line in the same place for the firms it covers: Section 10 requires a custodian to treat a customer's stablecoins as the customer's and keep them separately accounted for, with an omnibus exception at a depository institution or trust company. Its scope is narrow, so ask which regime covers a provider's custody, in writing.
On Lumx, every customer gets a custodial wallet on each supported network, at a real address on the blockchain, enabled once verification is approved, and BitGo custodies them. Segregation is total: they are separate wallets, there is no omnibus account, and a customer's balance is not mixed with other customers' balances or with Lumx's own. Lumx does not allow pooling funds for parties it has not onboarded: each payout debits the customer's own wallet.
What the law protects in the United States and in Brazil
In the United States, the GENIUS Act deals with the issuer and a defined class of custodians. Section 11 puts a holder of a payment stablecoin ahead of the issuer's other creditors for the required reserves, and lets a court lift the automatic stay for redemptions. It applies to a permitted issuer only, and takes effect on the earlier of 18 months after enactment, January 18, 2027, or 120 days after final implementing rules. The GENIUS Act guide covers scope.
In Brazil, the provider is the regulated party. The Central Bank of Brazil (BCB) set the operating rules in Resolution 520 of November 10, 2025, which we read in full. Article 28 requires a provider to keep its own funds apart from clients' funds, in individual accounts in the clients' names. Articles 29 and 30 require client virtual assets in wallets distinct from the provider's own, under a written policy that names the proof-of-reserve method and a biennial independent audit. Article 88 gives companies already operating 270 days to request authorization, held as a PSAV (Prestadora de Serviços de Ativos Virtuais) through an SPSAV (Sociedade Prestadora de Serviços de Ativos Virtuais). The PSAV explainer covers it, and what a VASP is maps the equivalents. How the rules play out in a liquidation is a question for counsel, and we found no readable source.
How long does recovery take, and what if the stablecoin loses its peg?
Recovery runs from minutes to more than nine months, depending on who failed.
Time to recover by failure type, with the source for each
What failed | What the record shows | Source |
Your provider, balance already sent to your own address | Minutes. A transfer you control needs no one's permission | How a blockchain transfer works |
A pooled-account provider (Synapse) | Frozen May 2024, most paid by February 2025, appeals open | Trustee's fifteenth status report |
A permitted US issuer | Best efforts to enter a final order within 14 days of the required hearing on lifting the stay for redemptions | GENIUS Act, Section 11 |
The 14 days are a court target, not a promise to holders. A depeg is the issuer's failure, and the provider cannot fix it. For a permitted US issuer, the Act requires identifiable reserves of at least 1 to 1 (Section 4(a)(1)(A)), a public redemption policy with procedures for timely redemption (Section 4(a)(1)(B)), and a monthly reserve report examined by a registered public accounting firm and certified by the CEO and CFO (Section 4(a)(3)). That is the attestation to ask about. A stablecoin from another issuer follows its own country's law.
On Lumx, the first row is the Transfer endpoint, which sends USDC or USDT from a customer's wallet to any external address. A balance is held in USDC or USDT, so issuer exposure is to those two.
Ten questions to put to a provider before you fund it
I would ask the exit question first: how a client gets its balance out, in what form and on whose action. I would ask it before the licence and before the reserves, because a provider that can describe the way out in two sentences has thought about the day it stops, and one that answers with its uptime has not. I would also size the balance on a provider to the next payout run and not to the month, so the exposure is small by design.
Ten questions about failure, the red flag and how Lumx answers
# | Question | A red flag | On Lumx |
1 | Which legal entity holds my assets, and where? | A brand name only | Lumx US OP LLC in the US, Lumx Sociedade Prestadora de Serviços de Ativos Virtuais Ltda in Brazil |
2 | Who holds title to them? | Title passes to the provider | Separate wallets custodied by BitGo; read the clause in the agreement |
3 | How are balances held? | Nothing stated | A wallet per customer on each supported network, with no omnibus account |
4 | Which regime and licence cover my flow? | A licence list unrelated to your corridors | FinCEN-registered MSB, with regulated activities through licensed partners. In Brazil, the Article 88 transition |
5 | Where is the fiat held, in whose name? | Silence on the bank | A banking partner's account in the customer's name |
6 | What happens to a payout in progress if service stops? | Silence | A status per stage, a webhook on each change |
7 | How do I withdraw? | Withdrawal at the provider's discretion | The Transfer endpoint, to any external address |
8 | Can I read each stage and its proof myself? | One "processing" state | A receipt with the blockchain transaction hash |
9 | What is audited, insured or attested? | A badge with no scope | BitGo, the custodian, is insured; payment stablecoins carry no FDIC or NCUA insurance, by statute |
10 | How long can a compliance hold last? | An open-ended hold | An RFI status that names the information needed |
Title to the balance and its treatment in an insolvency are written in the agreement, so read those two clauses for any provider, Lumx included. The standard Lumx agreement covers the sequence for returning funds on exit, the export of transaction history and addresses, and a liability cap. Choosing a stablecoin infrastructure provider puts them in a full evaluation.
What to do the day a provider stops
Stop new payouts and collections through the provider, with a feature flag.
Revoke the provider's API keys and its access to your systems.
Give payers new deposit details.
Sort every payout in flight by the last recorded stage: not started, stablecoin sent, fiat sent, complete.
Reconcile your ledger against the blockchain, where hashes show what left and when.
Move what you can, starting with stablecoin sent to an address you control.
Tell affected recipients the amount, the date and the plan.
Reroute priority corridors through a second provider, and keep every record for counsel.
Steps 6 and 8 only work if prepared in advance, as how to migrate a payout provider shows. On Lumx, step 6 is the Transfer endpoint. Step 2 is the dashboard, where an API key can be revoked and rotated, and steps 4 and 5 use webhooks.
When a provider balance is the wrong place for your money
Idle treasury carries counterparty risk, so hold it in a wallet whose keys you control, or with a regulated custodian, and leave the provider the operating balance. Custodial against non-custodial wallets for businesses sets out the key-risk tradeoff.
How a payout in flight shows up on Lumx when something stops
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.
If something stops mid-payout, the stage is on the record. A landed on-ramp sits in the customer's custodial wallet, and the client can send it to its own address. The fiat side runs through banking partners: a virtual account is issued by a Lumx banking partner in the customer's name, and the docs say the partners hold the funds and execute the rails. For BRL, the account is named and a Pix (Brazil's instant payment system) payout shows the customer as the payer.
The supported countries page says Lumx US OP LLC is an MSB (money services business) registered with FinCEN and that Lumx is not a bank. In Brazil, Lumx says its Sociedade Prestadora de Serviços de Ativos Virtuais Ltda. has applied for authorization and operates under the Article 88 transition (operator map).
Methodology and sources
We read the enrolled text of the GENIUS Act on congress.gov on November 1, 2026, and took Sections 4, 10, 11 and 20 from it. We read BCB Resolution 520 of November 10, 2025 in full, as a copy of the BCB page hosted by Migalhas, and took Articles 28, 29, 30 and 88. For Synapse, whose figures are the banks' own reports as relayed, we read the Chapter 11 Trustee's Fifteenth Status Report (Doc 485, Case 1:24-bk-10646-MB, Bankr. C.D. Cal.), hosted by the trustee's law firm. We read the Lumx documentation the same day, including wallets, accounts, webhooks and the Transfer endpoint.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Ken Cheung on Unsplash.
What happens if a stablecoin provider fails?
It depends on which company failed and where the money sat. A wallet you control is not affected, a balance the provider held depends on segregation and the contract, and fiat in transit depends on the bank behind it. On Lumx, each customer has its own wallet on each supported network, fiat sits in a banking partner's account in the customer's name, and balances can be sent to an external address.
Has a payments provider failed before, and what did customers get back?
Synapse, a banking-as-a-service middleman, froze about $219 million of customer money in May 2024 when its ledgers stopped reconciling with its partner banks. By February 2025 the banks had paid the vast majority, and some users were still disputing amounts. On Lumx, each stage has its own status and a webhook, and a successful transaction carries the blockchain transaction hash.
How long does it take to get money back, and are balances insured?
A balance already sent to your own address takes minutes, a pooled-account failure like Synapse took months, and for a permitted US issuer a court is asked to enter a final order within 14 days of the hearing. Payment stablecoins carry no FDIC or NCUA insurance under the GENIUS Act. On Lumx, the Transfer endpoint sends USDC or USDT from a customer's wallet to any external address, and fiat accounts are issued by a banking partner in the customer's name.
What happens if the stablecoin issuer fails or loses its peg?
For a permitted US issuer, Section 11 of the GENIUS Act gives holders priority over the issuer's other creditors for the required reserves, and Section 4 requires at least 1 to 1 reserves with a monthly examined report. A stablecoin from another issuer follows its own country's law. On Lumx, a balance is held in USDC or USDT, so issuer exposure is to those two.
