To be able to trade online securities the user have to know about the balance of his account, so he can decide whether or not he will trade.
For this process the user uses a web api, that will stay online for more than five minutes to be able to trade direct without delay by a new authentication.

It is our understanding of RTS Article 4 (3) d), that given authentication runs off in browser-based application, if user has no activity by online access to his payment accounts. After that the authentication has to be renewed. In browser-based application this means, that the affected functionalities should be deactivated. The session has expired and for further actions a new authentication is required.

The fixed time is impractical in our opinion.

The actual available funds on payment account are constantly displayed in browser-based application for trading securities. The related payment account belongs to the securities account of the user. The payment account is used for clearing transactions on the security account (referring to Question 2018-4023). The user observes trends of securities and wants to be able to act without hesitation in our browser based application. Observing trends of securities often needs more time than five minutes. So we want to avoid, that the user has to renew his authentication for online access to his payment account, when he wants to check his funds for placing an order.

By using the exemption from SCA for payment account information (RTS Art. 10) we (ASPSP) shall be allowed not to apply SCA where the conditions mentioned in RTS are accordingly met. Applying this exemption leads in our opinion to the fact, that we do not have to deactivate the display of payment account information in browser-based application when the user has no activity for five or more minutes. We think, there is no difference between accessing payment account information for example through AISP to accessing it in browser-based application. The channels used for
accessing payment account information are not marked to be relevant for applying exemption from SCA in RTS. So, if user is not accessing payment account information for the first time and the last authentication using SCA is not 90 days or more ago, the payment account information can be displayed independently from activity by the user in the application. When applying SCA for log in the browser-based application the payment account information can constantly displayed, because counting the days starts new with log in every time.

Accessing remittance form can act independent to payment account information in sense ot the five-minute-rule an requires authentication after more than five minutes inactivity. Our focus are the payment account information for displaying them to the user.