AA Industry Practices

Consent template:

A Consent Template refers to the outer bounds for mandatory attributes (as defined by the ReBIT specs) of consent artefact that can be employed for a specific use case. While few attributes, such as purpose code, consent type, fetch type, etc. are described in absolute terms, attributes that carry a value and unit are described as upper bounds.

Sahamati introduced the AA Consent Template Library as a community asset to harmonize consent attributes, setting upper-bound reference parameters for various use cases across sectors.

Please refer to this link for additional information https://sahamati.org.in/aa-consent-template-library/

Reciprocity Obligations

The term “Reciprocity” refers to an implicit obligation of a financial services institution to play two roles, in the AA network – that of an FIP and that of an FIU.Discharging this implicit obligation implies that every financial services institution wishing to join the AA ecosystem as an FIU (a “user” of information) also agrees to be an FIP (a “provider” of information).

The principle of reciprocity being an obligation is to ensure citizens are benefited as also to ensure the usage of the AA network by participants is fair and equitable.Such an obligation can however only be practically implemented, if a financial institution is the custodian of one or more of the financial information types listed as part of the open API specifications (published by ReBIT).In the absence of the FIP service being practically implementable, a financial institution may still participate as an FIU, with a clear commitment to implementing its FIP service as and when applicable.

Please refer to this link for additional information https://sahamati.org.in/aa-community-guidelines-v1-2/reciprocity-obligation/#:~:text=The%20term%20%E2%80%9CReciprocity%E2%80%9D%20refers%20to%20an%20implicit%20obligation,implementing%20its%20FIP%20service%20as%20and%20when%20applicable.