Industry
Fintech
Company
Get Orbital
Role
Product Designer
Status
Shipped
Fintech Compliance Platform- Inbound Payments
Fintech Compliance Platform- Inbound Payments
Fintech Compliance Platform- Inbound Payments
Designing a scalable compliance solution to support evolving Travel Rule requirements across core financial flows.
Project Overview
Project Overview
The EU Travel Rule requires capturing regulated sender and beneficiary data across crypto transactions. I designed a scalable solution to integrate this into existing payment flows without disrupting user experience or completion rates.
The EU Travel Rule requires capturing regulated sender and beneficiary data across crypto transactions. I designed a scalable solution to integrate this into existing payment flows without disrupting user experience or completion rates.
Users initiate a payment flow
Users initiate a payment flow
If the beneficiary does not exist, users create one — triggering Travel Rule data capture.
Product Walkthrough Video
Note: The video reflects a more recent version of the product using the updated design system. The designs shown in this case study were created prior to this update.
Problem
Problem
Existing payment flows did not capture required regulatory data. Adding steps risked drop-off, complexity, and inconsistent compliance.
Existing payment flows did not capture required regulatory data. Adding steps risked drop-off, complexity, and inconsistent compliance.
Approach
Approach
Designed a scalable compliance layer across transaction flows and beneficiary creation, capturing required data only when needed. Ensuring consistency through reusable patterns while minimising disruption to critical actions.
Designed a scalable compliance layer across transaction flows and beneficiary creation, capturing required data only when needed. Ensuring consistency through reusable patterns while minimising disruption to critical actions.
Discovery & System Definition
Discovery & System Definition
Travel Rule requirements introduced complex conditional flows across payment states, sender types, and compliance scenarios. Early discovery focused on defining how regulatory data capture could integrate into existing payment journeys with minimal disruption to critical financial actions.
Working across product, compliance, and engineering constraints, we mapped reusable interaction patterns and progressive disclosure models to support scalable implementation across multiple transaction flows.
Travel Rule requirements introduced complex conditional flows across payment states, sender types, and compliance scenarios. Early discovery focused on integrating regulatory data capture into existing payment journeys with minimal disruption.
Working across product, compliance, and engineering constraints, we explored scalable interaction patterns for multiple transaction flows.
Travel Rule requirements introduced complex conditional flows across payment states, sender types, and compliance scenarios. Early discovery focused on integrating regulatory data capture into existing payment journeys with minimal disruption.
Working across product, compliance, and engineering constraints, we explored scalable interaction patterns for multiple transaction flows.
Entry points into compliance flows
Compliance requirements were surfaced contextually through transactions, notifications, and payment states.
Conditional disclosure logic
Required information adapted dynamically based on sender relationship, ownership, and asset type.
Progressive completion states
Users complete only the information required for the specific transaction context, reducing disruption to payment flows.
Discovery Exploration
Discovery Exploration
Early exploration focused on identifying scalable entry points for compliance actions across existing payment journeys.
Early exploration focused on identifying scalable entry points for compliance actions across existing payment journeys.
Notification-driven compliance actions
Concept exploration for using the notifications centre as an alternative entry point for outstanding compliance and transaction information requests.
Inline compliance entry points (homepage)
Exploration of how “information required” states could surface across the homepage dashboard, transaction history, and account views without interrupting core payment workflows.
Notification-driven compliance actions
Concept exploration for using the notifications centre as an alternative entry point for outstanding compliance and transaction information requests.
Inline compliance entry points (homepage)
Exploration of how “information required” states could surface across the homepage dashboard, transaction history, and account views without interrupting core payment workflows.
Transaction detail exploration
Exploring where compliance actions could integrate within existing transaction flows.
Modal interaction exploration
Testing progressive disclosure patterns for collecting additional regulatory information.
Embedded compliance within payment details
Early exploration of inline compliance states, editable sections, and contextual information capture directly within transaction views.
Modal-based compliance capture
Concept for handling additional regulatory requirements through focused modal interactions layered over existing payment flows.
Final Designs
Initial exploration informed a scalable approach for embedding Travel Rule requirements into existing payment journeys.
Compliance triggered inline
Appears only when required, preserving flow continuity.
Final Designs
Initial exploration informed a scalable approach for embedding Travel Rule requirements into existing payment journeys.
Compliance triggered inline
Appears only when required, preserving flow continuity.
Source of funds selection
Required data is collected step-by-step to reduce friction.
Sender type — Individual vs company
Individual details — Progressive data capture (Modal dropdown)
Inbound payment — Completed status
A single compliance pattern scales across products.
Inbound payment — Completed status
A single compliance pattern scales across products.
Inbound payment — Completed status
A single compliance pattern scales across products.
Trade offs & Risks
Trade offs & Risks
Prioritised payment completion over upfront compliance by deferring non-critical data capture.
Adopted a single reusable modal instead of flow-specific solutions, increasing internal complexity but ensuring consistency across products.
Prioritised payment completion over upfront compliance by deferring non-critical data capture.
Adopted a single reusable modal instead of flow-specific solutions, increasing internal complexity but ensuring consistency across products.
Scope Expansion & Platform Impact
Scope Expansion & Platform Impact
Regulatory changes expanded requirements across users, products, and jurisdictions during delivery.
The solution evolved from flow-specific handling to a platform-wide compliance model applied consistently across Payments, Payouts, Receivables, and Wallets.
Regulatory changes expanded requirements across users, products, and jurisdictions during delivery.
The solution evolved from flow-specific handling to a platform-wide compliance model applied consistently across Payments, Payouts, Receivables, and Wallets.
How The Solution Evolved
How The Solution Evolved
Shifted from minimising surface area within individual flows to defining a reusable compliance pattern applied across the platform.
Shifted from minimising surface area within individual flows to defining a reusable compliance pattern applied across the platform.
Impact & Outcomes
Impact & Outcomes
• Embedded Travel Rule compliance into existing payment journeys without disrupting core transaction flows.
• Created scalable patterns that supported rollout across multiple transaction types and compliance scenarios.
• Reduced operational and UX complexity through reusable components and shared interaction models.
• Successfully supported client onboarding and adoption following rollout of the new compliance experience.
• Embedded Travel Rule compliance into existing payment journeys without disrupting core transaction flows.
• Created scalable patterns that supported rollout across multiple transaction types and compliance scenarios.
• Reduced operational and UX complexity through reusable components and shared interaction models.
• Successfully supported client onboarding and adoption following rollout of the new compliance experience.
• Embedded Travel Rule compliance into existing payment journeys without disrupting core transaction flows.
• Created scalable patterns for multiple transaction types and compliance scenarios.
• Reduced complexity through reusable components and shared interaction patterns.
• Successfully supported client onboarding following rollout of the new compliance experience.