Industry

Fintech

Company

Get Orbital

Role

Sole Product Designer

Status

Shipped

Fintech Compliance — Inbound Payments

Designing regulatory compliance workflows for cryptocurrency transactions.

Project Overview

I designed scalable UX/UI workflows to integrate EU Travel Rule compliance into existing crypto payment journeys, capturing required sender and beneficiary data while minimising disruption.

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

Existing payment flows lacked the regulatory data required for compliance. Introducing additional steps risked increasing friction and transaction drop-off.

Approach

I developed reusable interaction patterns to capture compliance data when needed, balancing regulatory requirements, usability and technical constraints.

Discovery & System Definition

I mapped conditional requirements across transaction types, user scenarios and payment states, working with Product, Compliance and Engineering to define a consistent approach.

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

Early exploration focused on identifying scalable entry points for compliance actions across existing payment journeys.

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.

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.

Compliance status in pending transactions

Flags transactions requiring additional information

Compliance status in pending transactions

Flags transactions requiring additional information

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.

Compliance status in pending transactions

Flags transactions requiring additional information

Compliance status in pending transactions

Flags transactions requiring additional information

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

I prioritised payment completion by deferring non-critical data capture and using a shared modal pattern rather than separate solutions for each flow.

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.

Impact & Outcomes

Compliance: Integrated Travel Rule requirements across existing payment journeys.

Scalability: Established reusable patterns across multiple transaction types.

Successful rollout: Supported client onboarding with zero compliance-related support tickets.

Trade offs & Risks

I prioritised payment completion by deferring non-critical data capture and using a shared modal pattern rather than separate solutions for each flow.

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.

Impact & Outcomes

Compliance: Integrated Travel Rule requirements across existing payment journeys.

Scalability: Established reusable patterns across multiple transaction types.

Successful rollout: Supported client onboarding with zero compliance-related support tickets.

Trade offs & Risks

I prioritised payment completion by deferring non-critical data capture and using a shared modal pattern rather than separate solutions for each flow.

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.

Impact & Outcomes

Compliance: Integrated Travel Rule requirements across existing payment journeys.

Scalability: Established reusable patterns across multiple transaction types.

Successful rollout: Supported client onboarding with zero compliance-related support tickets.

Design System Governance