The consent Detail object is the core of the AA framework. When an FIU requires data about the user, the request is packaged in the form of a consent object.

This consent object carries 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. All params described below are required, except for DataFilter.

Property nameDescription
consentStart and consentExpiryDate time fields that define the time period for which the consent is valid and can be use for data fetch.
consentModeEnum for the type of consent. Possible values are VIEW, STORE, QUERY, STREAM
fetchTypeEnum to specify either ONETIME or PERIODIC fetch of data.
consentTypesAn array to specify 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.
  • fiTypesAn array specifying 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.
    DataConsumer.idThis is the identifier for the entity that’s requesting for the data
    Customer.idWhat your customer would use to login to Setu’s AA. It should be sent in the format of <customer_mobile_number>@onemoney-aa
    PurposeThis 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
  • FIDataRangeThis 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.
    DataLifeThis is the time period for which you are allowed to store the data. Choose between MONTH, YEAR, DAY, INF as the unit and define a numeric value alongside.
    Frequency has 2 components—unit and valueunit can be HOURLY, DAILY, MONTHLY, YEARLY. value has to be greater than 0.
    Additionally the maximum frequency value is defined is 1 request per HOUR. So, no more than 24 requests are allowed per DAY
    DataFilterAllows 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 and value keys to set the filters.
    redirectUrlRedirect your users back to your application once the consent is reviewed. By default, the redirectURL is
    Property NameDescription
    idUnique consent reference Id generated by Setu. Use this to poll consent status or initiate data session requests.
    urlRedirect your users to Setu AA screens to initiate consent review flow using this url
    statusConsent status of the consent request id. This will be PENDING for a newly created consent.
    UsageThis field specifies lastUsed and count which corresponds to data fetches against the consent id. It is also available in Get Consent Status response.

    Was this page helpful?