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.

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.

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.

API​

Added​

• Transaction API: Updated the API response to include the schemeReferenceIdentifier field.

Features​

Changed​

• Performance Optimization: Improved performance of the admin UI for users with many locked transactions.
• Post Processing Jobs: Added a new post-processing option that calculates the sum total for line items with the same type and details (e.g. chargebacks) in the data export. A new field, thisLineItemValue sum has been added for this purpose.

Added​

• Push Adapters: The OfflineInvoice and SepaDummy adapters now support preauthorize, register, capture, void, refund, debit and payout transactions, allowing these transactions to be included in IXOPAY.

Fixed​

• Currency Conversion: The New Deviation Tolerance button is now only displayed if the user has permission to edit deviation tolerances.
• Currency Conversion: Fixed an issue where a JSON response was received instead of an HTML page when pressing Enter while entering data for deviation tolerances.
• Customer Profiles: Fixed an issue that caused a new customer profile to be added when sending a paymentToken of an existing customer profile by supplying a transactionToken and a customerProfileData.customerIdentification in the request.
• Customer Profiles: Fixed an issue with how deleted customer profiles are handled.
• Provider Setting: Only a single rolling reserve configuration can now be defined per payment method.
• Provider Settlements: The timestamp for when a transaction was last modified is now updated correctly in the settlement status.
• User Settings: Fixed permissions for merchants assigned to sub-tenants.

Adapters​

Changed​

• dLocal (DLO-EP1): Extended the dLocal adapter to support transactions in Ecuador.
• dLocal (DLO-EP1-BT): Added support for bank transfers in Costa Rica.
• Straight2Bank Pay (STRAI-E01): Added a new option checkPaymentMethod for Straight2Bank settlements that only retrieves Billdesk transactions with the status CREDITED but not with the status SUCCESS.
• Valitor (VALIT-EP1-CC): The ValitorPay adapter now supports network tokens.

Added​

• Braintree (BRA-EP1): Extended the Braintree adapter to support Venmo as a payment method.
• Braintree (BRA): Switched from a deprecated SDK version to the latest version, migrated from checkout.js to JS SDK and added support to passthrough items, shipping/billing address details, invoice ID, discounts and shipping costs.

Fixed​

• ATOM (an NTT DATA Company) (ATOM-EP1-CC): Fixed an issue that caused the signature to be calculated incorrectly if data contained special characters.
• Braintree (BRA-EP2): Updated the handling of Braintree disbursement and settlement handling to reflect the file structure supplied by Braintree for Interchange plus (IC+).
• EquensWorldline (EQW-EP2): Fixed the handling of responses using v3 of the API.
• Mashreq (MASH-EP01-CCRD): Fixed the mapping of transaction IDs in settlements for Mashreq.
• Nets Group (NETS-EP1): Fixed an issue with the Nets widget not displaying correctly on payment pages.
• Nuvei (NUV-EP1-CC, NUV-EP2-CC): Fixed an issue caused by Nuvei no longer providing the auth code in callbacks, which would cause refunds to fail.
• Nuvei (NUV-EP2): Fixed the mapping of errors to IXOPAY error codes.
• PAYONE (PASIX-EP1-CC): Added a new payment reference for Six that is valid for all countries.
• Volt (VOL-EP1): Fixed the mapping of Volt transactions in 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.

API​

Added​

• Transaction API: Added the parsedMerchantAdviceCode to transactions that contains the parsed merchant advice code for those adapters that support MAC, including the Simulator adapter.

Features​

Added​

• 3DS: The CardholderInfo field from the issuer is now returned for failed 3DS authentications. The information in this field provides additional information on why 3DS failed and can be displayed to the user.

Removed​

• Setup: Merchant and connector templates have been removed. The same functionality can now be achieved using the global settings.

Fixed​

• Callback: Fixed an issue with callbacks when the postback format was set to inherit and a follow-up transaction was using a different API version than the initial transaction.
• Post Processing: Fixed the verification of a mandatory job period setting in job schedules.
• Post Processing: Fixed an issue introduced by a recent UI update that caused some buttons to no longer work in the Post-processing configuration.
• UI Navigation: The UI has been updated to support 8-digit BINs.
• Virtual Terminal: Fixed an issue where confirmation emails were sent out incorrectly. Mails would be sent if the "vt mail on success" setting was enabled, even if the transaction was not related to the virtual terminal. Mails were also sent for all pay-by-link transactions, even if the option to send out emails for PBL was disabled.

Adapters​

Changed​

• American Express (AMX-EP1-AMX): A new setting is available for the American Express settlement data fetcher that saves the Amex payment number as the batch number, instead of using the date and time.
• Worldpay (WOR-EP1): The line item SETTLED_MISCELLANEOUS (for fees not associated with a particular transaction) is now handled without creating a conflict.

Fixed​

• 2C2P (2C2P-EP1): Fixed an issue where settlements were sometimes fetched twice.
• Adyen (ADY-EP3-APP, ADY-EP3-CC, ADY-EP3-GOP): Fixed a bug that occurred when cross-referencing a transaction at another PSP.
• Braintree (BRA-EP2): Billing address data from the initial transaction is now stored and can be used in follow-up transactions. This billing address data is now used to process debit and preauthorization transactions.
• Braintree (BRA-EP2): The field additionalId1 can now be mapped to the descriptor object, allowing the invoice number to be passed to Braintree.
• Nuvei (NUV): File names for settlements can now be entered using a new optional regular expression field.
• Volt (VOL-EP1): Fixed an issue with settlements caused by both debits and refund transactions related to the same transaction having the same ID in Volt, causing refunds to sometimes be settled instead of debits.

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.