...
# | Field Name | Description/ Definition |
1 | Performance and Availability | |
1.1 | ReportDate | The reported date for each calendar day. |
1.2 | Entity Name | Reporting entity’s name. |
1.3 | Endpoint ID | Reported EndPoint ID as defined in the API Endpoint List of the Reporting Template. ASPSPs/ AISPs/ PISPs must only report endpoints that have gone live in their systems. |
1.4 | Uptime | Uptime per each individual endpoint in hours and minutes. (Elapsed time) Calculated as 100% minus the total percentage downtime for each day. |
1.5 | Planned Downtime | Any planned duration that the API endpoints become unavailable. For the avoidance of doubt, this extends to include all systems that are required for the relevant endpoint to be fully functional. |
1.6 | Unplanned Downtime | Any unplanned duration that the API endpoints become unavailable due to technical faults or any other reasons. For the avoidance of doubt, this extends to include all systems that are required for the relevant endpoint to be fully functional. |
1.7 | Max Payment Initiations Per Second (PIPS) | This field is only applicable to Payment Initiation Service (PIS) endpoints. For Account Information Service (AIS) endpoints it should be populated with NULL. The maximum number of successful payment initiations per second (PIPS) for the payment order POST API calls. The PIPS must be reported as whole numbers. |
1.8 | Average TTLB Response Time (Time to Last Byte) | The average (mean) value across all values of Time to Last Byte (TTLB) response time for each API endpoint. The response time clock should start at the point the endpoint call is fully received by the ASPSP and should stop at the point the last byte of the response message is transmitted to the AISP or PISP. |
1.9 | Average TTFB Response Time (Time to First Byte) | The average (mean) value across all values of Time to First Byte (TTFB) response time for each API endpoint. The response time clock should start at the point the endpoint call is fully received by the ASPSP. |
1.10 | Total Number of API calls | This is the total number of API calls per day per endpoint. |
1.11 | Total TTLB Response Time (Time to Last Byte) | This is the sum of all the TTLB responses of all endpoint calls of each endpoint type. For the avoidance of doubt, this is the sum of all the TTLB response times generated by the total number of API calls for each endpoint. |
1.12 | Total TTFB Response Time (Time to First Byte) | This is the sum of all the TTFB responses of all endpoint calls of each endpoint type. For the avoidance of doubt, this is the sum of all the TTFB response times generated by the total number of API calls for each endpoint. |
1.13 | Total ResponsePayload Size | This is the sum of the payload of all the response messages for all endpoint calls of each endpoint type. For the avoidance of doubt, this is the sum of all the payloads of the response messages generated by the total number of API calls for each endpoint. |
2 | Authentication | |
2.1 | ReportDate | The reported date for each calendar day. |
2.2 | Entity Name | Reporting entity’s name. |
2.3 | Authentication Type | This is the type of authentication journeys provided by the ASPSP. It will include 'redirection' and where implemented 'decoupled' model. |
2.4 | API Type | This is the type of services that are being reported for the efficacy of the authentication journey. It includes Account Information Services (AIS) and Payment Initiation Services (PIS). |
2.5 | API Request AISP/PISP Channel | This is the reported AISP/PISP channel for initiating the AIS or PIS consent. This may be provided by AISPs/PISPs in the endpoint Request Header under the field 'x-customer-user-agent'. If the string cannot be mapped to a browser, then it will probably be a mobile app. |
2.6 | ASPSP Authentication Channel | This is the reported ASPSP Authentication channel. It can be web-based (Web) or using the mobile banking app (App). |
2.7 | Consents requiring Authentication | The total number of user/customer consents to require authentication at the ASPSP for the particular combination of authentication type, API type, AISP/PISP channel and ASPSP authentication channel. |
2.8 | Authentications Attempted by users/customers | The total number of authentications that have been attempted by the users/customers (not abandoned). This means that the Users/ Customers have tried to authenticate according to the authentication method required providing biometrics, username, passwords etc. |
2.9 | Authentications Abandoned by users/customers | The total number of user/customer consents to require authentication that has been abandoned by the users/customers. |
2.10 | Authentications Succeeded | The total number of consents requiring authentication that have completed authentications by users/customers and the authentications have succeeded. |
2.11 | Authentications Failed | The total number of consents requiring authentication that have completed authentications by users/customers and the authentications have failed. |
2.12 | Confirmations Required | The total number of consents requiring authorization, that after successful authentication, required a confirmation step. |
2.13 | Confirmations Accepted by user/customer | The total number of successful authentications that required a confirmation step and have been accepted by users/customers. This means that the users/customers proceeded with the access request or the payment order submission and did not cancel the process. |
2.14 | Confirmations Rejected by users/customers | The total number of successful authentications that required a confirmation step and have been rejected by users/customers. This means that the users/customers cancelled the process and did not proceed with the access request or the payment order submission. |
3 | User/ Customer Volumes | |
3.1 | ReportMonth | Reported calendar month and year. |
3.2 | Entity Name | Reporting entity’s name. |
3.3 | Retail/Business user/customer | This identifies Retail and Business users/customers for separate reporting. |
3.4 | User/Customer used AIS for the first time | The number of unique users/customers who have authorised access to their account(s) to one or more AISPs for account information services for the first time during the reporting period. For the avoidance of doubt, this refers to new consent/authorisations and not re-authorisations. |
3.5 | Total users/customers used AIS | The total number of unique users/customers who: a. have authorised access to their account(s) to one or more AISPs for account information services during the reporting period for the first time. b. have previously authorised access to their account(s) to one or more AISPs for account information services and had their account accessed at least once by any of the AISPs during the reporting period. c. have previously authorised access to their account(s) to one or more AISPs for account information services and had to re-authenticate to refresh the account access at least for one of the AISPs during the reporting period. |
3.6 | User/Customer used PIS for the first time | The number of unique user/customer who have authorised a payment initiation of any type from any of their account(s) via one or more PISPs for the first time during the reporting period. For the avoidance of doubt, a user/customer initiating a payment (e.g. single domestic) using a PISP A and then initiating another payment of different type (e.g. international) using a PISP B within the same ASPSP , should not be double-counted. For business customers, unique users/customers should refer to all employees of the business who have separate authentication credentials and can be identified separately. Multi-banked users/customers cannot be identified so they may be double-counted by different ASPSPs. |
3.7 | Total users/customers used PIS | The total number of unique users/customers who: a. have authorised a payment initiation of any type from any of their account(s) via one or more PISPs for the first time during the reporting period. b. have authorised a payment initiation of any type from any of their account(s) via one or more PISPs during the reporting period and have initiated payments using PIS services before. |
3.8 | Unique users/customers used both AIS and PIS for the first time | Users/Customers accessing both AIS and PIS using the same authentication credentials. |
3.9 | Total unique users/customers used both AIS and PIS | Total users/customers accessing both AIS and PIS using the same authentication credentials. |
3.10 | Total new users/customers for Online Banking | The number of unique users/customers who have been granted access to Online Banking for the first time. |
3.11 | Total new users/customers for Mobile Banking | The number of unique users/customers who have been granted access to Mobile Banking for the first time. |
3.12 | Total number of users/customers used Online Banking | The total number of unique users/customers who have used the Online Banking service for either accessing account information or initiating a payment. |
3.13 | Total number of users/customers used Mobile Banking | The total number of unique users/customers who have used the Mobile Banking service for either accessing account information or initiating a payment. |
4 | AISP/PISP Volumes | |
4.1 | ReportMonth | Reported calendar month and year. |
4.2 | Entity Name | Reporting entity’s name. |
4.3 | Total AISPs Registered (at 1st of the month) | This is the cumulative total number of AISP’s, that have been already been on-boarded into the live environment (i.e. production environment) with the ASPSP as at the 1st of the reported month. |
4.4 | AISP Additions | This is the number of AISPs that have been on-boarded into the live environment (i.e. production environment) during the reported month. |
4.5 | AISP Deregistrations | This is the number of AISPs, that have been deregistered with the ASPSP during the reported month. |
4.6 | Cumulative Monthly number of AISPs | This is the cumulative total number of AISP’s, that have been already been on-boarded into the live environment (i.e. production environment) with the ASPSP as at the end of the reported month. |
4.7 | Total PISPs Registered (at 1st of the month) | This is the cumulative total number of PISP’s, that have been already been on-boarded into the live environment (i.e. production environment) with the ASPSP as at the 1st of the reported month. |
4.8 | PISP Additions | This is the number of PISPs that have been on-boarded into the live environment (i.e. production environment) during the reported month. |
4.9 | PISP Deregistrations | This is the number of PISPs, that have been deregistered with the ASPSP during the reported month. |
4.10 | Cumulative Monthly number of PISPs | This is the cumulative total number of PISP’s, that have been already been on-boarded into the live environment (i.e. production environment) with the ASPSP as at the end of the reported month. |
5 | Daily Volumes | |
5.1 | ReportDate | The reported date for each calendar day. |
5.2 | Entity Name | Reporting entity’s name. |
5.3 | Endpoint ID | Reported EndPoint ID as defined in the API endpoint list of the Reporting Template. ASPSPs must only report endpoints that have gone live in their systems. |
5.4 | Successful API Calls (200, 201 or 204 codes) | This is the total number of successful endpoint calls for each endpoint that have been received successfully by the ASPSP and generated an AISP/PISP Status Code of 200, 201 or 204 depending on the HTTP method of the endpoints. |
5.5 | Failed API Calls Business Reasons (4xx Codes) | This is the total number of failed endpoint calls for each endpoint that have been received by the ASPSP and failed due to business rules reasons generating an HTPP HTTP Status Code of 4xx). |
5.6 | Failed API Technical Calls Reasons (5xx Codes) | This is the total number of failed endpoint calls for each endpoint that have been received by the ASPSP and failed due to technical reasons (generating an HTPP HTTP Status Code of 500 Internal Server Error). |
5.7 | API Calls Rejected Status | This is the total number of rejected endpoint calls that have been rejected for each defined endpoint which might be due payment/account consent being rejected due to authorisation failing or consent authorisation being rejected, payment initiation being rejected as part of proceeding checks such as technical validation and customer profile. |
...