Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Manage your Account Holders and Applications using Fusion APIs. In this article you learn about:
- Application states
- Duplicate applicationApplication
- Updating Account Holder Application details
- Getting application Application details
- Getting Account Holder details
Application states
After you create an Application, it moves through various states. Each state provides crucial information about your Application.
- Review: Your Application is submitted to the Issuer and is being processed.
- Provisioning: Issuer approves the Application. Account Holder is created and a unique identifier (
accountHolderID
,individualID
) is assigned. - Post approval, you can issue Bundle to Account Holder.
- Rejected: Issuer rejects the Application.
Duplicate
applicationApplication
There might be instances where the Account Holder you are trying to create already exists with the same
Span | ||||
---|---|---|---|---|
| ||||
Vector |
.
Tooltip | ||||||
---|---|---|---|---|---|---|
|
Update
applicationApplication
Edit Application details like Account Holder’s name, date of birth, gender, and so on, using the /applications
API. The ID
of the Application whose details you are editing is required to call the API.
Endpoint URI
|
|
Input parameters
ifiID
: Required. Unique identifier of the IFI.applicationID
: Required. Unique identifier of the Application.firstName
: Optional. Account Holder’s first name.lastName
: Optional. Account Holder’s last name.middleName
: Optional. Account Holder’s middle name.mothersMaidenName
: Optional. Account Holder’s mother’s maiden name.gender
: Optional. Account Holder’s gender. Example: “male”, “female”.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 12day
: 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, the day must be 30 or less.profilePicURL
: Optional. Link to Account Holder’s profile image.Salutation
: Optional. Salutation using which the Account Holder is addressed. Example: Mr., Mrs., Ms.
Example
In the following example, we change the year of birth for Account Holder John Doe.
Div | ||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Get
applicationApplication details
When you create an Application for a new Account Holder, applicationID
(unique identifier), is generated. Use the application ID to get details of your Application. The response displays Application/Applicant details and the current status of your Application.
Endpoint URI
|
|
Input Parameters
ifiID
: Unique identifier of the IFI.applicationID
: Unique identifier of the Application.
Example
In the following example, we fetch the details with Application ID 145437. The "status": "PROCESSING" shows that the Application is being processed.
Div | ||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Get Account Holder details
There are two ways to fetch details for an Account Holder— using Account Holder ID or Vectors.
Using Account Holder ID
If you have Account Holder’s ID (individualID
), use the /accountHolders
API to fetch their details.
Endpoint URI
|
|
Input parameters
ifiID
: Required. Unique identifier of the IFI.accountHolderID
: Required. Unique identifier of the Account Holder. Same asindividuaID
.
Example
In the following example, we fetch Account Holder’s details using Account Holder's ID (individualID
):
Div | ||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Using Vector
Vectors are unique identifiers, like phone and email, used to identify an Account Holder. Use the /individualByVector
API and pass the Account Holder’s Vector as path parameter to fetch their details.
Endpoint URI
|
|
Input parameters
ifiID
: Required. Unique identifier of the IFI.vectorType
: Required. Type of Vector using which details are being fetched. Allowed values: p for phone number; e for email.vectorValue
: Required. Value based on Vector type specified. For example, ifvectorType
is p, specify Account Holder’s phone number; ifvectorType
is e, specify email ID.
Example
In the following example, we fetch Account Holder’s details using phone number:
Div | ||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Panel | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
|