#Analytics and reports
#Overview
Analytics and reports are separate per product, since they function differently. For payments products like UPI, or BBPS, you get details related to customer payments; while for data products like Account Aggregator or our KYC suite, you can view all data requests and success rates.
Analytics for live products are made available on the home page, and provide an overview of your integration’s performance. You can dive into detailed analytics and reports for more information on each transaction or data request, their statuses, and other relevant details.
Reports, with all columns included, can also be downloaded in CSV or Excel formats for a specified time range. If the count of rows in the table is too large, you will get an option to mail it to yourself.
#Are combined analytics and reports available for my products?
Yes, the Bridge aggregates data across product instances and child accounts, but only within each product category.
For example, let’s say your company is ABC Pvt. Ltd. You have multiple child sub-orgs with Setu, as described below:
- One Account Aggregator sub-org for an FIU integration.
- Two BBPS BOU sub-orgs for different BBPS BOU biller integrations. Let’s say your company offers different products to customer via two subsidiaries—ABC Loans for lending and ABC Mutual Funds for distributing ETFs. Since these are two separate entities, Setu needs to do KYC verification and on-boarding for each entity, to let you collect payments for these use cases via BBPS.
In this case, analytics and reports are separate for the Account Aggregator and BBPS BOU product categories. But for BBPS BOU, data is combined across both child accounts by default, and you can filter reports by product instance ID on the UI to view them separately.
#Who can access the reports?
Admin or reporter roles can both access product data. However, you can choose to limit access when you have multiple child sub-orgs—you can extend access to data across multiple child accounts, or only a subset of child accounts.
You can control access for users by going to Settings > User management. Select the child account to add a new user or edit access for an existing one. Please note, you can view and edit user details only if you are an admin for the parent Bridge account, or at least one of its child accounts that you want to control access to.
#Ignore below data for Docs, but a refined version can be used to train AI bot
Account Aggregator
The account aggregator API consists of two components: consent request and data fetch. Analytics reports provide insights into the performance of both APIs. Each analytics and report can be filtered by time period or product instance.
1. Analytics
The consent request API enables the generation of consent requests, which can subsequently be approved, rejected, or left pending. Analytics provide insights into the total number of consent requests generated and their statuses, such as approved, pending, or rejected.
From consent generation to approval, several steps are involved, including consent generation, opening of the approval interface, user login, account verification, and final approval. Analytics offer insights into each of these steps through a funnel visualisation.
Consent request generation and conversion trends can be monitored for specific time periods. Additionally, if any consent remains pending or gets rejected, the system displays the reason for it.
2. Reports
The consent request report displays details for each request. It includes data points such as consent ID, mobile number, consent creation time, consent status, approval or rejection time, number of accounts linked, user AA handle, purpose, FIP, last user event, multi-consent ID, and product ID.
These reports can be emailed or downloaded in CSV or XLSX format. Invoices for any particular month can also be downloaded from the reports section.
Various filters are available, including product instance, time range, consent status, consent ID, FIP, mobile number, fetch type, and purpose code.
BBPS Collect
For BBPS BOU, there are three main categories for analytics and reports:
- Transactions
- Refunds
- Disputes
Each report and analytics section can be filtered by time period or product instance.
1. Analytics
This section provides data on transaction completion, transaction failure, total amount collected, and expired payment requests.
The distribution of various apps used to complete these transactions can also be analyzed. Additional insights include transaction failure reasons and category distribution across all transactions.
2. Reports
The transaction report contains details of each transaction, with data points such as transaction ID, transaction status, RRN, net amount, last update time, payer VPA, payee VPA, product type, MDR charge, and failure reasons if applicable.
Filters are available for transaction ID, product instance, time frame, transaction status, RRN, transaction amount range, payer VPA, payee VPA, and product type.
These reports can be emailed or downloaded in CSV or XLSX format.
KYC
1. Analytics
PAN analytics gives you insights into how the PAN API is performing. It shows details like how many PAN verification requests have been made, how many failed, and what the success-to-failure ratio looks like. You can also view reasons for failure through easy-to-understand visuals. You can filter these analytics by any timeframe you choose.
2. Reports
PAN reports provide a breakdown of each PAN request. Key details include request ID, verification status, verification time, and the failure reason (if applicable). You can filter reports by request ID or verification status. You also have the option to email or download the reports in CSV or XLSX format.
UPI
For Setu UPI, there are five main categories for analytics and reports:
- Transactions
- Mandates
- Refunds
- Disputes
- Settlement
Each report and analytics section can be filtered by time period or product instance.
1. Analytics
This section provides data on transactions, including the total payments processed, total transaction amount, and average time to complete payments.
The distribution of various apps used to complete these transactions can also be analysed.
Additionally, insights into the success and failure rates of transactions, along with failure reason distribution, are provided. These analytics can be filtered by time period, merchant, integrated product, and payer apps.
2. Reports
The transaction report contains details of each transaction, including data points such as transaction ID, RRN, net amount, transaction status, last update time, payer VPA, payee VPA, product type, MDR charge, and failure reasons if applicable.
Filters are available for transaction ID, time frame, transaction status, integrated products, RRN, transaction amount range, payer VPA, payee VPA, and product type.
These reports can be emailed or downloaded in CSV or XLSX format.
Was this page helpful?