We manage your security to weather the AI storm →

← Resource Hub

Stablecoin Settlement Risk Framework for Banks and PSPs

By Owen ThurmPublished 7 min read

Part of our guide to stablecoin regulation

Stablecoin Settlement Risk Framework for Banks and PSPs

Quick answer. Cover nine risks: issuer and reserves, legal settlement, chain finality, liquidity and redemption, custody and keys, reconciliation, sanctions, third parties and recovery. For each, record a control, dated evidence, a metric, a warning level, a hard limit, a named owner and who can restart.

Watch: Stablecoin Settlement Risk Framework for Banks and PSPs 1:52
Video transcript

Settling in stablecoins means depending on an issuer, a chain, a custodian and an offramp at once. Each can fail on its own clock.

Cover nine risk areas: issuer and reserves, legal settlement, chain finality, and liquidity and redemption.

Then custody and keys, reconciliation, sanctions, third parties, and recovery.

A webhook is not settlement. In Guardian's Orderly report, a resolved Medium finding, the integration booked the full CCTP burn, though less arrived after Circle's fee.

Holding is not redemption access. For issuers it supervises, the OCC's final rule, effective January 18, 2027, sets a two-business-day outer limit for redemption.

Fill one register row per risk: the scenario, control and evidence date, metric, warning and hard limits, owner, and restart evidence.

No cited source sets a universal threshold. Set your own. Typical triggers: stale reserve evidence, changed redemption terms, price outside your peg band, delayed finality, and a screening outage.

Each trigger must say whether it stops new exposure, changes servicing of accepted obligations, or both. Guardian's Citrea bridge report, a Low acknowledged finding, shows why: a pause during confirmation would make in-flight credits fail.

Restart only with reconciled positions, restored controls, lawful handling of restricted funds, usable funding and recorded approval.

Guardian's Digital Asset Assurance Pilot assesses custody and settlement architecture, audits in-scope contracts and pentests signing services. Read the full framework, or talk to Guardian.

Why Settlement Needs a Framework

A bank or PSP settling in stablecoins depends on an issuer, a chain, a custodian and an offramp at once. Each can fail on its own clock.

The OCC announced its final GENIUS Act rule for issuers under its jurisdiction on October 21, 2026. It takes effect January 18, 2027.[1, 2]

In the EU, DORA has applied since January 17, 2025 to in-scope financial entities.[3]

This article is the operating register for a live program. Coin selection sits in our stablecoin risk assessment template, and pre-integration evidence in our stablecoin due diligence checklist.

Corridor design is in our stablecoin cross-border payments guide, and capital treatment in our Basel crypto standard explainer. Synthetic dollars need checks beyond this fiat-backed template.

Risk Taxonomy

CPMI and IOSCO separate legally irrevocable settlement from ledger state, and warn that probabilistic settlement and forks can misalign the two. The settlement asset's credit and liquidity risk is a separate question.[4]

Their July 2022 guidance targets systemically important arrangements that transfer value. It applies to the arrangement; ask counsel whether any role you play in one brings you into scope.[5]

The FSB's 2023 recommendations to authorities cover governance, risk management, data, recovery, disclosures and redemption rights. They do not bind each firm directly, but map the ground.[6]

Risk areaFailure scenarioPrimary owner
Issuer and reservesReserves impaired, or redemption terms changeTreasury, with Credit Risk and Legal
Legal settlementLedger shows done, obligation not dischargedLegal
Chain and finalityReorg, stalled finality or unapproved routePlatform Engineering; Risk sets policy
Liquidity and redemptionNo fiat by the payout deadlineTreasury
Custody and keysSigner compromise or unauthorized address changeCustody owner and CISO
ReconciliationBooks credit more than arrivedPayments Operations; Finance owns ledgers
SanctionsPayment to a blocked partyDesignated compliance officer
Third partiesCustodian, attester, offramp or bank outageService owner; COO for continuity
RecoveryPause or outage with transfers in flightProgram executive

Controls by Risk Area

Issuer and reserves: keep dated evidence of the issuing entity, reserve composition, custodians, segregation, holder claims and insolvency treatment. An attestation does not prove your redemption route works.

The FSB's October 12, 2026 note says reserves and holders' legal protections may stay at least partly anchored in specific jurisdictions. Where affiliated issuers hold separate reserves, rebalancing them may face frictions in stress.[7, 8]

Chain and finality: allowlist exact contracts, networks and routes, each with a versioned finality assumption. Our finality guide by chain has per-chain values.

Protocol parameters are not block counts. In CCTP V2, threshold 1000 means confirmed and 2000 finalized; Circle's offchain attestation sits between source burn and destination mint.[9]

Liquidity and redemption: holding is not redemption access. Circle's USDC terms outside the EEA, updated October 15, 2026, allow direct redemption through a Circle Mint account in good standing.[10]

MiCA Article 49 requires e-money token issuers to redeem at par, at any time, and bars redemption fees, except recovery-plan measures under Article 46. It governs EU e-money tokens only.[11]

For OCC-supervised issuers, the final rule sets a two-business-day outer limit for redemption. The clock starts when the request is received, the customer is onboarded and other legal conditions to redemption are met.[2, 12]

Redemption counts once the issuer initiates the transfer, not when you hold spendable cash.

Custody and keys: the July 2025 Federal Reserve, FDIC and OCC statement covers key compromise or loss, sub-custodian oversight and independent audit of transfer and settlement controls.[13]

Reconciliation: match each instruction to the amount received, fees, token and chain identifiers, bank statements and customer liabilities. A webhook or source debit alone is not settlement.

Guardian's Orderly Solana Vault report shows the gap (Medium, resolved). The integration booked the full CCTP V2 burn, though less arrived after Circle's fee.[14]

Sanctions: OFAC applies its obligations to virtual currency as it does to fiat. It recommends a risk-based program with risk assessment, internal controls, testing and training.[15]

  • Redemption: test eligibility, minimums, fees, cutoffs, holidays and actual fiat receipt, apart from the legal right.
  • Keys: name who can isolate a signer or suspend an integration; never plan on reversing an onchain transfer.
  • Sanctions: set actions for unresolved matches, screening outages and blocked property; no fallback route may release restricted funds.
  • Third parties: a second vendor sharing your issuer, reserve bank, cloud or rail is not independent resilience.
  • Third parties: record shared dependencies, notice terms, data access, tested alternatives and exit constraints.

Limits and Triggers

Track five exposures apart: own inventory, assets in transit, redemption receivables, prefunded counterparties and payouts advanced before the incoming leg settles, each with its own approval and limit. Reconcile them so nothing counts twice.

A simple measure, per currency and deadline: obligations due minus legally usable funds available by then, floored at zero.

Frozen, encumbered or expected funds do not count.

None of the sources cited here sets a universal safe concentration, confirmation count or depeg threshold for a settlement program. Set your own from exposure and stress analysis, approved by committee.

Each trigger should say whether it stops new exposure, changes how accepted obligations are serviced, or both.

Overrides need a named authority, a written rationale, compensating controls and an expiry. No override can authorize unlawful activity.

  • Reserve evidence past its policy age, or a qualified attestation.
  • Changed redemption terms, fees, minimums or account eligibility.
  • Price outside your approved band around peg.
  • Finality delayed, or node providers disagree on chain state.
  • Pending value in transit above its limit.
  • A custody control failure or unauthorized configuration change.
  • Sanctions screening outage, or a backlog of unresolved matches.
  • Reconciliation breaks aged beyond tolerance.

Owners and Escalation

DORA Article 5 puts ultimate responsibility for ICT risk on the management body. Article 28 keeps the firm responsible when it uses third-party ICT services.[3]

A workable split: the board or a delegated committee approves appetite, the program executive owns delivery, and first-line owners run controls.

Risk and Compliance challenge; Internal Audit gives independent assurance. Name deputies with out-of-hours authority.

The FSB note lists operating-hour constraints among cross-border vulnerabilities, so escalation cannot wait for business hours.[8]

Legal owns whether a payment discharges the obligation.

Payments Operations owns each state: submitted, final, attested, completed, paid out and reconciled, plus blocked and failed branches.

Testing and Restart

Test failures in combination: a bank holiday during a redemption delay, chain disruption after an early payout, a custody outage, or a pause with transfers in flight.

Guardian's Citrea Stablecoin Bridge report shows the last case (Low, acknowledged). A bridge pause during the confirmation window would make in-flight credits fail on arrival, obstructing migration reconciliation.[16]

Keep an in-flight register, and record expected states, funding needs and customer messages for each test.

Restart only with reconciled positions, restored controls, lawful handling of restricted funds, enough usable funding and a recorded approval.

The Risk Framework Template

Fill the header once per program, then one register row per risk. Review rows together with open exceptions and breaks.

  • Legal entity, and whether it acts as issuer or user.
  • Own or customer funds; currencies and jurisdictions served.
  • Exact token contracts, chains, bridges and attesters.
  • Custody model, banks and offramps, with operating hours.
  • The contractual payout point that discharges the obligation.
  • Approved use cases and explicit exclusions.
  • Policy version, approvers and next review date.
Register columnWhat to record
Risk ID and scenarioOne failure: what breaks, and for whom
Affected obligationThe payment or counterparty duty it puts at risk
Inherent riskRating before controls
Control and evidenceThe control, its evidence and the evidence date
MetricDefinition, data source and observation frequency
Warning and hard limitApproved values for this program
Owner and escalationNamed owner, deputy and escalation authority
Breach actionStop new exposure, service accepted obligations, or both
Residual risk and exceptionsRating after controls; expiry for each exception
Restart evidenceWhat must be true, and who signs off

Frequently Asked Questions

When did MiCA's e-money token redemption rules start to apply?

MiCA Titles III and IV, covering asset-referenced and e-money tokens, have applied since June 30, 2024. Article 49 also gives holders a claim against the issuer and requires redemption in funds other than electronic money.[11]

Did the OCC keep its proposed automatic redemption extension?

No. The final rule dropped the proposed automatic seven-day extension. An issuer must instead notify the OCC within 24 hours when redemption requests exceed 10% of a brand's outstanding issuance in a single 24-hour period. It may request an extension, which the OCC expects to grant sparingly.[2, 12]

Can a security audit replace this risk framework?

No. An architecture assessment, smart contract audit or offchain pentest produces control evidence for the register. It does not assess issuer solvency, give a legal opinion, grant authorization or make the institution's risk-acceptance decision.[17]

Sources

  1. Office of the Comptroller of the Currency: OCC Advances U.S. Digital Asset Leadership with Final Rule to Implement GENIUS Act
  2. Office of the Comptroller of the Currency, via GovInfo: Implementing the GENIUS Act for the Issuance of Stablecoins by Entities Subject to OCC Jurisdiction: Final Rule
  3. European Union: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector
  4. CPMI and IOSCO; hosted by Crowdfund Insider: Application of the Principles for Financial Market Infrastructures to stablecoin arrangements: final guidance
  5. CPMI and IOSCO: Application of the Principles for Financial Market Infrastructures to stablecoin arrangements
  6. Financial Stability Board: High-level Recommendations for the Regulation, Supervision and Oversight of Global Stablecoin Arrangements: Final report
  7. Financial Stability Board: Global Stablecoin Arrangements: Cross-border vulnerabilities and financial stability monitoring
  8. Financial Stability Board: Global Stablecoin Arrangements: Cross-border vulnerabilities and financial stability monitoring
  9. Circle: CCTP technical guide
  10. Circle: USDC Terms
  11. European Union: Regulation (EU) 2023/1114 on markets in crypto-assets
  12. Orrick: OCC finalizes GENIUS Act rule for payment stablecoin issuers
  13. Federal Reserve, FDIC and OCC: Crypto-Asset Safekeeping by Banking Organizations
  14. Guardian: Orderly Solana Vault: M-01, CCTPv2 Rebalance Credits Ignore Bridge Fees
  15. U.S. Department of the Treasury, OFAC: Sanctions Compliance Guidance for the Virtual Currency Industry
  16. Guardian: Citrea Stablecoin Bridge: L-03, Pausing _credit During ULN Confirmation Window
  17. Guardian: An assurance pilot for regulated digital asset programs

Test the Controls Behind Your Settlement Register

Guardian's Digital Asset Assurance Pilot assesses custody and settlement architecture, maps controls to MiCA, DORA and GENIUS, audits in-scope contracts and pentests the APIs and signing services behind your program.