Home / Companies / Didit / Blog / Post Details
Content Deep Dive

The 6 Travel Rule Statuses & the Sunrise Issue

Blog post from Didit

Aggregate trend data notice

Excluded from normalized aggregate trends after staff review: 3056 posts were attributed to March 2026; 671 shared March 14, 2026. The preceding six-month median was 13.5 posts.

Review evidence: 3,056 posts in March 2026; 671 shared March 14, 2026; preceding six-month median 13.5. Reviewed August 9, 2026.

This company's pages remain public, but its content is excluded from normalized aggregate trends. Unfiltered raw trends and advanced filtering are available to Accelerate and Lead accounts.

Post Details
Company
Date Published
Author
Didit
Word Count
1,421
Company Posts That Month
190
Language
English
Hacker News Points
-
Post removed?
No
Summary

Didit offers a structured solution for handling the FATF Travel Rule obligations related to crypto transfers by introducing a clear six-status model, providing a systematic approach to managing compliance challenges such as the "sunrise issue," which arises from uneven global adoption of the rule. The statuses—UNKNOWN, COMPLIANT, PENDING_ACTION, PENDING_COUNTERPARTY, FAILED, and EXEMPT—help categorize the state of each transfer, identifying responsibilities and actions required from either the originator or counterparty. This framework ensures each obligation is resolved with clarity, helps manage non-adopting jurisdictions, and creates an audit trail, thereby reducing ambiguity and manual interpretation of compliance statuses. By integrating these statuses into Transaction Monitoring, Didit allows for seamless tracking and management of crypto transfers, ensuring that businesses can document and automate compliance processes effectively, while also offering wallet screening services starting at a minimal cost.

Trends Found in this Post

No tracked trend matches for this post yet.

Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.