Switch to dark theme

Switch to light theme

Create Account Holder


To create a new Account Holder, you must create an Application on Fusion. Issuer reviews your Application and post approval Account Holder is created with a unique identifier (accountHolderID, individualID).

Before you begin

Familiarize yourself with key Account Holder concepts explained in About Account Holders before you proceed.

Extensibility

When an Account Holder is on-boarded on Fusion, all necessary details like personal information, OVD, and so on, are captured. If you need to collect additional information, Fusion provides custom attributes for this purpose. For example, you can store an Account Holder’s additional mobile number or UCIC against the Application.

Account Holder Profile Ownership

The Account Holder on-boarded on Fusion has a banking relationship with the Issuer that the fintech has partnered with. Therefore, the Issuer determines which details of the Account Holder are accessible by the fintech.

Create Application

Use the /newIndividualApplication API to create an Application for a new Account Holder. Provide Account Holder’s personal, contact and KYC information in the request body.

Endpoint URI

POST /api/v1/ifi/{ifiID}/applications/newIndividualApplication

Input parameters

  • ifiID: Required. Unique identifier of the IFI.

  • formID: Optional. Unique identifier of the form. If specified, value must be unique for each request.

  • applicationType: Required. Type of Application being created. Allowed values: KYC, CREATE_ACCOUNT_HOLDER, EDIT_ACCOUNT_HOLDER. As we are creating an Account Holder, set the value to CREATE_ACCOUNT_HOLDER.

  • description: Description of the Application. Use the parameter to add comments regarding the Application or the Account Holder.

  • individualType: Required. Type of Account Holder being created. As the Application is for RAH, set the value as REAL. individualID: Optional. Unique identifier of the Account Holder.

  • salutation: Optional. Salutation using which the Account Holder is addressed. Example: Mr., Mrs., Ms.

  • firstName: Optional. Account Holder’s first name. lastName: Optional. Account Holder’s last name. middleName: Optional. Account Holder’s middle name. profilePicURL: Optional. Link to Account Holder’s profile image.

  • gender: Optional. Account Holder’s gender.

  • mothersMaidenName: Optional. Account Holder’s mother’s maiden name.

  • dob: Account Holder’s date of birth details.

  • year: Optional. Year of birth in YYYY format.

  • month: Required. Month of birth in MM format. Value must be between 1 and 12

  • day: Required. Day of birth in DD format. Value cannot be more than the number of days in the specified month. For example, if the month of birth is June, day must be 30 or less. Vectors: Account Holder’sVector details.

  • type: Optional. Type of Vector. Allowed values: p for phone number; e for email. value: Optional. Value based on Vector type specified. For example, if vectorType is p, specify Account Holder’s phone number; if vectorType is e, specify email ID.

  • isVerified: Optional. Specify whether the Vector is verified or not. Allowed values: true, false. If the parameter is omitted or any other value is specified, it is set to false. kycDetails: Account Holder’s KYC details.

  • authType: Optional. Type of document submitted for KYC. Allowed values: AADHAR, PAN, PASSPORT, VOTER_ID, DRIVING_LICENSE.

  • authData: Required. Details based on the KYC type specified in authType. For example, if PAN is specified, provide the ten-character PAN identifier.

  • expiryTime: Optional. Expiry time of KYC in the ISO 8601 format YYYY-MM-DD’T’HH:MM:SS:sss’Z’

  • kycAttributes: Optional. Additional information related to KYC.

  • kycStatus: Optional. KYC status of the Account Holder. Supported values: MINIMAL, AADHAR_OTP,

  • kycStatusPostExpiry: Optional. Status of KYC post expiry. UpdateTime: Optional. ISO 8601 Format YYYY-MM-DD’T’HH:MM:SS:sss’Z’

  • customFields: Optional. Any additional information you want to capture. Example: alternate phone number, UCIC.

  • pops: Required. Account Holder’s address details.

  • tags: Optional. A mechanism for classifying and filtering objects in Fusion.

Example

In the following example, we create an Application for John Doe.

cURL Sample
Switch Theme
Expand More
Copy
curl -X POST 'https://fusion.preprod.zeta.in/api/v1/ifi/140827/applications/newIndividualApplication' \
-H 'Content-Type: application/json' \
-H 'X-Zeta-AuthToken: {{AUTH_TOKEN}}' \
--data-raw '{
    "ifiID": 140827,
    "formID": "form_D6478",
    "applicationType": "CREATE_ACCOUNT_HOLDER",
    "description": "Application for creating Account Holder",
    "individualType": "REAL",x
    "salutation": "Mr.",
    "firstName": "John",
    "middleName": "Marcus",
    "lastName": "Doe",
    "profilePicURL": "http://mypic.picland.somewhere.com/profile_pic.jpg",
    "gender": "MALE",
    "mothersMaidenName": "Mary",
    "dob": {
        "year": 1997,
        "month": 7,
        "day": 5
    },
    "vectors": [
        {
            "type": "p",
            "value": "+918830145227",
            "isVerified": false
        }
    ],
    "kycDetails": {
        "kycStatus": "MINIMAL",
        "kycStatusPostExpiry": "string",
       "updateTime":"2020-06-12T09:39:30.253Z",
        "kycAttributes": {},
        "authData": {
            "PAN": "ALQIG10219"
        },
        "authType": "PAN"
    },
    "customFields": {},
    "pops": [],
    "tags": [],
    "spoolID": "123"
}' 
Code Copied
JSON Sample
Switch Theme
Expand More
Copy
  {
    "applicationID": "150635",
    "formID": "form_D6478",
    "ifiID": 140827,
    "spoolID": "123",
    "status": "PROCESSING",
    "applicationType": "REAL",
    "salutation": "Mr.",
    "firstName": "John",
    "middleName": "Marcus",
    "lastName": "Doe",
    "profilePicURL": "http://mypic.picland.somewhere.com/profile_pic.jpg",
    "dob": {
        "year": 1997,
        "month": 7,
        "day": 5
    },
    "gender": "MALE",
    "mothersMaidenName": "Mary",
    "vectors": {
        "8b15e284-b960-4a6d-aead-87ab8df37b03": {
            "type": "p",
            "value": "+918830145227",
            "isVerified": false,
            "tags": [
                {
                    "type": "vbo-id",
                    "value": "4fa18593-d2d9-4bf3-bea7-7f6deb9f2ca4",
                    "attributes": {}
                }
            ]
        },
        "b6266e38-3bf3-43c0-9394-248cfef1d787": {
            "type": "p",
            "value": "+918830145227",
            "isVerified": false
        }
    },
    "pops": {},
    "tags": {
        "2dffbd68-900b-4617-a444-4f7d173c51e7": {
            "type": "vbo-id",
            "value": "4fa18593-d2d9-4bf3-bea7-7f6deb9f2ca4",
            "attributes": {}
        }
    },
    "kycDetails": {
        "kycStatus": "MINIMAL",
         "updateTime": "Jun 12, 2020 9:39:30 AM",
        "kycStatusPostExpiry": "string",
        "authType": "PAN",
        "authData": {
            "PAN": "ALQIG10219"
        },
        "kycAttributes": {}
    },
    "customFields": {},
    "createdAt": "Jun 12, 2020 10:51:19 AM",
    "updatedAt": "Jun 12, 2020 10:51:19 AM",
    "statusDetails": {},
    "headers": {}
}
Code Copied

Review Application

After your Application is successfully created, it is submitted to the Issuer for review. Based on the details submitted and the qualifying criteria set, Issuer approves or rejects your Application. If your Application is rejected, address the reason and re-submit the Application.

Keep track of this space for more updates