Zing.gg, one API from application to settlement.
I designed the merchant onboarding and agent back office for a payments API, cutting eight tabs per decision to one.
Role
Senior Product Designer
When
2019 - 2020
Team
PM, compliance ops, 4 engineers
Surfaces
Merchant portal · Agent back office · Onboarding
Background
Zing.gg had a payments engine with KYC and AML built into a single API. It needed a surface for two user groups, merchants signing up and the agents reviewing them, on one backbone.
Process
Service mapping
Mapped the merchant journey across capture, verify, review and settle.
User research
Half a day with each underwriter showed eight tabs and no risk context.
Wireframes & prototypes
Low fidelity wireframes of the agent back office, validated with the compliance team.
Production UI
Every state designed in high fidelity, with the spec ready on build day.
Agent back office · application review screen
Onboarding flow · desktop primary, mobile responsive
Outcome
Onboarding and back office went live in one release window and "no more eight tabs" became a design rule.