Redesigning Divest around a remittance-first experience

I was one of three designers working on the V3 redesign. My primary ownership was the Money Exchange experience end-to-end, alongside the Rates and Profile Management sections. I worked closely with Product, Engineering and QA to translate product requirements into clear flows, resolve edge cases and maintain consistency across the redesigned experience.

Divest was repositioning from being primarily associated with crypto toward a remittance-first financial product. The redesign needed to support users who move money across African markets while still accommodating Divest's existing crypto experience.

This created a broader UX challenge than simply updating the interface. The product needed clearer navigation between different financial modes, a more understandable Money Xchange experience, visible exchange rates and a profile structure that could support security, account management and future growth.

The core challenge was making a growing financial product easier to understand without hiding the complexity behind the transactions. Users needed to know what they were sending, where their money was going, what rate they were receiving and what would happen next.

At the same time, the redesign had to support different currencies, payment methods, KYC requirements, transaction limits, validation states and failure scenarios.

One of the early design challenges was giving the product a clearer structure as Divest expanded beyond its original crypto-first experience. The redesigned architecture needed to separate major financial modes while still making the overall product feel like one system.

Money Exchange was the largest area of my ownership. The flow had to support the complete journey from entering an amount and selecting currencies to choosing a payment method, providing recipient details, reviewing the transaction and completing payment.

The complexity wasn't in the happy path alone. The experience also needed to handle KYC gates, amount limits, beneficiary validation, country-specific payment methods, failed verification and changing transaction states.

Financial flows are only as good as the states users encounter when something doesn't go as expected. I designed the experience around insufficient balances, amount limits, KYC verification requirements, invalid recipient details and payment failures rather than treating them as secondary screens.

Rates should not be a dead-end information page. I designed the Rates experience so users could understand available conversion rates and move directly into the relevant transaction.

The “Send” action carries the selected currency pair into Money Exchange, reducing repeated input and creating a direct path from information to action.

Rather than treating Profile as a collection of settings, I structured it around the tasks users actually need to manage: personal information, payout accounts, KYC and limits, security and legal information.

The work involved close collaboration with Product, Engineering and QA. Requirements often exposed edge cases that changed how a flow needed to behave, so design decisions had to account for both the intended experience and the underlying product rules.

I used these conversations to refine flows, resolve ambiguity and make sure the final screens were practical to build and consistent across the product.

The work evolved through repeated refinement of transaction states, hierarchy and navigation. Rather than treating the first high-fidelity design as final, I used edge cases and implementation feedback to simplify the experience where possible and make important information more visible.

The redesigned experience established a clearer foundation for Divest's remittance-first direction and created a more structured system for money movement, rates and account management.

Redesigning a financial product is rarely about making individual screens cleaner. The harder problem is making the relationships between screens, rules and decisions easier for users to understand.

This project strengthened how I think about state management, progressive disclosure and trust in financial flows — especially when a user is moving real money through a system with multiple constraints.