Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »

image-20241211-155845.png

IMPORTANT

The Travel Rule currently requires that every BUY order must be sent to your customer via either 1) a paper wallet, or 2) a PDF wallet.

There is currently no way (using the TR) to send coin to any other type of wallet!

  • It is impossible to technically identify the owner of the wallet, and

  • therefor customer owned wallets do not comply with Travel Rule requirements.

What is this?

This feature enables you to comply with your regional Travel Rule legal requirements, and enables compliant transactions for your customers.

The intent of the Travel Rule is to attach both Sender and Recipient details to every transaction.

The Travel Rule is a regulatory requirement designed to prevent money laundering and terrorist financing, particularly in the financial and cryptocurrency industries. It comes from the Financial Action Task Force (FATF) guidelines. FATF is an international organization created to combat money laundering, terrorist financing, and other threats to the integrity of the global financial system.

The Travel Rule mandates that certain information about the sender and receiver of a transaction must "travel" with the transaction itself when money (or value) is transferred between financial institutions or Virtual Asset Service Providers (VASPs) (or Crypto-Asset Service Providers: CASPs).

For transactions over a certain threshold (often $1,000 or €1,000, but this depends on local regulations), the following details are typically required:

  • Sender Information, including: name, wallet address, and a physical address, national ID number, or other identifying information. This may be your information - or your funding Exchange’s information. The Travel Rule now forces you to disclose and attach it to the transaction so that it may be examined by any authorized party.

  • Receiver Information, including: name & wallet address. If you haven’t already implement strict KYC, then the Travel Rule now forces the matter. To comply with the Travel Rule, you must now (at least) collect your customer’s Name.

Glossary

The Travel Rule introduces some new terms and acronyms. Here’s a quick reference:

Term

Description

Reference

CASP

VASP

Crypto Asset Service Providers

Virtual Asset Service Providers

EU Document 32023R1113

In the context of CAS, the Provider may be yourself or the funding Exchange.

DID

Digital ID

https://www.dock.io/post/decentralized-identifiers

Envelope

A packaged transaction (in CAS),

  • compliant with the Travel Rule.

Travel Rule Provider

A third-party that enables authorized access to view the TR envelopes.

Originator

You, Sender, Payor

  • When sent from an Exchange, the Originator will be that Exchange.

Beneficiary

Your customer, Receiver, Payee


Components

image-20241212-155224.png

Outgoing Transfers

View the transfer logs.

image-20241212-155149.png

Travel Rule Settings

Configure your Travel Rules.

image-20241212-155127.png

Travel Rule Providers

Add or adjust a Travel Rule Provider.

  • You may be your own Travel Rule Provider (“internal”), or you can contract with an external provider.

  • We will begin adding additional Providers in 2025.

image-20241212-155057.png

VASPs

Add or adjust a VASP:

  • Virtual Asset Service Provider


Example

This example enables immediate self-hosted compliance for your Organization.

  1. Create a Travel Rule Provider: “Internal”, see: Travel Rule Providers

  2. Create a new VASP, see: Travel Rule VASPs

  3. Add a new Setting, see: Travel Rule Settings

  4. Configure your AML/KYC setting to use the new Travel Rule, see: https://generalbytes.atlassian.net/l/cp/U57zcH33

  5. Configure your Terminal(s) to use the proper AML/KYC setting, see: https://generalbytes.atlassian.net/wiki/spaces/ESD/pages/963281004/Terminal+Settings#General-Settings

Any transaction that has been packaged via a Travel Rule can be viewed from the Transaction Log:

image-20241206-122806.png

An example Transfer/Envelope:

image-20241206-122403.png

More information

  • No labels