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
- Fiat funds are sent from a verified bank account to Conduit, following the provided deposit instructions.
- Conduit converts the received fiat to stablecoin using a locked exchange rate (Quote).
- The converted stablecoin is credited to your balance.
Key fields
- Source: bank account ID (
bank_...) — the origin of the funds. - Destination: wallet ID (
wlt_...) or bank account ID (bank_...) — the ultimate recipient of the funds, for compliance reasons. - Quote: 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
- Create a quote: get the current conversion rate
- Create the onramp transaction: use your payment method IDs and the quote
- Receive deposit instructions: use the provided deposit instructions to send your fiat payment to Conduit
- Send your fiat payment: use the provided deposit instructions; Conduit converts and delivers crypto to your custody wallet
Transaction status flow
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
- 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
- The vendor or account receiving funds is the true recipient
- Example: You pay your supplier → The supplier is the true recipient
These may not always appear as explicit API fields but remain critical for compliance.
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 and set alerts for potential failures.
Troubleshooting
- Invalid or expired quote: generate a new Quote and retry the transaction.
- Amount mismatch: send the exact quoted amount and include all required references.