SahamatiNet
  • Background
  • SahamatiNet POC
    • Introduction
    • Applications
    • Observability
    • Integration Steps
      • Sandbox Onboarding
      • IAM APIs
      • CR APIs
      • Integration with Router
        • Sample Code Snippets
          • Python
          • Java
          • JavaScript
          • GoLang
          • C#
        • Router APIs Specifications
          • FIU API Specification
          • AA API Specification
          • FIP API Specification
      • ReBIT Workflows using Router
        • Account Discovery & Linking
        • Consent Workflow
        • FI Request Workflow
    • Integration with Simulators
      • AA Simulator
      • FIP Simulator
      • FIU Simulator
    • Validation of Integration
  • Glossary
  • Guidelines
  • Frequently Asked Questions
  • How To Guides
    • How To Onboard to Sandbox ?
    • How To Decide on an Entity ID ?
    • How To Generate a Certificate ?
    • How To Generate Tokens ?
Powered by GitBook
LogoLogo

Copyright © 2025 - Sahamati Foundation

On this page

Was this helpful?

Export as PDF
  1. SahamatiNet POC
  2. Integration Steps
  3. ReBIT Workflows using Router

Consent Workflow

PreviousAccount Discovery & LinkingNextFI Request Workflow

Was this helpful?

The consent workflow is a fundamental part of the Account Aggregator (AA) ecosystem. It ensures that Financial Information Users (FIUs) can access user data from Financial Information Providers (FIPs) only after obtaining explicit consent from the user. This workflow is governed by a series of secure and standardized interactions using the ReBIT APIs.

Steps Involved in Consent Workflow:

Pre-requisites:

The is handled by the user to execute the Consent workflow.

Consent Workflow

1. FIU Initiates Consent Request through Router:

The FIU initiates the process by sending a consent request to the Account Aggregator (AA). The request specifies the type of financial data, the duration, and the purpose for which it is being requested. This consent request is made by the FIU to the AA through Router, following these steps:

  • Retrieve the FIP identifier from the Central Registry.

  • Construct the request header (x-request-meta) using the retrieved identifier for Router compatibility.

  • Transmit the request to the Router along with the prepared header.

ReBIT API: /Consent (POST) with 'x-request-meta' header: The FIU sends the consent request to the AA using this API through Router. The request includes the data access requirements, purpose, and duration for which access is required.

API (AA Internal Spec): /Consent/create (POST): The AA create the consent artefact and stores for future use with pending status.

2. AA Presents Consent to User:

After receiving the consent request, the AA communicates with the user via its mobile app or web portal, presenting the consent details. The user reviews and either approves or denies the request.

API (AA Internal Spec): /Consent/read (GET): The AA retrieves the consent artefact details to present to the user for approval.

3. User Grants Consent:

If the user approves the consent request, the AA generates a consent artefact. This artefact is a formal document containing all the details of the user’s consent, such as the scope, purpose, and validity.

API (AA Internal Spec): /Consent/accept (POST): The AA update the status and stores the consent artefact after the user grants approval.

4. AA Shares Consent with FIU & FIP through Router:

Once consent is granted, the AA sends the consent artefact to both the FIU and the relevant FIP. The FIP uses this consent artefact to validate requests for financial data.

ReBIT API: /Consent/Notification (POST) with 'x-request-meta' header: The FIU & FIP is notified about the granted consent via this API. It helps,

  • FIU to fetch the consent artefact from AA and use it for FI request.

  • FIP to validate the future FI data requests from the FIU.

ReBIT API: /Consent/fetch (POST) with 'x-request-meta' header: The FIU fetches the Consent artefact from AA through Router to use it for future FI data requests.

5. Consent Revocation (Optional):

The user has the ability to revoke consent at any time, cutting off access to their data.

API (AA Internal Spec): /Consent/revoke (POST): This API allows the user to revoke previously granted consent.

Account Discovery & Linking