Verify PAN

Verify PAN

Description: runs Trulens PAN KYC then eFundzz bureau pull in one customer action. Phone comes from the OTP session when omitted.

Usage: after profile is saved, when the screen offers verify_pan (or as an alternative to the journey PAN pair).

Details: body { pan, phone? }. Screen comes back with summary.creditScore when bureau resolves. Invalid PAN / wrong status → 400. Vendor failure → provider_failed. Same legal name as another person → 409 name_already_exists. Same PAN on a new phone migrates the existing Customer (old phone picker drops them). Binding someone else's PAN as a Customer → 409 pan_already_exists.

Next: POST /application/acknowledge-credit-score. The offer appears later, after Aadhaar and the short Under verification wait.

Auth: Authorization: Bearer {{accessToken}}

Errors: 400 Invalid PAN, wrong status, or missing phone · 401 unauthorized | session_expired · 403 Forbidden · 404 Application not found · 409 step_not_ready | name_already_exists | pan_already_exists

curl --location 'https://api-dev.myemipay.com/application/verify-pan' \ --header 'Authorization: Bearer ' \ --header 'Content-Type: application/json' \ --data '{ "pan": "ACUPA7085R", "phone": "9000000003", "redirectUrl": "https://trulens.in", "revision": "" }'

{ "application": { "id": "app_1735123456789", "reference": "PME-A1B2C3D4" }, "status": "verifying", "message": "Your credit score is ready. Please review and continue.", "summary": { "creditScore": "750", "activeAccounts": "2", "worstDpdDays": "0" }, "youCanNow": [ { "action": "acknowledge_credit_score", "title": "Continue", "submitTo": "/application/acknowledge-credit-score" } ], "revision": "3", "accessToken": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9…", "refreshToken": "refresh_…", "tokenType": "Bearer", "expiresIn": 86400, "identityKind": "customer", "customerId": "cust_1735123456789", "productId": "prod_personal" }

Request

Responses