# Getting started

This guide walks you through the quickest path from a newly activated account to your first transaction in Ripple Custody (Wallet). The steps below use the web console. For an API-first walkthrough, see [Getting started with the API](/pt-br/products/wallet/get-started/use-the-api).

Sandbox and production
Ripple provides sandbox access during onboarding so you can test the platform before going live. Sandbox mirrors production functionality, so the steps below apply to both environments. Sandbox operates against testnet blockchains; production operates against mainnet.

| Environment | Console URL | API base URL |
|  --- | --- | --- |
| Sandbox | `https://app.sandbox.palisade.co` | `https://api.sandbox.palisade.co` |
| Production | `https://app.palisade.co` | `https://api.palisade.co` |


## Before you begin

During onboarding, Ripple creates your organization on the Ripple Custody (Wallet) platform and sends an invitation email to your organization's first owner. Make sure you have the following before you start:

- An invitation email from Ripple Custody (Wallet)
- At least 2 devices available for MPC key shard distribution (mobile devices running Ripple Custody (Wallet) Mobile, CloudSign instances, or a combination)
- If you plan to use the API: IP addresses you want to allowlist for API credential access
- A signed-in account. If this is your first login, accept your invitation and sign in as described in [Set up your organization](/pt-br/products/wallet/get-started/set-up-your-organization). That page also covers planning roles, quorums, and approvals, and the full recommended setup order for a production organization.


MPC is required
Ripple Custody (Wallet) uses Multi-Party Computation (MPC) to secure wallet private keys in production. You must set up devices and create an MPC quorum before you can create a wallet. HSM-based wallets are available in sandbox environments only.

## Setup checklist

Complete these steps in order. Each step depends on the one before it.

| Step | What you do | Guide |
|  --- | --- | --- |
| 1 | Add devices and create an MPC quorum | [Configure devices and quorums](/pt-br/products/wallet/get-started/console/configure-devices-and-quorums) |
| 2 | Create a vault to organize your wallets | [Create your first vault](/pt-br/products/wallet/get-started/console/create-your-first-vault) |
| 3 | Create a wallet and fund it | [Create your first wallet](/pt-br/products/wallet/get-started/console/create-your-first-wallet) |
| 4 | Set up a policy, add addresses, and enable transactions | [Unlock outgoing transactions](/pt-br/products/wallet/get-started/console/unlock-outgoing-transactions) |
| 5 | Submit and confirm a transaction | [Send your first transaction](/pt-br/products/wallet/get-started/console/send-your-first-transaction) |


Zero-trust security model
Ripple Custody (Wallet) operates a zero-trust security model. New wallets are **deposit-only** by default. Outgoing transactions are blocked until you create a transaction policy, add destination addresses, and explicitly enable transactions on the wallet. Step 4 is the most commonly missed step during onboarding.

## Other getting-started guides

| Guide | Who it's for |
|  --- | --- |
| [Getting started with the API](/pt-br/products/wallet/get-started/use-the-api) | Developers who want to create vaults, wallets, and transactions programmatically |


## What to do next

After you send your first transaction, consider these next steps:

- [Getting started with the API](/pt-br/products/wallet/get-started/use-the-api) — create vaults, wallets, and transactions programmatically
- [Create approval groups](/pt-br/products/wallet/governance-and-controls/approvals/configure-approval-flows#create-an-approval-group-via-the-console) — add human oversight to transactions
- [Review supported blockchains](/pt-br/products/wallet/vaults-and-wallets/supported-blockchains-and-tokens) — feature availability and chain-specific details