Quick answer: A Multi-Purpose Token (MPT) is a fungible token standard on the XRP Ledger, defined in XLS-33 and enabled by the MPTokensV1 amendment that activated in October 2025. MPTs carry on-chain metadata and compliance controls (allow-listing, transfer limits, locking, clawback) at the protocol level, so issuers set rules in the token itself rather than in a separate custom contract. Complex flows like automated coupon payments still need additional application logic on top.
Part of our guide: XRP Explained.
Updated 07/17/2026. By Jake Claver. Educational content, not investment advice.
Tokenizing a real financial instrument means more than minting a balance. It means encoding who can hold it, whether it can move, and how an issuer keeps control if something goes wrong. The XRP Ledger added a token type built for exactly that: the Multi-Purpose Token. This explainer sticks to what the standard actually specifies, sourced to the XRPL documentation and the XLS specifications.
What is an MPT on the XRP Ledger?
MPTs are defined in XLS-0033 as a fungible token type built as an alternative to trust-line tokens, redesigned for efficiency based on lessons from the older model. Each issuance gets a unique on-chain MPT Issuance ID (a 192-bit identifier) and can carry up to 1024 bytes of arbitrary metadata following the XLS-89 schema, covering fields like ticker, name, asset class, issuer name, and icon. The MPTokensV1 amendment went live on the ledger in October 2025 after the standard 14-day validator activation window.
A useful way to read MPTs: they are the ledger’s answer to “how do we represent a regulated asset natively” rather than approximating it with a general-purpose smart contract. The full feature set is documented in the XRPL Multi-Purpose Tokens concept page.
What MPTs do at the protocol level
The XRPL documentation lists concrete, protocol-level capabilities. These are flags and settings on the issuance itself, enforced by the validator network:
- Transfer controls. A Can Transfer flag governs peer-to-peer movement, and a Require Auth flag lets issuers allow-list who may hold the token.
- DEX and escrow eligibility. A Can Trade flag makes an issuance eligible for the native decentralized exchange, and a Can Escrow flag permits placement into escrow for conditional settlement.
- Supply cap. Issuers can set a maximum amount that limits how much of the token can ever circulate.
- Transfer fees. An optional fee from 0% to 50%, in 0.0001% increments, charged on top of the delivered amount (it does not apply to direct issuer payments).
Compliance built into the token standard
The part that matters most for institutions is that compliance controls are part of the standard, not a bolt-on. The documentation describes a Can Lock flag for freezing (individually or globally, including a deep-freeze on a single holder) and a Can Clawback flag that gives the issuer authority to reclaim tokens. Combined with Require Auth allow-listing, an issuer can approximate rules like holder eligibility and restricted transfers using native ledger features that a large validator set enforces, instead of hoping a custom contract behaves correctly. For the U.S. regulatory backdrop on digital assets generally, the CFTC digital assets page is a primary reference.
What still needs extra programming
It is worth being precise about the boundary. MPTs give issuers the token-level primitives above. They do not, by themselves, run a bond’s coupon schedule or execute tranche-by-tranche waterfall distributions; those are application behaviors that require additional logic built around the token. The honest framing is that MPTs make the asset representation and its compliance rules native, which removes a large class of custom-contract risk, while richer cash-flow automation still sits in the layer above the token. Treating the standard as the full solution to structured products would overstate what XLS-33 specifies.
Confidential MPTs (XLS-96)
Privacy is being added as an extension rather than a redesign. XLS-0096 introduces confidential transfers for MPTs using EC-ElGamal encryption and zero-knowledge proofs (compact sigma proofs and Bulletproof range proofs). It hides transaction amounts while keeping supply consistent through plaintext fields that track confidential circulation totals, so balances can be private without breaking the accounting guarantees of XLS-33.
Why this matters
For anyone weighing where to tokenize a regulated asset, the practical question is where the compliance rules live. When allow-listing, freezing, clawback, and supply caps are protocol features, an issuer is relying on standardized, network-enforced behavior instead of auditing bespoke code for every issuance. That is a meaningfully different risk profile. It does not remove the need for legal and regulatory work off-chain, and it does not automate every financial workflow, but it narrows the surface where things can silently go wrong. As always, separate the technology from any investment view: a capable token standard is not a statement about the price or prospects of any asset built on it. Broader context on the network is on Ripple’s site and the XRP Ledger documentation.
Common questions
What is an XRP Ledger Multi-Purpose Token?
It is a fungible token standard on the XRP Ledger defined in XLS-33 and enabled by the MPTokensV1 amendment that activated in October 2025. Each issuance carries an on-chain ID, metadata, and configurable transfer and compliance controls enforced by the validator network.
What compliance features do MPTs support?
MPTs support allow-listing via a Require Auth flag, a supply cap, transfer fees, a Can Lock flag for freezing (including deep-freeze of a single holder), and a Can Clawback flag for reclaiming tokens. These are native protocol features rather than custom contract code.
Can MPTs automatically pay bond coupons or run tranche waterfalls?
Not by themselves. XLS-33 defines the token, its metadata, and its transfer and compliance controls. Automated coupon schedules or tranche-by-tranche distributions require additional application logic built around the token, not just the token standard.
Are MPT transactions private?
They can be, through the XLS-96 extension for confidential transfers, which uses EC-ElGamal encryption and zero-knowledge proofs to hide amounts while keeping total supply verifiable. Standard MPTs without that extension are transparent on the ledger.
When did MPTs go live on the XRP Ledger?
The MPTokensV1 amendment activated on the XRP Ledger in October 2025 following the standard 14-day validator activation period.
This content is educational only. It is not tax, legal, or investment advice. Check primary sources and speak with a qualified professional before making financial decisions.
