# Getting started

This guide walks you through the complete setup process for Wallet-as-a-Service (Palisade), from your first login to your first transaction. The steps below use the web console. For an API-first walkthrough, see [Getting started with the API](/products/wallet/getting-started/getting-started-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 Wallet-as-a-Service (Palisade) platform and sends an invitation email to your designated administrator. Make sure you have the following before you start:

- An invitation email from Wallet-as-a-Service (Palisade)
- At least 2 devices available for MPC key shard distribution (mobile devices running Wallet-as-a-Service (Palisade) Mobile, CloudSign instances, or a combination)
- If you plan to use the API: IP addresses you want to whitelist for API credential access


MPC is required
Wallet-as-a-Service (Palisade) 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 | Accept your invitation and sign in | [Set up your organization](/products/wallet/introduction/set-up-your-organization) |
| 2 | Add devices and create an MPC quorum | [Configure devices and quorums](/products/wallet/getting-started/configure-devices-and-quorums) |
| 3 | Create a vault to organize your wallets | [Create your first vault](/products/wallet/getting-started/create-your-first-vault) |
| 4 | Create a wallet and fund it | [Create your first wallet](/products/wallet/getting-started/create-your-first-wallet) |
| 5 | Set up a policy, add addresses, and enable transactions | [Unlock outgoing transactions](/products/wallet/getting-started/unlock-outgoing-transactions) |
| 6 | Submit and confirm a transaction | [Send your first transaction](/products/wallet/getting-started/send-your-first-transaction) |


Zero-trust security model
Wallet-as-a-Service (Palisade) 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 5 is the most commonly missed step during onboarding.

## Other getting-started guides

| Guide | Who it's for |
|  --- | --- |
| [Getting started with the API](/products/wallet/getting-started/getting-started-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](/products/wallet/getting-started/getting-started-api) — create vaults, wallets, and transactions programmatically
- [Create approval groups](/products/wallet/user-interface/security-controls/approvals) — add human oversight to transactions
- [Review supported blockchains](/products/wallet/user-interface/wallets/supported-blockchains) — feature availability and chain-specific details