Saafe AA - Docs
HomeSandbox
  • Overview
  • Supported FIPs on Saafe
  • Become an FIU
  • Environment
  • Central Registry
    • Overview
    • Create FIU Entity
    • IAM User Endpoints
      • Generate IAM User Token
      • Secret Management
        • Entity Secret Read
        • Entity Secret Reset
    • Entity Auth Token
    • ❌Entity Auth Token (Deprecated)
    • Central Registry APIs
      • GET AA List
      • GET FIP List
      • GET FIU List
    • Postman Collection
  • FIU Module
    • Introduction
    • AA API v2.0.0
    • FIU API v2.0.0
    • JWS Signature
      • Create JSON Web Key (JWK)
      • Create JWS
      • Verify JWS
    • End-to-end Encryption
  • FIP Module
    • Overview
  • AA Client
    • Web Redirection
Powered by GitBook
On this page
  • (CR) Central Registry APIs
  • Detached JWS Signature
  • End-to-end encryption of Data Request

Was this helpful?

  1. FIP Module

Overview

PreviousEnd-to-end EncryptionNextWeb Redirection

Last updated 7 months ago

Was this helpful?

FIP Module will host set of ReBIT API that the AA will call from their Backend. Those APIs are defined here you will have to implement 2.0.0 version or 2.1.0 for Insurance FIPs

Your FIP module will further call your CBS to discover accounts and fetch data.

Central Registry FIP Entity Onboarding

You can follow the steps here Create FIU Entity to create an FIP entity as well. Just select FIP instead of FIU

(CR) Central Registry APIs

Ref- Central Registry APIs

Central Registry host a list of APIs that you can use

1. Token Generation API

2. AA List

When you are making API call to the AA you need to pass the token generated in the CR to be sent in the header as fip_api_key

Detached JWS Signature

All API response that you are sending needs to have the x-jws-signature refer - JWS Signature

End-to-end encryption of Data Request

Ref -

Note: The 2.0.0 ReBIT version requires you to support both curve25519 and X25519 curve of ECDH

https://api.rebit.org.in/spec/fip
https://github.com/Sahamati/rahasya