Case · Cross-border payments platform

One platform for money that crosses borders.

We researched, designed and built ORRERY: wallets, payouts, FX, crypto and compliance in one product.

12Currencies
5Fiat and crypto providers behind one interface
40+Product flows, web and mobile
End to endResearch, design, build and operation by one Sednor team

Client and partner names are withheld under NDA.

The starting point

Complex money, scattered tools.

The client served businesses that send international payouts every week. Their finance teams needed one system they would trust with large amounts.

ProblemWhat it cost the operator
Two or more provider dashboards to move one batchBalances, limits and fees in different places; slow routing decisions
Compliance requests handled by email and spreadsheetNo proof of who answered what, and when
No quote before a payoutUnexpected rates discovered after the payment landed
One failed line could block a whole batchBatches restarted instead of fixed

Problem

  • Two or more provider dashboards to move one batch
  • Compliance requests handled by email and spreadsheet
  • No quote before a payout
  • One failed line could block a whole batch

What it cost the operator

  • Balances, limits and fees in different places; slow routing decisions
  • No proof of who answered what, and when
  • Unexpected rates discovered after the payment landed
  • Batches restarted instead of fixed
What we did

We built the whole product, from research to a platform in daily use.

One Sednor team of eight: five developers, a QA engineer, a UI/UX designer and a manager.

ORRERY on a foldable phone: the home screen on the cover display, and payment routing with the overview on the inner display.
  1. 01Researched the problem

    Stakeholder and in-depth interviews with finance, treasury, compliance and payment-operations staff; jobs to be done; a review of how Wise Business, Airwallex, Payoneer and legacy bank portals handle quotes, recipients and compliance.

  2. 02Defined the product

    An information architecture of five branches, with no task deeper than three levels; user flows for every module; a map of seven compliance steps, five providers and twelve currencies.

  3. 03Designed the product and the brand

    Wireframes, a clickable payout prototype, high-fidelity web and mobile UI, a design system and the ORRERY identity.

  4. 04Built the platform

    Everything behind the screens: the ledger and routing engine, integrations with five fiat and crypto providers, the admin and operations tools, and the web and mobile apps, running on AWS.

  5. 05Tested and shipped

    Usability sessions with finance and compliance users on the prototype, flow-by-flow handoff with component specs and design tokens, and QA of every build against the design before release.

  6. 06Kept developing it

    New modules, flows and design-system updates since the first release, shaped by feedback from operators and compliance teams.

Product decisions

Three decisions shaped every flow.

01

Show the number before the money moves.

“I want the quote first, with the fee, with the timer.”

Every payout and conversion opens on a quote: rate, fee and recipient amount, with a validity timer. An expired quote refreshes in place, and nothing is sent until the operator has read the numbers.

ORRERY FX conversion over the dashboard: the quote has expired and the operator is asked to refresh it before converting.
02

Make compliance a conversation, not a wall.

“I need one list, one owner and a trail an auditor can read.”

Requests for information live in one place with statuses, due dates, sources and an audit trail.

ORRERY requests for information: counts of requests needing action, under review and resolved, and the list with type, due date and status.
03

Let admins see why a payment took its route.

“Show me balances and fees side by side and let me route in one click.”

Provider accounts, routing and an approval queue expose every decision, with explicit approve and reject steps.

ORRERY pending approvals: a queue of transfers with reason, creator, waiting time and amount, two selected for approval.
The platform

A ledger at the core, every provider on its own orbit.

Every module sits around a single ledger and routing core. The closer a module is to the core, the more often an operator uses it.

ORRERY's portfolio screen on a laptop: total value, balances in USD, USDC, USDT, BTC and ETH, and recent transactions.

Ledger and routing

One source of truth for every balance; routing rules pick the provider and rail for each payment.

Wallets and global view

Wallets and virtual accounts in 12 currencies, in one dashboard.

Recipients

A recipient list with recent payouts, and a four-step add flow ending in a full summary.

Batch payouts

File upload, live quotes per currency, and row-level error fixing without re-uploading.

FX conversion

Live rate, a 30-second quote hold, and conversion on web and mobile.

Crypto and settlements

USDC and USDT transfers, trades, and fiat or crypto settlement to whitelisted destinations.

Onboarding and KYB

Seven-step business verification with a persistent stepper and a final review.

Compliance (RFI)

Requests for information with owners, statuses, sources and an audit trail.

Approvals

An approval queue with waiting time, bulk actions and second-approver limits.

Provider admin

Five fiat and crypto providers, their accounts and routing, managed in one place.

Key flows

Dense where it has to be, explicit everywhere.

Getting a business verified

Business verification is the longest form on the platform, so it had to feel short. The stepper stays visible and shows what is left; country and entity type shape the questions that follow, so nobody answers twice; every section is summarized and confirmed before it is sent.

ORRERY business verification, step 1 of 7: country of registration, entity and business type, with the stepper on the left.

Paying out in many currencies

Batch payouts and FX conversion move the most money. Both lead with how long the quote is valid, the rate, the fee and exactly what the recipient receives. Invalid rows are fixed inside the batch rather than re-uploaded.

ORRERY batch payout confirmation: quotes for EUR, GBP and CAD with rate, fee and recipient amount, the transaction list and a summary.
ORRERY batch payout with five rows to fix inside the batch, each with its error and a field to correct it.

Answering a compliance request

Compliance staff work in a queue all day. Each request keeps the questions, the linked transaction, the answers in progress and the audit trail on one screen, and drafts save as they type.

ORRERY request for information RFI-20418: the linked transaction, the audit trail and two questions to answer.

Recipients

Recipients are where payment errors begin, so the list and the add flow are built for certainty.

Crypto and settlements

Moving between fiat and crypto is where operators make the most expensive mistakes, so settlements show destination, timing and approval limits before anything moves.

Global view

One dashboard for twelve currencies: wallets, virtual accounts and transactions.

On a phone

The same system in your pocket.

A currency conversion runs end to end in three steps: set the amounts, review the locked rate, get a confirmation with a reference ID.

ORRERY mobile app, step 1 of a currency conversion: amounts and the live rate.ORRERY mobile app, step 2: review with the locked rate before converting.ORRERY mobile app, step 3: conversion complete, with a reference ID.
Brand and design system

One core, every orbit.

We named and branded the product after its architecture: one core, every rail and provider on its own orbit. The mark is two circles in a precise eclipse, the instant the right rail crosses the right transfer.

ORRERY brand board: the eclipse mark and wordmark, the idea behind the name, the color palette and light and dark lockups.

Palette

Midnight, Navy ink, Platinum and Steel, with one point of Signal blue: used once per screen, for the one action that matters.

Design system

Tokens first, then components. Every control has default, hover, pressed, focus, error, disabled and loading states; status chips always carry a label.

Redesign

After the first release proved the flows, we rebuilt the interface around one navigation, denser tables and a strict 16 px grid.

Contact

Let's get your platform moving money.

Bring a business plan, a prototype or just an idea. No technical specification needed: we'll work out the rest together.

Talk with Nikita

Delivery Lead at Sednor