Note on performance for STET PSD2 with Airlock IAM

The Airlock Gateway (WAF) sends all bank API request to Airlock IAM for verification according to STET PSD2 (see STET interaction models for details). This adds latency to every bank API request and consumes a considerable amount of CPU power in Airlock IAM.

Therefore you need to think about scaling when using the feature.

So far, there are no performance measures or real-life experiences available. The following is an assumption and not a guarantee!

We assume that performance is likely to be the same as described in Performance measures (scaling example) for NextGenPSD2 (Airlock IAM), resulting about being able to handle 1000 requests/second adding 50ms of latency (conditions see linked page).