Update customer profile

Update customer profile

When to call: journey step update_profile (after begin-verification, before PAN). Also whenever the customer edits name / DOB / address / employment / income after begin-verification.

Why: underwriting and later bank-name match need a saved profile. Email cannot be set here. Calling this while the application is still started returns 409 step_not_ready — finish begin_verification first.

What it does: partial body — any of fullName, dob (dd-mm-yyyy only — not ISO, not slashes), address (string; objects are flattened, [object Object] is rejected), employmentType (salaried | self_employed), employerName, monthlyIncomePaise (integer paise, ₹15,000 = 1500000). Unknown keys like email / dateOfBirth are ignored. Journey step completes only when name + DOB + employment + income are all saved. Returns the same shape as GET.

What happens next: GET /application/journey — current should move to kyc_pan. Then POST /application/kyc/pan (or POST /applications/verify-pan).

Auth: Authorization: Bearer {{accessToken}}

Errors: 409 step_not_ready — finish begin_verification (or the current journey step) first · 422 validation_failed

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

curl --location 'https://api-dev.myemipay.com/application/profile' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "fullName": "{{fullName}}", "dob": "{{dob}}", "address": "{{address}}", "employmentType": "salaried", "employerName": "GTET", "monthlyIncomePaise": 1500000 }'

Update customer profile

Request

Responses