- Manage wallets via the console – Create, list, and tag wallets, enable outgoing transactions, and configure wallet settings in the console
- Manage wallets via the API – Create, list, update, and tag wallets, change wallet settings, and check and refresh balances through the API
- Understanding balances – How balances are calculated and displayed
- Asset sweeping – Automate fund consolidation across wallets
- Blockchains and tokens – Feature availability by chain and supported token standards
| Action | Console role | Console procedure | API procedure |
|---|---|---|---|
| Create a wallet | Owner, Administrator, Proposer | Create a wallet | Create a wallet |
| View wallet details | All roles | General settings | Get a wallet |
| List wallets | All roles | List wallets | List wallets |
| Update wallet details | Owner, Administrator, Proposer | Details settings | Update a wallet |
| Enable outgoing transactions | Owner, Administrator, Proposer | Enable outgoing transactions from a wallet | Update wallet settings |
| Turn on raw signing | Owner, Administrator, Proposer | Raw signing | Update wallet settings |
| Freeze deposits by default | Owner, Administrator, Proposer | Freeze transactions by default | Update wallet settings |
| Enable sweeping | Owner, Administrator, Proposer | Sweeping settings | Update wallet settings |
| Get a wallet's sequence | - | - | Get a wallet's sequence |
| Tag a wallet | Owner, Administrator, Proposer | Tag a wallet | Tag a wallet |
| Check organization balances | All roles | List vaults | Get organization balances |
| Check vault balances | All roles | Viewing balances | Get vault balances |
| Check wallet balances | All roles | Viewing balances | Get wallet balances |
| Refresh wallet balances | Owner, Administrator, Proposer | Refreshing balances | Refresh wallet balances |
| Delete a failed wallet | Owner, Administrator | Delete a wallet | Delete a wallet |
Similarly to a physical wallet, a digital asset wallet stores your funds and digital assets.
When transacting with assets in your digital asset wallet, you need a public key and a private key. Keys are cryptographically generated strings of characters.
A public key is a public address that assets can be sent to. It is a way of identifying your wallet. In contrast, a private key is a personal code which is used to authorize transactions from your wallet.
It is essential that your private keys remain private to prevent malicious actors from accessing your wallets.
Ripple Custody (Wallet) provides a secure platform for keeping these keys and wallets safe.
Ripple Custody (Wallet) generates wallets and stores keys using one of two sophisticated storage types: Hardware Security Modules (HSMs) or Multi-Party Computation (MPC).
HSMs are secure, tamper-resistant hardware devices specifically designed to manage, process, and store cryptographic keys. Ripple Custody (Wallet) leverages the key management functionalities of HSMs to manage the entire lifecycle of keys, from generation to retirement.
When wallets are generated and housed within HSMs in Ripple Custody (Wallet), private cryptographic keys are generated using hardware-based entropy sources for maximum randomness and unpredictability. These private keys are never exposed to external environments, mitigating the risks associated with exposure and unauthorized access. Transactions are then signed within the secure boundary of the HSM using the stored private key, ensuring the digital signature's authenticity and integrity without exposing the sensitive key material.
Alternatively, wallets can be generated and protected using MPC, a cryptographic protocol that allows multiple parties to jointly compute a function over their inputs while keeping them private. Within Ripple Custody (Wallet), MPC is implemented via MPC quorums, which split wallet keys among multiple user devices. This is enabled through Ripple Custody (Wallet)’s dedicated mobile application, Ripple Custody (Wallet) Mobile, and CloudSign. Splitting wallet key shards using either type of device ensures that even if one device is compromised, the wallet remains secure as no single device or share of the key holds the complete key.
For a detailed explanation of how MPC-TSS works, see Understanding MPC-TSS.
In Ripple Custody (Wallet), users have the flexibility to opt for their desired wallet generation and key storage type, depending on their specific security requirements, operational needs, and risk assessments. For example, users could hold both MPC and HSM wallets in the same vault. HSM wallets are available in sandbox only; production wallets use MPC.
Regardless of the chosen method, Ripple Custody (Wallet) maintains a high standard of security protocols and access controls to ensure the utmost protection and confidentiality of the wallets, reinforcing the robustness of the overall digital asset security infrastructure.
A passkey wallet is a wallet that your organization provisions for one of its end users. The end user's WebAuthn passkey is the sole approver for the wallet's transactions: your organization's users and devices don't approve them. MPC protects the wallet key, so the key never exists in full, and there's no seed phrase. A passkey is the only way the end user can authenticate, and approving a transaction requires a network connection.
Passkey wallet transactions appear with the transaction types PASSKEY_SIGN and PASSKEY_RAW.
If an end user loses their only passkey, they lose access to the wallet, and Ripple can't recover it. Advise end users to store their passkey in a cloud-synced passkey manager before they fund the wallet. See Lost passkey (passkey wallets).
For EVM-compatible blockchains, your wallet address works across all supported chains. This is because EVM chains share the same address derivation—when you create an Ethereum wallet in Ripple Custody (Wallet), that same address is valid on Arbitrum, Polygon, Base, BNB Chain, Avalanche and 1Money.
- Cross-chain deposits: Ripple Custody (Wallet) automatically detects deposits on any supported EVM chain and credits them to your wallet. It doesn't detect native assets that a smart contract sends to your wallet. See Native-asset deposits sent by smart contracts.
- Cross-chain withdrawals: Send funds on any chain where you have a balance by specifying the target blockchain
- Unified management: Manage assets across all EVM chains from a single wallet
Multi-chain operations are only supported for EVM-compatible chains. Non-EVM wallets (XRP, Bitcoin, Solana, etc.) operate exclusively on their native blockchain.