REST API
Showing for Platform
RELEASE_20230928.00
Version
|
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.
- Mapped error code 33000833 to HTTP status 400 INVALID_VALUE.
- Mapped error code 30841001.
- 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.
Changed
- The property networkTokenData.cryptogram is now optional if you create a payment with an external network token.
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 a transaction made with the payment product Pix 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.
RELEASE_20230810.00
Version
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.
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.
- The limit of the order.references.merchantReference property has been increased to 50 characters.