On-ramps convert fiat into crypto and off-ramps convert crypto into fiat, through providers like Alfred Pay, Yellow Card, and Scrypt. Like exchange transactions, these can trigger the same kind of participant-identification requirements. Fireblocks integrates with on/off-ramp providers directly through Connected accounts, rather than routing them through a Travel Rule provider. See Connected accounts for how to connect one.
Ordering and quoting occur through the API. If an order draws from a vault account, the resulting transfer to the provider still goes through your workspace's transfer policy, the same as any other transfer, so you may need to approve or sign it in the Console.
How it works
Whether additional identification data is required depends on who the funds belong to:
- Cashing out or funding your own account. If you are both the originator and the beneficiary, for example moving your own crypto to your own bank account, no additional identification data is required.
- Moving funds on behalf of someone else. If a third party is the originator or the beneficiary, the provider requires identity details for whoever is not you: at minimum a name, and depending on the provider, details like address and date of birth too. Exactly how much is required varies by provider.
You can register external bank accounts and crypto addresses as whitelisted destinations, so they are verified once and can be reused for future orders rather than re-entered each time.
FAQ
The questions below are the ones readers ask most often.
Do I need to provide identification information for my own transactions?
Not if you are both the sender and the receiver of the funds. It is only required when a third party is involved on either end.
Does every provider require the same amount of information for third parties?
No. The type of data (first-party vs. third-party) is standardized across providers, but how much of it a given provider requires varies.
Developer portal
See On/Off-Ramp, and cross-chain Swap via CeFi for order creation, quotes, and the participant identification schema. Trading API overview covers the trading flow.