FATF Recommendation 16 — the "Travel Rule" — has moved from principle to production over the past five years. Southeast Asian regulators now require VASPs to transmit originator and beneficiary information for cross-institution transfers. But once Travel Rule becomes daily operations, operators hit a two-sided problem: the two ends of the same transfer may use different protocols (Notabene, TRP, Sygna, TRISA), each with its own field semantics, encryption and identity verification. This article covers IVMS101, the Sunrise issue, cross-protocol bridging and a productized compliance data plane — a reference for Southeast Asian VASPs.

1. Industry Background: Five Years of Travel Rule

1. 2019–2021 — FATF issues Recommendation 16, requiring VA transfers > USD 1,000 to carry originator/beneficiary information.
2. 2022–2023 — Singapore MAS, the Philippines BSP, Thailand SEC operationalize Travel Rule.
3. 2024–2025 — Malaysia SC, Indonesia Bappebti, Vietnam, Cambodia join.
4. 2025–2026 — the region enters production, with cross-protocol interoperability as the core challenge.

Across SoonTech's Southeast Asia white-label clients, protocol heterogeneity has overtaken "field gaps" as the dominant Travel Rule pain point.

2. Market Pain Points: Five Interoperability Challenges

• Protocol heterogeneity — Notabene, TRP, Sygna, TRISA each with distinct encryption and message formats.
• Sunrise issue — the counterparty may not be on any protocol, leaving nowhere to send.
• IVMS101 field semantics — jurisdictions disagree on name, address, ID number formats.
• Identity verification — no unified directory to verify counterparties as licensed VASPs.
• Audit trails — how does the local regulator audit delivery failures, retries and rejections?

3. Data and Trends

Travel Rule has moved beyond "do we send it" into "how do we send it reliably across protocols, fields and jurisdictions with defensible audit".

4. Case Analysis: End-to-End Travel Rule Flow

Anonymized scenario: SG VASP A transfers USDT 50,000 to ID VASP B.

• Step 1: A initiates transfer; risk engine flags Travel Rule threshold.
• Step 2: compliance data plane looks up VASP directory; B uses Sygna.
• Step 3: A runs Notabene; SoonTech bridges IVMS101 → Sygna transparently.
• Step 4: B's KYC team receives, matches beneficiary, acknowledges.
• Step 5: if 24h passes without ACK, A auto-enters Sunrise flow.
• Step 6: full event stream into compliance log.

Interoperability is not "add more protocols" — it is turning IVMS101 mapping, protocol bridging, VASP directory, Sunrise handling and audit into a committable compliance data plane.

5. SoonTech Travel Rule Interoperability Capabilities

5.1 IVMS101 field mapping

• IVMS101 standard templates.
• Jurisdiction differences (name / address / ID / DOB).
• Missing-field prompts and remediation.

5.2 Cross-protocol bridging

• Notabene, TRP, Sygna, TRISA.
• Auto message-format and encryption translation.
• Zero manual intervention.

5.3 VASP directory

• Merged multi-source directory.
• Custom whitelist / blacklist.
• Every directory update logged.

5.4 Sunrise handling

• Auto Sunrise flow when counterparty is off-protocol.
• Email / API fallback disclosure.
• Cases logged into compliance stream.

5.5 Delivery observability

• Success / failure / retry / rejection visualized.
• Delivery SLA reports.
• SIEM export.

5.6 Compliance data plane

• Unified log format.
• Multi-regulator exports (MAS / SC / Bappebti / BSP).
• One data source, multiple outputs.

6. Enterprise Implementation Suggestions

1. Map jurisdictions.
2. Define protocol strategy — ≥2 major protocols + bridging.
3. Build a VASP directory.
4. Publish a Sunrise workflow.
5. Ship delivery observability.
6. Consolidate into a compliance data plane.

Vendor Selection Checklist

• ≥3 Travel Rule protocols + bridging.
• IVMS101 field mapping and localization templates.
• Multi-source VASP directory merging.
• Sunrise fallback disclosure workflow.
• Delivery SLA reports + SIEM integration.
• Multi-regulator compliance log export.

7. Future Outlook

1. Protocol convergence — bridging becomes default.
2. Neutral VASP directories — cross-protocol neutral services emerge.
3. Data plane productization — KYT, sanctions, tax share the plane.

Travel Rule is no longer "one more feature" — it is the first piece of a compliance data plane strategy.

FAQ

Q1: Does a VASP need every Travel Rule protocol?

A1: No. SoonTech recommends ≥2 major protocols + bridging.

Q2: How is the Sunrise issue handled?

A2: Email + API fallback disclosure with logged cases for audit.

Q3: Do IVMS101 fields differ significantly across jurisdictions?

A3: Moderately. National ID, tax ID and address formats vary; SoonTech provides local templates.

Q4: How to avoid "pseudo-VASPs" in the directory?

A4: Multi-source merging + whitelist review + risk assessment before activation.

Q5: How to negotiate when delivery success is low?

A5: SLA reports. Traceable delivery reports support workflow improvement negotiations.

Conclusion

Travel Rule has entered the era of interoperability + compliance data plane. Those who turn IVMS101 mapping, protocol bridging, VASP directory, Sunrise handling and audit trails into a committable product will earn institutional trust in Southeast Asia's next compliance cycle.

🌐 Build secure and scalable Web3 platforms with SoonTech.

Explore our solutions for White Label Crypto Exchanges, Prediction Markets, MPC Wallets, Matching Engines, Liquidity Integration, and Compliance.