Modify Without Document

Introduction

Once the application is created then certain data can be modified such as email, phone number, etc can be modified with any supporting document for further validation and operations can be performed.

The Push Onboarding JSON Consists of Below Objects with Input Variables:

KYC data: Contains personal and financial information such as gender, marital status, nominee relationship, PAN number, Aadhaar number, residential status, occupation details, annual income, and contact details.

Identity proof: Contains details about the identity proof provided by the customer, such as type of proof, name, father's name, PAN number, date of birth, and file URL.

API Endpoint - Modify without Document

Preproduction- https://backops-investor-onboarding-preproduction.signzy.tech/kra-handler/api/onboardings/push

Sample Request

Preproduction

curl --location 'https://backops-investor-onboarding-preproduction.signzy.tech/kra-handler/api/onboardings/push' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'Authorization: <authorization token>' \
--data '{
    "task": "cvlModifyWithoutDocuments",
    "onboardingData": {
        "kycData": {
            "gender": "...",
            "maritalStatus": ".....",
            "fatherTitle": "....",
            "panNumber": "...pan…",
            "residentialStatus": "....",
            "kycAccountCode": "03",
            "kycAccountDescription": "modifyWithoutDocuments",
            "fatherName": "....",
            "mobileNumber": "...",
            "countryCode": "...",,
            "emailId": "...",
            "annualIncome": "...",
            "occupationCode": "...",
            "occupationOther": "..."
        },
        "identityProof": {
            "type": "...",
            "name": " …",
            "fatherName": "...",
            "number": "...",
            "dateOfBirth": "...",
            "fileUrl": [
                "..."
            ]
        },
        "esign": {
            "signedPdf": "..."
        }
    },
    "callbackUrl": "..."
}'

Request Field Description

Object Name	Key	Data type	Required/ Optional	Description
	Header
	Content-type	string	Required	application/json
	Authorization	string	Required	Access token from login
	Body
Kyc Data	gender	string	Required	investor’s Gender values: “Female” / “Male” / “Transgender”
	maritalStatus	string	Required	investor’s marital status, values: “MARRIED” / “UNMARRIED” / “OTHERS”
	fatherTitle	string	Required	Pass the title of Father or Spouse, possible values “Mr.” / “Mrs.”
	panNumber	string	Required	Investors PAN number or incase of PAN EXEMPT pass PANEXEMPT
	residentialStatus	string	Required	Investor’s residential status, values: “Resident Individual” / “Foreign National” / “Person of Indian Origin”
	kycAccountCode	string	Required	KYC account code, Pass 03
	kycAccountDescription	string	Required	Modify without documents
	fatherName	string	Required	Pass the Father or Spouse name
	mobileNumber	string(Required), valid 10 digit mobile number	Required	Mobile number
	countryCode	string	Required	Country code of mobile number
	emailId	string	Required	Email Id of Investor
	annualIncome	string	Required (allow empty)	Annual Income code (Refer Table 1.8)
	occupationOther	string	Required in case of CVL KRA if Occupation Code is 99	String of 50 characters
identityProof	type	Enum string	Optional	“individualPan” /"panDigilocker
	name	String ,string of min length of 2 consisting of any character	Optional	Name on POI document
	fatherName	string	Optional	Father's name on POI document
	number	string	Required	PAN number on POI document
	dateOfBirth	string	Required	DOB on POI document in DD/MM/YYYY or DD-MM-YYYY format
	fileUrl	Array of URLs	Optional	An array of image URLs of the ID card, front side. In case of PAN, pass URL of front Image
esign	signedPdf	string	Required	Signed form URL combined of all the data and documents
callbackUrl	callbackUrl	string	Optional	Callback URL to receive the response on KRA push

Sample Response

{
   "customerId": "...",
   "requestId": "...",
   "callbackUrl": "..."
}

Response Field Description

Key	Data Type	Description
customerId	string	ID of the particular customer for onboarding every customer has one customer ID.
requestId	string	The merchant ID for the onboarding journey
callbackUrl	string	The URL where the complete data of the customer will be posted once the onboarding process is completed

Getting help

Please feel free to contact us if you have any questions, require clarification, or have ideas for how to make the documents or any of our services better.

You can reach out to us at [email protected].