1. Introduction

This page provides a generalised view of API performance across TPPs, the API Hub, and LFIs.

...

• The operation for a TPP to get a new Access Token, when required, is out-of-scope of the SLA.

• The TTLB for each API call (e.g. post /payments) should be 500ms from the time the TPP makes the call to the API Hub to the time the TPP receives the response back from the API Hub.

• The TTLB for each API call made by the API Hub to a given LFI is 250m.

• The Bulk/Batch Payments operations to upload a payment file and retrieve a payment report is out-of-scope of the API performance SLA and there this diagram. This is due to the inherent latency of these operations, due to the size of the data transfer being undertaken.

• Response datasets greater than 100 records will be paged. Each page is subject to the API Performance SLA.

• All Aani SLAs that are relevant to the end-to-end flow are shown for information and do not dictate the required flow for processing an Aani Credit Transfer.

• All Aani SLAs must be read separately to Open Finance Framework SLAs as the subsequent steps at Aani are completed asynchronously.

• Aani SLAs are only shown in the context of a real-time credit transfer message, as defined in Section 15.2.2.1 of the Aani Rulebook.

• The terms “Payer” and “Payee” are used in this context as they reflect the definition of the SLA definitions in the Aani Rulebook.

2. Sequence Diagram

...