# CR FIP Schema | Field Name | Definition | Example | | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | entityinfo-name | Name of the entity as submitted while listing itself in the CR. | “Goods and Service Tax” | | entityinfo-id | ID, as issued by the CR, to the entity | FIPGSP | | entityinfo-code | ID, as issued by the financial sector regulator, regulating that entity. | GSTN | | Identifiers – category | Relevant only for FIPs. To be read in conjunction with identifier type. Every FIP can declare one or more identifiers that it allows end-users to present, for account discovery. | STRONG | | Identifiers- type | Relevant only for FIPs. To be read in conjunction with identifer category. Every FIP can declare one or more identifiers that it allows end-users to present, for account discovery. Atleast one of the identifiers must be of type - Strong. | MOBILE | | baseurl | The URL of the FIP service that hosts all ReBIT-compliant API endpoints | “ | | fitypes | Relevant only for FIPs in the CR. The Financial information types (from the master list of schemas published by ReBIT) that the FIP currently supports account-linking and data-sharing for. | DEPOSIT | | inboundports | The ports of the FIP that the AA can connect to. | \["1234","0001"] | | outboundports | The ports of the FIP that the AA can expect to receive requests from. | \["5678","8876"] | | ips | The IP addresses of the FIP that the AA can send and receive requests to. | \["111.222.333.444","012.345.678.901"] | | certificate | The X.509 Digital Certificate issued to the AA by a Certificate Authority (JSON Web Key format) |

"alg": "RS256",
"e": "AQAB",
"kid": "1b94c",
"kty": "RSA",
"n": "vrjOfz9Ccdgx5nQudyhdoR17V-IubWMeOZCwX\_jj0hgAsz2J\_pqYW08PLbK\_PdiVGKPrqzmDIsLI7sA25VEnHU1uCLNwBuUiCO11\_-7dYbsr4iJmG0Qu2j8DsVyV1azpJC\_NG84Ty5KKthuCaPod7iI7w0LK9orSMhBEwwZDCxTWq4aYWAchc8t-emd9qPvWtVMDC2BXksRngh6X5bUYLy6AyHKvj-nUy1wgzjYQDwHMTplCoLtU-o-8SNnZ1tmRoGE9uJkBLdh5gFENabWnU1m1ZqZPdwS-qo-meMvVfJb6jJVWRpl2SUtCnYG2C32qvbWbjZ\_jBPD5eunqsIo1vQ",
"use": "sig"

| | tokeninfo – url | The URL of the Token Issuance Service of the entity that other entities can connect to, to get API tokens. This can be ignored for now. | “ | | tokeninfo - maxcalls | Ignore for now | 1 | | tokeninfo - desc | Ignore for now | "string" | | gsp - id | The ID issued to a GSP, acting as an FIP gateway for GSTN | FIPGSP000001 | | gsp - name | The name of the GSP acting as an FIP gateway for GSTN | Some Services Pvt. Ltd | | gsp - ip | The IP that the AAs can connect to, for the GSP listed above. | | | gsp - url | The URL that the AAs need to whitelist for endpoints belonging to the GSP listed above. | [https://example.com](https://vayana.com) | | signature – signValue | Ignore for now | “u2j8DsVyT1azpJC\_NG84Ty5KKthuCaPod7iI7w0LK9orSMhBEwwZDCxTWq4aYWAchc8 “ | --- # 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://sahamati.gitbook.io/aa-common-service/reference/cr-fip-schema.md?ask= ``` 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.