---

The POST request will be send over HTTPS to the endpoint.

---

Sample Request

---

Sample Response

---

How to generate verification Hash?

Verification Hash has to be calculated with following combination using SHA256 algorithm and need to be send along with the authentication parameters in each server-to-server request. Parameters required for creating hash are :
<seckey><customerId><walletOwnerId>

---

Sample Code

---

Request Parameters

This reference lists all the standard flow parameters to be send in request.

Parameter	Description	Format	Required
customerId	Generated unique customer id on per user sign up.	A255	Yes
walletOwnerId	Provided by Unique id.	N20 [0-9]	Yes
firstName	User's first name.	A255	Yes
lastName	User's last name.	A255	Yes
dob	User's Date of birth.	N [0-9]	Yes
roles	Set user's roles.Roles can be director","ubo","primaryContact"	A255 [a-zA-Z]	Yes
residentialAddress.postalCode	User's postal code	AN [a-zA-Z0-9]	Yes
residentialAddress.countryISO	Postal code/ Zip code of the user.	N [0-9]	Yes
residentialAddress.address	Address details of the user.	AN [a-zA-Z0-9\\p{Space}\\,]	Yes
residentialAddress.street	Building name, and/ or street name of the user's residential address.	AN [a-zA-Z0-9\\p{Space}\\,]	Yes
residentialAddress.city	City of the user's residential address.	AN50 [a-zA-Z0-9\\\\#&\\p{Space}\\p{L}\\p{M}\\-;.,~`/%$#@ ]{0,1000}	Yes
verificationHash	Verification Hash has collected combination of parameters.Should be generated using SHA256 Algorithm	String	Yes

---

Response Parameters

This reference list lists all the standard flow parameters to be received in response.

Parameter	Description	Format	Required
status	Response status (SUCCESS/FAILED).	A [A-Z]	Yes
responseCode	Response code	[a-zA-Z0-9]	Yes
personid	A unique Person ID generated.	[a-zA-Z0-9]	Yes
customerId	ID of the customer.	[a-zA-Z0-9]	Yes