Account Holders FAQs

Fusion system supports 3 types of account holders to support various usecases of the issuer - Real (individual), Legal (company), and Headless (anonymous). See Account Holders for more information.

An HAH can be termed as an anonymous account holder as their identity can not be ascertained using identifiable documents.

Yes, an application request with details must be submitted prior to creating an Account Holder for an applicant.

You can use vectors such as phone number or email to retrieve account holder details. Pass the type of vector (p for phone and e for email) used while creating an Account Holder in the request header.

Yes, this is possible. Users have the flexibility to enroll themselves with multiple Fintech programs.

When you hit the account holder creation API (newIndividual), you need to ensure that form ID, OVD ID (eg PAN number), and mobile number are always unique.

For example, Account Holder (AH) is already created at our end. When you hit the account holder creation API again, you get a timeout error and do not get the Account Holder(AH) value. Hence, when hitting the API again with the same vectors and parameters, you must ensure that the form ID, OVD ID, and mobile number are unique. Else, an error will be thrown.

The difference is:

• Min KYC users can be issued accounts, cards, etc.

• Shortfall users could be considered as account holders with lapsed KYC. Hence, no account or payment instruments can be used for them.

Spool contains the details of the list of actions during and post application approval, such as:

• The kind of relationship that will be established after application approval
• The details to be filled in the application

• RAH is any account holder onboarded, irrespective of their KYC status.
• Full KYC account holders are a subset of RAH.

• RAH is a term used for the users onboarded on the fintech.
• LAH is a unique account holder for all fintechs.

Any valid OVD is accepted for account creation. Refer to the authType value defined in the Fusion developer documentation.

No, there are no such limits imposed.