Quellengeprüfte Recherche: Payment Stablecoin Margin Collateral
Der Artikeltext wird im geprüften englischen Original angezeigt. Die Übersetzung folgt nach der Quellenprüfung.
Direct answer
CFTC Staff Letter 26-05 reissued prior no-action relief with a limited revision that can include a national trust bank as a permitted payment-stablecoin issuer for the specified margin-collateral framework. That is conditional staff relief, not universal approval of every stablecoin or account. A decision-ready review must still confirm the exact issuer, redemption claim, reserve evidence, FCM acceptance, segregation, custody, valuation haircut, concentration limit and liquidation process.
Weniger anzeigen
Verified source facts
1. CFTC Staff Letter 26-05 was issued on February 6, 2026. 2. The letter reissues prior relief with a limited revision to the payment-stablecoin issuer definition. 3. The revision specifies that a national trust bank may be a permitted issuer for purposes of that no-action position. 4. CFTC staff FAQs provide additional guidance on digital assets accepted as margin collateral.
Comparison at a glance
Artikeltabelle: horizontal scrollen oder den Tabellenbereich fokussieren und die Pfeiltasten verwenden.
| Decision layer | What to inspect | Minimum safe action |
|---|---|---|
| Document scope | conditional no-action position | read conditions |
| Issuer | named legal entity | verify eligibility |
| Claim | redemption right | read terms |
| Reserves | composition and evidence | retain reports |
| FCM acceptance | specific intermediary policy | confirm account |
| Segregation | customer asset treatment | trace books |
| Custody | wallet and keys | map chain |
| Haircut | discounted value | stress parameter |
| Concentration | issuer and asset cap | set limits |
| Liquidation | sale or redemption path | test readiness |
1. Rights analysis: Document scope
Tokenization analysis must follow the legal and operational chain, not the visual token. The document scope question asks about conditional no-action position. Identify the issuer, tokenization sponsor, recordkeeper, custodian, broker or platform, and every agreement connecting them. Then read conditions. A wallet balance alone cannot answer which person or system has the enforceable obligation.
Test the arrangement under a disagreement. If the chain record and master securityholder file diverge, which one controls? If an intermediary fails, is the holder a customer, beneficial owner, secured claimant, or unsecured creditor? If a transfer is technically possible but legally restricted, what process reverses or freezes it? The available sources frame these questions, while blanket-approval error remains outside the evidence set.
Turn the document scope finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Read conditions before comparing yield, speed, or interface quality. Because blanket-approval error is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
2. Rights analysis: Issuer
The issuer question asks about named legal entity. Then verify eligibility.
The available sources frame these questions, while affiliate confusion remains outside the evidence set.
Turn the issuer finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Verify eligibility before comparing yield, speed, or interface quality. Because affiliate confusion is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
3. Rights analysis: Claim
The claim question asks about redemption right. Then read terms.
The available sources frame these questions, while weak claim remains outside the evidence set.
Turn the claim finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Read terms before comparing yield, speed, or interface quality. Because weak claim is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
4. Rights analysis: Reserves
The reserves question asks about composition and evidence. Then retain reports.
The available sources frame these questions, while timing gap remains outside the evidence set.
Turn the reserves finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Retain reports before comparing yield, speed, or interface quality. Because timing gap is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
5. Rights analysis: FCM acceptance
The fcm acceptance question asks about specific intermediary policy. Then confirm account.
The available sources frame these questions, while unsupported asset remains outside the evidence set.
Turn the fcm acceptance finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Confirm account before comparing yield, speed, or interface quality. Because unsupported asset is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
6. Rights analysis: Segregation
The segregation question asks about customer asset treatment. Then trace books.
The available sources frame these questions, while commingling remains outside the evidence set.
Turn the segregation finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Trace books before comparing yield, speed, or interface quality. Because commingling is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
7. Rights analysis: Custody
The custody question asks about wallet and keys. Then map chain.
The available sources frame these questions, while operational loss remains outside the evidence set.
Turn the custody finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Map chain before comparing yield, speed, or interface quality. Because operational loss is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
8. Rights analysis: Haircut
The haircut question asks about discounted value. Then stress parameter.
The available sources frame these questions, while depeg remains outside the evidence set.
Turn the haircut finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Stress parameter before comparing yield, speed, or interface quality. Because depeg is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
9. Rights analysis: Concentration
The concentration question asks about issuer and asset cap. Then set limits.
The available sources frame these questions, while correlated failure remains outside the evidence set.
Turn the concentration finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Set limits before comparing yield, speed, or interface quality. Because correlated failure is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
10. Rights analysis: Liquidation
The liquidation question asks about sale or redemption path. Then test readiness.
The available sources frame these questions, while market stress remains outside the evidence set.
Turn the liquidation finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Test readiness before comparing yield, speed, or interface quality. Because market stress is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
Decision scenarios
Scenario 1: when document scope becomes decisive
Consider a reader whose main constraint is conditional no-action position. The correct response is not to infer a universal platform or product winner. It is to read conditions, retain the evidence, and define a stop condition before funds or permissions are committed. If the evidence changes, the decision must be reopened. This produces a repeatable operating rule rather than a one-time opinion.
Scenario 2: when issuer becomes decisive
Consider a reader whose main constraint is named legal entity. It is to verify eligibility, retain the evidence, and define a stop condition before funds or permissions are committed.
Scenario 3: when claim becomes decisive
Consider a reader whose main constraint is redemption right. It is to read terms, retain the evidence, and define a stop condition before funds or permissions are committed.
Scenario 4: when reserves becomes decisive
Consider a reader whose main constraint is composition and evidence. It is to retain reports, retain the evidence, and define a stop condition before funds or permissions are committed.
Scenario 5: when fcm acceptance becomes decisive
Consider a reader whose main constraint is specific intermediary policy. It is to confirm account, retain the evidence, and define a stop condition before funds or permissions are committed.
Scenario 6: when segregation becomes decisive
Consider a reader whose main constraint is customer asset treatment. It is to trace books, retain the evidence, and define a stop condition before funds or permissions are committed.