> ## Documentation Index
> Fetch the complete documentation index at: https://docs.conduit.financial/llms.txt
> Use this file to discover all available pages before exploring further.

# Deposits

> Receive crypto into a Conduit account from an external wallet.

## **Deposits**

Deposit transactions represent inbound, on‑chain transfers into a Conduit‑held wallet or account. When funds arrive at your account’s blockchain address, Conduit detects the transfer, attributes it to your account, and records a transaction of type `deposit`.

**Type:** `deposit`

### **When to use**

* Funding a Conduit account from self‑custody or an exchange.
* Accepting customer payments in crypto.
* Moving funds onto the platform before conversions or payouts.

### **Key fields**

* **Source:** blockchain address, asset, network, amount.
* **Destination:** Conduit account ID (`acct_...`), asset, network, amount.

<Note>
  You don’t create deposits via API. They are created automatically when Conduit detects an inbound on‑chain transfer to your account’s deposit address.
</Note>

### **How deposits work**

1. Retrieve deposit instructions for the destination account (address, memo/tag if required).
2. Send the asset on the specified network to that address, including any required memo/tag.
3. Conduit monitors the blockchain, attributes the transfer, and creates a `deposit` transaction.
4. After required confirmations, funds are credited and the transaction completes.

### **Transaction status flow**

```mermaid theme={null}
flowchart LR
  A[Initializing] --> B[Awaiting Deposit]
  B --> C[Funds Received]
  C --> D[Processing Settlement]
  D --> E[Completed]
```

### **Supported Asset Types**

* USDC (Ethereum, Base, Polygon, Solana).
* USDT (Ethereum, Tron).
* RLUSD (Ripple).

### **Best practices**

* Send the correct asset on the correct network (no cross‑chain deposits).
* Always include the required memo/tag when present (e.g., XRPL destination tag).
* Test with a small amount for first‑time flows and new assets.
* Monitor status via [Webhooks](/developer-sections/webhooks) (e.g., `transaction.completed`) and surface alerts for failures/delays.

### **Troubleshooting**

* Missing or incorrect memo/tag: provide proof; credit may be delayed or require manual review.
* Wrong network/asset: funds may be irrecoverable.
* Under‑minimum or dust amounts: may not be credited automatically.
* Slow confirmations/congestion: settlement may take longer than usual.

## **What’s next?**

* Retrieve account deposit instructions: `GET /accounts/{id}/deposit-instructions` (see API Reference)
* Set up webhook handling to receive deposit updates: see [Configuring Webhooks](/guides/webhooks/first-webhook)

## Support

Reach out to our [support team](https://support.conduitpay.com/) to get help and share your feedback.