# Travel Rule for crypto transfers

Myaza Travel Rule helps your organisation decide when a crypto transfer requires originator, beneficiary and counterparty information. It assesses that information with identity, sanctions, PEP, adverse-media and wallet evidence, then recommends whether the transfer can proceed, must be held for review or must be stopped.

The operational result always answers three questions:

1. **What happened?** The assessment is not required, needs information, needs review, is blocked, can proceed or failed validation.
2. **Why?** Myaza records the matched policy rule, missing fields, identity evidence, VASP evidence and screening results.
3. **What next?** Supply missing information, open the exact investigation, retry a failed validation or take no action.

## Choose your next step

| Task | Guide |
|---|---|
| Your company, institutions and application. | [Set up Travel Rule](https://trust.myaza.co/documentation/travel-rule-setup/markdown) |
| Choose rules, information packages and publication. | [Transfer requirements](https://trust.myaza.co/documentation/travel-rule-policies/markdown) |
| Send the information you already hold in one request. | [Create a transfer](https://trust.myaza.co/documentation/travel-rule-transactions/markdown) |
| Recover incomplete transfers without creating duplicates. | [Supply missing information](https://trust.myaza.co/documentation/travel-rule-information/markdown) |
| Secure messaging and the customer wallet's execution gate. | [Exchange and authorise](https://trust.myaza.co/documentation/travel-rule-execution/markdown) |
| Review incoming information and admit a verified deposit. | [Receive a transfer](https://trust.myaza.co/documentation/travel-rule-incoming/markdown) |
| Report wallet confirmation and track message delivery. | [Confirm an outgoing transfer](https://trust.myaza.co/documentation/travel-rule-confirmation/markdown) |
| Events, current status and safe notification handling. | [Receive Travel Rule updates](https://trust.myaza.co/documentation/travel-rule-webhooks/markdown) |
| Signed control proof and separate address review. | [Self-hosted wallets](https://trust.myaza.co/documentation/travel-rule-self-hosted/markdown) |
| Exercise information gaps, review and stopped transfers. | [Test and troubleshoot](https://trust.myaza.co/documentation/travel-rule-testing/markdown) |

## What this feature includes

When a policy permits identity alternatives, the missing-information form lets you
choose one accepted option. For a government ID, enter its number, choose the actual
ID type and provide its issuing country. Business-only rules can accept an LEI.
Do not guess an identifier's type. Existing untyped records are not converted, and
completing these fields does not verify the person's or company's identity.

- A governed rule library and guided rule builder.
- Organisation and environment-scoped policy versions.
- Impact testing against recent crypto transactions before publication.
- Draft-first publication with an immutable publisher record for every active version.
- Immutable assessment generations and policy snapshots.
- Plain-language API and webhook summaries with the complete evidence retained.
- Idempotent information submission when a transfer is missing required data.
- Deterministic, non-billable Sandbox scenarios through the API.

Myaza combines information checks with a Crypto Provider Directory, address book and governed institutional connections. A directory entry does not prove wallet ownership or establish a messaging connection. Live exchange requires a reviewed connection with the receiving institution. Your organisation remains responsible for the jurisdictions, thresholds and information requirements applicable to its regulated activity.

## Integrate with an AI agent

Use the [AI integration guide](https://trust.myaza.co/documentation/ai-integration/markdown) for the product index, downloadable skills and machine-readable API contracts. Start with the Travel Rule skill and fetch only the guides needed for your workflow.