Edit individual VA customer
Virtual Account APIs use the same access token as the rest of the platform. Obtain it from the Authentication API and send it on every VA call:
Authorization: Bearer <access_token>
Base URLs for each environment are listed under API environments.
What this does: Updates an existing Individual customer. This also doubles as "Remittance customer → Virtual customer" conversion — pass a customer code that already exists in the platform and this call promotes/updates it as a VA customer.
Endpoint
/ewallet/api/v1/customer-registration/{code}Same payload shape as Create (Create individual VA customer), with one difference: code is now REQUIRED — it must be the existing customer's code (returned by Create/Receipt), both in the URL path and the payload body.
Fields That Can Actually Be Updated
| Field | Payload Key |
|---|---|
| Gender | gender |
| Mobile Number | mobileNumber |
| ID Type | idTypeCode |
| ID Number | idNumber |
| Occupation | occupationCode |
| Job Title | jobTitle |
| Job Industry | jobIndustry |
| Address Line 1 | addressLine1 |
| Country | countryCode |
| State | state |
| City | city |
| Pincode | pincode |
All other fields (name, date of birth, nationality, ID country, issue/expiry dates, etc.) are not editable through this endpoint, even if included in the payload — send the full payload as on Create, but only the fields listed above will actually change.
Payload Diff vs Create
"code": "1000000812", // was "customerCode": "" on Create — now the existing customer's code, field renamed to "code" on Edit
"docReferenceNumber": "CUS19SCMHK", // re-upload / re-reference documents if any changed
"firstName": "Rakesh", "lastName": "Doe" // updated fields