saferpay api update 1.23 => 1.31 #91
Conversation
* changes according to http://saferpay.github.io/jsonapi/#v1.24.0.0.20210914 Closes: Ticketpark#60 BREAKING-CHANGE: replaced Notification->notifyUrl with Notification->successNotifyUrl and Notification->failNotifyUrl
* changes according to http://saferpay.github.io/jsonapi/#v1.25.0.0.20211116 Closes: Ticketpark#61
* changes according to http://saferpay.github.io/jsonapi/#v1.26.0.0.20220118 Closes: Ticketpark#62 BREAKING-CHANGE: replaced AddressForm->display with AddressForm->addressSource
…>isB2B * the Order property in RiskFactors is invalid, it should be IsB2B. BREAKING-CHANGE: replaced invalid RiskFactors->order with RiskFactors->isB2B
* changes according to http://saferpay.github.io/jsonapi/#v1.27.0.0.20220315 Closes: Ticketpark#63
* changes according to http://saferpay.github.io/jsonapi/#v1.28.0.0.20220517 Closes: Ticketpark#64
* changes according to http://saferpay.github.io/jsonapi/#v1.30.0.0.20220920 * 1.29 and 1.31 do not contain any API interface changes Closes: Ticketpark#71, Ticketpark#72, Ticketpark#73
|
Thank you very much for this valuable contribution! I added some more changes in #93 (mostly replaced serializer types with native property types) and merged this. If you want, you are welcome to take the current master branch on a test drive as a potential v5.0 of this library. |
We are directly testing https://github.com/i-web/SaferpayJsonApi/tree/Saferpay-Api-Update-BC this week (we need 1.37 because of the new PaymentMethod POSTFINANCEPAY) and are planning on taking it to production by the end of the week. |
|
@giriroub How did your release go? |
|
The release passed all our tests, but we haven't deployed it yet. Due to other circumstances this might take another couple weeks. |
Closes #60, #61, #62, #63, #64, #71, #72, #73
This PR contains all changes from 1.23 to 1.31, according to http://saferpay.github.io/jsonapi/#changelog