| Note |
|---|
Please familiarize yourself with the Travel Rule here.
|
...
Examples: BUY - cash to crypto | |||
|---|---|---|---|
Customer (Payer) inserts cash into the crypto-ATM machine and scans the destination wallet address. | |||
BUYdestination address: | Classification: | Example: | |
Scenario A |
| CASP to CASP transfer. CASP is required to send the Envelope to the beneficiary’s CASP. | Customer inserts cash and wants his coins to go to his wallet on Binance exchange. |
Scenario B |
| CASP to self-hosted wallet transfer. CASP needs to perform best effort to confirm the address is not hosted. | Customer inserts 100 EUR in cash and wants his coins to go to his mobile Trust wallet that has private keys in his mobile phone. |
Scenario C |
| CASP to self-hosted wallet transfer. CASP needs to perform best effort to confirm the address is not hosted. CASP should require proof of ownership/control over the wallet. | Customer inserts 1000 EUR in cash and wants his coins to go to his mobile wallet that has private keys in his mobile phone. CASP will require him to provide cryptographic proof. |
Examples: SELL - crypto to cash | |||
|---|---|---|---|
Customer (Payee) selects amount he wants to withdraw on the ATM and prints a redeem ticket. Customer or somebody else sends coins to a wallet address on a redeem ticket that belongs to the BATM Operator (CASP). | |||
SELL - originating address is: | Classification: | Example: | |
Scenario D |
| CASP to CASP transfer. CASP is required to receive PII from originating CASP. | Customer sends coins to you from his Binance account. |
Scenario E |
| Self-hosted wallet to CASP transfer. CASP needs to perform best effort to confirm the address is unhosted. | Customer sends coins worth of 100 EUR from his mobile Trust wallet that has private keys in his mobile phone. |
Scenario F |
| Self-hosted wallet to CASP transfer. CASP needs to perform best effort to confirm the address is unhosted. | Customer inserts 1000 EUR in cash and wants his coins to go to his mobile wallet that has private keys in his mobile phone. CASP will require him to provide cryptographic proof. |
...
Version 20241001 - Delivered
PDF paper wallet support has been added allowing operators to test drive a new vehicle for how to send coins to customer self-hosted wallets, with the proof of ownership requirement satisfied.
Releasing PDF support ahead of time gives operators time to customize their PDF wallet templates to better explain to customers how to use them.
Version 20241101 - Delivered
Input Queues were introduced. Input Queues allow operators to review or suspend incoming coin transfers. This feature is an essential tool for KYC review when the PII from the originator’s CASP hasn’t arrived yet.
Version 20241201 - Delivered
Added support for scenarios B and C. General Bytes has concentrated on supporting and improving usability for these scenarios first - as it is expected that CASP to CASP Travel Rule Providers will be facing significant interoperability and usability issues at the beginning of 2025.
Version 20241201 - Delivered
Added support for customer is declaring that his wallet is unhosted for transactions bellow threshold (1000 EUR for example).
Version 20250101
Added support for scenario A using NotaBene travel rule provider.
Added Extensions API to add your own Travel Rule Provider implementation.
Version 20250201
Added support for scenario D,E,F using NotaBene travel rule provider.
Version 20250301