# Send your first transaction

This guide walks you through sending an outgoing transaction from the Wallet-as-a-Service (Palisade) console.

Prerequisites
Before you proceed, make sure you've completed [Unlock outgoing transactions](/products/wallet/getting-started/unlock-outgoing-transactions). Your wallet must have:

- At least one active transaction policy for the asset you want to send.
- The destination address registered in your address book (for external transfers).
- Outgoing transactions enabled.


## Submit a transaction

Sending a transaction is a two-step process in the console.

### Step 1: Transaction details

1. Navigate to your wallet.
2. Click **Send transaction**. The **New transaction** form opens.
3. Select the **asset** you want to send. The form shows your available balance and whether policy rules exist for the asset.
4. Enter the **total amount**.
5. Enter the destination **address**:
  - Choose an address from your address book (for external transfers), or
  - Choose a wallet within your organization (for internal transfers).
6. (Optional) Enter a **Destination Tag** if the blockchain requires one (for example, XRP Ledger transactions).
7. (Optional) Enter a **Source Tag**, **Correlation ID**, or **External ID** for tracking purposes.
8. Click **Confirm transaction details** to proceed to the review step.


### Step 2: Review and confirm

1. Review the transaction summary. Verify the asset, amount, and destination are correct.
2. Click **Submit transaction** to submit.


Transactions are irreversible
Once a transaction is submitted and confirmed on the blockchain, it cannot be reversed. Double-check all details before you confirm.

## Approve the transaction

If your organization has configured an [approval group](/products/wallet/user-interface/security-controls/approvals) for transactions, the transaction enters a **Pending approval** state after submission.

1. Designated approvers receive a notification in the Wallet-as-a-Service (Palisade) web console and on their mobile device (if they have one registered).
2. Each approver reviews the transaction details and clicks **Approve** or **Reject**.
3. After the required number of approvers authorize the transaction, it moves to the signing stage.


Approval timeout
Approvers must respond within the configured timeout window (default: 1 hour). If the required number of approvals isn't met before the timeout expires, the transaction is automatically rejected.

If no approval group is configured for transactions on this wallet, the transaction skips this step and goes directly to signing.

## Sign the transaction

After the transaction passes policy checks and approvals (if configured), the MPC quorum signs it.

- **CloudSign devices** sign automatically within seconds.
- **Mobile devices** send a notification to the device owner, who reviews and signs manually.


The minimum number of signatories defined in the quorum must participate within 5 minutes. After enough devices sign, the platform constructs the complete signature and submits the transaction to the blockchain.

HSM signing in sandbox
If your sandbox wallet uses an HSM keystore, signing is handled automatically by the Hardware Security Module. No device interaction is required.

## Track the transaction

After the transaction is signed and submitted, you can monitor its progress.

1. Open your wallet and view the transaction list, or navigate to the transactions tab within the wallet detail page.
2. Find your transaction and check its status:


| Status | What it means |
|  --- | --- |
| Policy checks pending | Transaction is being evaluated against your active policies |
| Approval checks pending | Waiting for approvers to authorize |
| Signature pending | Waiting for MPC quorum devices to sign |
| Confirmation pending | Signed and broadcast to the blockchain, waiting for confirmation |
| Confirmed | Confirmed on the blockchain — transaction is complete |
| Rejected | Rejected by an approver, timed out, or failed a policy check |
| Failed | The blockchain rejected the transaction (for example, insufficient gas) |


See [Transactions overview](/products/wallet/user-interface/transactions/overview) and [Manage transactions](/products/wallet/user-interface/transactions/manage-transactions) for the full reference.

## Troubleshoot common issues

| Symptom | Cause | Fix |
|  --- | --- | --- |
| "No matching policy" error | No policy exists for the asset, or the destination doesn't match the policy's allowed counterparties/addresses | Create a policy that covers the asset and destination you're trying to use |
| "Address not found" error | The destination address isn't registered in your address book | Add the counterparty and address to the address book |
| Transaction stuck in "Pending" | An approval group is configured and approvers haven't responded yet | Ask your designated approvers to review the transaction in the console or mobile app |
| Transaction rejected automatically | The transaction amount exceeds the policy limit, or the approval timed out | Check the policy limits and try again with a lower amount, or coordinate with approvers to respond within the timeout window |


## What to do next

You've completed the getting started walkthrough. Here are the recommended next steps to get the most from Wallet-as-a-Service (Palisade):

### Automate with the API

- [Getting started with the API](/products/wallet/getting-started/getting-started-api) — Create vaults, wallets, and transactions programmatically with complete `curl` examples.
- [API credentials best practices](/products/wallet/user-interface/api/api-credentials-best-practices) — Scope permissions, rotate credentials, and configure IP whitelisting.
- [Wallet-as-a-Service (Palisade) API reference](/products/wallet/api-docs/palisade-api/palisade-api) — Full endpoint documentation.


### Integrate with your systems

- [Connections](/products/wallet/user-interface/integrations/open-a-connection) — Open connections to external platforms.


### Add oversight and controls

- [Approval groups](/products/wallet/user-interface/security-controls/approvals) — Require human authorization before transactions execute.
- [Manage policies](/products/wallet/user-interface/policies/policies-manage) — Create more granular policies for different assets, amounts, and destinations.
- [User roles and permissions](/products/wallet/user-interface/users-and-roles/user-roles-and-permissions) — Assign appropriate access levels to your team.
- [Connections](/products/wallet/user-interface/integrations/open-a-connection) — Open connections to external platforms.


### Learn more about the platform

- [Supported blockchains](/products/wallet/user-interface/wallets/supported-blockchains) — Feature availability and chain-specific details.
- [Asset sweeping](/products/wallet/user-interface/wallets/asset-sweeping) — Automate fund consolidation across wallets.
- [Raw signing](/products/wallet/user-interface/transactions/raw-signing) — Sign arbitrary blockchain transaction types.
- [Cross-chain transactions](/products/wallet/user-interface/transactions/cross-chain-transactions) — Send funds across EVM-compatible chains.