Resource validity time
General information
The Berlin Group standard strongly recommends limiting the validity time of resources created through the XS2A interface.
During the first request/response interaction, the ASPSP generates a new resource representing this transaction. The default validity time of this resource is 30
minutes.
During this validity time, the TPP may address the resource by means of requests permitted by XS2A API.
Validation rules
In the XS2A interface, the validity time check is applied on
/{consentId}
whereconsentStatus
=received
consent
/{authorisationId}
wherescaStatus
<>finalized
payment
/{authorisationId}
wherescaStatus
<>finalized
- for all payment types (single, periodic, bulk) and products.Learn more about payment products at Payment Products and Services.
Consent
Consent authorisation must be completed within the defined validity time.
If consent validity time is over and consent status = received
then the status of the consent is changed to rejected
.
The authorisation of given consent is no longer possible. This means, a new consent creation must be initiated.
Consent authorisation sub-resource
If consent authorisation validity time is over and its scaStatus
<> finalized
then scaStatus
is changed to failed
.
The authorisation of consent with the given authorisationId
is no longer possible. This means, a new consent authorisation must be initiated.
Payment authorisation sub-resource
If payment authorisation validity time is over and its scaStatus
<> finalized
then scaStatus
is changed to failed
.
The authorisation of payment with the given authorisationId
is no longer possible. This means, a new payment authorisation must be initiated.