Integration Steps

For the SahamatiNet Proof Of Concept (POC)

SahamatiNet POC Onboarding Checklist

Register as a Ecosystem Member for POC
1. Identify the key fields needed for registration.
  1. Choose your member type: Account Aggregator (AA), Financial Information Provider (FIP), or Financial Information User (FIU).
  2. Provide the following organisation details for the Central Registry (CR):
    Entity ID (unique identifier)
    Base URL for your service
    RSA Public Key for secure communication
    IP Address, Inbound and Outbound Ports (for production; optional for UAT and Sandbox)
  3. Designate a user (preferably with a service email account) to manage the entity as an admin in CR and IAM.
2. Complete the Google Form for Registration to onboard with the Central Registry (CR).
Verify and Set Up User and Entity Access Tokens
1. The designated user will receive an email with a password reset link.
2. Reset the password and complete the account setup.
3. Generate the User Access Token using the user’s email and new password.
4. Use the User Access Token to read the entity’s secret from the Sahamati IAM API.
  1. If needed, reset the secret using the designated API.
5. Use the entity secret to generate the Entity Access Token for ReBIT APIs.
6. Refer to the section on these APIs here
Integrate with SahamatiNet Router in Sandbox
1. Understand the required changes for integration with the Router.
  1. Sahamati Router simplifies the process by allowing members to send requests to any recipient by adding the recipient identifier (recipient-id) in the header under x-request-meta. Refer here for more details.
2. Changes of additional step of onboarding in your application
  1. With the transition to integrating with the SahamatiNet Router, the onboarding process for FIUs (Financial Information Users), AAs (Account Aggregators), and FIPs (Financial Information Providers) is no longer necessary. Previously, this step was essential for establishing peer-to-peer trust and enabling communication within the AA ecosystem. However, with Router integration, trust is managed through technical means, eliminating the need for additional onboarding on your side.
  2. As an AA Ecosystem participant, you can bypass the manual onboarding for FIUs, AAs, and FIPs in your application. These participants would undergo the required compliance through SahamatiNet before interacting with other entities via the Router. This change streamlines the integration process, removing the need for extra code or configuration, and improving the efficiency and ease of connections across the AA ecosystem.
  3. Note that while the technical integrations are now handled through the Router, the necessary commercial agreements between AA ecosystem participants remain unchanged and will continue as they are.
3. Review ReBIT workflows relevant to your entity using the Router.
Integration with Simulators
1. Test and validate the Router's functionality with ReBIT workflows tailored to your entity type by using the integration simulators in the sandbox environment (FIU, AA, FIP). You can also test this with your own simulators, if you have them. Please be sure to include the simulator details in the Google form provided above. We will onboard it for validation in the Sandbox environment as part of the POC.
2. Refer to the section on how to use SahamatiNet simulators here and respective simulators links below
Validate Integration with Simulators and Regulated Entities
1. Conduct tests with other onboarded entities in the sandbox environment to review all integration points and ensure seamless operation.
2. More details on this step will be provided as we progress through the POC.

By following these steps, you will successfully onboard and integrate with SahamatiNet in the sandbox environment, ensuring compliance with ReBIT specifications and the AA ecosystem standards

PreviousObservability NextSandbox Onboarding

Last updated 26 days ago

Was this helpful?

SahamatiNet POC Onboarding Checklist

Register as a Ecosystem Member for POC

Identify the key fields needed for registration.
1. Choose your member type: Account Aggregator (AA), Financial Information Provider (FIP), or Financial Information User (FIU).
2. Provide the following organisation details for the Central Registry (CR):
  - Entity ID (unique identifier)
  - Base URL for your service
  - RSA Public Key for secure communication
  - IP Address, Inbound and Outbound Ports (for production; optional for UAT and Sandbox)
3. Designate a user (preferably with a service email account) to manage the entity as an admin in CR and IAM.
Complete the Google Form for Registration to onboard with the Central Registry (CR).

Verify and Set Up User and Entity Access Tokens

The designated user will receive an email with a password reset link.
Reset the password and complete the account setup.
Generate the User Access Token using the user’s email and new password.
Use the User Access Token to read the entity’s secret from the Sahamati IAM API.
1. If needed, reset the secret using the designated API.
Use the entity secret to generate the Entity Access Token for ReBIT APIs.
Refer to the section on these APIs here

Integrate with SahamatiNet Router in Sandbox

Understand the required changes for integration with the Router.
1. Sahamati Router simplifies the process by allowing members to send requests to any recipient by adding the recipient identifier (recipient-id) in the header under x-request-meta. Refer here for more details.
Changes of additional step of onboarding in your application
1. With the transition to integrating with the SahamatiNet Router, the onboarding process for FIUs (Financial Information Users), AAs (Account Aggregators), and FIPs (Financial Information Providers) is no longer necessary. Previously, this step was essential for establishing peer-to-peer trust and enabling communication within the AA ecosystem. However, with Router integration, trust is managed through technical means, eliminating the need for additional onboarding on your side.
2. As an AA Ecosystem participant, you can bypass the manual onboarding for FIUs, AAs, and FIPs in your application. These participants would undergo the required compliance through SahamatiNet before interacting with other entities via the Router. This change streamlines the integration process, removing the need for extra code or configuration, and improving the efficiency and ease of connections across the AA ecosystem.
3. Note that while the technical integrations are now handled through the Router, the necessary commercial agreements between AA ecosystem participants remain unchanged and will continue as they are.
Review ReBIT workflows relevant to your entity using the Router.

Integration with Simulators

Test and validate the Router's functionality with ReBIT workflows tailored to your entity type by using the integration simulators in the sandbox environment (FIU, AA, FIP). You can also test this with your own simulators, if you have them. Please be sure to include the simulator details in the Google form provided above. We will onboard it for validation in the Sandbox environment as part of the POC.
Refer to the section on how to use SahamatiNet simulators here and respective simulators links below

Validate Integration with Simulators and Regulated Entities

Conduct tests with other onboarded entities in the sandbox environment to review all integration points and ensure seamless operation.
More details on this step will be provided as we progress through the POC.

By following these steps, you will successfully onboard and integrate with SahamatiNet in the sandbox environment, ensuring compliance with ReBIT specifications and the AA ecosystem standards