On this page
Webhook events
Subscribe to the Travel Rule events in Developers → Webhooks:
| Event | Meaning |
|---|---|
travel_rule.required | The active policy requires Travel Rule information. |
travel_rule.data.pending | Required information is still missing. |
travel_rule.assessment.completed | The current validation generation completed. |
travel_rule.data.completed | The required information package is complete. |
travel_rule.mismatch.detected | Identity, sanctions, VASP or wallet evidence needs action. |
travel_rule.failed | Validation failed because of a service problem. |
travel_rule.exchange.updated | Preparation, delivery or an authenticated institutional reply changed. Read current clearance; this event does not grant execution permission. |
Every event includes the assessment ID, validation generation, status, field coverage, exact API paths and the same plain-language summary. Webhooks never contain the regulated party values submitted to Myaza.
Use the shared webhook authentication and testing guides. Verify the signature against raw bytes, reject stale signatures and deduplicate the event ID before applying an action. Delivery can be repeated or arrive after a newer revision. Fetch the current transfer before deciding what to do; a historical event never grants fresh wallet authority.