pending with a fresh url — open it again. Only status: resolved + verified: true is done.data: fullName, maskedPan, dateOfBirth, documentType. PDF is fetched and stored only after that match; XML is parsed and not stored. Same legal name (if they have no unique profile name yet) or a PAN already in the database — this phone or another — returns 409 and they cannot continue. May rotate tokens.POST /application/bureau, then POST /applications/acknowledge-credit-score. On name_already_exists / pan_already_exists, sign in to the existing account — do not add another.Authorization: Bearer {{accessToken}}401 unauthorized | session_expired · 404 not_found · 409 name_already_exists | pan_already_existscurl --location --request POST 'https://api-dev.myemipay.com/application/kyc/pan/status' \
--header 'Authorization: Bearer <token>'{
"status": "resolved",
"verified": true,
"data": {
"fullName": "Rajavarapu Yaswanth Kumar",
"maskedPan": "XXXXXX085R",
"dateOfBirth": "15-08-1990",
"documentType": "PAN"
},
"accessToken": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9…",
"refreshToken": "refresh_…",
"tokenType": "Bearer",
"expiresIn": 86400,
"identityKind": "customer",
"customerId": "cust_1735123456789",
"productId": "prod_personal"
}