Future-state concepting for a cross-border B2B payments platform by Zach SmythFuture-state concepting for a cross-border B2B payments platform by Zach Smyth

Future-state concepting for a cross-border B2B payments platform

Zach Smyth

Zach Smyth

Overview

PayRecs is a B2B payments platform for organizations that move money across many entities and currencies — parent and child banks, inbound and outbound flows, approvals, and exception handling, all in one place. I partner with the founding team as an ongoing product design and front-end prototype partner, concepting future-state features and keeping the experience clear as the product grows.
Multi-entity home — inbound and outbound activity across currencies at a glance
Multi-entity home — inbound and outbound activity across currencies at a glance

The challenge

Cross-border, multi-entity payments are inherently complex — currencies, funding accounts, approval chains, rejects and reconciliation. Every new capability is a chance to make the product heavier. The team needed a design partner who could push the roadmap forward on discoverability, retention, and engagement while protecting the simplicity their customers value most.

Approach

Embedded with the founders as an ongoing partner, so design thinking is part of how the product evolves rather than a one-off engagement.
Concepted future-state features and flows aimed squarely at discoverability, retention, and engagement.
Designed the core surfaces — a multi-entity dashboard, the payments ledger with status and currency filters, a guided send flow, approvals, accounts, and cases.
Built the screens as clickable, front-end prototypes so the team could react to the real thing, not just static comps.
Ran a structured UX review of the prototype, turning findings into prioritized, actionable fixes.
Held every decision to one bar: does this make the product more capable without making it feel more complex?
The payments ledger — filter by status, currency and funding account across a multi-currency book
The payments ledger — filter by status, currency and funding account across a multi-currency book

The solution

An ongoing stream of product concepting and built prototype work that moves the roadmap forward while holding the line on simplicity. The surfaces make a genuinely complex payments operation feel calm: a multi-entity home that reads inbound and outbound activity across currencies at a glance, a payments ledger you can filter by status, currency and funding account, a step-by-step send flow that keeps a cross-border transfer simple, and clear accounts and approvals. The throughline is turning a complex payments product into something that feels obvious to use — which is exactly the feedback the team hears most from their own customers.
Send Payment — a guided flow that keeps a cross-border transfer simple
Send Payment — a guided flow that keeps a cross-border transfer simple
Accounts — USD and multi-currency accounts across the entity hierarchy, pay-from in one tap
Accounts — USD and multi-currency accounts across the entity hierarchy, pay-from in one tap
Like this project

Posted Mar 26, 2025

Concepted and built clickable prototypes for a multi-entity, multi-currency payments product, so the team could react to the real thing, not comps.