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

Start PAN KYC via DigiLocker

POST

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

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

Start PAN KYC via DigiLocker

When to call: journey kyc_pan — after profile is complete. Local 10-character PAN check runs first.

Why: DigiLocker issues PAN XML/PDF. The entered PAN must match the XML or the step fails. This is the journey start; POST /applications/verify-pan is the screen-level cousin that also kicks bureau.

What it does: body { pan, redirectUrl? }. Pending → { status: "pending", url }. Already verified returns the resolved status shape.

What happens next: open url in a browser/WebView (customer completes DigiLocker). Then poll GET /application/kyc/pan/status. Do not start Aadhaar yet.

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 ********************

Header Params

Body Params application/json

Examples

Responses

🟢200

application/json

Bodyapplication/json

Request Example

Shell

JavaScript

Java

Swift

curl --location 'https://api-dev.myemipay.com/application/kyc/pan' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
  "pan": "{{pan}}",
  "redirectUrl": "{{kycRedirectReturnUrl}}"
}'

Response Example

{}

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

Application journey

PAN KYC status