Stablecoin depeg risk for payment companies: what past depegs teach and how to set limits

A stablecoin depeg only hurts a payment company while it holds the stablecoin at a floating price. A payout locked by a quote and converted within minutes carries almost no depeg risk. A treasury balance, a pre-funded float, or unconverted customer receivables carry all of it. Set limits on those holdings, not on payments.

This article is general information, not legal or investment advice.

Key takeaways

• Exposure is time multiplied by balance. A payment flow that converts within minutes has a tiny exposure window. Balances held for days have a large one.
• USDC fell to 86 cents in March 2023 when $3.3 billion of reserves were stuck at Silicon Valley Bank, per a Federal Reserve note. It recovered within days.
• Depegs hit on weekends. The issuer's redemption window was shut over the SVB weekend while secondary markets traded around the clock.
• Depegs spread. Stablecoins backed by or linked to USDC fell with it. USDT traded above par as money fled.
• Write the playbook before the event: concentration caps, holding-time limits, price triggers, and a token fallback.

Definition. A stablecoin depeg is a period when a stablecoin trades on the open market away from its target value, usually one US dollar.

Why is depeg risk different for a payment flow than for a treasury?

A payment flow holds a stablecoin for minutes, while a treasury holds it for weeks, so the same price move costs them very different amounts.

Think of exposure as balance multiplied by time held. A payout that locks a rate, pulls the stablecoin, and pays out in local currency is exposed only between the lock and the conversion. A company that keeps a stablecoin float to fund payouts, or lets merchant receivables sit in stablecoins until month-end, is exposed for the whole holding period.

Here is where stablecoin exposure actually sits in a typical payments business:

The design question is simple: which rows can you shrink? The no pre-funding model removes the third row entirely.

What happened in past stablecoin depegs?

Two events show the two main failure types: a fiat-backed stablecoin with a reserve problem, and an algorithmic stablecoin with no real reserve.

USDC, March 2023 (reserve concentration). On March 10, Silicon Valley Bank failed and Circle disclosed that $3.3 billion of USDC reserves, about 8 percent, were held there. The Federal Reserve's December 2025 note on the episode records:

1. USDC hit a low of 86 cents on March 11.
2. Circle suspended primary minting and redemption over the weekend, citing US banking hours.
3. Secondary market trading volume rose to nearly $2 billion an hour on March 11, and decentralized exchange volume far exceeded centralized exchange volume.
4. Stablecoins linked to USDC also fell: DAI through its USDC-backed stability modules, and USDP to 91 cents. USDT traded above par in a flight to safety.
5. The Treasury, the Federal Reserve, and the FDIC said on March 12 that all SVB depositors would have access to their money on March 13. The peg recovered once Circle's primary market reopened that Monday.

UST, May 2022 (algorithmic design). TerraUSD tried to hold its peg through an exchange mechanism with a sister token, LUNA, not through cash reserves. The SEC's complaint states that in May 2022 UST depegged and its price, along with its sister tokens, "plummeted to close to zero." It never recovered.

The lesson for payments teams: a reserve-backed stablecoin can trade at a discount for a weekend and recover. An unbacked one can go to zero. Payment flows should only touch the first kind. USDC vs USDT for payments compares the two largest issuers' track records.

Why do depegs tend to happen on weekends?

A fiat-backed stablecoin's redemption depends on the banking system, which closes on weekends, while blockchains and exchanges keep trading.

That gap is the mechanism. During the week, an arbitrageur who buys USDC at 97 cents can redeem it with the issuer at one dollar, which pulls the price back up. When redemption pauses, that pull disappears, and the secondary market price floats freely until banks reopen. The SVB failure landed on a Friday, and the trough came on Saturday.

For a payment company, this means the riskiest time to hold a stablecoin balance is Friday evening through Monday morning, which is also when local bank rails are thinnest. Plan for both at once.

How do depegs spread between stablecoins?

A depeg spreads through backing and liquidity links: a stablecoin that holds another stablecoin as collateral, or trades mainly against it, inherits its stress.

In March 2023, DAI fell because a large share of its backing was USDC held in stability modules. USDP fell too. Meanwhile USDT rose above one dollar because traders sold USDC for it.

So diversifying across two stablecoins helps only if they don't share reserves, banks, or collateral. Before you count a second token as a hedge, check what backs it.

What controls should a payment company set?

Set limits on holdings, not on payment volume, and decide the rules before an event.

1. Concentration cap per token. Cap the share of any balance held in one stablecoin. If the corridor supports both USDC and USDT, split holdings so one issuer's bad weekend can't take out your float.
2. Holding-time limit. Convert stablecoin receivables to fiat, or into the payout, within a set window. Every extra day held is extra exposure.
3. Price triggers. Watch the market price of each token you hold. Set tiers in advance, for example a warning at 99.5 cents and a stop on new holdings at 99 cents. These numbers are illustrative; set your own from your balance size and risk appetite.
4. Locked quotes only. Execute payouts against a quote that fixes the rate. Never price a payout from a live market feed during an event.
5. Requote discipline. If a quote expires mid-event, the new one may price the token differently. Show the user the new numbers before executing. Stablecoin API quotes explained covers expiry handling.
6. Token fallback. Know in advance which corridors can switch tokens. A payout to Brazil over Pix may work from either token on several chains; some chains carry only one.
7. Redemption access. If you hold large balances, know who can redeem directly with the issuer at par, and whether you can.
8. Customer terms. If customers hold balances through you, state in the contract who bears a depeg loss.

Depeg playbook (the failure modes to plan for)

• Issuer redemption paused for a weekend while markets trade.
• A second stablecoin you count as a hedge falls too, because it is backed by the first.
• A quote expires and the requote prices the token below par.
• A customer sends stablecoins during the event and expects par value.
• Local payout rails are closed, so you can't convert out until Monday.
• Liquidity on your chain of choice thins out and spreads widen.

Which controls fit which use case?

The right controls depend on how long each use case holds stablecoins.

Read the table from the right: the further a use case sits from "minutes," the more of the playbook it needs.

Does regulation reduce depeg risk?

Regulation reduces the reserve-quality risk behind past depegs, but it does not stop market prices from moving during a panic.

The GENIUS Act requires permitted US issuers to hold 1:1 reserves in cash and short-term Treasuries and to publish monthly reserve reports. Its core provisions take effect on January 18, 2027. The GENIUS Act guide has the full timeline. In the EU, MiCA already requires e-money tokens to be fully reserved and redeemable at par.

Better reserves make a 2023-style bank concentration less likely. They don't make a weekend gap between redemption and trading go away. Confirm how any regulation applies to your business with qualified counsel.

How does BlindPay handle depeg exposure?

BlindPay converts USDC and USDT into local currency over Pix, SPEI, ACH, RTP, SEPA, and SWIFT (POBO/COBO), and payouts execute against a quote that locks the rate and fee for 5 minutes. There is no pre-funded balance to hold, so the exposure window in a payout is the minutes between the quote and the execution.

Token support varies by chain: USDT payouts run on Ethereum, Polygon, Solana, Tron, and Tempo, while Base, Arbitrum, Arc, and Stellar carry USDC only. The supported chains reference has the full matrix, which is what you need to plan a token fallback. For the wider map of who holds what in each kind of provider, see types of stablecoin APIs.

What should you do next?

List every place your business holds a stablecoin for longer than a few minutes, and put a size and a time limit on each one. Then write the weekend version of the playbook: who decides, which token you fall back to, and which payouts keep running. Do it this week, not during the next event.