Version 1.32 is a SaaS release that introduces the Gas Station Service for automated transaction fee sponsorship and Multi-Purpose Token (MPT) issuer operations, enabling clients to create, manage, and control the full lifecycle of MPTs on the XRP Ledger.
Ripple Custody Version 1.32 introduces the Gas Station Service, a background service that automatically funds transaction fees for sponsored accounts on Ethereum and EVM-compatible chains. This eliminates the need for end-user accounts to hold native tokens (ETH) just to pay gas fees.
When a sponsored account initiates a transaction without sufficient native tokens for fees, the Gas Station:
- Detects the pending transaction
- Estimates the required fee using a dry-run API call
- Transfers the exact amount (plus a safety margin) from the sponsor account
- Allows the original transaction to proceed
This is essential for onboarding users who hold only stablecoins or other tokens, removing friction from end-user transactions.
- Account-level sponsorship — Designate specific accounts to receive automatic fee funding
- Domain-level sponsorship — Fund all accounts within a domain, with optional subdomain inheritance
- EVM chain support — Works with Ethereum and EVM-compatible blockchains (support for Solana and XRPL will be added in the future)
- Low-balance alerts — Configure thresholds to receive notifications when sponsor accounts need refunding
- Just-in-Time (JIT) funding — Transfer exact fee amounts only when needed
- Full audit trail — All sponsorship actions logged through the Ripple Custody intent system
The Gas Station Service uses a dedicated bot user for automated transaction signing. Configure the bot user with auto-approval policies to enable unattended operation.
The Gas Station uses a mechanical funding approach: it detects pending transactions and transfers gas fees from sponsor accounts to sponsored accounts as standard blockchain transactions.
This release does not use native gas abstraction mechanisms such as ERC-4337 Paymasters. Support for native paymaster integration (including EIP-7701 Native Account Abstraction) will be added in the future.
| API Operation | Endpoint |
|---|---|
| Create sponsor configuration | POST /v1/domains/{domainId}/account/{accountId}/sponsor |
| Get sponsor configuration | GET /v1/domains/{domainId}/account/{accountId}/sponsor |
| Update sponsor configuration | PUT /v1/domains/{domainId}/account/{accountId}/sponsor |
| Delete sponsor configuration | DELETE /v1/domains/{domainId}/account/{accountId}/sponsor |
| List gas stations in domain | GET /v1/domains/{domainId}/sponsors |
| Find the gas station sponsoring an account | GET /v1/domains/{domainId}/sponsors/account/{accountId}/sponsor |
| List sponsored accounts | GET /v1/domains/{domainId}/sponsors/sponsored-accounts |
| List sponsored domains | GET /v1/domains/{domainId}/sponsors/sponsored-domains |
| List sponsorable accounts | GET /v1/domains/{domainId}/account/{entityId}/sponsorable-accounts |
| Add sponsored accounts | POST /v1/domains/{domainId}/account/{entityId}/sponsored-accounts |
| List sponsorable domains | GET /v1/domains/{domainId}/account/{entityId}/sponsorable-domains |
| Add sponsored domains | POST /v1/domains/{domainId}/account/{entityId}/sponsored-domains |
| Get audit events | GET /v1/domains/{domainId}/sponsor/events |
For more information, see:
Multi-Purpose Tokens (MPTs) are a new form of fungible token on the XRP Ledger designed for greater efficiency and institutional use cases. Ripple Custody v1.31 introduced holder operations for receiving and transferring MPTs. Version 1.32 expands this to full issuer capabilities, allowing custody clients to create and manage their own token issuances.
| Operation | Description |
|---|---|
| Create issuance | Define new MPT assets with configurable flags for authorization, transfer restrictions, and clawback. |
| Mint tokens | Issue tokens to specific holders. |
| Burn tokens | Reduce supply when tokens are sent to the issuer. |
| Freeze/Unfreeze | Control token transfers at the individual holder or global level for compliance. |
| Clawback | Recover tokens from holders for regulatory compliance or fraud recovery. |
| Authorize holders | Manage holder allowlist for MPTs that require issuer approval. |
| Destroy issuance | Permanently retire an MPT when the supply reaches zero. |
| Escrow | Place tokens in escrow with time-based or conditional release. |
See also:
- Multi-purpose tokens overview — Complete documentation for issuer and holder operations.
- Multi-purpose tokens concepts — Conceptual information about MPTs, lifecycle, and flags.
- Full token lifecycle management — Create, distribute, and retire tokens entirely within Ripple Custody.
- Compliance controls — Use authorization, freeze, and clawback capabilities to meet regulatory requirements.
- Institutional-grade governance — All issuer operations follow Ripple Custody intent-based workflows with policy enforcement and multi-signature approval.
Issuer operations are available via API only in this release. Choose token flags carefully during issuance — most flags cannot be changed after the MPT is created.
Version 1.32 extends the dry-run functionality to support all MPT transaction types. You can now simulate MPT operations before submitting them to the ledger, including:
- Issuance creation and configuration validation
- Token transfers (minting, burning, payments)
- Holder authorization and revocation
- Freeze/unfreeze operations
- Clawback transactions
- Escrow completion
Dry runs validate MPT-specific requirements such as flag settings, holder authorization status, and token balances, helping you catch issues before transactions are broadcast.
Version 1.32 will be progressively deployed across SaaS environments starting Q1 2026.
Ripple takes great care in testing its applications and ensuring that there are no regressions or breaking changes. Should you experience unexpected behavior, reach out to the Support team by creating a ticket on our Support Portal or contact your Customer Partner Engineer (CPE).