Releases
RELEASE_20201006.00
|
Sandbox
|
Published on 15 Oct 2020
|
Sandbox
|
|
Pre-prod
|
Published on 15 Oct 2020
|
Pre-prod
|
|
Prod
|
Published on 22 Oct 2020
|
Prod
|
Highlights
- To better comply with the Swedish payment product selection regulation the getPaymentProducts call sorts payment products differently for Sweden. Debit products come first. The payment product selection page in the MyCheckout hosted payment pages now shows debit products on top for Swedish consumers
- Fixed a bug with the post purchase engagement flow
Components updated in this release
View detailed release notes for each component
RELEASE_20200922.00
Highlights
- Expanded the input properties for the mobilePaymentMethodSpecific input object to allow more control over the way we process Apple Pay and Google Pay transactions
- Included the ability to provide threeDSecure related properties for Google Pay transactions to support a full 3D Secure flow on PAN_ONLY transactions to comply with the PSD2 SCA regulation
- Loosened the restrictions on allowed input characters for the cardHolderName field. We are now substituting characters that are being used by issuers on their cards that do not meet the very strict validation rules from EMVco in their 3Dv2 specification. This way we are not frustrating consumers when entering the name as it is printed on their card, while we also make sure we maximize the number of 3Dv2 successful authentications
- Some more improvements to our API documentation and fixed a bug regarding the validation of the currencyCode in our IIN lookup API
Components updated in this release
View detailed release notes for each component
RELEASE_20200908.00
Highlights
- We are now returning a new property acquirerCountry as part of the getPaymentProduct and getPaymentProducts responses to indicate the location of the acquirer that will most likely process the transaction. This has been added to support use cases for both Google Pay and Apple Pay that need this information to make sure they are compliant with PSD2 Strong Customer Authentication requirements.
- Events for Apple Pay and Google Pay payments are now transmitted (if you have subscribed to these payment events)
- Resolved an error which appeared in case you update a token with an obfuscated card number
- Various other bug fixes
Components updated in this release
View detailed release notes for each component
RELEASE_20200825.01
Fixed
- If you send in numberOfInstallments greater than 1, we no longer reject the request in case the service provider configured for your account does not support installments.
Components updated in this release
View detailed release notes for each component