Results for

icon-search-large No search results yet
Enter your search query above
Showing for Platform
Version 1.134.0
Sandbox
Published on 17 Sep 2020
Pre-prod
Published on 17 Sep 2020
Prod
Published on 24 Sep 2020

Added

  • New property "acquirerCountry" added to getPaymentProduct and getPaymentProducts responses. Indicates the country of the acquirer which will process the transaction.

Fixed

  • In case you provide invalid value in unscheduledCardOnFileRequestor you will now get a correct error message.
  • Resolved an error which appeared in case you update a token with an obfuscated card number

Changed

  • 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.
Version 1.133.1

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.
Version 1.133.0

Added

  • The company name (merchantName) and the company URL (merchantOrigin) used for Google Pay info is now taken from values provided in the configuration center in case these properties are not provided in the create hosted checkout request. You can still overrule the values which you have provided in the configuration center, by adding these to the create hosted checkout request for Google Pay. 

Fixed

  • Resolved UNKNOWN_SERVER_ERROR for refunds of e-Przelewy payments (paymentProductId 402).
  • Don't require Google Pay specific properties in the paymentProduct320SpecificInput object, when the Google Pay payment product (paymentProductId 320) is excluded by the paymentProductFilters.

Changed

  • In case the Google Pay product (paymentProductId 320) is used and a PAN_ONLY payload is returned, the transaction will be further processed as a regular card transaction using the appropriate payment product. Example: You submit a Google Pay transaction using paymentProductId 320, but we return and process the transaction using for instance paymentProductId 1 for Visa cards.
  • Payment product PaySafeCard (paymentProductId 830) will no longer use statusCode 20, 25 or 30 and will return statusCode 50 immediately upon a successful transaction creation for statusREDIRECTED. This change will also remove an additional redirect from the process, which will improve the user experience.
Version 1.132.1

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.
Version 1.132.0

Changed

  • The payment product ordering for the getPaymentProducts call is changed for Sweden, as new Swedish regulations require a non-credit product to be shown as the first payment product to a consumer.
Version 1.131.1

Fixed

  • allowsInstallments flag for AfterPay Installments (PPID 9000) now has the correct value "true".

Changed

  • numberOfInstallments must be greater than zero, if present on createPayment or createdHostedCheckout.
Version 1.131.0

Added

  • New property's numberOfInstallments, amountOfMoneyPerInstallment, frequencyOfInstallments and interestRate under order.additionalInput.installments to send the installment details while performing a Create Payment or Create Hosted Checkout for card payments for which acquirers do support installments.
  • New API endpoint to retrieve the raw output of the deviceFingerprint check for a payment (/v1/{merchantId}/payments/{paymentId}/devicefingerprint)
  • Added allowInstallments flag to getpaymentproductgroup and getpaymentproductgroups response.

Fixed

  • In case you provide a negative amount while trying to obtain the IIN details, you will now get a correct error message.
  • The bankcode property of payment product ACH (730) now correctly shows the min and max lengths inside the dataRestrictions object.
  • Decryption of the Google Pay payload, has been fixed.

Deprecated

  • The order.AdditionalInput.numberOfInstallments property is deprecated. Please use order.additionalInput.installments.numberOfInstallments.

Changed

  • A new logo for payment product e-Przelewy has been added
Version 1.130.0

Added

  • Added an endpoint for creating a payment product session to support Apple Pay on the Web integrations using your own website.
Version 1.129.0

Fixed

  • A correct error is returned in case you try to tokenize a payment that was done using a payment product which does not allow to tokenize the payment details.
  • In case you want to make a payment with Pago Fácil (paymentProductID 1506) it is no longer mandatory to send in order.additionalInput.typeInformation
  • Fixed incorrect property key mapping for error 410120 and 2800000 (instead of "order.price.amount" we now correctly return "order.amountOfMoney.amount")
  • The Do Risk Assessment API for cards now returns a proper error message in case the validation fails for order.additionalInput.airlineData.agentNumericCode
Version 1.127.2

Changed

  • Payment products iDEAL, SOFORT & PayPal (paymentProductIds 809, 836 & 840 respectively) will no longer use statusCode 20, 25 or 30 and will return statusCode 50 immediately upon a successful transaction creation for status REDIRECTED. This change will also remove an additional redirect from the process, which will improve the user experience 
Version 1.127.2

Fixed

  • Corrected error mapping for error code 480023 (Invalid parameter for UCOF)
Version 1.127.0

Added

  • New property allowsInstallments added to getPaymentProduct and getPaymentProducts responses. Indicates whether installments are possible for a given payment product. Known issue: allowsInstallments currently still returns "false". This will be fixed in an upcoming release.
  • Get privacy policy Server API call now supported in combination with Ingenico's Global Collect Payment Platform.
Version 1.126.0

Changed

  • Changed the way we handle redirects for Netbanking (paymentProductId 882). We are now skipping statusCodes 20, 25, and 30 to make the process more smooth.
  • Added reversalReason in the Find Payments and Retrieve Payment API response for transactions that have a CHARGEBACK_NOTIFICATION or CHARGEBACKED status.
Version 1.125.0

Added

  • There are five new error codes introduced. All these error codes are related to the Boleto service provider. Here is a quick summary of new codes with their corresponding HTTP status codes and a brief description.
    • 4380070 - 400 - When an invalid parameter was sent or when the service provider fails to process the request for any unspecified reasons (mostly due to invalid input that cannot be parsed)
    • 4380080 - 400 - When a required parameter is missing
    • 4380090 - 402 - When the server fails to process the given request for any unspecified reasons (mostly due to invalid input that cannot be parsed)
    • 4380095 - 500 - When the Boleto service provides fails internally while handling a request
    • 4380100 - 400 - When a parameter is not supported or when the server fails to process the given request for any unspecified reasons (mostly due to invalid input that cannot be parsed)
  • Added real-time banking payment products:
    1. FPX (paymentProductId 884) which can be used in Malaysia
    2. Maybank2u (paymentProductId 885) which can be used in Malaysia
    3. CIMB Clicks (paymentProductId 886) which can be used in Malaysia
    4. Bank Islam (paymentProductId 887) which can be used in Malaysia
    5. RHB Now (paymentProductId 888) which can be used in Malaysia
    6. AmOnline (paymentProductId 889) which can be used in Malaysia
    7. Hong Leong Connect (paymentProductId 890) which can be used in Malaysia
    8. PEx+ by HLBB (paymentProductId 891) which can be used in Malaysia
    9. Affin Bank (paymentProductId 892) which can be used in Malaysia
    10. Bangkok Bank (paymentProductId 893) which can be used in Thailand
    11. Krung Thai Bank (paymentProductId 894) which can be used in Thailand
    12. Siam Commercial Bank (paymentProductId 895) which can be used in Thailand
    13. Krungsri e_payment (paymentProductId 896) which can be used in Thailand
    14. Dragonpay RealTime (paymentProductId 897) which can be used in the Philippines

Fixed

  • Validate whether client session belongs to the current merchantId and not only to the current account.
Version 1.124.0

Added

  • Three new fields have been added in preparation for external cardholder validation of Carte Bancaire. These fields are exposed in the request and response of createPayment. The fields are: acsTransactionId, appliedExemption, and schemeRiskScore. The fields are not used at the moment.
  • New optional authenticationAmount object added to the Create payments and Create hostedCheckouts requests, allowing you to specify a higher authentication amount for 3-D Secure transactions.

Fixed

  • Fixed a error in the script that is returned in the html property when a collectorCallback is provided as input for the Retrieve Device Fingerprint request

Changed

  • The getIINdetails call has been updated. The call now returns more accurate results and can return (more) cobrands when more than 6, up to 8 digits are provided.
Version 1.123.0

Added

  • Three new fields have been added in preparation for external cardholder validation of Carte Bancaire. These fields are exposed in the request and response of createPayment. The fields are: acsTransactionId, appliedExemption, and schemeRiskScore. The fields are not used at the moment.
  • The payment product GCash (paymentProductID 871) has been added.

Fixed

  • The redirectPaymentMethodSpecificInput.requiresApproval property now also works correctly for PayPal payment requests when the request doesn't contain a paymentProduct840SpecificInput object

Deprecated

  • The externalCardholderAuthenticationData.threeDServerTransactionId should no longer be used as it has been deprecated.
Version 1.122.0

Added

  • Added cash payment products for several countries in Asia, being:
    • e-Pay (paymentProductId 1521) which can be used in Malaysia
    • Tesco - paysbuy Cash (paymentProductId 1522) which can be used in Thailand
    • ATM Transfers Indonesia (paymentProductId 1523) which can be used in Indonesia
    • DragonPay (paymentProductId 1524) which can be used in the Philippines
    • 7-11 MOLPay Cash (paymentProductId 1526) which can be used in Malaysia
  • For the payment product Trustly, specific output properties providing details about the consumer's bank account and the billing address are now returned if available.

Changed

  • For the payment product Boleto Bancário (paymentProductId 1503) now returns that it is optimized mobile.

Removed

  • The payment product Bank Transfer Argentina (PPID 53) can no longer be used as it has been disabled.

Fixed

  • The status of a refund will now be correctly returned as "REFUND_REQUESTED" when the statusCode is 975 for all payment products except PayPal,  Netbanking, AliPay, WebMoney, Qiwi, Yandex.Money
  • Merchant Action - Redirect is now only present in Create Payment responses when both redirectURL and RETURNMAC fields are present.
  • Removed an incorrectly placed } from the html property that is returned with the retrieve deviceFingerPrint API.
Version 1.121.2

Fixed

  • Fixed a bug in the script that is returned in the html property of the Retrieve DeviceFingerPrint API call
Version 1.121.1

Fixed

  • Merchant Action - Redirect is now only present in Create Payment response when both redirectURL and RETURNMAC fields are present.
Version 1.121.0

Added

  • Create token now accepts encryptedCustomerInput for card payments.
  • If you are performing PayPal transactions, you can now supply "requiresApproval" property to direct the transaction flow according to the approval requirement.
  • Updated and re-enabled payment product (882) Citrus to Netbanking.
  • Added a new output property called refundProductId as identifier of the refund product that was used to process the refund.

Changed

  • CardPaymentMethodSpecificInput.customerReference is now limited to 17 characters long.
  • For createPayment and createHostedCheckout requests with China UnionPay (payment product ID 869) the presence of a ShoppingCart object with one or more items is mandatory and for every item the below mentioned fields are mandatory:
    • amountOfMoney.amount
    • amountOfMoney.currencyCode
    • invoiceData.description
    • orderLineDetails.lineAmountTotal
    • orderLineDetails.productType
    • orderLineDetails.productName
    • orderLineDetails.quantity
    • orderLineDetails.productPrice
  • For createPayment requests with China UnionPay (payment product ID 869) the presence of the below mentioned field are required:
    • redirectPaymentMethodSpecificInput. paymentProduct869SpecificInput.residentIdName
    • redirectPaymentMethodSpecificInput. paymentProduct869SpecificInput.residentIdNumber
    • redirectPaymentMethodSpecificInput. paymentProduct869SpecificInput.residentMobilePhoneNumber
    • redirectPaymentMethodSpecificInput. paymentProduct869SpecificInput.issuerId
  • New validation rules have been enforced on residentIdNumber, residentIdName and residentIdMobileNumber fields for the payment product China UnionPay. The checksum digit is validated when residentID numbers that contain 18 digits are given. No checksum validation is performed on numbers with 15 digits. The residentIdName field should contain only Simplified Chinese characters. If the international code "+86" is present in residentMobileNumber field, then it is stripped before sending the payment requests to the provider.

Fixed

  • A PayPal-specific error now results in a rejected payment with the '402 - EXTERNAL_ACQUIRER_ERROR' error. It previously resulted in a '500 - INTERNAL SERVER ERROR'.
  • Bugfix for a corner case of create client session.

RELEASE_20200107.02

Version 1.120.2

Fixed

  • Fixed issue in redirect payment product