Ali Faraahani
Portfolio
Real productIQPayzPayments · Wallets · Service operations

Building a modern payment ecosystem

I designed mobile-first deposits and withdrawals across online, crypto, and assisted offline payments, with clear fees, status, and recovery.

What changed?

5,000+

payments per month

Monthly volume; not a growth percentage.

5

partner sites

Reported number of partner sites.

−15%

deposit support tickets

Reported decrease in deposit-related tickets.

~20 sec

online withdrawal

Reported online withdrawal time.

The problem & the evidence

Where the problem came from

The product grew out of market needs and shopping experiences in Iraq, where banks did not share a unified network. Customers and merchants needed payment options that worked across this fragmented infrastructure, including assisted offline payments.

  • Iraqi market needs
  • Shopping experience
  • Fragmented banking network
How it was measured
The original case study reports monthly payment volume, partner sites, the change in deposit-related tickets, and online withdrawal time.
A/B testing

Case-specific A/B results are not documented.

Measurement context

Raw queries, ticket baselines, and the method used to aggregate withdrawal time are not supplied here.

Screens & design decisions

Online deposit flow

Method, amount, fee, and provider handoff in one continuous path.

Crypto deposit flow

Network choice and irreversible transfer details appear before commitment.

Offline payment receipt upload

Receipt evidence supports a payment rail that requires human approval.

Irreversible transfer warning

Risk friction appears at the moment it can still prevent a mistake.

Payment system states

Pending, confirming, successful, and rejected share one operational language.

My direct work

  • Owned the mobile-first payment experience from zero to one.
  • Designed online, crypto, and assisted-offline deposit and withdrawal.
  • Aligned transaction behavior with backend and operations.

What I learned

A payment ecosystem feels unified when cost, risk, status, and recovery share one contract.

More on the decisions

Different rails, one promise

Merchants needed online, crypto, and assisted offline deposits to fund product wallets. Each rail had different fees, limits, confirmation times, provider responses, and failure modes—but users still needed one coherent explanation of what was happening.

Cash was not an edge case

Local research showed uneven trust in digital banking. Offline payment with receipt and operational approval therefore became a first-class rail, not a legacy exception hidden at the end of the flow.

Design the state machine before the screen

Method selection, fees, provider handoff, evidence, warnings, and recovery were organized around explicit Pending, Confirming, Success, and Rejected states. That common contract aligned backend, operations, support, and the user experience.

Choose “Save as PDF” in the print dialog to save the current page.