-
Remove deprecated methods in SpiResponse
-
Removed deprecated enum
-
Wrong error code on deleting an account information consent
-
Bugfix: NPE during executing Confirmation of Funds request without currency
-
Bugfix:
batchBookingPreferred
is not persisted for bulk payments -
Event query for Oracle DB was fixed
-
Refactor: PaymentAuthorisationType enum moved to xs2a-core
-
Update version of jackson-databind to 2.9.9.3
-
Migrate to .yaml OpenAPI v. 1.3.4
-
Added fundsAvailable field in getPaymentStatusById response
-
POST cancellation-authorisations doesn’t return cancellationId
-
TPP URIs compliance checks
-
Added
Error 406
for PIS -
Get PIIS consent results with error
From now on, some changes in SpiResponse
and SpiResponseStatus
were made:
-
removed method
fail()
in builderSpiResponseBuilder
, please usebuild()
instead; -
removed
responseStatus
property fromSpiResponseBuilder
builder, please useerror()
method instead; -
removed
getMessages()
method fromSpiResponse
class; -
removed
responseStatus
property fromSpiResponse
class; -
removed
SpiResponseStatus
enumerator.
Removed deprecated enum value ALL_ACCOUNTS_WITH_BALANCES
in AccountAccessType
class.
From now on, trying to delete account information consent (via DELETE /v1/consents/{consentId}
endpoint) with TPP
certificate that differs from the one used for creating the consent will result in an error with HTTP code 403 instead of 400.
The same change has also been applied to following endpoints:
- Get Status Request (GET /v1/consents/{consentId}/status
)
- Get Consent Request (GET /v1/consents/{consentId}
)
- Start Authorisation Request (POST /v1/consents/{consentId}/authorisations
)
- Update PSU Data Request (PUT /v1/consents/{consentId}/authorisations/{authorsationId}
)
- Get SCA Status Request (GET /v1/consents/{consentId}/authorisations/{authorisationId}
)
- Get Authorisation Sub-Resources Request (GET /v1/consents/{consentId}/authorisations
)
From now on, it is possible to create PIIS consent without the currency in AccountReference and launch the funds
confirmation request for it (POST /v1/funds-confirmations
) without the currency in account
field.
From now on, batchBookingPreferred
field is persisted for bulk payment during the payment initiation request (POST /v1/{payment-service}/{payment-product}
)
and return correct value on get payment information request (GET /v1/{payment-service}/{payment-product}/{paymentId}
)
From now on, CMS endpoint GET /aspsp-api/v1/events/
performs correctly on Oracle DB (before it was Internal Server Error
response).
Now the database schema is set with spring.jpa.properties.hibernate.default_schema
property and must be provided explicitly.
PaymentAuthorisationType
enumerator was moved to xs2a-core and CmsAuthorisationType
enumerator was deleted and
replaced with PaymentAuthorisationType
.
Fixed severe security vulnerability detected in com.fasterxml.jackson.core:jackson-databind < 2.9.9.2 defined in pom.xml.
XS2A models and interfaces were updated in accordance with version 1.3.4 of OpenAPI 3.0 file by Berlin Group.
-
Field
data
fromChallengeData
is changed type to list of string. -
Fields in
Address
are changed: city → townName, street → streetName, postalCode → postCode -
Field
availableAccountsWithBalance
inAccountAccess
is renamed fromavailableAccountsWithBalances
-
Field
creditLimitIncluded
is added inSpiAccountBalance
From now on, get payment status requests (GET /v1/{payment-service}/{payment-product}/{paymentId}/status
) can return
information about fundsAvailable
. Additionally some changes in payment SPI were made:
-
Added class
SpiGetPaymentStatusResponse.java
; -
The return type of
PaymentSpi#getPaymentStatusById
changed fromTransactionStatus
toSpiGetPaymentResponse
.
From now on, response on start authorisation for payment cancellation (POST /v1/{payment-service}/{payment-product}/{paymentId}/cancellation-authorisations
)
will contain cancellationId
property instead of authorisationId
.
From now on, TPP URIs from TPP-Redirect-URI
and TPP-Nok-Redirect-URI
headers are being checked for compliance
with TPP eIDAS QWAC certificate URIs (CN
or SubjectAltName
fields).
If URIs are not compliant 400 FORMAT_ERROR
error will be returned in the response.