Releases
RELEASE_20230928.00
Published on 27 Sep 2023
|
Sandbox
|
Published on 27 Sep 2023
|
Pre-prod
|
Published on 28 Sep 2023
|
Prod
|
Added
- Added the hostedCheckoutSpecificInput.recurringPaymentsData object for the POST /v1/{merchantId}/hostedcheckouts endpoint. We will provide more information soon about the new feature related to this object.
- The complete payment endpoint can now be used for completing 3D Secure payments.
- The getInstallmentInfo endpoint has been added, which will provide you information about the available installment plans for consumers in Turkey. Please reach out to your account manager if you want to offer installments in Turkey.
- It is now possible to enable 2-Step 3D Secure on the feature configuration page.
Fixed
- Resolved an issue where if a customer selects to pay with a token that did not contain a cardholderName on the MyCheckout hosted payment pages, the token would not be updated with the newly provided cardholderName
- Resolved an issue where if a customer selects to pay with a token that contains a cardholderName on the MyCheckout hosted payment pages, the cardholderName field would not be editable
- ThirdPartyStatus.COMPLETED is now being returned if the pix payment is successful, declined or expired.
- Fixed an issue with find payments.
- The property KeyValuePair.value is now returned even when the value is null.
- The property merchant is now made visible on the CreateHostedCheckoutRequest.
- Payment products where not updated when changing between different currencies.
- Payment products without instructions are now not being shown in the editor.
- Resolved an issue that caused the MyCheckout editor to remain stuck on the loading screen.
- A JavaScript runtime error that will prevent browser data to be collected at payment time.
- Fixed an issue with testing webhooks endpoints.
- Registered shared subdomains are now being displayed as registered at Apple.
- Fixed an issue so that token events are ignored in case tokenization failed.
Changed
- The property networkTokenData.cryptogram is now optional if you create a payment with an external network token.
- The Responsive Payment Pages flow for Pix (ppid 6105) has been improved with an intermediate page to show the user that the Responsive Payment Page is waiting for the payment to be completed.
Components updated in this release
View detailed release notes for each component
RELEASE_20230810.00
Highlights
The highlights of this release are:
Added
- The properties refundOutput.cardRefundMethodSpecificOutput.card.cardNumber and refundOutput.cardRefundMethodSpecificOutput.card.expiryDate are added on the refund response.
- The properties payoutOutput.references.providerId, payoutOutput.references.providerMerchantId and ~statusOutput.isRetriable~ are now returned on the Payout response.
- Added support for 2-step 3D-Secure on the WL Online Payment Acceptance only.
- It is now possible to find payments based on a merchantReference.
Fixed
- Resolved an issue where if a customer selects to pay with a token that did not contain a cardholderName on the MyCheckout hosted payment pages, the token would not be updated with the newly provided cardholderName.
- Resolved an issue where if a customer selects to pay with a token that contains a cardholderName on the MyCheckout hosted payment pages, the cardholderName field would not be editable by the consumer.
- Fixed an issue so that subdomains are correctly displayed in the configuration center.
- Fixed an issue with registering shared subdomains at Apple in the configuration center.
- Fixed an issue that was causing the copy button on the dashboard to copy the wrong content in the configuration center.
Changed
- The payment status CAPTURED is now returned if you retrieve a payment with a final partial capture.
- Updated Google Pay logo to its latest version.
Components updated in this release
View detailed release notes for each component
RELEASE_20230622.00
Highlights
Added
- payoutOutput.references.merchantReference is now returned for payouts in the webhook event.
- The properties payment.paymentOutput.references.providerId, payment.statusOutput.isRetriable payment.statusOutput.providerRawOutput, payment.paymentOutput.references.providerMerchantId and payment.cardPaymentMethodSpecificOutput.authorisationCode are now returned on the payment response.
- Added the new response property isCheckedRememberMe for the getHostedCheckout API call, which will allow you to see whether a customer ticked the "Remember my details for future purchases" checkbox on the page on which they enter their card details and press the actual pay button.
- It is now possible to create payments using an externally provisioned network token. The data regarding such a network token can be submitted using the cardPaymentMethodSpecificInput.networkTokenData object.
- Create and Get Payout now return payoutOutput.references.merchantReference.
Changed
- The property cardPaymentMethodSpecificInput.networkTokenData.eci is now made optional.
- Refunds that are requested will move to the REFUND_REQUESTED status first, once the funds are settled, it will move to the REFUNDED status. Payouts that are requested will move to the PAYOUT_REQUESTED status first, once the funds are settled, it will move to the PAYOUT_REQUESTED status.
Components updated in this release
View detailed release notes for each component
RELEASE_20230511.01
Highlights
The highlights of this release are:
-
Added
- The optional property "cardholderName" is now available on the property "cardPaymentMethodSpecificInput.networkTokenData" when creating a payment.
Changed
- If the properties "cardPaymentMethodSpecificInput.card" and "cardPaymentMethodSpecificInput.networkTokenData" are both set when creating a payment, only the data from the property "cardPaymentMethodSpecificInput.networkTokenData" is sent to our processing platform.
Components updated in this release
View detailed release notes for each component