Results for

Results for search.results.searching
Showing for Platform
Version

Added

  •  The merchant object is now fully supported for 3-D Secure V2 Payments made through the WL Online Payment Acceptance payment platform.
  •  The fiscalNumber property is now supported for refunds and 3-D Secure payments that are routed through the WL Online Payment Acceptance payment platform.
  •  The companyInformation property is now supported for refunds and 3-D Secure payments that are routed through the WL Online Payment Acceptance payment platform.
  •  Added support for the merchantReference property for payouts created using the WL Online Payment Acceptance payment platform.

Fixed

  •  Added getRefund failing when retrieving the refund 5 seconds after creation
  •  Added getCapture failing when retrieving the capture 5 seconds after creation
  •  Added getPayout failing when retrieving the payout 5 seconds after creation
Version

Added

  • The order.shoppingCart properties can now be used
  • The order.shipping properties can now be used 
  • The merchant.seller properties can now be used 
Version

Added

  • Added support for the following 3-D Secure version 2 flows:
    • Challenge flow
    • MethodURL followed by a challenge flow
    • MethodURL followed by a frictionless flow
  • Support added for personal and company fiscalnumbers in Argentina
Version

Added

  • Support for with installments on cards

Fixed

  • The getPayment and getHostedCheckout API calls used to erroneously return false for the isAuthorized property in case of Apple Pay and Google Pay
  • Cancel payment now returns the correct id
Version

Added

  • merchant.seller.phoneNumber and merchant.seller.externalReferenceId added to Create Payment and Create Hosted Checkout API endpoints
  • Added support for the following payment products:
    • Santander, paymentProductId 6116 

Changed

  • New logo's have been added for the following payment products
    • Maybank2u, paymentProductId 885
    • CIMB Clicks, paymentProductId 886
    • Hong Leong Connect, paymentProductId 890
    • Affin Bank, paymentProductId 892
    • Bangkok Bank, paymentProductId 893
    • Krung Thai Bank, paymentProductId 894
    • Krungsri e_payment, paymentProductId 896
    • Dragonpay, paymentProductId 897
    • Tesco - paysbuy Cash, paymentProductId 1522
    • 7-11 MOLPay Cash, paymentProductId 1526
  • The WL Online Payment Acceptance platform property TransactionID is now used as the id for payments, refunds, captures and payouts
  • The property order.references.merchantReference can now be used to set the WL Online Payment Acceptance platform OrderID
Version 2205.00.02

Fixed

  • Fixed failing getPayment calls
  • Fixed payment status for rejected payments
Version 2205.00.01

Changed

  • The WL Online Payment Acceptance platform property TransactionId is now used as the id for payments, refunds, captures and payouts 
  • The property order.references.merchantReference can now be used to set the WL Online Payment Acceptance platform property orderId
Version

Added

  • Added the following new payment products:
    • BBVA, paymentProductId 6114
    • Carnet, paymentProductId 6014
    • Cartão Mercado Livre, paymentProductId 6015
    • Censosud, paymentProductId 6011
    • CMR Falabella, paymentProductId 6009
    • Cordial, paymentProductId 6013
    • Cordobesa, paymentProductId 6012
    • Interbank, paymentProductId 6207
    • Mach, paymentProductId 6010
    • Presto, paymentProductId 6008
    • ScotiaBank, paymentProductId 6115
  • Added support for the following payment products:
    • Argencard, paymentProductId 140
    • Aura, paymentProductId 146
    • Discover, paymentProductId 128
    • JCB, paymentProductId 125
    • Nativa, paymentProductId 145
    • Tarjeta Shopping, paymentProductId 149

Fixed

  • The size of the Rupay and UPI logos is now 300x200

Changed

  • Company name and email addresses in the privacy policy
  • BASE_AMOUNT can be now used in as a type in shoppingCart.amountBreakdown
Version 2204.01.00

Added

  • Added support for the following payment products:
    • Banco de Occidente, paymentProductId 6112
    • Santander Cash, paymentProductId 6206
    • BCP, paymentProductId 6113

Fixed

  • Fixed bug for payments with authorizationMode 'PRE_AUTHORIZATION' 

Changed

  • Company name and email addresses in the privacy policy.

Removed

  • Removed default payment product sorting order for Russia.
Version

Added

  • Created initial link to the network token service. We will communicate separately about the ability to beta test this in the future.
  • Added support for the following payment products:
    • Visa Debit, paymentProductId 114
    • MasterCard Debit, paymentProductId 119
    • Visa Electron, paymentProductId 122
    • Lider, paymentProductId 6003
    • Creditel, paymentProductId 6004
    • OCA, paymentProductId 6005
    • Prex, paymentProductId 6006
    • Midinero, paymentProductId 6007
    • SafetyPay Cash, paymentProductId 6204
    • SafetyPay Banking, paymentProductId 880
    • PagoEfectivo, paymentProductId 6205
    • Baloto, paymentProductId 6202
    • Efecty, paymentProductId 6203
    • PSE, paymentProductId 6111
    • Nequi, paymentProductId 6110
  • The property transactionChannel can now also be used 
  • Added support for the following payment products in the Create Payment and Refund endpoints:
    • Sezzle, paymentProductId 8004
    • Clearpay, paymentProductId 8013
    • Afterpay, paymentProductId 8014

Fixed

  • CardholderName is no longer missing in the 'cards' hostedcheckout payment page.
  • The error code UNKNOWN_PAYMENT_ID is now returned when cancelPayment is performed with an unknown payment id.
  • Get Payment Products is now restricted to currencyCode INR.
  • Fixed cancel payment for payments.

Changed

  • The regular expression for the cardholderName field is extended to allow Thorn (Þ, þ) as a character to be used.
Version

Added

  • It is now possible for the getProduct, getProducts and getNetworks endpoints to return the Mir network for Apple Pay. Please note that Apple has suspended the use of Mir cards.
  • Made properties fiscalNumber, firstName, surname and emailAddress required for payments in both Uruguay and Peru.
Version

Added

  • 3-D Secure version 1 is now supported for payments that are created through the WL Online Payment Acceptance payment platform.
  • Added support for the following payment products:
    • Visa, paymentProductId 1
    • Visa Debit, paymentProductId 114
    • Visa Electron, paymentProductId 122
    • Mastercard, paymentProductId 3
    • Mastercard Debit, paymentProductId 119
    • Discover, paymentProductId 128
    • Diners Club, paymentProductId 132
  • Added support for the following payment products:
    • Magna, paymentProductId 6001
    • Recompra, paymentProductId 6002
    • OXXO Pay, paymentProductId 6201
    • WebPay, paymentProductId 6109

Fixed

  • The payment response field creationOutput.token should now return the correct value.
  • Improved payment, refund, capture and payout status mapping. The mapping is now more granular based on the payment method used.
  • Removed empty bullet point from the privacy policy.
  • Attempting to capture a payment that is not capturable results now in a 400 error.
  • Fixed potential error when listRefunds is called for failed payments.

Changed

  • Updated logo for payment product Sofort (paymentProductId 836)
Version 1.169.0

Added

  • Implemented support for the cancelPayment endpoint.
  • Implemented support for the getRefunds endpoint.
  • Payment product Klap (paymentProductId 6108) has been added.

Fixed

  • Payments and refunds that are routed through the TechProcess Payment Platform are only possible with currency code INR.
  • Payments done by consumers with a company fiscal number in Brazil (CNPJ) no longer give an 'invalid fiscalnumber' error. This applies to both create payments and hosted checkouts. Also the countryCode can no longer be changed for Pix, PayPal and Boleto Bancario payments in hosted checkouts.
  • Failed Pix payments now return a proper response.

Changed

  • When the tokenize property is set to true in a create payment request for a card payment, a token will be returned in the token property of the payment response.
  • The Get device fingerprint call will now return a different HTML snippet depending on the device fingerprint provider that is configured.
  • The region returned in createClientSession calls will now be INDIA instead of ASIA for the environment hosted in India.
Version 1.168.2

Fixed

  • .
    Fixed an issue that prevented the completion of a redirect payment through hosted checkout.
Version 1.168.1

Fixed

  • Resolved an internal bug related to device fingerprinting.
Version 1.168.0

Added

  • It is now possible to perform a create payouts call using a token instead of card data.
  • Refunding a payment is now possible when a payment has zero or one capture.
  • Added support for the following payment products:
    • PayPal, paymentProductId 840
    • Boleto Bancario, paymentProductId 1503
    • Pix, paymentProductId 6105
    • SPEI, paymentProductId 6501
  • It is now possible to poll the status of a payment with Pix, paymentProductId 6105, using the thirdPartyStatus endpoint.
  • Added validation on the property billingAddress.stateCode

Fixed

  • Payments done by consumers in Argentina, Brazil, Chile and Mexico are now properly validated on the supplied fiscal number, address, name and email address. This applies to both the create payments and the create hostedCheckouts calls.
Version 1.167.1

Added

  • Card payments with installments are now possible.

Fixed

  • A redirectURL is now returned for payments using:
    • PagoFacil, paymentProductId 1506
    • RapiPago, paymentProductId 1508
    • Cobro Express, paymentProductId 1511
    • OXXO, paymentProductId 1515

Removed

  • Removed payment product specific input for 
    • PagoFacil, paymentProductId 1506
    • RapiPago, paymentProductId 1508
    • Cobro Express, paymentProductId 1511
    • OXXO, paymentProductId 1515
Version 1.167.0

Added

  • Webhooks are now supported for merchants that are using the WL Online Payment Acceptance Payment Platform.
  • The create payout endpoint has been implemented.
  • The get payout endpoint has been implemented.
  • Added support for payment product PicPay, paymentProductId 6107.
  • Added support for payment product OXXO, paymentProductId 1515.
  • Added support for payment product ServiPag, paymentProductId 1512.
  • Added support for payment product Sencillito, paymentProductId 1513.
  • Added support for payment product Itau, paymentProductId 6102.
  • Added support for payment product Banrisul, paymentProductId 6103.
  • Added support for payment product Bradesco, paymentProductId 6104.
  • statusOutput.errors properties are returned for payments and refunds that are created through the WL Online Payment Acceptance platform and have errors.

Fixed

  • Correct payment details are now returned for payments that are created through the WL Online Payment Acceptance platform.
  • OrderIds provided by the merchant via the property merchantOrderId are no longer used.
  • It is possible to create a cash payment that is processed by the WL Online Payment Acceptance payment platform.

Changed

  • A proper error with id ACTION_NOT_ALLOWED is now returned in case refunds are not enabled for a TechProcess merchant.
  • Improved the validation of the phoneNumber property for for payment product Konbini, paymentProductId 1504.
Version 1.166.0

Added

  • The statusOutput.isCancellable and statusOutput.isRefundable flags are now set for payments created throught the TechProcess Payment platform.
  • Added Client-side field validation for WL Online Payments Acceptance platform. These validations are also used in the MyCheckout hosted payment pages.
  • Added support for payment product MercadoPago (paymentProductId 6106). 
  • Added support for payment product RapiPago (paymentProductId 1508). 
  • Added support for payment product Banco do Brasil (paymentProductId 6101). 
  • The API References now allows filtering the documentation applicable to the WL Online Payments Acceptance platform.
  • Settlement Details containing the acquirerReferenceNumber (ARN) and the retrievalReferenceNumber (RRN) can be fetched with paymentId for GlobalCollect payments. Please note that this information is only available for transactions that were processed through certain acquirers. Please note that this new endpoint should not be considered stable yet. We will make changes to this endpoint and the data it returns in a future release.
  • Added support for payment product Cabal (paymentProductId 135).
  • Added support for payment product Credimas (paymentProductId 153).
  • Added support for payment product Naranja (paymentProductId 136).
  • Added support for payment product PagoFacil (paymentProductId 1506).
  • Added support for payment product Cobro Express (paymentProductId 1511).
Version 1.165.0

Added

  • A new Connect field "productSku" is added to OrderLineDetails for the TechProcess payment engine.
  • Additional optional Connect properties are now sent to the TechProcess payment engine.
  • Implemented the refund capture call for the TechProcess payment engine.
  • The format of the fiscal number will be validated for international TechProcess merchants. The format has to be 5 letters, 4 digits and 1 letter.
  • The statuscode field mapping configuration is updated for the TechProcess payment engine.
  • Implemented the Create refund call for WL Online Payments Acceptance Platform (also called Worldline One Commerce Hub).
  • Implemented the GET refund call for WL Online Payments Acceptance Platform (also called Worldline One Commerce Hub).
  • Mastercard payments can now be processed through the WL Online Payments Acceptance Platform (also called Worldline One Commerce Hub).
  • American Express payments can now be processed through the WL Online Payments Acceptance Platform (also called Worldline One Commerce Hub).
  • Maestro payments can now be processed through the WL Online Payments Acceptance Platform (also called Worldline One Commerce Hub).
  • Diners Club payments can now be processed through the WL Online Payments Acceptance Platform (also called Worldline One Commerce Hub).
  • ELO payments can now be processed through the WL Online Payments Acceptance Platform (also called Worldline One Commerce Hub).
  • Hipercard payments can now be processed through the WL Online Payments Acceptance Platform (also called Worldline One Commerce Hub).
  • Implemented the getCapture call for the WL Online Payments Acceptance Platform (also called Worldline One Commerce Hub).
  • Implemented the getCaptures call for the WL Online Payments Acceptance Platform (also called Worldline One Commerce Hub).

Fixed

  • Fixed the getRefunds implementation for the TechProcess payment engine.
  • The correct payment status should now be returned for UPI payments that are created through the TechProcess payment engine.
  •  The correct capture details are now returned for captures that are created through the Worldline Payment Acceptance Platform (also called Worldline One Commerce Hub).
    An error message with more information is now returned when an API is called,  that is not supported by the Worldline Online Payments Acceptance Platform (also called Worldline One Commerce Hub).

Changed

  • The status codes of payment responses now reflect the actual status of the returned payments for the Worldline Online Payments Acceptance Platform (also called Worldline One Commerce Hub.
Version 1.164.0

Added

  • Added support for Cancel Payment for the TechProcess payment engine.
  • Added support for List Captures for the TechProcess payment engine.
  • Implemented the capturePayment call for the Worldline Online Payment Acceptance Platform (also called Worldline One Commerce Hub).
  • Implemented the get token call for the Worldline Online Payment Acceptance Platform (also called Worldline One Commerce Hub). 

Fixed

  • GetHostedCheckout response is now returning proper showData and renderingData properties for the available merchantActionTypes.
  • fixed an issue that was causing UNSUPPORTED_TECHPROCESS_PAYMENT_PLATFORM_OPERATION to occur for Rupay payments.
  • Throw an appropriate exception if updateToken is called for the Worldline Online Payment Acceptance Platform (also called Worldline One Commerce Hub) using an invalid tokenId.

Changed

  • The UPI integration types 'urlIntent' and 'QRCode' are combined into the integration type 'mobile'
Version 1.163.0

Added

  • Implemented the getPrivacyPolicy call for the Worldline Online Payment Acceptance Platform (also called Worldline One Commerce Hub).
  • Proper error codes for the Worldline Online Payment Acceptance Platform (also called Worldline One Commerce Hub) related errors.
  • Implemented the create token call for the Worldline Online Payment Acceptance Platform (also called Worldline One Commerce Hub).
  • Implemented the update token call for the Worldline Online Payment Acceptance Platform (also called Worldline One Commerce Hub).
  • Added South Korean Local Cards payment products BC Card(paymentProductId 180),Hana Card(paymentProductId 181), Hyundai Card(paymentProductId 182), KB Card(paymentProductId 183), Lotte Card(paymentProductId 184), NH Card(paymentProductId 185), Samsung Card(paymentProductId 186) & Shinhan Card (paymentProductId 187). Property partialPin is added under "card" object.
  • Implemented Hosted checkout functionality for Worldline.
  • Translations specific to Pay with your bank, South Korean Local Cards products have been added to the language packs. Improved validation message on zip code field for Boleto in the language packs.

Fixed

  • The property payoutDetails.customer is no longer required for card-payout requests.
  • The updateToken API call now accepts obfuscated card numbers.

Changed

  • Order ids towards the Worldline Online Payment Acceptance Platform (also called Worldline One Commerce Hub) are no longer generated beforehand when creating hosted checkout pages
Version 1.162.0

Added

  •  The GetPayment call is now available in case you use the Worldline Online Payment Acceptance platform (also called Worldline One Commerce Hub).
  •  The convert amount endpoint is implemented for the Worldline Online Payment Acceptance Platform (also called Worldline One Commerce Hub).
  •  The testConnection call is implemented for the Worldline Online Payment Acceptance Platform (also called Worldline One Commerce Hub).
  •  Added support for Microsoft Fraud Prevention.
  • HostedCheckouts can be removed with a DELETE call.

    Changed

    •  The logo for WL Account-Based Payments has been changed (paymentProductId 865).

    Fixed

    •  In case you send an updateTokenRequest, it is possible to send the obfuscated cardNumber.
    Version 1.161.0

    Added

    • The Create Payment and get Payment Products calls can now also be used against the Worldline Online Payment Acceptance platform (also called Worldline One Commerce Hub). We will communicate separately about the ability to beta test this in the future.
    • Added a new payment product AlipayHK (paymentProductId 873). We will communicate separately about the ability to beta test this in the future.

    Changed

    • We have loosened up the paymentProductId vs IIN (Issuer Identification Number, aka BIN or Bank Identification Number) data validation. So any call where the IIN doesn't match with the paymentProductId, the first matched IIN data will be appended to the transaction. We will not reject the request.
    Version 1.160.0

    Added

    • You can now provide proof regarding the authentication you have already performed to support delegated authentication through the new property data in the order.customer.account.authentication object
    • Added a new property transactionRiskLevel to the cardPaymentMethodSpecificInput.threeDSecure object in the create hostedCheckout and create Payment endpoints to allow you to submit your own risk-score for us to use in case you use the automatic option for the exemptionRequest property.

    Fixed

    • Remove non-required field validation for Create Token request.
    Version 1.159.0

    Added

    • Implemented the shared IIN service for the WOPA payment engine.
    • We have added support for two new authentication methods to support delegated authentication scenarios. They are added to the order.customer.account.authentication.method property.
    Version 1.158.0

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

    RELEASE_20210707.00

    Version 1.155.0

    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