Skip to main content

​
Transfers

Move money between bank accounts in the same currency efficiently using Conduit’s transfer transactions. Type: transfer

​
When to use

  • Same-currency bank-to-bank payments (domestic or international)
  • Managing multi-currency operating accounts
  • Moving funds between your own accounts
  • Paying suppliers and contractors globally
  • Examples: USD → USD (US to Singapore), EUR → EUR (France to Germany), MXN → MXN
Transfers are strictly same-currency payments, regardless of location. For cross-currency payments (e.g., USD → EUR), use a conversion transaction.

​
How transfers work

  1. Create transaction with type: transfer
  2. Receive deposit instructions — banking details to send funds to Conduit
  3. Send funds — wire money to Conduit using provided instructions
  4. Conduit processes — funds are sent to recipient’s account
  5. Completed — recipient receives funds in the same currency

​
Common fields

Key characteristics:
  1. Deposit instructions — banking details to send funds to Conduit
  2. Uses bank account IDs — format: bank_... for both source and destination
  3. Quote required — locks in rates or fees for transfers
  4. Compliance requirements — may require supporting documentation
  5. Settlement time — typically 1–3 business days (varies by corridor)
Processing Details:
  • Settlement time: 1–3 business days (varies by corridor)
  • Supporting documentation may be required for compliance
  • Real-time status updates via webhooks

​
Key terms

TermDefinition
TransferMoving same currency between accounts (type: transfer)
Deposit instructionsBanking details provided for sending funds to Conduit
Source currencyThe fiat currency you’re sending from
Target currencyThe fiat currency recipient receives (same as source for transfers)
QuoteLocked-in rate/fees with expiration time
Bank account IDBank account identifier (e.g., bank_...)
RailPayment method (Fedwire, SEPA, etc.)

​
Understanding true sender and true recipient

​
Why this matters

Compliance regulations require full visibility into the actual parties involved in each transaction—not just the platform or intermediary. Misidentifying these parties 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 from your operating account → 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
While the true sender/recipient concept is important for compliance understanding, these may not always be explicit fields in the API depending on the transaction type.

​
What’s next?

Now that you know what a fiat transfer is and how it works, learn how to create one by following Creating a Fiat Transfer Transaction. For full request details, see the API Reference.

​
Support

Reach out to our support team to get help and share your feedback.
⌘I