Skip to main content

​
Conversions (Fiat and Crypto)

Conversions let you either exchange fiat between currencies (e.g., USD → EUR) or exchange crypto between assets/networks (e.g., USDC on Ethereum → USDT on Tron). Type: conversion

​
When to use conversions

  • Cross-currency fiat payments to international recipients (e.g., USD → MXN)
  • Treasury FX rebalancing across operating currencies
  • Switching crypto assets (USDC ↔ USDT) or bridging across networks (Ethereum ↔ Tron)
  • Optimizing fees or aligning with recipient preferences

​
Key fields (fiat conversions)

  1. Source bank account ID bank_... and source currency
  2. Amount to convert
  3. Destination bank account ID bank_... and target currency
  4. Quote — locks exchange rate and fees until expiration
  5. Documents/purpose — when required for compliance

​
Key fields (crypto conversions)

  1. Source account ID acct_..., source asset and network
  2. Amount to convert
  3. Destination account ID acct_..., target asset and network
  4. Quote — locks conversion/bridge rate until expiration

​
How conversions work

  • Create quote: get a locked rate for your source/target
  • Create conversion: submit with IDs and quote
  • Process: Conduit executes FX or crypto swap/bridge
  • Completed: target funds are delivered to destination

​
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
These may not always appear as explicit API fields but remain critical for compliance.

​
Best practices

  • Always act before quote expiration; regenerate if expired
  • Ensure bank accounts and wallet accounts are verified and supported
  • For crypto, confirm asset/network support and consider fee differences
  • Keep supporting documents ready for compliance

​
What’s next?

For full request details, see the API Reference.

​
Support

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