Follow confirmed deadlines, licence changes, new rules and enforcement updates. Each item links to its primary source and names the team most likely to act.
Evidence before interpretation
The regulatory record is stated in plain language. The “Atlas practical note” is a separate interpretation, not legal advice.
34
Changes tracked
Each one links to a source
2
Critical deadlines
Within the next 30 days
11
Future key dates
Across every change type
30/34
Explicit source-check dates
18 markets represented; every signal remains source-linked
Filter regulatory changes
Separate deadlines, active transitions and newly effective rules.
The CGA PDF contains 663 licence rows: 569 B2C and 94 B2B. Its displayed statuses split into 281 assessment, 207 indefinite, 60 expired, 50 revoked and 65 unqualified rows; only 60 unqualified rows have coherent terms covering the snapshot date.
What teams should check
Confirm eligibility, evidence requirements, local entity needs and application sequencing.
Joint remote-identification provisions apply immediately to new systems. Eligible solutions already in use may continue only while implementation work is demonstrable and must comply fully by 1 May 2027; the transition is not a general KYC exemption.
What teams should check
Check how the requirement affects onboarding, payments, monitoring, reporting and suppliers.
The Radar only includes changes linked to an official source. Deadlines move to passed states, ended monitoring windows are labelled only when a source supplies an end date, and older signals lose urgency without being presented as finished. Latest explicit source check: 2026-09-15. 30 of 34 signals currently store a signal-level source-check date; the remaining 4 show the broader market-profile review date instead and remain in the provenance backlog.
Editorial information only, not legal advice. Operator status can differ by product, domain and location. Commercial relationships are labelled and will never override regulatory status.