Versioning
If you are implementing new payment methods and/or features, please make sure to implement the correct SpecVersion of our API. If you are unsure, you should refer to the newest SpecVersion. Our Changelog will give you further information about the current and past spec-versions. You'll also find the newest Version in the top left of our API Specification. Furthermore, each Payment Method will list the minimum required SpecVersion under its requirements.
Attention: This guide will always assume the latest SpecVersion of the Saferpay JSON API, unless stated otherwise. While some features do work with older versions, please always consult the specification and, if need be, the version, you have currently implemented, as stated below.
Furthermore, it is possible to go back to previous spec-versions, by adding the version to the url. For example, if you want to go back to the 1.4 specification, simply add the version to the url like this:
Note: SpecVersion 1.1 and lower are not available, since those were only released for internal use.
Important Changes in certain SpecVersions
If you plan on upgrading to a newer SpecVersion, you may have to keep the following major and breaking changes in mind:
SpecVersion | Changes |
1.40+ |
|
1.39+ | The |
1.36+ | The values for the parameter Condition have been changed.
|
1.33+ | Error |
1.32+ | The |
1.26+ | The newely introduced parameter |
1.24+ | The |
1.17+ | Alias Insert Redirect: The |
1.12+ | Notification E-Mail: |
1.10+ | Refund Handling: Due to the introduction of Partial Captures and thus the splitting of a transaction into multiple transactions, you must do a refund using the |
1.9+ | Shift of the ThreeDs-container: Due to the introduction of the Fraud Free Service, the Liability can now be accepted by one of two entities. Thusly the old |
Tip: You should also keep an eye on our API Changelog, where we keep a record of API changes!
Last updated