Travel Rule Policy
Policy on Compliance with FATF Recommendation 16 on Information Transfer for Virtual Asset Transfers
Version 1.0 | Effective Date: 04/30/2026
1. General Provisions and Legal Basis
1.1. This Policy establishes the procedures by which xcex.io (3-102-947550 SOCIEDAD DE RESPONSABILIDAD LIMITADA) complies with Travel Rule requirements pursuant to: FATF Recommendation 16 and the FATF Guidance on Virtual Assets and VASPs (2021); EU Regulation 2023/1113 (in force from December 2024); FinCEN BSA/AML for transfers ≥USD 3,000 (31 CFR §1010.410); and equivalent requirements of applicable regulatory jurisdictions.
1.2. The Travel Rule requires the Company, in its capacity as a VASP, to transmit originator and beneficiary data with every virtual asset transfer exceeding the applicable threshold.
1.3. This Policy applies to all outgoing and incoming virtual asset transfers processed through the xcex.io Platform.
2. Jurisdiction-Specific Thresholds
| Jurisdiction / Authority | Instrument | Threshold | Notes |
|---|---|---|---|
| FATF (global) | Rec. 16 (2012/2021) | ≥1,000 USD/EUR | Base global standard for all VASPs |
| European Union | Regulation 2023/1113 | EUR 0 (any amount) | From December 2024, the Travel Rule applies to all transfers within the EU with no minimum threshold |
| United States (FinCEN) | BSA, 31 CFR §1010.410 | ≥3,000 USD | Also applies to fiat wire transfers |
| United Kingdom | FCA / MLR 2017 | ≥1,000 GBP | FCA Travel Rule requirement in force from September 2023 |
| Switzerland | FINMA (AMLO-FINMA) | ≥1,000 CHF | Applies to unhosted wallets as well |
| Singapore | MAS (PSA 2019) | ≥1,500 SGD | MAS Notice PSN02 |
| xcex.io jurisdiction of incorporation | National AML/CTF legislation | Per local law | The Company complies with the requirements of its jurisdiction of incorporation |
Where the applicable threshold is uncertain, the Company applies the most conservative standard: USD/EUR 1,000.
3. Originator and Beneficiary Data
| Data Field | Originator | Beneficiary |
|---|---|---|
| Full legal name | Required (KYC-verified) | Required |
| Cryptocurrency wallet address | Required | Required |
| Physical address | Required (country + address) | One of: address / date of birth / tax ID / document number |
| Date of birth | If physical address unavailable | If physical address unavailable |
| National identification number | If physical address unavailable | Alternative to physical address |
| Originating VASP name | Required | N/A |
| Beneficiary VASP name | N/A | Required (if known) |
| Transfer amount and asset | Required | Required |
All originator data is retained for a minimum of five (5) years and made available to competent authorities upon request.
4. Data Transfer Protocols (VASP-to-VASP)
| Protocol | Description | Status | Notes |
|---|---|---|---|
| TRISA | Decentralised PKI architecture; direct encrypted channel between VASPs | Production / widely deployed | Open standard; EU support |
| OpenVASP | Open protocol based on Ethereum Whisper/Waku; P2P transfer | Emerging | Fully decentralised |
| VerifyVASP | Centralised hub (Korea/Asia) | Production (Asia) | Widely used in Southeast Asia |
| Sygna Bridge | CoolBitX commercial platform | Production | High adoption among exchanges |
| Bilateral / direct exchange | Secure email or API under mutual agreement | Where no shared protocol exists | Requires execution of a DASA |
5. Outgoing Transfer Procedure (Step-by-Step)
| Step | Action | Description |
|---|---|---|
| 1 | Transfer initiation | The User creates a request to transfer virtual assets to an external address. |
| 2 | Threshold check | The system automatically compares the transfer amount against the applicable threshold (USD 1,000 or applicable local threshold). |
| 3 | Beneficiary VASP identification | Lookup against VASP directories (TRISA Directory, OpenVASP Whitepages, Sygna Network). |
| 4 | Originator data collection | Data retrieved from the verified KYC profile; if unavailable, requested from the User. |
| 5 | Beneficiary data collection | Data requested from the User; where a connection to the beneficiary VASP is available, confirmation is requested. |
| 6 | Beneficiary screening | Automated screening against OFAC SDN, EU, UN, and blockchain analytics databases. |
| 7 | Travel Rule data transmission | Encrypted transmission to the beneficiary VASP via a supported protocol, prior to or simultaneously with execution of the transfer. |
| 8 | Execution or freeze | If steps 1–7 are completed successfully, the transfer is executed. If a sanctions match is identified or data transmission is not possible, the transfer is suspended pending MLRO review. |
6. Incoming Transfer Procedure
Upon receipt of an incoming transfer, the Company: records the transfer details; requests originator data from the initiating VASP; conducts screening against sanctions lists and blockchain analytics databases; freezes funds and notifies the MLRO upon any match; and applies the Sunrise Issue procedure set out in Section 8 where applicable. Incoming transfers from unidentified originators above the threshold are subject to mandatory enhanced review.
7. Unhosted Wallets
7.1. For transfers between the Platform and an unhosted wallet, inter-VASP Travel Rule data exchange does not apply; however, the Company is required to: establish the identity of the User (KYC); conduct Proof of Ownership for transfers above the threshold; and screen the wallet address.
7.2. Proof of Ownership
Proof of Ownership is established by: cryptographic message signing from the wallet; or a micro-transaction to the Company’s verification address.
8. The Sunrise Issue
8.1. The Sunrise Issue arises where a counterparty VASP has not yet implemented the Travel Rule or is not registered in any available VASP directory.
8.2. Procedure for Handling the Sunrise Issue
- Alternative data transmission: transmission via secure email to the compliance address of the counterparty VASP.
- Acknowledgement request: confirmation of receipt to be obtained within 2 business days.
- Manual verification: review of the counterparty VASP against publicly available VASP registries.
- Escalation to MLRO: where data transmission is not possible, the transfer is suspended.
- Refusal to execute: where the MLRO assesses the risk as unacceptable, the transfer is declined and a SAR filed if warranted.
8.3. All Sunrise Issue cases are documented, recording: the counterparty VASP, date, measures taken, and final decision.
9. Risk Matrix for Unhosted Wallets
| Risk Parameter | Low Risk | Medium Risk | High Risk | Action |
|---|---|---|---|---|
| Transfer amount | <USD 1,000 | USD 1,000–10,000 | >USD 10,000 | Enhanced controls at high risk |
| Address risk score (blockchain analytics) | 0–25% | 26–69% | ≥70% | Freeze funds at ≥70% |
| Address history | Clean history | Minor flags | Mixers, darknet, OFAC SDN | SAR; refuse at high risk |
| Proof of Ownership (PoO) | Confirmed | Not required | PoO refused | Block if PoO refused |
| Wallet jurisdiction | FATF-compliant | Partially compliant | FATF blacklisted | Refuse if blacklisted |
| User KYC status | Level 2–3 | Level 1 | Level 0 / no KYC | Transaction requires KYC |
10. Refusal to Execute a Transfer
The Company will refuse to execute a transfer in the following circumstances: a sanctions list match (OFAC SDN, EU, UN, HM Treasury); address risk score ≥70%; the User refuses to complete Proof of Ownership for an above-threshold transfer; data transmission under the Travel Rule is not possible and the MLRO assesses the risk as unacceptable; connection to mixers (Tornado Cash or equivalent) or ransomware is identified; the User has not completed KYC.
The User is notified of the refusal without disclosure of the specific grounds (reason stated as: “AML/compliance requirements”).
11. Travel Rule Data Retention
The Company retains the following records for a minimum of five (5) years: originator and beneficiary data for all above-threshold transfers; transmission records (protocol metadata, timestamps); refusal records; Sunrise Issue documentation; and wallet address screening results. All data is stored in encrypted form with restricted access.
12. Training and Oversight
All staff involved in the processing of virtual asset transfers complete annual Travel Rule training. The MLRO updates this Policy in response to legislative changes. An annual internal audit report is submitted to senior management. The Company monitors updates from FATF, the EU, FinCEN, and the FCA and implements procedural changes promptly.
13. Contact Information
| Detail | Information |
|---|---|
| Service Name | xcex.io |
| Legal Name | 3-102-947550 SOCIEDAD DE RESPONSABILIDAD LIMITADA |
| Director | Marat Aiilchiev |
| MLRO / Travel Rule Officer | Alfred Atabaev |
| Email (Compliance / Travel Rule) | support@xcex.io |
| Registered Address | Forum One Business Center, Tower G, First Floor, NCC Law Offices, Pozos, Santa Ana, San José, Costa Rica |
| Registration Number | 3-102-947550 |
Note: This Policy forms part of the xcex.io legal documentation suite and is to be read in conjunction with the KYC/AML Policy and the Terms of Service.