Results for

icon-search-large No search results yet
Enter your search query above
Showing for Platform
Version 1.158.0
Sandbox
Published on 01 Sep 2021
Pre-prod
Published on 01 Sep 2021
Prod
Published on 14 Sep 2021

Added

  • The Wordline Online Payment Acceptance (also referred to as Worldline Once Commerce Hub) payment engine identifier supported by the Worldline support organisation.
  • Enables Recurring functionality for all AlipayOSP Payment Products (871, 872, 874, 875, 876).
Version 1.157.0

Added

  • Additional errors from the Ogone payment platform are now returned as clearer Connect errors.

Fixed

  • The convert amount call now returns the correct error code (400) when an currency code is provided of which the corresponding currency has no rates.
  • In case of validation error for a deprecated property in Create Payout, the original property will be shown in response.
  • Tokenize payment will no longer update the card number of already existing tokens.
Version 1.156.1

Fixed

  • Tokenize payment will no longer update the card number of already existing tokens.

RELEASE_20210721.00

Version 1.156.0

Added

  • In case you use the MyCheckout hosted payment pages, your consumer will need to provide the name on their card in case they are using one of the following cards and you have 3-D Secure enabled on your account: Visa (payment product ID 1), American Express (payment product ID 2), Mastercard (payment product ID 3), Visa Debit (payment product ID 114), Maestro (payment product ID 117, Mastercard Debit (payment product ID 119), Visa Electron (payment product ID 122), Discover (payment product ID 128), Carte Bancaire (payment product ID 130) and Diners Club (payment product ID 132). The cardholderName property will be returned as being mandatory if you perform a GET paymentProduct(s) call.
  •  In case Google Pay is the only payment product you offer on the MyCheckout hosted payment pages to your consumer and you have not provided the merchantOrigin or merchantName in the Configuration Center and/or in the createHostedCheckout request, we will return the error NO_PAYMENT_PRODUCTS_AVAILABLE, as both aforementioned properties are mandatory to be provided for a Google Pay transaction.

Fixed

  •  In case you offer Google Pay on the MyCheckout hosted payment pages, we will now ensure that the merchantOrigin and merchantName you provided in the Configuration Center will be used in case you send the recommended paymentProduct320SpecificInput.threeDSecure object in for the createHostedCheckout request.
  •  In case you offer Google Pay on the MyCheckout hosted payment pages, we will no longer throw an error in the use case that we have just enabled the payment product for you on your merchantID and you have not yet provided the merchantName and merchantOrigin in the Configuration Center and/or the createHostedCheckout request.

Removed

  •  Removed input field transactionNote for payment product 4101 (UPI), instead order.reference.descriptor is now used.

Changed

  •  Changed input field names for payment product 4101 (UPI) from vpa to virtualPaymentAddress and from merchantName to displayName.