Skip to content
FIU / FIP Onboarding to Onemoney
- Consent request placed by FIU with consent parameters to Onemoney AA and Consent handle returned in response.
- Consent request from FIU is displayed to consumer in Onemoney application for customer approval. Once customer approves consent artefact is generated.
- Copy of consent artefact which includes the consent parameters and linked accounts to FIP
- Onemoney notifies FIU of customer approval for the consent request placed.
- FIU retrieves the consent artefact from Onemoney
- FIU places data request along with key material to encrypt the data in accordance to the consent parameters included in the consent artefact.
- Onemoney forwards the data request to FIPs whose accounts are linked with the consent
- FIP sends data ready notification
- Onemoney fetches the encrypted data from FIP
- Onemoney sends data ready notification to FIU
- FIU places data fetch request to Onemoney and Onemoney responds sending the encrypted FI data to FIU.
- FIU decrypts the data with the key material received in data fetched from Onemoney
Steps for onboarding of Onemoney by FIU / FIP
- Whitelisting of Onemoney UAT and Onemoney Production Public IP(s)
- Fetching of Onemoney UAT and Production Central Registry (CR) details in FIU / FIP local cache
- Upload of Central Registry (CR) details by FIU and FIP in Sahamati UAT and Production CR repository
- Completion of interoperability testing by the FIU and FIP with Onemoney
- FIU application integration with Onemoney either through web redirection or Onemoney SDK for end to end seamless customer journey
- Completion of end-to-end testing with Onemoney UAT and Production after integration mentioned in point 5.
- Go live…