Notifications
Clear all
Topic starter
10/06/2026 10:43 pm
TL;DR: Stablecoins are now operating as payment infrastructure at cross-border scale, and the FATF Travel Rule is forcing VASPs to embed originator and beneficiary checks directly into transaction flows, according to SumSub. Compliance models built around manual, after-the-fact review no longer match the speed or jurisdictional complexity of stablecoin transfer.
NHIMG editorial — based on content published by SumSub: stablecoin compliance and the Travel Rule
Questions worth separating out
Q: How should VASPs build Travel Rule compliance into stablecoin payments?
A: VASPs should treat Travel Rule handling as part of the payment workflow, not a separate compliance task.
Q: Why do stablecoins create more compliance complexity than traditional transfers?
A: Stablecoins combine real-time settlement with cross-border reach, so compliance must keep pace with the transfer itself.
Q: What breaks when compliance sits outside the transaction flow?
A: When compliance is separate from execution, organisations lose timing, consistency, and auditability.
Practitioner guidance
- Embed Travel Rule checks in the transaction path Place originator and beneficiary data collection inside the payment workflow so the transfer cannot proceed without the required compliance state.
- Standardise jurisdiction-specific policy routing Maintain versioned rules for thresholds, reporting obligations, and supervisory expectations by market so the same transfer type is treated consistently across jurisdictions.
- Instrument compliance for auditability Log when information is collected, transformed, transmitted, and confirmed so investigators can reconstruct the full control path later.
What's in the full report
SumSub's full whitepaper covers the operational detail this post intentionally leaves for the source:
- How the FATF Travel Rule is applied to stablecoin transactions in practice
- The impact of MiCA and the GENIUS Act on cross-jurisdiction compliance design
- How compliance infrastructure supports scalable, cross-border operations without interrupting user experience
- A practical checklist for VASPs building integrated, compliant stablecoin flows
👉 Read SumSub's whitepaper on stablecoin compliance and the Travel Rule →
Stablecoin travel rule compliance: what changes for VASPs?
Explore further
11/06/2026 2:52 am
Stablecoin compliance has become an identity and governance problem, not just a regulatory one. Once originator and beneficiary information must move with the transaction, the control surface looks less like a policy document and more like an identity workflow. The important question is whether the organisation can preserve accountability across counterparties, jurisdictions, and execution speed. Practitioners should treat the transaction path as a governed system, not a passive transport layer.
A few things that frame the scale:
- 80% of identity breaches involved compromised non-human identities such as service accounts and API keys, according to Ultimate Guide to NHIs.
- Only 5.7% of organisations have full visibility into their service accounts, according to Ultimate Guide to NHIs.
A question worth separating out:
Q: Who is accountable when stablecoin transfers cross multiple jurisdictions?
A: Accountability sits with the VASP orchestrating the transfer, but it is shared across the operational chain that collects, validates, and transmits the required information. The practical issue is not only legal responsibility but whether the control design can prove consistent handling under different rulesets.
👉 Read our full editorial: Stablecoin compliance is moving into transaction flows
