Results for

icon-search-large No search results yet
Enter your search query above
Showing for Platform
Version 1.155.0
Sandbox
Published on 19 Jul 2021
Pre-prod
Published on 19 Jul 2021
Prod
Published on 26 Jul 2021

Added

  • Added support for card payouts for GlobalCollect merchants. We will communicate separately about the ability to beta test this in the future.
  • The payment product Alipay recurring (paymentProductId 864) has been added. We will communicate separately about the ability to beta test this in the future.
  • Automatic tokenization of Unscheduled Card On File payments where unscheduledCardOnFileSequenceIndicator is 'first' and there is no token in the request.
  • Updating of tokens if the /tokenize payment endpoint is called for a payment with a card that already had a token. Note that only the expiryDate property will be updated in this manner.
  • The merchantAction.showData  array will now also return a COUNTRY key in the response of Bank Transfer Product (paymentProductId 11).

Fixed

  • The convert amount call now returns the correct error code (400) when an invalid currencyCode is provided.

Deprecated

  • Deprecated property for hosted checkout mobilePaymentMethodSpecificInput.paymentProduct320SpecificInput.threeDSecure.redirectionData
    Version 1.154.0

    Added

    • The ability to do get payment calls for payments processed on the TechProcess platform that are still in a redirected state. Note that the get payment will still fail after the redirection url expires after 10 minutes.
    • The payment product kakaoPay (paymentProductId 876) has been added.

    Fixed

    • Changes to the default locale in the Configuration Center are now immediately used by the API Gateway.
    • Improved the mapping from IIN + charge type to paymentProductId.
    Version 1.153.0

    Added

    • The method getThirdPartyStatus now supports UPI payments. We will communicate separately about the ability to beta test this in the future.
    • The fields merchantName is added to RedirectPaymentProduct4101SpecificInput. The values of these fields are added to the intent url according to the TechProcess documentation. We will communicate separately about the ability to beta test this in the future.
    • The payment product DANA (paymentProductId 875) has been added. We will communicate separately about the ability to beta test this in the future.
    • The payment product Touch 'N Go eWallet (paymentProductId 874) has been added. We will communicate separately about the ability to beta test this in the future.

    Fixed

    • The createPayment API now returns a correct payment ID for payments processed through the TechProcess payment engine. We will communicate separately about the ability to beta test this in the future.

    Changed

    • The CreateHostedCheckout API now supports TechProcess merchants. We will communicate separately about the ability to beta test this in the future.
    • The GetHostedCheckout API now supports hosted checkouts created with a TechProcess merchant. We will communicate separately about the ability to beta test this in the future.
    • The payment IDs for payments processed through the TechProcess payment engine now follow a new format. We will communicate separately about the ability to beta test this in the future.
    • cardPaymentMethodSpecificInput.threeDSecure.sdkData.deviceRenderOptions.sdkUiType was deprecated. Please use cardPaymentMethodSpecificInput.threeDSecure.sdkData.deviceRenderOptions.sdkUiTypes instead.
    Version 1.152.0

    Added

    • Support for the Indian UPI payment product (paymentProductId 4101) has been added. We will communicate separately about the ability to beta test this in the future.
    • Support for the URL Intent flow with QR code for UPI (paymentProductId 4101) is added to the Create Payment call. We will communicate separately about the ability to beta test this in the future.
    • Support for the VPA flow for UPI (paymentproductId 4101) is added to the Create Payment call. We will communicate separately about the ability to beta test this in the future.
    • Support for the URL Intent flow for UPI (paymentProductId 4101) is added to the Create Payment. We will communicate separately about the ability to beta test this in the future.
    • Support for getPayouts call for cards payout.
    • Added support for the getIINDetails call for TechProcess merchants.
    • The payment product TrueMoney Wallet (paymentProductID 872) has been added. We will communicate separately about the ability to beta test this in the future.

    Fixed

    • We improved the validation of credit card numbers in the create payment request.

    Changed

    • The order.customer.fiscalNumber field is now mandatory for international merchants processing through the TechProcess platform
    Version 1.151.0

    Added

    • Added support for Get privacy policy for the TechProcess payment engine.
    • The convert amount service can now be used for merchants from all payment engines.

    Fixed

    • Fixed issue that prevented cardholder name, expiry date or card number to be updated on an existing token on certain cases

    Changed

    • Property cardPaymentMethodSpecificInput.threeDSecure.sdkData.deviceInfo is deprecated.
    Version 1.150.0

    Fixed

    • Error message for invalid customer country code will display the correct property name.
    Version 1.149.0

    Fixed

    • Subsequent customer-initiated UCOF transactions will now be properly flagged.
    • Fixed the response of create payment product session endpoint for Apple Pay so that the configured businessName is used as displayName.
    Version 1.148.0

    Added

    •   Instant Bank Transfer (payment product ID 865) specific output fields like BBAN bank account information are now returned if available. A bankAccountBban object and bic property have been added to the redirectPaymentMethodSpecificOutput object.

    Fixed

    • Fixed a bug which caused all properties related to 3-D Secure and Unscheduled-Card-On-File (UCOF)in the cardPaymentMethodSpecificInput property of the createPayment request to be ignored if a payment attempt was made with an account-on-file.
    • Subsequent Unscheduled-Card-On-File (UCOF) transactions will now be properly flagged as recurring transactions.
    • If you send an in invalid locale in GET paymentProduct, GET paymentProducts, GET paymentProductGroup and GET paymentProductGroups, we will use the locale that you have set as default in the configuration center.
    Version 1.147.0

    Added

    • Added mapping of new statusCode 675 for redirect payment products to AUTHORIZATION_REQUESTED in preparation of Open Banking (paymentProductId 865). We will communicate separately about the ability to beta test this in the future.

    Fixed

    • It is no longer needed to send in the returnUrl for an Apple Pay transaction in case encryptedCustomerInput is submitted in your request

    Changed

    • If you send in numberOfInstallments greater than 1, we reject the request in case the service provider configured for your account does not support installments.
    • Changed the stateCode field validators to use a case-insensitive regular expression with all Brazilian states. This change applies only for Boleto Bancario (paymentProductId 1503).
    • Updated our eNets (paymentProductId 810) integration (more detailed error messages)
    Version 1.146.0

    Added

    • Added support for Capture Payment for the TechProcess payment engine.
    • Added support for Get Capture for the TechProcess payment engine.
    • The fiscalNumber (pan) property is now sent to TechProcess.
    • Support for a new payment product Open Banking (paymentProductId 865) for Create Payment and Refund requests.

    Fixed

    • Fixed an error that occurred if a payment request was made for NetBanking (payment product 882), without providing the 'redirectPaymentMethodSpecificInput.paymentProduct882SpecificInput' property.

    Changed

    • We now return a more user friendly error message in case of invalid IBAN.
    • China UnionPay field residentIdNumber in object RedirectPaymentProduct869SpecificInput is no longer case sensitive
    Version 1.145.0

    Added

    • Added support for the requiresApproval property for the directDebitPaymentMethodSpecificInput and the sepaDirectDebitPaymentMethodSpecificInput. This property allows you control if an additional approval step is needed after the submission of a transaction with a valid mandate.
    • Added new server side card number validation for Create Payment using Luhn Algorithm.
    • Added support for Get payment products, Get payment product, Get payment product groups and Get payment product group for the TechProcess payment engine.
    • Added support for Get payment product directory for the TechProcess payment engine.
    • Added support for creating card payments for the TechProcess payment engine.
    • Added support for Get payment for the TechProcess payment engine.
    • Added support for handling TechProcess payment engine errors.
    • Added support for Create Refund for the TechProcess payment engine.
    • Added support for Get Refund for the TechProcess payment engine.
    • Added support for TestConnection for the TechProcess payment engine.
    • Added support for Create Payment with authorizationMode FINAL_AUTHORIZATION for the TechProcess payment engine.
    • Added support for creating NetBanking payments for the TechProcess payment engine.
    • Added support for Get Refunds of a payment for the TechProcess payment engine.

    Fixed

    • Get paymentProduct and Get paymentProducts calls now correctly report the allowsInstallments flag.

    Changed

    • The logo for the Bancontact payment product (3012) has been updated.
    Version 1.144.0

    Added

    •  We mapped errorCode 883000 to return HTTP status code 502. This error will be triggered in case an invalid merchant id for the external provider has been configured  by us in your account for Netbanking (paymentProductId 882).

    Fixed

    • The API Reference will now show "yes" instead of "no" in the table indicating whether a hosted checkout is possible for the payment products Google Pay and Apple Pay.
    • We removed the validation we implemented for the locale property in order.customer and in the hostedCheckoutSpecificInput
    Version 1.143.2

    Fixed

    • We removed the validation we implemented for the locale property in order.customer and in the hostedCheckoutSpecificInput
    Version 1.143.1

    Fixed

    • Fixed an issue where the GetPaymentProducts call would sometimes return payment products that wouldn't work given the provided currencyCode 
    Version 1.143.0

    Fixed

    • Added validation for create token request on field card.data.firstTransactionDate. On case of invalid date format, the error message will now be INVALID_VALUE on card.data.firstTransactionDate. Length validation still occurs.
    • Token id is now returned on update token error message when ZIP code is too long.
    • Removed the Luhn validation for create payment requests for card payment product.

    Changed

    • Create Hosted Checkout has to ignore blank or empty property hostedCheckoutSpecificInput.paymentProductFilters. That means, if this property is part of a Create Hosted Checkout request, the property will be ignored if blank or empty.
    • New logo for Google Pay
    • Payments with Alipay will be redirected via a different domain, this affects the redirect URL returned in the Create Payment response. In addition, the initial status code of these payments will be 50 (REDIRECTED) instead of 20 (REDIRECTED).
    Version 1.142.1

    Fixed

    • Removed the Luhn validation for create payment requests for card payment product.
    Version 1.142.0

    Added

    • Added new creditcardnumber validation for createPayment and RPP entered card numbers. When enabled, the card number validations will be using a new source of data for validations.
    • Improving the IIN validation with a new data source for IIN/BIN data, increasing acceptance of transactions.

    Fixed

    • Fixed the response of errorCode 800220 to correctly indicate the correct property: bankRefundMethodSpecificInput.bankAccountBban.swiftCode
    • Added check to ignore multiple payment specific input objects on create payment calls.
    • Adding new creditcardnumber validation for createPayment for length and luhn check. When enabled, the data is validated earlier in the process and the card IIN/BIN validations will be using a new source of data.
    • We removed the validation we implemented for the locale property in order.customer and in the hostedCheckoutSpecificInput

    Changed

    • cardPaymentMethodSpecificInput.card.cardNumber with minimum input length value 12 digits
    • Payments with ePrzelewy will be redirected via a different domain, this affects the redirect URL returned in the Create Payment response. In addition, the initial status code of these payments will be 50 (REDIRECTED) instead of 20 (REDIRECTED).
    Version 1.141.2

    Fixed

    • We removed the validation we implemented for the locale property in order.customer and in the hostedCheckoutSpecificInput
    Version 1.141.0

    Changed

    • New logo for iDeal
    • New logo for Trustly
    • The value for the field "paymentProduct320SpecificData.gateway" is now changed to return the value "globalcollect" if you send a GET payment products or GET payment product request. It is required for all Google Pay transactions in case we decrypt the sensitive payment data for you and you use your own hosted payment pages. 
    Version 1.140.1

    Fixed

    • We removed the validation we implemented for the locale property in order.customer and in the hostedCheckoutSpecificInput
    Version 1.140.0

    Added

    • Added support for lodging specific properties to be included in a createPayment and a createHostedCheckout as part of order.additionalData
    • Added the ability to return details regarding the requested PSD2 SCA exemption. Depending on applicability we will return the exemptionRequest submitted by you, the exemptionRaised towards the acquirer and a exemptionRejectionReason in case the exemption was not granted.

    Fixed

    • Locale with hyphen in order.customer and order.customer.device is no longer causing internal server error
    • Instead of returning an error that a returnUrl is required when a SCA step-ups requested by the issuer we now return the correct rejection reason stating that SCA is required. Please note that when you do include a returnUrl in your request we will automatically perform the SCA when required by the issuer.

    Changed

    • Returning a proper error response in case of incorrect amountOfMoney
    Version 1.139.0

    Added

    • In certain cases a communication problem with a 3rd party payment service provider could occur would result in a 500 - INTERNAL SERVER ERROR. This has been changed to 402- EXTERNAL_ACQUIRER_ERROR
    • A 500 - INTERNAL SERVER ERROR would be returned if a payment's status could temporarily not be determined in certain cases. This has been changed to a new error 409 - PAYMENT_STATUS_UNCERTAIN
    • We are no longer returning renderingData in case the merchantAction.actionType equals SHOW_TRANSACTION_RESULTS
    Version 1.138.0

    Fixed

    • Payment validation for Boleto object billingAddress field city and zip will show now only single error instead of two errors

    Removed

    • Removed payment product FPX with paymentproductId 884
    Version 1.137.0

    Changed

    • Payment product Skrill (paymentProductIds 843) 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.136.0

    Changed

    • getPaymentProducts call sorts payment products differently for Sweden. Debit products come first.
    Version 1.135.0

    Added

    • Added the properties authorizationMode, customerReference, skipFraudService, requiresApproval to the mobilePaymentMethodSpecificInput object for the createHostedCheckout.
    • Added the properties customerReference to the mobilePaymentMethodSpecificInput object for a createPayment.
    • Added the threeDSecure object to the paymentProduct320SpecificInput object to support 3D Secure authentication on PAN_ONLY Google Pay transactions.

    Fixed

    • Get IIN Details call now properly validates currency

    Changed

    • The regular expresion for the cardholderName field is extended to allow non-ASCII characters to now be submitted. The EMVco 3-D Secure version 2.x specification only allow ASCII characters, but this doesn't match with reality. We will automatically convert any non-ASCII characters to their closest matching ASCII character.
    Version 1.134.0

    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.

    RELEASE_20200630.00

    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