# Overview

Ripple Custody (Wallet) provides multiple layers of security controls to protect your digital assets. Policies, approvals, and MPC signing work together to ensure that only authorized transactions are executed and that your wallet keys remain secure.

In this section
- [Approvals](/products/wallet/governance-and-controls/approvals) – Set up approval workflows for transactions and operations
- [Policies](/products/wallet/governance-and-controls/policies) – Set limits on what can leave each wallet, and where it can go
- [Address book](/products/wallet/governance-and-controls/address-book) – Register the counterparties and external addresses your wallets can send to


Related: [MPC quorums](/products/wallet/signing-and-key-management/mpc-quorums) – Configure multi-party signing with distributed key shards

## How these controls work together

```mermaid
flowchart TD
    TX[Transaction Created] --> PC[Policy Check]
    PC -->|Pass| AP{Approvals Required?}
    PC -->|Fail| REJ[Transaction Rejected]
    AP -->|Yes| AG[Approval Group Review]
    AP -->|No| SIG
    AG -->|Approved| SIG[MPC Signature]
    AG -->|Rejected| REJ
    SIG --> BC[Blockchain Submission]
    BC --> CONF[Confirmed]
```

1. **Policies** define what transactions are allowed (amounts, destinations, frequency). Destinations outside your organization must be registered in the [address book](/products/wallet/governance-and-controls/address-book).
2. **Approvals** ensure human oversight before execution.
3. **MPC quorums** cryptographically sign approved transactions.


For the full transaction pipeline, see [Policy evaluation](/products/wallet/governance-and-controls/policies#policy-evaluation).

## Policies

Transaction policies control what outgoing transactions your wallets can execute. Every wallet is deposit-only until it has an active policy for an asset. Policies set per-transaction, rolling, and lifetime limits, and can restrict destinations and initiators.

See [Policies](/products/wallet/governance-and-controls/policies) for details.

## Approvals

Approval groups add a human authorization layer to transactions. Before a transaction is submitted to the blockchain, designated approvers must review and approve it through the web console or mobile app.

Key features:

- Configure approval groups for transactions, addresses, policies, and more
- Set minimum required approvers (for example, 2 of 3 must approve)
- Configurable timeout periods for approval windows


See [Approvals](/products/wallet/governance-and-controls/approvals) for how approvals work, and [Configure approval flows](/products/wallet/governance-and-controls/approvals/configure-approval-flows) for setup instructions.

## MPC quorums

Multi-Party Computation (MPC) quorums split wallet private keys across multiple devices, ensuring that no single device holds the complete key. When a transaction requires signing, multiple devices must participate to create a valid signature.

MPC quorums support:

- **Mobile devices**: Manual review and approval via the Ripple Custody (Wallet) Mobile app
- **CloudSign devices**: Programmatic signing for high-volume operations
- **Mixed quorums**: Combination of mobile and CloudSign for flexibility


See [MPC quorums](/products/wallet/signing-and-key-management/mpc-quorums) for configuration details.