AstraPay

Designing One-Pass KYB Review for a 15K-Merchant Program

A partnership targeting ~15K SRC merchants created a capacity challenge for an approximately three-person KYB Operations team still handling BAU. I redesigned the desktop Admin Web review around backend-validated referral eligibility, a consolidated first-pass workspace, and Instant Approve for eligible clear cases, while retaining deeper review for exceptions. A whitelisted pilot and reviewer training preceded a roughly 3–5-month rollout. Actual time savings were not quantified.

Role: Product DesignerKYBMerchant OnboardingOperations DesignInternal ToolsRisk & Fraud
DESIGNING FOR OPERATIONS · KYB ADMIN WEB

One review for clear cases. Deeper review where it matters.

A partner onboarding program targeted roughly 15,000 SRC merchants while a small Operations team continued business-as-usual KYB. I redesigned the desktop review journey around eligibility, a single-page first pass, and a bounded approval path.

~15KPartnership cohort target
~3Ops reviewers including BAU
3–5 moProgram rollout window

Program scope, staffing and rollout—not verified throughput, acceptance uplift, or fraud reduction.

DESKTOP ADMIN-WEB DESIGN ARTIFACTS

The redesign reduced review navigation before it changed approval authority.

The documented baseline required four UI review steps plus verifier and approver. The two design artifacts below show the consolidated first-pass workspace and its separate Instant Approve action—without passing off an unverified baseline illustration as real UI.

Changed interface · Fewer navigation steps

Scan the relevant evidence in one continuous view

A single desktop view brings core merchant information and supporting documents together for the first review.

01Information density

Keep the data and documents within one scanning context instead of asking an operator to switch between four review steps.

02Action hierarchy

Make the approve action distinct from rejection, especially during repetitive review.

03Review depth

Only merchants who passed cohort validation and the first review could take the fast route.

INTERACTIVE ROUTING MODEL

Fast track is conditional—not a shortcut anyone can choose.

Follow the routing decisions behind the interface. This is an explanatory model of the documented workflow, not a live Admin Web system.

01 · COHORT ELIGIBILITY

Was the merchant submitted with a backend-validated SRC referral code?

Choose a cohort route above to explore what happens.

There is no verified time-to-review reduction, fraud-rate uplift, or approval-rate improvement in this record. The evidence supports a bounded rollout and a changed review design—not quantified operational efficiency.

Source: desktop design artifacts retained in the AstraPay portfolio CMS and project notes. The route selector illustrates documented business rules; it is not a live Admin Web routing control.

Capacity problem

A workload model exposed the cost of repeated review

The 15K figure is the SRC program target, not measured applications processed. Distributed over 3–5 months, ~3 reviewers would need roughly 45–80 SRC reviews each per workday in an even-demand model, before BAU. This is a model, not a measured rate.

15Ktarget cohortSRC merchants in the partnership program
3–5 morollout windowrough duration of the program rollout
~3Ops reviewersthe same team continued handling BAU KYB
~45–80/daymodeled SRC reviews / reviewer / day15K target divided by 3 reviewers and 3–5 months at ~22 workdays; assumes even distribution and excludes BAU.
Context

The same three reviewers also had ordinary KYB to run

The project came from an AstraPay partnership. The CMO asked Operations and Product to smooth the SRC onboarding path because roughly 15K merchants needed to move through KYB without stopping BAU work.

The Operations team handling the workload was only about three reviewers. The existing UI had four review steps. A verifier checked merchant data and documents, then an approver reviewed the case again before the final decision.

With a rollout of roughly 3–5 months, the problem was no longer how quickly one screen could be clicked. I needed to remove repeated work from clear cases without opening a faster route to merchants who were not eligible.

At this volume, click speed was not the main problem. Every clear case was paying for the same review depth.
Design decision

Move repeated review to eligible cases and exceptions

I proposed reusing the referral code, one-page review, Instant Approve, the exception queue, and removing the second approver for eligible clear cases. We worked through each change with Product, Ops, Tech, and the control functions to make sure it was feasible.

Standard KYB

Four UI steps, then verifier and approver

Every merchant moved through sequential review. Even after verification, a clear case still continued to a second approver.

Reasonable for general traffic, expensive when partnership volume arrives on top of BAU.
Fast-track cohort

One review for clear cases, deeper review for exceptions

Merchants from the validated cohort entered a one-page review. Clear cases could finish with Instant Approve. Cases with issues moved to secondary review.

The same data and documents were still checked. What changed was when a second review was actually needed.
Validation and control

Risk controls made a one-pass path defensible

SRC merchants had already been screened by the aggregator before entering the program. AstraPay then bounded the fast track again through the existing referral code validated by the backend. Regular merchants could not opt themselves into the faster path.

The control-model change was reviewed together with Operations, Fraud, Risk, and Compliance. The goal was not to remove review. It was to avoid repeating the same second review for clear cases from a known source while keeping a deeper path for exceptions.

Before wider rollout, we whitelisted a sample of SRC merchants to test the fast-track path against the operational SLA. Reviewers were also trained on the one-page review, Instant Approve, and exception handling before the cohort expanded.

The faster path was never open to everyone. Speed depended on a known source, validated eligibility, and a fallback when a case needed deeper inspection.
Rollout

A bounded rollout for a program targeting ~15K merchants

Whitelisted sample validation, reviewer training and 3–5-month rollout are documented. This record does not prove the whole target was processed or quantify saved review time, approval uplift, or fraud reduction.

15Kpartnership program targetthe partnership scope the KYB operation needed to absorb
3–5 morolloutwider rollout after sample whitelisting and reviewer training
1 passeligible clear case designno second approver after the first review
No rebuildcore KYBthe change stayed in existing routing, review UI, and operational workflow
What I took forward

Review depth should follow eligibility and risk

Instant Approve was the most visible change, but the leverage came from cohort gating and exception routing. We did not make all KYB looser. We made review depth follow the risk context.

If mass onboarding becomes recurring work, I would not keep extending referral codes. I would productize eligibility, sampling, audit trails, review time, exception rate, and rework monitoring so the trade-off between throughput and control can be measured.

A healthy fast track is not just fewer steps. It knows who can move quickly and when a case needs deeper review.