Industry
Fintech
Company
Get Orbital
Get Orbital
Role
Product Designer
Status
Shipped
Fintech Compliance Platform- Inbound Payments
Fintech Compliance Platform- Inbound Payments
Fintech Compliance Platform- Inbound Payments
Crypto Travel Rule compliance at enterprise scale
The EU Crypto Travel Rule fundamentally changed how crypto payments, payouts, and wallet transfers operate. Get Orbital needed a scalable way to collect and transmit regulated sender and beneficiary data across products and jurisdictions—without disrupting existing payment flows or user trust.
The EU Crypto Travel Rule fundamentally changed how crypto payments, payouts, and wallet transfers operate. Get Orbital needed a scalable way to collect and transmit regulated sender and beneficiary data across products and jurisdictions—without disrupting existing payment flows or user trust.
Context & Scope
1. Enterprise crypto & payments platform operating across EU & Gibraltar
High-risk, regulated environment with evolving regulatory interpretation
Platform-wide impact across Payments, Payouts, Receivables, Wallets & Beneficiaries
Designed and shipped under active compliance, legal, and operational constraints
1. Enterprise crypto & payments platform operating across EU & Gibraltar
High-risk, regulated environment with evolving regulatory interpretation
Platform-wide impact across Payments, Payouts, Receivables, Wallets & Beneficiaries
Designed and shipped under active compliance, legal, and operational constraints
Problem
The new Travel Rule required additional sender and beneficiary data for certain crypto transactions, but existing payment flows were not designed to capture this information. Introducing extra steps risked increased drop-off, operational complexity, and inconsistent compliance across products and regions.
The new Travel Rule required additional sender and beneficiary data for certain crypto transactions, but existing payment flows were not designed to capture this information. Introducing extra steps risked increased drop-off, operational complexity, and inconsistent compliance across products and regions.
Goal
The goal was to enable Travel Rule compliance without breaking existing payment experiences. This meant capturing required regulatory data only when applicable, preserving completion rates, and creating a solution that could scale across products, regions, and evolving regulations.
The goal was to enable Travel Rule compliance without breaking existing payment experiences. This meant capturing required regulatory data only when applicable, preserving completion rates, and creating a solution that could scale across products, regions, and evolving regulations.
Scope
The solution needed to support crypto payments, payouts, wallets, and beneficiaries across EU and Gibraltar jurisdictions. It also had to accommodate both crypto-native and fiat-adjacent flows while remaining extensible to future regulatory expansion.
The solution needed to support crypto payments, payouts, wallets, and beneficiaries across EU and Gibraltar jurisdictions. It also had to accommodate both crypto-native and fiat-adjacent flows while remaining extensible to future regulatory expansion.
Constraints
Midway through delivery, regulatory interpretation expanded requirements Additional PDDL & PPOU modals were required for individuals and companies These requirements applied across Payments, Payouts, Receivables, Wallets, Beneficiaries The solution shifted from flow-specific to platform-wide compliance
Midway through delivery, regulatory interpretation expanded requirements Additional PDDL & PPOU modals were required for individuals and companies These requirements applied across Payments, Payouts, Receivables, Wallets, Beneficiaries The solution shifted from flow-specific to platform-wide compliance
Travel Rule entry point — Add information
Travel Rule entry point — Add information
Source of funds selection
Sender type — Individual vs company
Individual details — Progressive data capture (Modal)
Inbound payment — Completed status
Inbound payment — Completed status
Trade offs & Risks
To protect payment completion, upfront data capture was intentionally limited, accepting downstream follow-ups where required. A single configurable modal was chosen over multiple flow-specific UIs, increasing internal logic complexity in exchange for reduced UX fragmentation.
To protect payment completion, upfront data capture was intentionally limited, accepting downstream follow-ups where required. A single configurable modal was chosen over multiple flow-specific UIs, increasing internal logic complexity in exchange for reduced UX fragmentation.
Scope Expansion & Platform Impact
Midway through delivery, regulatory interpretation expanded requirements Additional PDDL & PPOU modals were required for individuals and companies These requirements applied across Payments, Payouts, Receivables, Wallets, Beneficiaries The solution shifted from flow-specific to platform-wide compliance
Midway through delivery, regulatory interpretation expanded requirements Additional PDDL & PPOU modals were required for individuals and companies These requirements applied across Payments, Payouts, Receivables, Wallets, Beneficiaries The solution shifted from flow-specific to platform-wide compliance
How The Solution Evolved
Existing payment and payout flows were reviewed end-to-end to identify compliant data capture points that would not interrupt completion. Early concepts focused on minimising surface area, leading to a single reusable compliance pattern rather than flow-specific solutions.
Existing payment and payout flows were reviewed end-to-end to identify compliant data capture points that would not interrupt completion. Early concepts focused on minimising surface area, leading to a single reusable compliance pattern rather than flow-specific solutions.
Impact & Outcomes
The solution enabled EU Travel Rule compliance across Orbital’s crypto products without breaking existing payment flows. Duplication across products was reduced through a shared compliance model, user friction was minimised through conditional data capture, and a scalable foundation was established for future regulatory change.
The solution enabled EU Travel Rule compliance across Orbital’s crypto products without breaking existing payment flows. Duplication across products was reduced through a shared compliance model, user friction was minimised through conditional data capture, and a scalable foundation was established for future regulatory change.