Admin Portal - Place where key entities are managed

The following are the key entities, whose data and behaviour is managed within the FIP server. Management of these entities is offered through an administration portal. In some cases, the entities are managed only through configurations needing developer support.

Institution management
“Institution” represents information related to financial providers. The FIP server stores configuration information such as the Authentication Type, the Financial Information (FI type) and other institution profile information. This information is used in the implementation of business rules governing the account linking and data fetch processes.

Central registry management
The Central Registry contains key information for identifying and authenticating licensed account aggregators. The FIU server can use this information to share the details of the implements a local store of the central registry and a mechanism for a periodic update of the registry maintained by the registry hosting entity. The concept of the Central Registry and the Registry Hosting Entity are still at an evolutionary stage.

Account Aggregator management
Once an Account Aggregator (AA) connects to a financial institution through the FIP server, details and operational status of the AA are managed within the FIP server. FIP Administrators may, at any point in time, control access given to an AA through this capability.

User management
This capability can be used by super administrators to create roles, assign privileges and create other admin users. The employee code of the employee is deemed to be the login ID for each admin user.

Discovered Accounts
All requests for Account Discovery result in details of the Discovered Accounts getting stored within the FIP server. Masked account numbers, internal account reference numbers and relevant details of the account discovery request received by the FIP server are logged.

Linked accounts
This capability refers to the management of the statuses of the account link requests received by the FIP server. All linking and de-linking requests result in changes to the “Linked Accounts” details.

Consent Artefact
A Consent Artefact is generated for a particular purpose for a particular FIU that has been approved by the consumer. Each consent has an array of accounts that consent has been provided for. The consent status for each such account is managed separately, with a common consent handle linking all such accounts to the consent request that was approved by the consumer. Consent status values managed by the FIP server are CONSENT-CREATED | CONSENT-REVOKED | CONSENT-PAUSED | CONSENT-RESUMED | CONSENT-EXPIRED. All account de-linking activities result in consent status being automatically set to exired.

Data Request
Requests for data fetch are logged, with appropriate status, in the FIP server.