Skip to main content

12 posts tagged with "checkout.com"

View All Tags

Gateway — v.24.9

API

Added

  • Transaction API: Added cardUpdateStatus and cardUpdatedAt to returnData for cardData responses when account updater is enabled.

Features

Added

  • Account Updater: The Payment Instruments section of Customer Profiles now shows the Status and Last Update columns for Credit Cards.
  • Meta connector: Added support for tokenizing Google Pay and Apple Pay payment information and routing these transactions to PSPs.

Fixed

  • Post Processing Jobs: Fixed an issue with the option to pause the execution of post-processing jobs. Previously, setting the job to wait until a specific time that included seconds meant that the next strategy job was never executed.
  • Provider Settlements and Reconciliation: Settlement conflicts are now resolved as a result of the transaction being set to successful.

Adapters

Changed

  • Adyen (ADY-EP3-CC): Added support for post-processing Adyen settlements and reconciliation via GlobalPayments.

  • Braintree (BRA-EP1-BLI): Added support for the Blik payment method. This is a popular bank transfer payment method in Poland.

  • Redsys (RED-EP1): Added a new setting for the Redsys Bizum payment method that allows users to include an error URL in the transaction data. If the URL is specified, the system will send this URL if the payment fails, improving error handling and the user experience.

  • Worldline (ING-EP5): PostFinancePay is now available as a payment method. The following countries are supported:

    • Switzerland
    • Belgium
    • France
    • Germany
    • Netherlands
    • United Kingdom
    • Additional EU countries

    Supported currencies include CHF and EUR.

Added

  • AllSecure (ALLSE): AllSecure is a global payment service provider that provides tailor-made online payment solutions. The adapter supports credit card payments.
  • PayPal Complete Platform (PPCP-EP1-PPE): Added a new PayPal Commerce Platform adapter. The adapter supports:
    • All transactions types using hosted payment pages
    • All transaction types by integrating PayPal directly on the merchant's website
    • PayLater capability
    • PayPal vaulting.

Fixed

  • Adyen (ADY): Fixed an issue where lines marked as a merchant payout were not correctly mapped to the paymentReference field.
  • checkout.com (CHE-EP1-IDE, CHE-EP2-IDE): Added BIC support for transactions not involving an IBAN customer.
  • Neteller (NET-EP1): Fixed an issue where the transaction status failed to update to ERROR after receiving a postback indicating an error.
  • Worldline (ING-EP2-MAS): Fixed an issue with unformatted chargeback amounts. Due to the lack of formatting, the result was increased by a factor of 100.

Please note that some of the features mentioned in the release notes may initially be available only within our sandbox environment for testing purposes. These features will be made available in the production environment upon successful testing and approval.

Gateway — v.24.7

API

Added

  • Provisioning API: Two new fields have been added to the merchant response model: ntsEnrollmentStatus and networkTokenizationEnabled.

Features

Changed

  • Job Configuration: Information on inherited job type templates is now displayed, informing users as to why the template cannot be edited.

Added

  • Network Tokenization:
    • Information on the status of enrollment for network tokenization is now available in the base data for a merchant. A new line, "Network Tokenization" has been added. If the merchant has a TRID assigned, the status is displayed as "enabled" when viewing the data as an admin with the permission "tokenization.networkTokenization.enrollment.show".
    • Merchants can now be filtered by their NTS status in the overview.

Fixed

  • Pay-by-Link: Fixed an issue with the virtual terminal's result page not updating correctly if the initial transaction fails. Instead of displaying transaction data from the most recent (successful) transaction, data from the first (failed) transaction continued to be displayed.
  • Provider Settlements and Reconciliation: Fixed an issue that would cause chargeback reversals to be created for the debit transaction, instead of the chargeback transaction.
  • Transaction List: Fixed an issue that would cause an error in the advanced search when changing the comparison operator from a range to any other operator.
  • Transaction List: Fixed an issue with sorting credit card fields. Note that BIN data cannot be sorted.
  • User Management: The frontend.statistics.show permissions now governs access to the pivot table as well.
  • Virtual Terminal: Fixed an unhandled exception in the virtual terminal that would occur if the fee set or fee entity was not found. The exception is now handled and an empty surcharge value is returned.

Adapters

Changed

  • Adyen (ADY): The payment reference for settlements is now saved.
  • Amazon Payment Services (AMAZO): It is now possible to filter transactions by the status "Accepted".
  • MultiSafepay (MUL): Added the chargeback reason for chargebacks.
  • Stripe (STRV2-EP1-MAS): Additional data from the Stripe API response is now included in the postback's extraData.

Added

  • dLocal (DLO-EP1): Added support for the Sinpe payment method. This method supports bank transfers in Costa Rica.
  • Worldline (ING-EP2): Added support for payments via Trustly.
  • Zona Virtual SA - Zonapagos (ZONA-EP1-ZP): Added a generic payment method that redirects to the Zona Pagos payment page. The consumer can then select the desired payment method on this page to initiate the transaction.

Fixed

  • Adyen (ADY-EP3-BIZ): Fixed an issue that would cause transactions that had been processed successfully to be assigned the status error or pending.
  • checkout.com (CHE): Fixed an issue that would cause an error when retrieving the session ID.
  • eMerchantPay (EME-EP3-SEP): Fixed an error that would occur if the customer was not an IBAN customer.
  • Mashreq (MASH): Fixed an issue when checking 3DS credentials that would cause a type error.
  • Mercado Pago (MERPA-PROD): Fixed an issue with register transactions caused by the Amount For Card Verification not being included in the request to retrieve the issuer and payment method ID from the PSP.
  • Skrill (SKR-EP1): Fixed an issue related to email addresses not being tied to a Skrill account when requesting a payout. This would cause the payout to fail.
  • Volt (VOL): Fixed an issue caused by incorrectly handling errors in a response as a result.

Please note that some of the features mentioned in the release notes may initially be available only within our sandbox environment for testing purposes. These features will be made available in the production environment upon successful testing and approval.

Gateway — v.24.6

Features

Changed

  • Post Processing Jobs:
    • The Collect Transactions by Uploaded CSV File post-processing job now allows multiple fields (arn, uuid, and adapterTxid) to be mapped. Previously, only the arn field could be mapped.
    • A new setting has been introduced, Cascading ID Mapping. If this option is activated, IXOPAY attempts to locate related transactions for every mapped identifier (in the same order as the fields are mapped in the post-processing job). If a transaction is found, it is added to the post-processing job, while all other identifiers in the CSV are ignored for that transaction.
  • Provider Settlements and Reconciliation: Improved the error message that is displayed when a transaction cannot be found due to a missing reference in the settlement file.
  • UI Navigation: New permissions have been added that determine whether users can access the dashboard (dashboard.show and frontend.dashboard.show). Existing users and roles will automatically receive these permissions. A welcome page is now displayed as the start page for users without access to the dashboard.

Fixed

  • Fee Management: Fixed an issue that meant it was possible to save fees even when the mandatory feeStrategyParameters field did not contain a value.
  • Fee Management: Fixed an issue where the amount was incorrect in retried transactions, as the amount would include previous surcharges if the surcharge was calculated dynamically.
  • Post Processing Jobs: Fixed an issue that prevented more than 1,000 connectors from being assigned to a post-processing job schedule.
  • Provider Settlements and Reconciliation: Fixed an issue that caused the delete button to be displayed for canceled transactions. The button is now only displayed if the status of the settlement is "new".
  • Provider Settlements and Reconciliation: Fixed an issue with resolving transactions by additionalId.
  • Transaction List: Fixed an issue with sorting by card type in the Transaction List.
  • Transaction List: Fixed an issue in the Transaction List filters that would cause no results to be returned if a filter was applied to the first 8 digits of the card number.
  • UI Navigation: Fixed an issue where the red highlighting of missing reconciliations was not applied when switching pages or applying a filter.
  • Virtual Terminal: Fixed an issue with surcharge fee calculations.

Adapters

Changed

  • GoCardless (GOC-EP1): GoCardless settlements now also include payment references.

Fixed

  • Adyen (ADY): Fixed an issue caused by the Izyco settlement data fetcher configuration parameter missing the regular expression for the file name.
  • Braintree (BRA-EP1): Improved the handling of the billing address. If the extra data fields for company, first name or last name are unavailable, the company, first name and last name are taken from the Customer object.
  • checkout.com (CHE-EP1-CC, CHE-EP2-CC):
    • Fixed an issue that would cause the status of a transaction to be set to ERROR if a callback is received that is not mapped in IXOPAY.
    • The following callbacks are now handled:
      • authorization_declined
      • card_verification_declined
      • card_verified
      • authentication_started
      • authentication_approved.
    • Added the mandatory provessingChannelId parameter for the NAS platform.
  • Nexi Group (NETS): Fixed an issue with settlements caused by a missing configuration.
  • PayU (PAU-E01): Fixed an issue that would cause a backend error if the payment_id is missing in the payload during callback processing.
  • Stripe (STRV2): Fixed an issue with Stripe settlements where transactions in IXOPAY were not correctly identified.
  • Volt (VOL): Fixed an issue with retrieving settlements.

Please note that some of the features mentioned in the release notes may initially be available only within our sandbox environment for testing purposes. These features will be made available in the production environment upon successful testing and approval.

Gateway — v.24.3

Features

Added

  • Audit Log: A color-coded diff of the changes to a post-processing job's configuration is now available.

Fixed

  • Multi-method connector: Fixed the status poll for multi-method connectors and added a new connector setting (Delay autoCapture for debits by 5min) that can be used to delay the automatic capture.
  • Network Tokenization: Fixed an issue that displayed disabled merchants in the NTS enrollment and Assign TRID drop-down lists.
  • Post Processing Jobs: Fixed an issue with exporting data that would cause credit card data (e.g. the brand) to be empty in the exported file.
  • Provider Settlements and Reconciliation: Fixed an issue with chargeback reversals that prevented them from being processed.
  • UI Navigation: The network token status tab is now hidden if no network token is available.
  • UI Navigation: Fixed an issue with sorting merchants and customer profiles.
  • Virtual Terminal: Fixed an issue with the formatting of surcharge amounts when entered as a percentage instead of an absolute value.

Adapters

Changed

  • Alignet (ALI-EP01-CC): Removed the merchant transaction ID section.
  • checkout.com (CHE-EP1-CC):
    • Added billing post code/ZIP and billing state fields for AFT transactions.
    • When the Postback/Status: Include Auth-Code in postback/response and status response connector setting is enabled, the auth-code sent by Checkout.com is now included in the callback.
  • Cybersource (CYS-EP1-CC):
    • Added support for partial capture
    • Mapped additional fields in API calls
    • Added support for the JapanPaymentOptions parameter for installments.
  • DPO Pay (PAYGA-PYGT): Added support for handling callbacks.
  • Nuvei (NUV): Added the ability to parse line items containing fees in settlement files.
  • PXP (PXP): An SFTP host can now be defined for the settlement data fetcher. If no SFTP host is specified, the default host (sft1.servebase.net) is used instead.
  • Zona Virtual SA - Zonapagos (ZONA-EP1): Added a setting to enable custom URLs for endpoints.

Added

  • China UMS (UMS): China UnionPay Merchant Services (China UMS) is a subsidiary of China UnionPay, a major financial services corporation in China. The adapter supports payments via Alipay and WeChat Pay.

Fixed

  • Adyen (ADY-EP3): Fixed an issue with the handling of the PresentToShopper result codes with the Multibanco payment method. The transaction is now set to pending instead of causing an error. This applies to all initial transaction types (debit, preauthorize and register).
  • Alignet (ALI-EP01-CC): Fixed an issue with ID duplicates caused by simultaneous transactions.
  • Alipay - Ant Group (ANT-EP1-ALIPL): Fixed a rare issue where an empty response would result in an error.
  • American Express (AMX):
    • Transactions in American Express settlements can now also be resolved using the additionalId1 field. The settlement handler first checks the UUID and then the additionalId1 field.
    • Refund amounts are now saved as absolute values.
  • checkout.com (CHE-EP1): Fixed an issue when mapping errors where the error code is empty.
  • checkout.com (CHE-EP1-IDE, CHE-EP2-IDE): Improved the adapter's error handling.
  • Mashreq (MASH): Debit calls include both a preauthorize and capture call. A 5 minute delay has been added to the capture due to recurring issues with instant captures.
  • Mashreq (MASH-EP01): Fixed an issue with parsing the API response that could result in an invalid value, leading to an error.
  • Worldline (ING-EP2): Fixed an issue with the data type used for the mandateDate.

Please note that some of the features mentioned in the release notes may initially be available only within our sandbox environment for testing purposes. These features will be made available in the production environment upon successful testing and approval.

Gateway — v.24.1

Features

Changed

  • Job Configuration: Strengthened TLS verification for the target host when utilizing the Send document to endpoint post-processing step.

Added

  • Connector Settings:
    • Added a new connector setting Postback/Status: include original adapter reference id in postback request and status response to enable sending extraData["originalAdapterReferenceId"] in callback requests and status responses for all transaction types.
    • Added a new connector setting Postback/Status: include reference uuid for all subsequent transactions in postback request and status response to enable sending referenceUuid in callback requests and status responses for all transaction types. This includes transactions referenced directly via the referenceUuid field, as well as related transactions in the customerProfileData.customerProfileGuid field of the customer profile, provided the customer profile belongs to the affected merchant.

Fixed

  • Customer Profiles: Fixed an issue where manually detaching a payment instrument without deleting it from a customer profile caused unwanted behavior.
  • Provider Settlements and Reconciliation: The callback URL for chargebacks initiated through settlement processing is determined automatically. If the related transaction lacks a callback URL, the transaction tree is searched for an appropriate destination.
  • User Management: Extended the Include Sub-Tenants filter to include sub-tenants of sub-tenants, not just direct sub-tenants.

Adapters

Changed

  • Adyen (ADY-EP3-MBWAY): Added support for the MB Way payment method to Adyen Checkout. MB WAY, provided by MULTIBANCO, serves as a mobile wallet within Portugal's interbank payment network.
  • checkout.com (CHE-EP2-IDE): Added support for the iDEAL payment method using the checkout.com NAS platform. iDEAL is an online payment method that enables consumers to pay online through their own bank. Payments are made via bank app or online banking.
  • Klarna (KLW-EP1):
    • Added documentation on required parameters.
    • Added fallback logic to populate essential customer fields when shipping data is missing.
  • Worldline (ING-EP2): Added support for the Sofort payment method. Sofort is the predominant online banking method in countries such as Germany, Austria, Switzerland and Belgium and continues to expand its global reach.

Fixed

  • 2C2P (2C2P-EP1): Improved the handling of empty HTTP responses received from 2C2P.
  • Alignet (ALI-EP01-CC):
    • Updated documentation to clarify that customer shipping address first and last name parameters are optional.
    • Included extraData from referenced transactions in follow-up transactions.
  • Bitpay (BTP-EP1): Fixed cancelUrl forwarding to Bitpay and introduced logging for Bitpay invoice adapter calls.
  • Braintree (BRA): Skip loading transaction data when receiving Braintree callbacks without a paymentId.
  • checkout.com (CHE):
    • Fixed an issue where settlement processing failed if a previous data fetcher returned no data.
    • Updated documentation with more detailed information about extraData fields relevant to the recipient of account funding transactions.
  • Sepa Express (SEP): Improved UTF-8 handling in the account holder field to handle invalid characters more effectively.
  • Unzer (UNZER-EP1): Fixed an issue with handling empty responses from the PSP.
  • Volt (VOL-EP1): Enhanced callback processing to immediately mark transactions as successful upon receiving a COMPLETED status callback and the successOnSettle connector setting is enabled.
  • Worldline (ING-EP2): Fixed an issue with follow-up debit transactions that reference transactions based on imported IBAN tokens.

Please note that some of the features mentioned in the release notes may initially be available only within our sandbox environment for testing purposes. These features will be made available in the production environment upon successful testing and approval.