Capture Travel Rule data inside your payment flow
Capture the originator and beneficiary information Travel Rule requires inside your payment flow, and pass it into the compliance systems you already run, with no parallel system to build.
Comply with regulations effortlessly, with Travel Rule data capture built-in
Configurable capture
Collect full legal name, date of birth, and country or place of birth, with fields configurable to your requirements.
One time collection
Captured once at first transaction, then reused so returning users skip straight to confirmation, stored in line with GDPR.
Screening built in
Sanctions & IP screening runs on every payment, against OFAC, UK, UN, and EU sanctions lists.
Fits your existing stack
Data flows into the compliance systems you already run, in the formats your controls read directly, with no reformatting or parallel tooling.
Global compliance
Adapts to each region's Travel Rule rules and thresholds, so you stay compliant across markets.
Verify ownership
Verify ownership of unhosted wallets with secure authentication, so even self-custodial accounts can comply.
FAQ
It requires sharing originator and beneficiary information for transfers above set thresholds, so regulated parties can screen and record who is sending and receiving funds.
It is captured inside your payment flow, including full legal name, date of birth, and country or place of birth, collected once and reused.
Yes. Data is delivered in the formats your controls read directly, so it flows into the systems you already run with nothing to reformat.
Securely and in line with GDPR. It is captured once at first payment and reused, so returning users go straight to confirmation.
Yes. Sanctions & IP screening is built into the flow.
Yes. It adapts to each region's Travel Rule rules and thresholds, so you stay compliant across markets.
No. Details are collected once, in about two minutes, and reused on every future payment.