diff --git a/content/data/account-aggregator/api-integration/account-availability-apis.mdx b/content/data/account-aggregator/api-integration/account-availability-apis.mdx index a9b11929..dfe2a150 100644 --- a/content/data/account-aggregator/api-integration/account-availability-apis.mdx +++ b/content/data/account-aggregator/api-integration/account-availability-apis.mdx @@ -51,7 +51,7 @@ Body: }, { "aa": "setu-aa", - "vua": "9999999999@onemoney", + "vua": "9999999999@setu", "status": false } ], diff --git a/content/data/account-aggregator/api-integration/consent-flow.mdx b/content/data/account-aggregator/api-integration/consent-flow.mdx index 796d27f1..8f4245b7 100644 --- a/content/data/account-aggregator/api-integration/consent-flow.mdx +++ b/content/data/account-aggregator/api-integration/consent-flow.mdx @@ -32,7 +32,7 @@ Call this API to create a consent request. The details of the request will be pr "unit" : "MONTH", "value": "4" }, - "vua": "999999999@onemoney", + "vua": "999999999", // {{mobile}} or {{mobile}}@handle. Ex: 999999999@setu or 999999999@onemoney "dataRange": { "from": "2020-04-01T00:00:00Z", "to": "2023-01-01T00:00:00Z" @@ -228,7 +228,7 @@ If the consent is approved, the status in the response will be `ACTIVE`. After t "status": "PENDING", "context": [], "detail": { - "vua": "9999999999@onemoney", + "vua": "9999999999@anumati", "consentStart": "2023-04-04T07:10:41.165Z", "consentExpiry": "2023-08-02T12:40:41.165Z" }, @@ -268,7 +268,7 @@ If the consent is approved, the status in the response will be `ACTIVE`. After t "unit": "MONTH" }, "fetchType": "PERIODIC", - "vua": "99999999999@onemoney", + "vua": "99999999999@anumati", "dataLife": { "value": 1, "unit": "YEAR" diff --git a/content/data/account-aggregator/consent-object.mdx b/content/data/account-aggregator/consent-object.mdx index 8e45f407..f9adbad9 100644 --- a/content/data/account-aggregator/consent-object.mdx +++ b/content/data/account-aggregator/consent-object.mdx @@ -28,7 +28,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 should be sent in the format of **{customer_mobile_number}@onemoney-aa** | 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 | diff --git a/content/data/account-aggregator/overview.mdx b/content/data/account-aggregator/overview.mdx index 7802561a..bddaa60f 100644 --- a/content/data/account-aggregator/overview.mdx +++ b/content/data/account-aggregator/overview.mdx @@ -7,7 +7,7 @@ visible_in_sidebar: true ## Account Aggregator -Account aggregators(AAs) are regulated entities that facilitate consented sharing of financial data by utilising the DEPA framework. They act as the bridge between data providers such as banks, and data consumers such as lenders—to enable the sharing of a user’s financial data based on their explicit consent. Setu currently provides AA-related services in close partnership with a fully-licensed AA. +Account aggregators(AAs) are regulated entities that facilitate consented sharing of financial data by utilising the DEPA framework. They act as the bridge between data providers such as banks, and data consumers such as lenders—to enable the sharing of a user’s financial data based on their explicit consent. Setu currently provides AA-related services in close partnership with fully-licensed AA(s). Data providers are called Financial Information Providers (FIPs) and data diff --git a/content/data/account-aggregator/v1/api-integration/consent-flow.mdx b/content/data/account-aggregator/v1/api-integration/consent-flow.mdx index fe9be8e9..b759b700 100644 --- a/content/data/account-aggregator/v1/api-integration/consent-flow.mdx +++ b/content/data/account-aggregator/v1/api-integration/consent-flow.mdx @@ -34,7 +34,7 @@ Read up more about the the `Detail` object
  • `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, buy/sell orders in a equities account, etc.
    • | Yes | | `fiTypes` | An 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. | Yes | | `DataConsumer.id` | This is the identifier for the entity that’s requesting for the data.
    On UAT, it is a static value – “setu-fiu-id”
    On production, it will be a unique “FIU ID” assigned to your organizaiton. | Yes | -| `Customer.id` | What your customer would use to login to Setu’s AA. It should be sent in the format of **@onemoney**
    Use this to pass on the customer's phone number and auto-fill their number when they login. | Yes | +| `Customer.id` | What your customer would use to login to Setu’s AA. It should be sent in the format of **@finvu**
    Use this to pass on the customer's phone number and auto-fill their number when they login. | 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(single option) | | `FIDataRange` | 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`.
    The `from` and `to` date-time can be both - past dates & future dates. Future dates, typically correspond to `PERIODIC` fetches, while a `from` and `to` date-time in the past corresponds to ONETIME fetches. | Only when `consentTypes` array includes `TRANSACTIONS` | | `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 ‘DataLife’ & “Data Storage” please [click here](https://sahamati.org.in/aa-community-guidelines-v1/storage-of-data/) (check SD001 from the list of guidelines) | Yes | diff --git a/content/data/account-aggregator/v1/overview.mdx b/content/data/account-aggregator/v1/overview.mdx index c38d536c..6962492a 100644 --- a/content/data/account-aggregator/v1/overview.mdx +++ b/content/data/account-aggregator/v1/overview.mdx @@ -7,7 +7,7 @@ visible_in_sidebar: true ## Account Aggregator -Account aggregators(AAs) are regulated entities that facilitate consented sharing of financial data by utilising the DEPA framework. They act as the bridge between data providers such as banks, and data consumers such as lenders—to enable the sharing of a user’s financial data based on their explicit consent. Setu currently provides AA-related services in close partnership with a fully-licensed AA. +Account aggregators(AAs) are regulated entities that facilitate consented sharing of financial data by utilising the DEPA framework. They act as the bridge between data providers such as banks, and data consumers such as lenders—to enable the sharing of a user’s financial data based on their explicit consent. Setu currently provides AA-related services in close partnership with fully-licensed AA(s). Data providers are called Financial Information Providers (FIPs) and data @@ -38,7 +38,7 @@ Try out our sample app built using Setu AA sandbox licensed NBFC-AA partner. The AA framework opens up a lot of opportunities for FIU apps to build financial user journeys with seamless user consented data sharing. This allows developers to build tech-first user applications and features powered by digital data sharing flows over conventional PDF documents upload. Some of the use cases worth exploring: +Setu’s AA related services are powered by licensed NBFC-AA partners. The AA framework opens up a lot of opportunities for FIU apps to build financial user journeys with seamless user consented data sharing. This allows developers to build tech-first user applications and features powered by digital data sharing flows over conventional PDF documents upload. Some of the use cases worth exploring: 1. **Income Verification** - Get access to users’ bank statements with their consents. While Setu AA ensures that the data payload remains standardised and error free, simplify your user verification process and improve conversion rates! 2. **Loan Monitoring** - Monitor your borrower’s financial health after loan disbursal by analysing cash flow across a user’s bank accounts. As a lender, get early signals from a user's bank statements and prevent potential loan defaults.