Money is integer paise — ₹15,000 = 1500000. Follow GET /application/journey. Skipping a step returns 409 step_not_ready.

PAN KYC status

GET

https://api-dev.myemipay.com/application/kyc/pan/status

Last modified:2026-09-09 21:56:13

PAN KYC status

When to call: on a timer after PAN start, and whenever the WebView returns from DigiLocker.

Why: consent or a missing PAN in the locker leaves the step pending with a fresh url — open it again. Only status: resolved + verified: true is done.

What it does: polls DigiLocker. Fetches PAN XML first and matches it to the PAN the customer entered. Verified data: fullName, maskedPan, dateOfBirth, documentType. PDF is fetched and stored only after that match; XML is parsed and not stored.

What happens next: GET /application/bureau (auto-pulls when PAN + phone are on file), then POST /applications/acknowledge-credit-score.

Auth: Authorization: Bearer {{accessToken}}

Errors: 403 Forbidden

Request

Authorization

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Responses

🟢200

application/json

Bodyapplication/json

Request Example

Shell

JavaScript

Java

Swift

curl --location 'https://api-dev.myemipay.com/application/kyc/pan/status' \
--header 'Authorization: Bearer <token>'

Response Example

{}

Modified at 2026-09-09 21:56:13

Start PAN KYC via DigiLocker

Start Aadhaar KYC via DigiLocker