API Reseller
Merchant Onboarding API
The KYC checks composed into one onboarding flow, returning a single decision with the evidence behind it. Built for products that sign up merchants at volume and need the audit trail to survive later scrutiny.
What you get
- Aadhaar, PAN and bank verification in one orchestrated flow
- A single decision with per-check evidence retained
- Document upload with server-side validation
- Status webhooks at each stage of onboarding
- Full audit trail per merchant
The contract
- Auth
- Issued credentials per key pair, over TLS. Signed requests where the rail requires it.
- Flow
- Submit, then poll or receive a webhook. Onboarding is asynchronous by nature.
- Documents
- Uploaded against the application, each independently statused.
- Rejections
- Returned with a machine-readable reason code, not free text.
- Webhook
- Signed, with replay protection. Retried until your endpoint returns 2xx.
- Environments
- Sandbox mirrors production semantics, including failures.
FAQ
About merchant onboarding api
Why is onboarding asynchronous?
Because the checks behind it are. A submission is accepted immediately and the decision arrives by webhook or poll once verification completes. An API that blocked until a decision was ready would hold a connection open for an unpredictable period and time out.
A merchant was rejected. Do I get a reason?
Yes, as a machine-readable reason code rather than free text, so your product can tell the merchant what to fix and let them resubmit. A rejection with no actionable reason just produces a support call.