Sandbox Onboarding

Sandbox Onboarding

To participate in the SahamatiNet Router in the Sandbox, an entity (AA, FIP, or FIU) must ensure its API implementation is ReBIT standards-compliant. This ensures that the entity's APIs meet the necessary interoperability standards for the AA ecosystem and can be tested via the SahamatiNet Router.

The onboarding process involves submitting the Entity (member) information such as

Property Name	Description
ID (Entity ID)	Unique identifier for your organisation used as Entity ID in Central Registry. Learn how to choose an Entity ID
Name	Name of the entity
Type	Entity Type - one of FIU, FIP, AA (Member Type)
Base URL	Base URL ( Endpoint ) of your respective application to access the APIs and send requests. (Only v2 API endpoint are supported in Sandbox environment)
Certificate	The RSA public key of the entity for secure communication. It will be used by the members to validate the signature (x-jws-signature) of the API request. Learn how to create this certificate.
ips	The IP address(es) of the entity to whitelist to access of Sahamati Network services (Ex: Router).
inboundports	The port of the member that the Sahamati services can connect to.
outboundports	The port of the member that the Sahamati services can expect to receive requests from.
entityhandle	Relevant and required only for AAs.

For Ecosystem Member Type: Specify whether you represent an AA, FIP or FIU.

• Account Aggregators (AA) : Entities that facilitate the secure sharing of user financial data between financial information providers (FIPs) and financial information ussers (FIUs)

• Financial Information Providers (FIP) : Entities that hold user financial data, such as banks, NBFC, etc.

• Financial Information Users (FIU): Entities that seek user financial data to provide value-added services like loans, wealth management, and more.

For IP Address, Inbound and Outbound Ports: Network details for connecting with the AA ecosystem are required for Production, optional for UAT and Sandbox.

The Designated User of the entity information such as

Property Name	Description
Name	Name of the user from entity who will manage client secret
Email	Email address of the user - preferably service account email
Mobile [Optional]	Mobile number of the user

The member (entity) will be onboarded along with a user with admin role for managing the profile, secret rotation of entity etc,.

Once the member entry is added to CR, they can whitelist Sahamati Router IP.

Designated User: Contact details of the representative responsible for generating and managing the client secret in IAM (Token Service). It is recommended to use a service account email for the long-term management and consistency.

Ecosystem Member should provide the above details in the Google Form. Sahamati team will validate the details and onboard the entity as the member to the Sahamati's Central Registry (CR) and IAM (Token Service).