> ## 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.

# Onramp

> Convert fiat to crypto and deliver to a designated wallet.

## **Onramp**

Onramp transactions represent the movement of value **from a traditional bank account (fiat)** to **your Conduit balance** in stablecoins.

**Type:** `onramp`

### **How onramps work**

1. Fiat funds are sent from a verified bank account to Conduit, following the provided deposit instructions.
2. Conduit converts the received fiat to stablecoin using a locked exchange rate ([Quote](/core-concepts/quotes)).
3. The converted stablecoin is credited to your balance.

### **Key fields**

* [**Source**](/core-concepts/payment-methods): bank account ID (`bank_...`) — the origin of the funds.
* [**Destination**](/core-concepts/payment-methods): wallet ID (`wlt_...`) or bank account ID (`bank_...`) — the ultimate recipient of the funds, for compliance reasons.
* [Quote](/core-concepts/quotes): valid quote ID to lock the conversion rate for the fiat → stablecoin pair.
* **Purpose** (optional): transaction purpose code (recommended).
* **Documents** (optional): supporting documentation for compliance or justification.
* **Reference** (optional): your internal tracking reference.

### **Transaction flow**

1. **Create a quote**: get the current conversion rate
2. **Create the onramp transaction**: use your payment method IDs and the quote
3. **Receive deposit instructions**: use the provided deposit instructions to send your fiat payment to Conduit
4. **Send your fiat payment**: use the provided deposit instructions; Conduit converts and delivers stablecoins to your custody wallet

### **Transaction status flow**

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

Your transaction progresses through these stages:

* **Initializing**: transaction is being created and validated.
* **Created**: transaction is accepted; deposit instructions are available.
* **Awaiting funds**: Conduit is waiting for the fiat payment to arrive.
* **Funds received**: payment has been received and verified.
* **Processing settlement**: Conduit is converting funds and crediting stablecoins to your wallet.
* **Completed**: stablecoins have been credited to your Conduit wallet balance.

### **Deposit instruction types**

Deposit instructions vary depending on the source currency and local payment rails

| **Currency** | **Supported Payment Rails** |
| ------------ | --------------------------- |
| USD          | SWIFT, Fedwire              |
| BRL          | TED, PIX                    |
| MXN          | SPEI                        |
| EUR          | SEPA                        |
| NGN          | NIP                         |

### **Common use cases**

* Funding a stablecoin portfolio.
* Acquiring stablecoins for business purposes.
* Setting up cross-border payments with stablecoins.

### **Understanding true sender and true recipient**

#### **Why this matters**

Compliance requires visibility into the actual parties involved in each transaction, not just intermediaries. Misidentification can result in:

* Payment delays or rejections
* Compliance review failures
* Risk of limited access or account offboarding

#### **True sender definition**

The true sender is the business that provides the funds for a transaction.

If you’re acting on behalf of a customer:

* The customer is the true sender — not your business, even if funds move through your accounts
* Example: Acme Corp pays a vendor via your platform → Acme Corp is the true sender

If the funds come from your own business account:

* Your company is the true sender
* Example: You pay a vendor directly → Your company is the true sender

#### **True recipient definition**

The true recipient is the person or business that ultimately receives and benefits from the funds.

If you’re paying on behalf of a customer:

* The final beneficiary is the true recipient — not your business
* Example: Acme Corp pays a contractor via your platform → The contractor is the true recipient

If the payment is for your own operations:

* The vendor or account receiving funds is the true recipient
* Example: You pay your supplier → The supplier is the true recipient

<Note>
  These may not always appear as explicit API fields but remain critical for compliance.
</Note>

### **Best practices**

* Send the fiat payment promptly after creating the transaction and monitor quote validity.
* Ensure the source bank account is verified and matches the transaction request.
* Retain records of deposit instructions, payment confirmations, and any supporting documents.
* Track transaction status via the API or [Webhooks](/developer-sections/webhooks) and set alerts for potential failures.

### **Troubleshooting**

* **Invalid or expired quote:** generate a new [Quote](/core-concepts/quotes) and retry the transaction.
* **Amount mismatch:** send the exact quoted amount and include all required references.

## **What's next?**

Now that you know what an onramp is and how it works, learn how to create one by following the [Creating an Onramp Transaction](/guides/transaction/first-onramp-transaction) guide.

For full request details, see the [API Reference](/api-reference/transactions/create-a-transaction).

## Support

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