> For the complete documentation index, see [llms.txt](https://help.token.gomining.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.token.gomining.com/faq/security/travel-rule.md). # Travel rule ### What is the Travel Rule? The **Travel Rule** is an international regulatory requirement, applied under the *Markets in Crypto-Assets Regulation (MiCA)* and the *Transfer of Funds Regulation (TFR*), that obliges crypto platforms (VASPs) to collect and share information about the sender and recipient when crypto is transferred to an external address. It exists to increase transparency and help prevent money laundering and fraud. ### Who does the Travel Rule apply to? The **Travel Rule** form appears for GoMining users who: * have a verified country of residence in the EEA or the UK, and * are withdrawing funds to an external wallet. If this applies to you, you'll be asked for a few extra details about the recipient before the withdrawal can be sent. {% hint style="info" %} Users outside the EEA/UK are not affected. {% endhint %} #### What information do I need to provide? **1. Who owns this wallet?** * **Me (self-transfer)** — the destination wallet is your own. * **Other person or company** — the wallet belongs to a third party. **2. Recipient (only if *****Other person or company*****)** Select the recipient type: * **Individual** → full name, country, city, address line 1, and address line 2 (optional). {% hint style="success" %} **Why is the recipient's address requested?** The Travel Rule requires the recipient of a transfer to be identified, so their address used during KYC may be requested. {% endhint %} * **Company** → company name, registration number, and country (optional). **3. Wallet type** * **Custodial (exchange / VASP)** — held by a platform or service (e.g., Binance). * **Non-custodial (self-hosted)** — a wallet you/the recipient control directly (e.g., MetaMask). **4. Provider or self-confirmation (depends on wallet type)** * *Custodial* → choose the **provider (exchange)** by searching the list (e.g., Binance, Bybit, KuCoin, Gemini, Crypto.com). * *Non-custodial, sending to your own wallet* → **self-confirm** ownership by ticking that the wallet belongs to you and is under your control. * *Non-custodial, sending to someone else* → no provider applies, so the recipient is identified through the recipient details from step 2 (Individual or Company) instead of a self-confirmation. **5. Consent** \ Tick the box agreeing to share recipient details to meet **MiCA / TFR** Travel Rule requirements before sending. ### What happens after I submit? The details are submitted for compliance verification. While this runs, the withdrawal amount is temporarily locked on your balance. * If verification passes, the withdrawal is executed. * If it does not pass, the funds are returned to your balance. ### How long does verification take? Verification usually takes a few seconds, but may take up to a few minutes in some cases. ### Can I create multiple withdrawals at once? No. Only one withdrawal can be processed at a time. After you submit a withdrawal, please wait until it is fully processed before starting a new one. If you have an active withdrawal, you will need to wait for it to complete (either successfully or be cancelled) before initiating another. ### Quick Q\&A #### Are you sending it to yourself, to another person, or to a company? This depends on who owns the wallet you’re sending to: * **Yourself** — if you’re sending to your own wallet (e.g., your own Binance account, your own hardware wallet, your own MetaMask). * **Another person** — if you’re sending to a wallet that belongs to a friend, family member, or any other individual. * **Company** — if you’re sending to a business, service provider, or other legal entity. #### Is the receiving wallet hosted or unhosted? * **Hosted wallet** — a wallet on a centralized exchange or service that holds your funds for you. Examples: Binance, Coinbase, Kraken, Bitstamp, Bybit. * **Unhosted wallet** — a wallet where you (or the recipient) personally hold the private keys. Examples: MetaMask, Trust Wallet, Ledger, Trezor, paper wallet. If you’re not sure, check whether you log in to a website to access the wallet (likely hosted) or use a browser extension / mobile app with a seed phrase (likely unhosted). #### How do I choose the VASP (exchange/service provider)? A VASP is the company that operates the wallet you’re sending to — like Binance, Coinbase, or Kraken. Search by exact name in the list. If multiple similar names appear (e.g., regional variants), choose the one matching the service you actually use. If your VASP is not in the list, contact our support team. We may be able to add it, or there may be specific reasons why this destination isn’t supported. #### Whose name should I enter? This field appears only when you're sending to **another person or company**. Enter the recipient's full name exactly as it appears on the receiving wallet or account. The name doesn't need to match your name in GoMining — what matters is that it matches the receiving wallet's account holder. When you send to your own wallet, no name is requested — you only select the provider (for custodial wallets) or confirm ownership (for non-custodial wallets). #### What address should I enter? This field appears only when you're sending to another person or company. Enter the recipient's residential address — typically the one used during their KYC verification on the receiving service. This is required by regulation to identify the recipient, not the wallet address itself (the wallet address is captured separately). When you send to your own wallet, no address is requested. #### What happens if I make a mistake? If verification doesn’t pass, your withdrawal is cancelled, and your funds are returned to your balance. We recommend double-checking the recipient’s name and details before submitting. ### Common scenarios #### **Example 1. Withdrawing to your own Binance account** You're sending crypto to your personal Binance account. * Who owns this wallet? → **Me** * Wallet type → **Custodial** * Provider (VASP) → **Binance** This is treated as a transfer to yourself via a centralized exchange. #### **Example 2. Withdrawing to your own Bybit / Coinbase / Kraken account** You're sending funds to your own account on another exchange. * Who owns this wallet? → **Me** * Wallet type → **Custodial** * Provider (VASP) → select the relevant exchange The process is the same as for Binance. #### **Example 3. Withdrawing to your own MetaMask** You're sending crypto to your own MetaMask wallet. * Who owns this wallet? → **Me** * Wallet type → **Non-custodial** * Confirm that the wallet belongs to you and is under your control Examples of such wallets: MetaMask, Trust Wallet, Rabby, Phantom, Ledger, Trezor. No additional VASP needs to be specified. #### **Example 4. Withdrawing to another person's exchange account** You're sending funds to someone else's account on a centralized exchange. * Who owns this wallet? → **Other person or company** * Recipient → **Individual** * Recipient details → Full name, Country, City, Address line 1, Address line 2 (optional) * Wallet type → **Custodial** * Provider (exchange) → select the recipient's exchange #### **Example 5. Withdrawing to another person's personal wallet** You're sending crypto to another person's MetaMask, Trust Wallet, Ledger, etc. * Who owns this wallet? → **Other person or company** * Recipient → **Individual** * Recipient details → Full name, Country, City, Address line 1, Address line 2 (optional) * Wallet type → **Non-custodial** No provider is needed; the recipient is identified through the details above. #### **Example 6. Withdrawing to a company** You're sending funds to a company (e.g., paying an invoice). * Who owns this wallet? → **Other person or company** * Recipient → **Company** * Company details → Company name, Registration number (optional), Country (optional) * Wallet type → **Custodial** or **Non-custodial** * If Custodial → select the **provider (exchange)** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.token.gomining.com/faq/security/travel-rule.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.