Ripple Custody (Wallet) is a self-custody technology platform for institutions, fintechs, and Web3 businesses that need full control over their digital assets. It provides the infrastructure to create, manage, and move digital assets securely, while, with an MPC keystore, your organization keeps ownership and control of them. The platform supports a wide range of digital asset operations, from custody and CeFi/DeFi trading to tokenization and treasury management.
Ripple Custody (Wallet) uses institutional-grade Multi-Party Computation (MPC) and Hardware Security Modules (HSMs) to generate and protect wallet keys, within a zero-trust architecture. With an MPC keystore, key shares live on your organization's own quorum devices, so no single party can sign alone, and you keep ownership and control of your assets without the counterparty risk of handing keys to a third party. With an HSM keystore, the Ripple Custody (Wallet) service creates the key and holds it in a hardware security module, which signs on the server without a device.
Ripple enables HSM wallets per organization in production. To use them, contact your Ripple representative.
The Approvals & Policy Engine controls how you authorize transactions. You define who can approve what — user roles, approval groups, transaction policies, and registered counterparty addresses — and a transaction executes only after it meets the requirements that apply to it. A few operations, such as asset sweeping and passkey transfers, aren't evaluated against policy limits. See Operations that bypass policies. The exception is asset sweeping: sweep transactions run without a wallet's policy rules or limits, but still wait for transaction approvers if the wallet or organization has any. This reduces manual steps and prevents unauthorized transactions.
- Ripple enables HSM wallets per organization in production. To use them, contact your Ripple representative.
- MPC on the mobile app is available in sandbox. It isn't available in production yet.
- Travel Rule policies and the Travel Rule provider connection are available in sandbox. They aren't available in production yet.
| Component | What it does |
|---|---|
| Organization, users, and roles | Your organization is the top-level account. Each user has one of six roles that sets what they can do. |
| Vaults | Group wallets that share a purpose, such as a business unit, risk profile, or asset class. |
| Wallets and keystores | Hold assets on a blockchain. Each wallet's key lives in an MPC or HSM keystore. |
| Devices and MPC quorums | Mobile devices and CloudSign instances hold key shares and sign. A quorum distributes a wallet's key shares across its devices. |
| Policies, approvals, and address book | Policies limit what can leave each wallet and where it can go, approval groups review transactions, and the address book registers counterparties. |
| Transactions | Transfers, raw signing, and cross-chain transfers, tracked from creation to confirmation on the blockchain. |
| Webhooks and audit logging | Webhooks notify your systems of transaction, wallet, and approval events. Audit logs stream all organization activity to AWS Data Firehose. |
| Travel Rule and transaction freeze | Exchange originator and beneficiary information with other VASPs, and hold funds in place for compliance review. |
- Set up your organization: If you're an owner or administrator, set up your organization after Ripple sends your invitation. Plan roles, quorums, and approvals, and follow the recommended setup order.
- Daily operations: If you're a proposer, approver, auditor, or viewer, see User roles and permissions for what your role can do, such as sending a payment, approving a transaction, or viewing transactions.
- Try the console: Go from a newly activated account to your first transaction in the web console with the console quickstart.
- Build with the API: Authenticate and send your first transaction programmatically with Getting started with the API.
For help, see Support.