Welcome to FinPro (FIU Platform of Moneyone) Self Service Portal !
| S No | Chanel Type | Sub Type 1 | Sub Type 2 | Document | Assets (SDK) | Remarks |
|---|---|---|---|---|---|---|
| 1 | FIU server integration | For All Chanel Types | Mandatory_FIU_Server_Integration Guide.pdf | Mandatory for all Chanels that shall integrate. | ||
| 2 | SDK | Mobile | Android | Android Standard SDK Integration Guide v1.pdf | Download | 1. If you want use pre build screen prefer standard SDK.
2. Download the SDK and integration guide from the self help portal 3. Follow the integration steps from the integration document 4. If everything goes well you will be able to initialise the SDK |
| IOS | Currently not available | |||||
| Flutter | Flutter Standard SDK Integration Guide v1.pdf | Download | 1. If you want use pre build screen prefer standard SDK.
2. Download the SDK integration guide from self help portal and follow the integration steps 3. Add a private gitlab repository in your pubspec.yaml file. 4. Add code mentioned in integration document for the SDK integration in pubspec.yaml file |
|||
| 3 | Web redirection (Technology Independent | Mobile (Web view ) | Refer Section "FinPro FIU Server APIs" of Mandatory_FIU_Server_Integration Guide.pdf | will work without any changes. | ||
| Mobile Native Browser | Refer Section "FinPro FIU Server APIs" of Mandatory_FIU_Server_Integration Guide.pdf | Use handle in mobile browser. | ||||
| Web | Refer Section "FinPro FIU Server APIs" of Mandatory_FIU_Server_Integration Guide.pdf | Website Only | ||||
| 4 | Assisted Mode | Integration Documentation | Base Document Mandatory_FIU_Server_Integration Guide.pdf
Learn more about Assisted Mode. |
Per Channel Custom Document needs to be prepared case to case basis. (No Technical Integration. Steps for Assisting the user to register, login and approve the consent) | ||
| 5 | Detached Mode | Integration Documentation |
Base Document Mandatory_FIU_Server_Integration Guide.pdf
Learn more about Detached Mode. |
User will place the request consent from the FIU channel app. He will open the Onemoney web app or android app separately to view the consent and approve the consent. |
FinPro Integration Docs
Helps to store customers’ consents, and use APIs to receive and share readily-usable,
fine-grained data across all data types supported by the Account Aggregation network.
Onemoney AA Integration Docs
Use Onemoney APIs and SDKs to place consent requests to customers for using their data,
for a specific purpose and time period.Customers can approve or deny consent for such requests
on Onemoney app. Consents, once given, can also be paused, resumed or revoked at any time.
This is a high level diagram showing how different channels of FIU will interact with the FinPro
server and the Onemoney AA SDK.
FIU and Account Aggregator Integration Flow
- FIU has different channels and the integration team can use the FinPro Server to integrate with the concerned channel.
- FIU channel developers can integrate the FinPro server with the Channel systems for Consent Generation and Management.
- FIU channel developers can integrate the Onemoney AA SDK within their applications to create embedded user journeys.
- All the FIU Channel servers will be connected with the FinPro FIU Server.
- As part of the user journey channels can request consent for users from FIU to the Account Aggregator.
- Onemoney AA will fetch the bank statement from different FIPs and share it with the FinPro (FIU) once the user approves the consent.
- FinPro (FIU ) will inform the respective channel system on the FI data arrival.
- The channel system will fetch the FI statement for the specific user from the FinPro server and process it as per the requirement.