The chain-native mandate primitive: one onchain program (De1egAFMkMWZSN5rYXRj9CAdheBamobVNubTsi9avR44, verified executable and transacting on mainnet-beta on 17 August 2026) that turns an unlimited (u64::MAX) SPL Token delegate approval into three bounded, program-enforced standing authorisations, with lifecycle events emitted onchain via self-CPI — and no dunning, no retries and an expressly disclaimed spend-time grace period, which is the correct answer for a rail rather than a failure of one. Upgrades are governed by a Squads multisig; the upgrade authority is an off-curve PDA, verified independently. Strongest on “If this provider is gone next quarter, do I still get paid — and whose licence is the money moving under today?” (10/10): Solana publishes the program at De1egAFMkMWZSN5rYXRj9CAdheBamobVNubTsi9avR44 and states that the Subscription Authority cannot move funds by itself; a transfer only succeeds when it matches one of the user's active authorizations. The merchant or a listed puller collects with no vendor server in the path. Weakest on “The second charge fails. What does the provider actually do next, and when do I hear about it?” (2/10): Solana documents rejection, not recovery: the program rejects transfers that exceed the current period's remaining allowance, and expiryTs is a hard stop with no spend-time grace period. No retry, overdue state or failure event is published. Published price: No price is published, and that absence is the finding. The Overview (https://
Crypto Subscriptions
Recurring payment rails evaluated on whether the merchant is told when a mandate is revoked, what happens when a renewal fails, whether payments survive the provider, and the exact scope of the permission the customer granted.
Ranked here: crypto subscription rails that let a merchant charge a customer again under a standing mandate, where the risk is the second charge rather than the first. Not ranked here: rails for a single completed payment, prepaid memberships with nothing to revoke, products where money flows the other way, such as bill pay or payouts to workers, and dead or pivoted products.
Show the arithmetic
How this page is reviewed
Reviewed means every product ranked on this page was read against its sources on or after that date; every ranked category is re-read at least every 45 days. Models research, extract and parse. A deterministic engine ranks. Every quote passes an adversarial refute pass.
Accountable for this review: Mathias Siemonsmeier, Founder.
How we review · Review calendar · Corrections log · How we make money
Ranked on 4 published criteria weighted 28/26/24/22, which set goal alignment — 30 of the 86 points. The rest: regional access 20, evidence depth 18 (constant here), ease of use 10 (constant here), institutional trust 8 (constant here). Profile match is shown in breakdowns but carries no weight.
- Custody failure: whoever holds the assets loses or withholds them.Scored by What exactly did my customer sign away, and what stops it from quietly becoming more than that? · 22% (Solana Subscriptions Delegation Program 8/10, Superfluid Money Streaming 6/10, Request Network Recurring Payments 9/10)
- Execution failure: you get a worse price, later, or nothing.Scored by The second charge fails. What does the provider actually do next, and when do I hear about it? · 26% (Solana Subscriptions Delegation Program 2/10, Superfluid Money Streaming 3/10, Request Network Recurring Payments 7/10)
- Exit failure: you cannot get out at par, on time, or with what is yours.Scored by If this provider is gone next quarter, do I still get paid — and whose licence is the money moving under today? · 24% (Solana Subscriptions Delegation Program 10/10, Superfluid Money Streaming 8/10, Request Network Recurring Payments 5/10)
- Information failure: the number is wrong or bought, or your data leaks.Scored by My customer kills the allowance at midnight. Am I told, or do I find out at the next billing run? · 28% (Solana Subscriptions Delegation Program 9/10, Superfluid Money Streaming 8/10, Request Network Recurring Payments 4/10)
What matters most before choosing in this category
Weighted on whether you are told when a mandate is revoked (28), what happens when a renewal fails (26), whether the mandate survives the provider (24), and what the customer actually authorised (22). Everything a payment gateway scores describes ONE COMPLETED PAYMENT; nothing there covers the second charge, a failed renewal, or an allowance revoked without telling you. The revocation ceiling here is 8 and nobody reaches the top band. The pool also splits cleanly and unhelpfully: the protocols that survive their operator are weak at recovering a failed charge, the commercial billers are the reverse, and NOT ONE scores 7 or above on both.
The #1 overall and the scoring weights
How this category is reviewed
Ranked on four questions: My customer kills the allowance at midnight. Am I told, or do I find out at the next billing run? The second charge fails. What does the provider actually do next, and when do I hear about it? If this provider is gone next quarter, do I still get paid — and whose licence is the money moving under today? What exactly did my customer sign away, and what stops it from quietly becoming more than that?