-
Support List of Trusted Beneficiaries Service
-
Bugfix: Validation does not work when using multiple values as accept header
-
Move certificate generator from XS2ASandbox to XS2A-core
-
Change type of
requestDateTime
inConsentEntity
-
Remove deprecated PaymentAuthorisationType
-
Drop deprecated tables for AIS and PIS authorisations
-
Remove deprecated PiisConsentTppAccessType
-
Move authorisation-related methods in separate service
From now on, it’s possible to create consent consent to get list of trusted beneficiaries. In order to do it,
one needs to update ASPSP profile settings with flag trustedBeneficiariesSupported
= true
and send to create
dedicated consent request with trustedBeneficiaries
list inside additionalInformation
.
If trustedBeneficiariesSupported
is false
, list trustedBeneficiaries
in create consent request body will be
ignored and not stored in database.
If detailed accounts are referenced, it is required in addition that any account addressed within the
additionalInformation attribute is also addressed by at least one of the attributes accounts
, transactions
or
balances
. If this requirement is not met, one will get en error 400 SERVICE_INVALID
.
It’s also possible to get consent object with attribute trustedBeneficiaries
from CMS PSU API
and update it in case
of Bank-Offered consent.
From now on, validation processes properly multiple accept headers.
From now on, certificate generator is located in XS2A project. All functionality remains as is.
See SPI Developer Guide
for more details.
From now on, type of requestDateTime
in ConsentEntity
was changed from LocalDateTime
to OffsetDateTime
.
The following columns (request_date_time
and creation_timestamp
) were modified data type to DATETIME
.
Following deprecated tables were dropped from CMS database:
-
ais_consent_authorization
-
pis_consent_authorization
-
ais_available_sca_method
-
pis_available_sca_method