Skip to main content

v.24.0

API

Fixed

  • Batch Upload API: Fixed a number of issues with the Batch Upload API:
    • Fixed a bug that generated an incorrect output format when an error occurred.
    • Fixed an issue when querying the status of a batch request that would result in an HTML response being generated when the batch ID referenced a non-existent batch. A JSON response is now generated containing "batch not found".
    • In cases where validation errors (e.g. the merchantTransactionId is already assigned) prevents a transaction from being created, the transaction was not written to the output at all. The output now includes a line with success = false, along with an error message in the output file for every transaction that could not be created.
  • Transaction API: Removed the thousands separator from the amount field in callbacks for transactions with a surcharge fee.

Features

Changed

  • UI: The Tools section in the platform has been overhauled. The entries previously located here have been moved to more relevant parts of the platform - this includes options such as BitPay pairing and Tokenization.

Added

  • Job Configuration: Added a new feature to automatically add comments to potentially fraudulent transactions and send out emails with relevant information.

Fixed

  • Connector Settings: Fixed a minor visual issue that occurred when selecting the same connector setting twice. The setting was then displayed twice. The setting is now only displayed once.
  • Post Processing Setting: Fixed an issue with sending callbacks for transactions created via settlements.
  • Transaction List Filter: Fixed an issue with the filter for transactions created in test mode not being applied correctly.
  • User Management: Fixed an issue where users were unable to add new merchant users unless they had the frontend.users.roles.edit permission.

Adapters

Changed

  • Amazon Payment Services (AMAZO-EP1-CC): Added support for the new JSON settlement format.

Added

  • Alignet (ALI-EP01-CC): Alignet is a leading technology company based in Peru, specializing in solutions for secure electronic transactions. They pioneered the use of 3-D Secure in Latin America and are a key supplier of major banks in the region. The adapter supports credit card transactions.
  • Braintree (BRA-EP1): Added support for the Blik payment method. Blik allows for bank transfers and covers all major Polish banks.
  • PayTabs (PAYT-EP01-VALU): PayTabs is a payment processing solution specializing in seamless online transactions in areas such as the Middle East, North Africa and Southeast Asia. The adapter currently supports payments using the valU BNPL payment method in Egypt.
  • Worldline (ING-EP2): Added a new endpoint as well as the option to switch between old and new endpoints in the configuration.
  • Worldpay, checkout.com (CHE, WOR): Updated the API documentation for checkout.com and WorldPay WPG to include AVS and CVV responses.

Fixed

  • Adyen (ADY-EP3): Fixed an issue with missing notification verification for AdyenCheckout.
  • Adyen (ADY-EP3-RIV):
    • Added support for partial captures for the Riverty payment method using Adyen Checkout.
    • The IP address field is now optional instead of mandatory when using the Riverty payment method with AdyenCheckout.
  • Bitpay (BTP-EP1-CR): Fixed pairing issues with the new Bitpay connector configuration.
  • Braintree (BRA-EP2): Fixed an issue with Braintree's Address Verification Service.
  • checkout.com (CHE):
    • Fixed the handling of settlements for transactions with multiple partial captures.
    • Multiple fees are now supported for a single transaction in the settlement report.
  • Klarna (KLW-EP1-APM): HTTP 400 responses are now mapped correctly.
  • Mashreq (MASH-EP01): Added handling for the status "Awaited", which previously returned an error (due to this status not being documented by CCAvenue). The transaction is now set to pending when this status is received.
  • MultiSafepay (MUL): Fixed an issue with the settlement fetcher that prevented settlements from being retrieved.
  • Nuvei (NUV-EP2): Enabled support for partial captures.
  • Zona Virtual SA - Zonapagos (ZONA-EP1):
    • A unique numeric value is now generated and sent to Zona Virtual as the payment ID Id_pago. This value is stored in the additionalId1 field in IXOPAY as a payment reference that is used if the payment fails.
    • Changes have been made to the mandatory fields. The following fields are no longer mandatory: merchantMetaData, extraData.idType, customer.identification.
    • Fixed the default error mapping.
    • Added mapping for the error when a payment cannot be found.

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.

v.23.22

API

Fixed

  • Batch API: Addressed issues with the conversion of files from CSV to JSON, and conflicting UUIDs due to latency between the time when a transaction is submitted and actually processed.
  • Transaction API: Fixed an issue where if a failover transaction returns a merchant advice code, this MAC is not returned by the origin transaction. The MAC is now returned by the origin transaction.

Features

Changed

  • Customer Profile: It is now possible to use the UUID or payment token from a customer profile to request a CVV refresh via payment.js. This makes it possible to ask the customer to enter their CVV for transactions using a stored credit card.
  • Post Processing Setting: Postback notifications are now sent when creating an "unknown" transaction.
  • UI: Information on the possible impact of daylight savings time is now displayed when editing job schedules.
  • User Management: Any changes to merchant users now require additional confirmation, and a message is displayed that these changes may have an effect on live processing.

Fixed

  • Global Connector Settings: Transaction expiry settings are now displayed in the connector's global settings section.
  • Post Processing Job Configuration: The calculation of the net settlement amount in the "Write customized Settlement CSV" job step is now the same for refunds and chargebacks.
  • Risk Profile: The "Allowlist" and "Blocklist" risk rules no longer list credit card-related options such as the BIN and CC fingerprint for the meta-connector, as the card cannot be evaluated at this stage of processing.

Adapters

Changed

  • Bitpay (BTP-EP1-CR): BitPay pairing has been moved to the connector's Additional Configuration tab.
  • dLocal (DLO-EP1): Support has been added for PuntoXpress and PayCash in Costa Rica.
  • HUA NAN COMMERCIAL BANK (HNCB-EP2-HBQR): The key version used for encryption is now a configuration option.
  • Paynetics (PNE-EP1-CC): Added API documentation for Paynetics.
  • PAYONE (PASIX-EP3-CC): Added API documentation for Payone.
  • Worldline (ING-EP2-CC): Fixed an issue where tokens are flagged as single use when they should be flagged as recurring. These tokens can now be reused.

Added

  • Adyen (ADY): Added a new data fetcher for settlements provided by Izyico.
  • Zona Virtual SA - Zonapagos (ZONA): Zona Virtual is a Colombian company with 23 years of experience in the e-commerce sector. The ZonaPagos adapter support payments via credit card and Pagos Seguros en Línea.

Fixed

  • checkout.com (CHE): Added support for "Partial Capture" settlement entries.
  • GoCardless (GOC): Fixed an issue with register transactions in the new server-to-server flow.
  • Nuvei (NUV-EP1-CC): Updated the API documentation to include mapping information.
  • Shift4 (CRE-EP1-CC): Fixed an issue with how UUIDs are formatted in failover transactions.
  • Sofort (SOF-EP2-SOF): Fixed an issue with refunds that would change the status of the original transaction from success to error.
  • Unzer (UNZER-EP1): The orderId in capture requests now uses the additionalId1 in the preauthorize transaction.
  • Valitor (VALIT-EP1-CC): Fixed an issue with duplicated preauthorize transactions in settlements.

Misc

Added

  • API Documentation: Updated the API documentation to include information on the bin_digits parameter.

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.

v.23.21

Features

Fixed

  • Transaction Details: Additional headers for callbacks including Content-Type, Accept and User-Agent are now added to the postback transaction logs in the transaction details view when the postback:send-test-plain-header or postback:send-useragent-header are set in the connector settings.
  • Transaction Export: Fixed an issue with the export of transaction data for merchants with mult-merchant access.
  • UI Navigation: The Croatian and Slovenian translations have been updated.

Adapters

Changed

  • Braintree (BRA-EP2-CC): The connector configuration has been updated, see the documentation for more information.
  • Braintree (BRA-EP1): The additionalId1 field is now mapped to the descriptor name instead of the descriptor URL.
  • Cybersource (CYS-EP1-CC): Updated the description of auxiliary data in the documentation.
  • DPO Pay (PAYGA-PYGT): The DPO Pay adapter now supports preauthorize, capture and void transactions for credit cards.
  • Worldpay (WOR-EP1-CC): The API documentation has been updated to include information on which parameters are mandatory for the Worldpay WPG PCI adapter.

Fixed

  • ATOM (an NTT DATA Company) (ATOM-EP1-CC): Fixed an error with retrieving the settlement that was introduced in an earlier change.
  • Braintree (BRA): The createdAt timestamp supplied in Braintree's postback is now used as the timestamp for PayPal chargebacks.
  • DPO Pay (PAYGA): Fixed an issue that prevented settlements from being processed due to an invalid date format.
  • EPG Financial Services Limited (EPG-EP01-PAYLA): If the additionalId1 field is not provided as part of the payout request, the alias of the referenced debit transaction is used as a fallback option.
  • GoCardless (GOC-EP1): Fixed an issue with the server-to-server flow caused by a missing parameter.
  • Valitor (VALIT-EP1-CC): Fixed an issue with settlements caused by duplicate transaction lifecycle IDs.

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.

v.23.20

Features

Added

  • Job Configuration: To simplify the process of exporting settlement file data for enterprises with multiple merchants, the External ID stored in the provider can now be used to store an identifier for each merchant. This ID can be selected in export jobs, allowing the same export job to be used for each company/merchant in cases where there are otherwise no differences between the exports. Previously, an individual export needed to be configured per company/merchant.

Fixed

  • Account Updater: Fixed an issue with the Account Updater that would lead to an incorrect Status being displayed for batch updates ("Finished" instead of "Waiting").
  • Account Updater: Fixed an issue with the new merchant overview where clicking on the details would not redirect users to the selected merchant, but to the selected tenant instead.
  • Merchant Interface: Updated some translations and reviewed the Croatian and Slovenian translations.
  • Pay-by-Link: Restricted the ability to cancel transactions to pay-by-link transactions only.
  • Post Processing Setting: Fixed an issue that would prevent settlements from being retrieved if the waitForAllFiles setting is enabled. Incomplete periods are now also handled correctly, with the last period only being updated if settlement files were processed.
  • UI: Fixed the 8-digit BIN display in the transaction details view.
  • UI Navigation: Fixed the broken icon for creating connectors.
  • Virtual Terminal: Removed trailing apostrophes for virtual terminal result URLs.

Adapters

Changed

  • American Express (AMX-EP1): Reinstituted a change that was reverted in the last release. A reference number is generated and passed to the vault as part of the capture request using the additionalId1 field. However, this could not be handled using the multi-method connector.
  • ATOM (an NTT DATA Company) (ATOM-EP1-CC): The data fetcher configuration has been updated, allowing additional field mappings for settlement files. The names of the fields selected here need to be added to the key column in the export job.
  • checkout.com (CHE-EP2): Added payout parameters for platform 2.
  • dLocal (DLO-EP1-PUNTO): The Punto Express payment method is now supported by the dLocal adapter.
  • eMerchantPay (EME-EP3-SEP): Added support for deregister transactions.
  • GoCardless (GOC-EP1): An additional configuration option has been added for the connector that provides a choice between redirect and server to server flows.
  • Nuvei (NUV-EP2): Fixed the mapping of Nuvei error codes, with "Service Busy" now being mapped to IXOPAY error code 3003 (temporarily unavailable).
  • Sepa Express (SEP-EP3-BTR): Added a new bank transfer payment method to the adapter. As this payment method uses open banking, some transaction types like register and deregister are unavailable, along with other transaction types not implemented in the original version of the adapter.
  • SoftBank Payment Service (SOB-EP1): The documentation was updated to include information on required fields.
  • Unzer (UNZER): Fixed the title for the Unzer API documentation.
  • Valitor (VALIT-EP1-CC): Fixed an issue that would cause refunds to fail for capture transactions. Instead of requesting a refund, IXOPAY now requests a capture refund, which resolves this issue.

Added

  • AsiaPay (ASIA): AsiaPay is a leading payment service provider in the APAC region. The adapter supports GCash, ShopeePay and credit card payments.
  • HypYaad (HYP-EP1-CC): Hyp is an Israeli all-in-one payments solution that provides online and in-store payment solutions. The adapter supports credit card payments.
  • Unzer (UNZER-EP1): Unzer is a leading fintech company based in Germany, specializing in providing innovative and secure payment solutions. With a strong focus on e-commerce, Unzer offers a wide range of payment methods and services.

Fixed

  • American Express (AMX-EP1): Fixed an issue with fees in American Express settlements that would only occur under certain circumstances.
  • AsiaPay (ASIA): The AsiaPay PesoPay logo is now displayed wherever the brand name is used instead of the adapter name.
  • checkout.com (CHE-EP1): Fee reports are now handled in a second process, rather than as part of the settlement. A new data fetcher configuration (gross type) is available for this purpose.
  • Klarna (KLW): Fixed an issue with validation that affected customers in specific locations. The validation now checks that the billingState is set if the country is US or Australia.
  • Nuvei (NUV-EP1): Improved the parsing of the CSV settlement files to be more robust. Under some circumstances, an error could occur when parsing settlement files.
  • Nuvei (NUV-EP1): Before parsing a row in the reconciliation file, the date is checked to ensure it is valid.
  • Straight2Bank Pay (STRAI-E01): Fixed an issue that would cause the retrieval process for settlements to be locked if an invalid response was received.
  • Unzer: Fixed errors caused when postback sharing is not set in the connector.
  • Worldpay (WOR-EP1-CC): The adapter transaction ID is now set when an incoming postback is received.

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.

v.23.19

API

Added

  • Transaction API: Added dedicated fields for the cardholder billing state (billingAddressState) and cardholder shipping state (shippingAddressState) used in 3DS authentication.

Features

Changed

  • Permissions: Front end user roles have been split into view and edit permissions.
  • UI: Autocompletion of password input fields has been disabled as a security measure.

Fixed

  • Multi-method Connector: Fixed an issue with converting register transactions to debit/preauthorize transactions for adapters that do not support register transactions directly. This conversion would fail when using multi-method meta-connectors in conjunction with the processing:convert-register-to-debit setting.
  • Post-processing Schedule: Fixed an issue in calculating the post processing schedule interval.
  • UI: Fixed the Token icon colour for white label tenants.

Adapters

Changed

  • Klarna (KLW-EP1-APM): In order to support an upcoming change, the IXOPAY UUID is now provided via the merchant_reference1 and merchant_reference2 fields. IXOPAY now checks for the UUID in merchant_reference2 when handling settlements, using this value as a fallback until changes to the handling of the UUID are complete.
  • Mashreq (MASH-EP01-CCRD): The response data is now used to set the transaction status instead of sending a separate request to retrieve the status.
  • Valitor (VALIT-EP1-CC): Changed the Valitor ID used to map settlements, as the ID used previously could not handle certain cases such as refunds.

Added

  • Adyen (ADY-EP3-BIZ): Bizum has been added as a new payment method.
  • AsiaPay (ASIA): AsiaPay is an Asian digital payment service provider, covering credit and debit cards, online banking, digital wallets, BNPL and other digital payments. The new adapter supports GCash, BPI and ShopeePay as well as credit card payments with JCB and Mastercard.

Fixed

  • eMerchantPay (EME-EP3): Fixed issues with invalid amounts that occurred when the currency is missing by using the related transaction's currency as a fallback.
  • Worldline (ING-EP2-CC): Updated the adapter to use the same error mapping for adapter calls and incoming callbacks.

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.