# Become an FIU

### Steps to become an FIU

* **Get registered and regulated** by at least one of the Financial Service Regulators (FSR), namely - RBI, SEBI, IRDAI, PFRDA.
* **Implement the FIU Module**
  * <https://api.rebit.org.in/spec/fiu> - This has the notification endpoints that you will need to create for an AA to send notifications to your FIU Module
  * <https://api.rebit.org.in/spec/aa> - This has the APIs of AA that you need to integrate for the process flow.
* **Test your module**\
  Saafe will provide you the credentials to raise a consent and test your module. This will be shared via an email once confirming step 1.
* **Enrol your module** \
  We will need to enroll your module in the UAT Central Registry which Saafe will guide you through it.
* **Get Certified** \
  Get your certification showing adherence to Technical Standards prescribed by ReBIT by a Sahamati empanelled auditor <https://sahamati.org.in/empaneled-certifiers/> \
  \
  The certifier will provide you with a testing kit that you can use it test your module. We recommend start using the testing kit from the initial stage of development so that you can test the endpoints in parallel to the development.
* **Get your details publicised**\
  After getting the certification from one of the certifiers, you will have to do a bi-lateral agreement with Saafe and we will onboard you on the Live environment.
* **Go Live** \
  You can start testing with the prod data after this with your beta testers and go live after that.&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.saafe.in/become-an-fiu.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
