Skip to content
Not a network amendmentTier BUpcoming standardsSpec: Draft

Subscriptions XLS-78

A draft for preauthorized recurring claims of XRP, IOUs, or MPTs with amount and time limits. This is a proposal, not an active network feature. Whether any part of it will launch, and when, remains open.

Sources reviewed Oct 5, 2026 · English page updated Oct 5, 2026 · Phil · CryptoTuts founder

Network status
Not a network amendment
XLS
XLS-78
Spec status
Draft
Spec revision
Sep 10, 2025

What does this XLS propose?

What problem is the proposal intended to solve?

Recurring payments currently require a new sender signature for each payment or an external custodial solution. Services therefore cannot receive a narrowly bounded on-ledger claim authorization.

How is the mechanism designed in the current draft?

SubscriptionSet creates a reserve-requiring Subscription object with SendMax, Frequency, NextClaimTime, and optional Expiration. SubscriptionClaim lets the destination claim a bounded amount using the current trust line TransferRate or MPT TransferFee. Either party can end it through SubscriptionCancel; destination, frequency, and start time are immutable. The draft's single-claim rationale conflicts with its partial-balance state transitions, so repeated claims within one period should not be treated as settled behavior.

How settled is the proposal?

This is a proposal, not an active network feature. Whether any part of it will launch, and when, remains open.

What changes compared with the predecessor?

BeforeAfter
Each recurring payment needed a fresh sender signature or off-ledger automation.A destination could claim XRP or tokens from the sender's account within a preapproved amount and time window.

Who is this change relevant to?

XRP holders and users

Payers retain a periodic ceiling and can cancel at any time. An authorized destination can claim funds without a new individual confirmation.

Wallets and app developers

Wallets must clearly show authorization parameters, the period's remaining balance, the next claim time, arrears, and current token fees.

Exchanges and issuers

Services could collect recurring or variable amounts. Freeze, authorization, MPT locking, and current transfer fees still apply to every claim.

Node operators

Nodes check time windows, the period balance, and asset rules. The first claim can create a trust line or MPToken object if reserve and authorization permit it.

What limitations and risks remain?

  • XLS-78 is a draft, not an active direct-debit mechanism.
  • At most one period is processed per claim. Missed periods can be caught up only through multiple claims, under the draft's state-transition rules.
  • Unused balance from a past period is forfeited when advancing to the next period rather than accumulating indefinitely.
  • Destination, Frequency, and StartTime cannot be updated. Changing them requires canceling and recreating the subscription.
  • There is no direct pause feature.
  • The current TransferRate or TransferFee applies at claim time; it is not fixed when the subscription is created.
  • A service can claim up to the approved ceiling. The ledger does not assess whether a claim is economically justified.

What fee and performance figures does the specification provide?

  • The Subscription object requires an owner reserve from the payer.
  • Automatically created trust lines or MPToken objects may require additional reserve from the destination.
Technical details: transactions, fields, codes and invariants

Transactions

  • SubscriptionSet
  • SubscriptionCancel
  • SubscriptionClaim

Ledger objects

  • Subscription (LedgerEntryType and key space 0x0055)
  • RippleState
  • MPToken

Fields and flags

  • SubscriptionID / Account / Destination / DestinationTag
  • SendMax / Balance
  • Frequency (at least 3,600 seconds)
  • StartTime / NextClaimTime / Expiration

Result codes

  • temDST_IS_SRC / temBAD_AMOUNT / temBAD_EXPIRATION / temBAD_CURRENCY
  • tecNO_DST / tecDST_TAG_NEEDED / tecNO_ENTRY / tecNO_PERMISSION
  • tecNO_ISSUER / tecNO_LINE / tecNO_AUTH
  • tecFROZEN / tecLOCKED / tecWRONG_ASSET
  • tecINSUFFICIENT_FUNDS / tecINSUFFICIENT_RESERVE / tecPRECISION_LOSS / tecTOO_SOON
  • tecOBJECT_NOT_FOUND / tecNO_LINE_INSUF_RESERVE

Invariants

  • Balance must not exceed SendMax.
  • NextClaimTime must not precede StartTime.
  • If present, Expiration must be later than NextClaimTime.
  • Frequency must be positive, and Account and Destination must differ.

What does a concrete workflow look like?

In a hypothetical example, a user authorizes a service to claim up to 50 XRP monthly. A claim of 35 XRP leaves 15 XRP of the period's allowance unused. The draft's partial-balance rules describe that remainder, but its single-claim rationale makes a second claim in the same period ambiguous; unused allowance does not accumulate indefinitely.

How does this proposal relate to others?

Every direct relationship has a type, an explanation and a primary source.

No direct family relationship supported by reliable evidence is recorded for this proposal. The page deliberately avoids showing an assumed connection.

What happens next for this proposal?

This is a proposal, not an active network feature. Whether any part of it will launch, and when, remains open.

The draft needs further technical development and may still change fundamentally or be abandoned. Only a corresponding xrpld (formerly rippled) amendment would trigger a separate network vote.

Where does it sit within its amendment family?

Subscriptions has no amendment family with other members on this site, so there is no progression to show here.

Which primary sources support this information?

← All XRPL amendments and XLS specifications