Upload documents. Wait for a person to check.
Each distributor supplied PAN and bank images. Staff reviewed the documents manually, so verification effort grew with registration volume.
Direct Selling
Automating distributor KYC with PAN and bank verification
Document-free distributor registration in under a second, with PAN and bank verification APIs, RabbitMQ processing and match-score routing for manual review.
Tranz / Engineering in practice- Sector
- Direct selling
- Workflow
- Distributor KYC
- Integrations
- PAN & bank verification APIs
- Architecture
- RabbitMQ · Async processing
- Registration response
- < 1 second
- Document images required
- None
- Manual verification
- Borderline matches
Registration returns before background verification completes.
No PAN photo or bank proof image to upload during this flow.
Strong and low matches receive automated decisions.
Reported by the Tranz delivery team. Registration response time is separate from KYC completion time.
The challengeLess manual checking.
Less manual checking.
More time for the team.
Previously, every registering distributor uploaded a PAN card photo and a bank statement or bank proof image. A member of the team manually checked those documents. With hundreds to thousands of daily registrations, this demanded substantial staff effort.
We replaced document uploads with PAN and bank verification APIs and a match-score decision system. Distributors now enter their details, and the system decides which registrations can be verified or rejected automatically and which need a person’s review.
Before & after
Moving verification into the system.
Enter details. Let the system assess the match.
The distributor enters their name, PAN and bank account details. API checks and match scores handle clear decisions automatically, while borderline matches go to manual review.
The workflowFrom submitted details
From submitted details
to verification results.
Registration and KYC completion are separate steps. RabbitMQ queues verification work so distributors can finish registering without waiting for external API responses.
- 01
Enter the details
The distributor enters their name, PAN and bank account details. No PAN photo or bank proof image is required.
- 02
Queue the checks
Verification work goes to RabbitMQ for asynchronous processing, allowing registration to return without waiting for the verification APIs.
- 03
Verify through APIs
PAN and bank verification APIs check the details. The system evaluates the returned data using a match score.
- 04
Assign a status
Strong matches are verified, low matches are rejected, and borderline matches remain pending for manual review.
Intelligent decision routingThree outcomes.
Three outcomes.
Human review where it matters.
The match score determines the next step. Clear matches and clear mismatches are handled automatically; borderline results stay pending for a person to review.
Verified
A score that meets the configured acceptance threshold is verified automatically.
Rejected
A score below the configured rejection threshold is rejected automatically.
Pending
An intermediate score routes the registration to a person for manual verification.
Engineering decisionsFast registration.
Fast registration.
Verification in the background.
API checks replace document uploads
PAN and bank verification APIs supply the data used by the match-score system. Clear results receive automated decisions; borderline matches go to a person for review.
RabbitMQ absorbs registration bursts
The delivery team reports bursts of hundreds of registrations within a second. Verification work goes to RabbitMQ, allowing registration to return without waiting for external API calls.
Other requests continue while verification runs asynchronously. The queue also supports failure handling outside the immediate registration request.
The outcomeReduced intervention.
Reduced intervention.
Staff time saved.
Distributors no longer need to photograph and upload PAN and bank documents for this flow. Registration takes less than a second, while verification continues asynchronously. This timing describes registration, not the completion of every verification check.
Staff time is saved by automatically verifying strong matches and rejecting low matches. Manual work is concentrated on borderline cases instead of reviewing every registration. The team reports a substantial reduction in verification effort.
Explore our direct selling platformBring us your workflowWhere does your team
Where does your team
spend time checking data?
Tell us about your onboarding process, verification steps and the exceptions your team handles. We can explore where integrations and automation would help.
Discuss your verification workflow