Now we can set parameters for delta-report support and redirect expiration time in ASPSP-Profile.
| Option | Meaning | Default value | Possible values |
|---|---|---|---|
deltaReportSupported |
This field indicates if an ASPSP supports Delta reports for transaction details |
false |
true, false |
redirectUrlExpirationTimeMs |
This field contains the limit of an expiration time of redirect url set in milliseconds |
600 000 |
milliseconds (1, 2,…) |
Now Swagger is not enabled for XS2A Interface by default.
To enable swagger in xs2a you have to add @EnableXs2aSwagger annotation on any of Spring configuration classes / Spring boot Application class in your application. To disable swagger just remove it.
You could also put PSD2 API yaml file to the resource folder of your connector to override default PSD2 API. To do that you need to fill in
xs2a.swagger.psd2.api.location property in your application.properties file. I.e.
xs2a.swagger.psd.api.location=path/in/my/classpath/my_swagger_api.yml
Now Swagger is not enabled for CMS Interface by default.
To enable swagger in cms you have to add @EnableCmsSwagger annotation on any of Spring configuration classes / Spring boot Application class in your CMS application. To disable swagger just remove it.
Now instead of using PaymentProduct enum class, string value is used. PaymentProduct enum class is removed. In database, instead of saving enum values(SEPA, INSTANT_SEPA, etc), raw string values are saved: sepa-credit-transfers, instant-sepa-credit-transfers, etc.
| Context | Method | Endpoint | Description |
|---|---|---|---|
Payment Initiation Request |
GET |
v1/{payment-service}/{paymentId}/authorisations |
Will deliver an array of resource identifications of all generated authorisation sub-resources. |
Account Information Consent Request |
GET |
v1/consents/{consentId}/authorisations |
Will deliver an array of resource identifications of all generated authorisation sub-resources. |
When payment is finished (has transaction statuses Cancelled, Rejected, AcceptedSettlementCompleted) there is no possibility to cancel it or to proceed payment cancellation authorisation flow. The error "FORMAT_ERROR" with http status 400 and TPP message "Payment is finalised already and cannot be cancelled" will be displayed.
Redirect url and related authorisation now have an expiration time. The value for expiration time is counted with formula "current time of authorisation creation + redirect url expiration time (set in ASPSP-profile)". We give redirect id (= authorisation id) in redirect link now (instead of payment id and authorisation id in previous versions), and to get payment/consent id and related payment information, online banking should call GET /psu-api/v1/pis/consent/redirect/{redirect-id} endpoint of consent management system. If redirect url is not expired, online banking gets payment, authorisation id, not ok tpp redirect url and ok tpp redirect url in response, otherwise http code 408 Request Timeout is sent.
Now the whole PIIS Consent object is being passed to FundsConfirmationSpi#performFundsSufficientCheck instead of just consent id. Also FundsConfirmationSpi#performFundsSufficientCheck now responds with de.adorsys.psd2.xs2a.spi.domain.fund.SpiFundsConfirmationResponse instead of java.lang.Boolean.
In order to provide a possibility to return list of transactions in other formats than JSON, i.e. MT9x,
AccountSpi::requestTransactionsForAccount now gets a string with acceptable content-types from TPP.
If required content-type is not supported, NOT_SUPPORTED response should be returned. Otherwise SPI Developer
can provide a raw transactions list, supplemented with a content-type. It will be proxied to TPP without further handling.
See corresponding method’s javadocs for more details.
Now AIS Consent contains TppInfo object instead of TPP Id. Developers should apply new liquibase migration scripts in order to update the database.
Now XS2A and CMS Interceptors, Advices and Filters are limited to specific packages and paths and won’t interfere with other controllers.
XS2A Advices are only applied to controllers, located in the de.adorsys.psd2.xs2a.web.controller package. XS2A Interceptors and Filters are applied only to the following endpoints: /v1/accounts, /v1/consents, /v1/funds-confirmations, /v1/payments, /v1/bulk-payments, /v1/periodic-payments and /v1/signing-baskets.
CMS Advices are only applied to controllers, located in the following packages: de.adorsys.psd2.consent.web.aspsp.controller, de.adorsys.psd2.consent.web.psu.controller and de.adorsys.psd2.consent.web.xs2a.controller