diff --git a/content/data/account-aggregator/api-integration/consent-flow.mdx b/content/data/account-aggregator/api-integration/consent-flow.mdx index 6ee6698e..bbd3f7ef 100644 --- a/content/data/account-aggregator/api-integration/consent-flow.mdx +++ b/content/data/account-aggregator/api-integration/consent-flow.mdx @@ -38,7 +38,10 @@ Call this API to create a consent request. The details of the request will be pr "to": "2023-01-01T00:00:00Z" }, "context": [ - ] + ], + "additionalParams": { + "tags": ["Loan_Tracking", "Partner_X"] + } }`} @@ -97,6 +100,10 @@ Call this API to create a consent request. The details of the request will be pr "count": "0", "lastUsed": null }, + "tags": [ + "Loan_Tracking", + "Partner_X" + ], "traceId": "1-6433a06a-4b99c3a81b538bc762b5aa08" } `} @@ -234,6 +241,10 @@ If the consent is approved, the status in the response will be `ACTIVE`. After t "consentExpiry": "2023-08-02T12:40:41.165Z" }, "accountsLinked": [], + "tags": [ + "Loan_Tracking", + "Partner_X" + ], "traceId": "26b8bc4c-5d33-43a1-a58f-be5d4d0acbd0" }`} @@ -289,6 +300,10 @@ If the consent is approved, the status in the response will be `ACTIVE`. After t "count": "0" }, "accountsLinked": [], + "tags": [ + "Loan_Tracking", + "Partner_X" + ], "traceId": "74d3032a-597e-40e1-859b-67b035e8a0e0" }`} diff --git a/content/data/account-aggregator/api-integration/data-apis.mdx b/content/data/account-aggregator/api-integration/data-apis.mdx index 6c8b36fd..68b99898 100644 --- a/content/data/account-aggregator/api-integration/data-apis.mdx +++ b/content/data/account-aggregator/api-integration/data-apis.mdx @@ -595,9 +595,7 @@ Auto-Fetch data feature aims to absorb this complexity from the FIUs. With Auto- InvalidConsentUse - + Consent fetch frequency exceeded @@ -605,9 +603,7 @@ Auto-Fetch data feature aims to absorb this complexity from the FIUs. With Auto- InvalidConsentStatus - + Consent for which data fetch has been requested has expired @@ -615,9 +611,7 @@ Auto-Fetch data feature aims to absorb this complexity from the FIUs. With Auto- SessionExpired - + Session to fetch data for a session ID has expired @@ -625,9 +619,7 @@ Auto-Fetch data feature aims to absorb this complexity from the FIUs. With Auto- ConsentRevoked - + Consent for which data fetch has been requested has been revoked @@ -635,9 +627,7 @@ Auto-Fetch data feature aims to absorb this complexity from the FIUs. With Auto- UpstreamServerDown - + Received 500 from upstream AA diff --git a/content/data/account-aggregator/consent-object.mdx b/content/data/account-aggregator/consent-object.mdx index f9adbad9..db6589a3 100644 --- a/content/data/account-aggregator/consent-object.mdx +++ b/content/data/account-aggregator/consent-object.mdx @@ -11,13 +11,24 @@ The consent object is the core of the AA framework. When an FIU requires data ab Consent object contains the information about all the different types of data the FIU needs, the purpose of the data, and how the FIU plans to use the data and so on. - + As specified in the table below, some parameters have to be passed mandatorily when creating a consent.
+ + Tagging helps you organize and track consent requests, reports, and analytics + more effectively. With this feature, you can add relevant labels (tags) to + different consent requests and data-fetch reports without creating separate + product instances. Tags make it easier to segment, analyze, and track data for + different use cases, such as monitoring traffic for specific partners or + campaigns. + + +
+ ### Consent request object | Property name | Description | Mandatory? | @@ -28,7 +39,7 @@ Consent object contains the information about all the different types of data th | `fetchType` | Enum to specify either `ONETIME` or `PERIODIC` fetch of data. | Yes | | `consentTypes` | Specifies the type of data being requested for, from your user—
  • `PROFILE`—Personal details such as mobile number, date of birth, PAN etc.
  • `SUMMARY`—Information like mutual fund summary for total amount invested, current value, number of MFs and more.
  • `TRANSACTIONS`—List of records against some financial data—e.g., a bank statement.
    • | Yes | | `fiTypes` | Specifies the type of financial information being requested for. Possible enums—`DEPOSIT`, `MUTUAL_FUNDS`, `INSURANCE_POLICIES`, `TERM_DEPOSIT`, `RECURRING_DEPOSIT`, `SIP`, `GOVT_SECURITIES`, `EQUITIES`, `BONDS`, `DEBENTURES`, `ETF`, and more. Click here to learn more about the data types. | Yes | -| `vua` | Virtual user address (VUA) that identifies your customer when they login to the Account Aggregator.
    It can be either mobile number or mobile number with handle (**{customer_mobile_number}@onemoney**)
  • If mobile@handle is used, consent will be created for the specified AA
  • If mobile is used, a best performing AA is selected for consent creation
    • | Yes | +| `vua` | Virtual user address (VUA) that identifies your customer when they login to the Account Aggregator.
    It can be either mobile number or mobile number with handle (**{customer_mobile_number}@onemoney**)
  • If mobile@handle is used, consent will be created for the specified AA
  • If mobile is used, a best performing AA is selected for consent creation
    • | Yes | | `purpose` | This is used to indicate the purpose of requesting for data. As per the AA spec, the following codes are supported—
  • `101`—Wealth management service
  • `102`—Customer spending patterns, budget or other reportings
  • `103`—Aggregated statement
  • `104`—Explicit consent to monitor the accounts
  • `105`—Explicit one-time consent for accessing data from the accounts
    • | Yes | | `dataRange` | This is used to specify the `from` and `to` date-time range for querying financial information. It is mandatory only when the `consentTypes` array includes `TRANSACTIONS`. | Mandatory | | `dataLife` | This is the time period for which you are allowed to process the data. Choose between `MONTH`, `YEAR`, `DAY`, `INF` as the `unit` and define a numeric `value` alongside.
    For more details on the difference between Data life and Data Storage, please see [Sahamati guidelines](https://sahamati.org.in/aa-community-guidelines-v1/storage-of-data/) (see SD001 in the table) | Yes | @@ -36,6 +47,7 @@ Consent object contains the information about all the different types of data th | `dataFilter` | Allows you to specify conditions for filtering the data being fetched. For example, fetch transactions where the `TRANSACTIONAMOUNT` is greater than or equal to INR 20,000. You can use the `type`, `operator` like `>, <, <=, >=` and `value` like `5000` keys to set the filters. | No | | `redirectUrl` | Redirect your users back to your application once the consent is reviewed. By default, the redirectURL is https://setu.co/. | Yes | | `context` | Allows you to specify an FIP OR Account type (Current, Savings, Insurance, etc) as a key value pair for you to be able to customise the accounts fetched on the consent flow. We support the context filters `accounttype` which takes the Key as `accounttype` where values can be `CURRENT` or `SAVINGS` and `fipid` with the `FIP ID` as the value(s). | No | +| `additionalParams` | Allows you to specify additional parameters for the consent request. Currently, we have `tags` specified under it. | No | #### Context property examples @@ -83,4 +95,41 @@ Consent object contains the information about all the different types of data th | `status` | Consent status of the consent request `id`. This will be `PENDING` for a newly created consent. | | `Usage` | This field specifies `lastUsed` and `count` which corresponds to data fetches against the consent id. It is also available in Get Consent Status response. | +
    + +### Understanding Tags in AA Framework + +• Tags must first be created at the product instance level before they can be used in any requests. + +• Tags can be created and managed while setting up or updating a product instance. They are unique identifiers (max 100 characters) that can be linked to multiple product instances. + +• Tags are visible in consent and data-fetch reports, and serve as filters in analytics dashboards. Use them to track user journeys, monitor failures, analyze behavior, measure campaign performance, and generate custom insights. + +• Key limitations and rules: + +- Tags are case-insensitive (e.g., "partnerA" = "PartnerA") +- Duplicate tags are not allowed +- Bulk tagging for historical data is not supported +- Number of tags per FIU is configurable +- Invalid characters will trigger errors +- System issues may prevent tag application (with error notifications) + +• Best practice: Use clear, consistent, and easily understandable tag names for effective tracking. + +• To add tags to a consent request, include them under the `additionalParams` field: + + + {`{ + "consentDetail": { + ... + }, + ..., + "additionalParams": { + "tags": ["Loan_Tracking", "Partner_X"] + } +}`} + + +
    +