Q:
If PSU (Payment Service User) will not complete SCA (Strong Customer Authentication), when a session is terminated?
A:
It's terminated after 10 minutes.
Q:
If the PSU does not confirm a payment, when is the session terminated?
A:
There is no timeout configured for this scenario. The payment will remain in the PendingConfirmation state indefinitely.
Q:
If PSU aborts the flow right after being redirected to the bank, when a session is terminated?
A:
It's terminated after 10 minutes.
Q:
How long does it usually take for a payment to change to "Rejected" or "Cancelled" if a PSU leaves the payment process before finishing?
A:
It's 15 minutes for Single SCA and 20 × 30 seconds (10 minutes) for 2SCA.
Q:
Is there any action that the PSU or TPP can take to force the payment into a "Cancelled" or "Rejected" state sooner if the PSU no longer intends to complete the payment journey?
A:
The session is cancelled when the PSU clicks the cancel button on the payment confirmation screen in the BankID SE application.
Q:
If a user abandons a payment journey on one platform and later wishes to start a new payment on either that platform or another, what approaches enable the establishment of a new BankID SE session without requiring the original journey to conclude first?
A:
A BankID session for a particular PSU is global within the Nordea context. Consequently, there will be no possibility of initiating a new session when the flow passes through a different TPP.
Q:
Is there any relationship between AIS consents and payment journeys? Can an active or pending AIS consent affect the creation of a new PIS payment journey or prevent the establishment of a new BankID SE session?
A:
Some scopes may result in consents not being received for certain accounts. In such cases, any payment from an account for which consent has not been received will be blocked during the confirmation stage.