Skip to main content

v.24.8

API

Fixed

  • Provisioning API: The frontend.dashboard.show permission, used to grant access to dashboards, has been added to the Provisioning API.

Features

Added

  • Blocklist: Extended the blocklist to include the ability to define automatic blocklist rules. These can be used to add credit cards to the blocklist based on the merchant advice code ("Do not retry") or error code.

Fixed

  • User Management: Fixed an issue with sending account recovery emails that would cause an error if the email failed to send.

Adapters

Changed

  • 2C2P (2C2P): Improved the error displayed when no transaction method is defined to better indicate the cause of the error.
  • 2C2P (2C2P-EP1): Refunds in 2C2P settlements are now handled.
  • PayPal (PPA-EP1-PPE): Added support for the Pay Later method to the Braintree adapter.
  • Sampath Bank (SAMPA-SVNP1): Added support for credit card payments via redirect.
  • Valitor (VALIT): Updated the adapter to automatically create a second chargeback if included in the settlements received from Valitor.
  • Worldline (ING-EP2): Improved the mapping of error codes based on the specific error, rather than just the HTTP status code.
  • Worldpay (WOR): Chargeback reversals for credit cards are now handled in settlements and included as line items.

Fixed

  • Adyen (ADY-EP3): Fixed an issue that could result in long request processing times caused by transactions being locked when multiple postbacks are received simultaneously.
  • Nexi Group (NETS-EP2): Fixed the incorrect mapping of adapter error messages.

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

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

v.24.5

Features

Changed

  • UI Navigation:
    • If the user only has access to a single connector, it is now automatically selected in the virtual terminal.
    • The last selected connector is stored locally to prevent having to re-select it for future transactions.

Added

  • BI Data Source: Scheme IDs are now available for post-processing.
  • Connector Configuration: Added a new project setting, Manipulation: Field Operation that can be used to manipulate data at the connector level prior to sending the data to the PSP. It is currently possible to truncate the data after a defined number of characters using this option. More operations will be added in the future.
  • Fee Management: Added the ability to specify the customer's billing state for fees.
  • UI Navigation: Added information on the deployed version to both the gateway and documentation.

Fixed

  • Fee Management: Fixed an issue that would result in an error if no target fee set has been specified and the source fee set is assigned to a sub-tenant.
  • UI Navigation: Fixed an issue that prevented archived jobs from being restored when in the table view.
  • Virtual Terminal: Fixed an error that could occur when calculating surcharges if no credit card number has been entered.

Adapters

Changed

  • American Express (AMX-EP1-AMX): Added support for Apple Pay.
  • China UMS (UMS-EP1): Added the optional expireTime parameter to the payload. The value of this parameter is taken from the extraData field. If the parameter is not provided there, it is taken from the project settings.
  • Cybersource (CYS-EP1-CC): The forwardedAcquirerCode field is now available for postback notifications.
  • HypYaad (HYP-EP1-CC): Added support for settlements in CSV format and stored on an SFTP server.
  • Klarna (KLW-EP1): The customer.birthDate field has been changed from required to optional.
  • PXP (PXP-EP1-CC): The SchemeTransactionIdentifier, SchemeSettlementDate and DinersRetrievalReferenceNumber in callbacks are now stored for use in recurring transactions.
  • SIA (SIA-E01): Added support for void and partial captures.

Added

  • Paymee (PAYME-EP1-CCRD): Paymee is a Tunisian payment gateway that accepts credit card payments via a redirect link.
  • Sampath Bank (SAMPA-SVNP1-BTR): Sampath is a secure Sri Lankan online payment platform. The adapter supports bank transfers.

Fixed

  • Adyen (ADY):
    • When submitting a transaction using a hosted payment page, clicking on the back button caused the transaction to be resubmitted. This caused two transactions to be sent to the PSP, but IXOPAY only counts this as a single transaction. The duplicate transaction is automatically closed by the PSP, which can overwrite the correct transaction ID of the transaction in IXOPAY.
    • Fixed an issue with settlement notifications that caused settlements to be ignored.
  • Amazon Payment Services (AMAZO):
    • A new option has been added that supports SHA-512 alongside the previously supported SHA-256 encryption. This setting should be configured in IXOPAY to match the one configured in the Amazon settings.
    • Fixed an issue generating settlement reports that would only occur when an existing settlement report was re-generated.
  • China UMS (UMS): Fixed an issue that prevented the status of pending transactions from being polled correctly.
  • China UMS (UMS-EP1): A refund order ID has been added, which now allows multiple refunds.
  • Klarna (KLW-EP1): Fixed a number of issues that could occur in cases where the customer's birthdate is missing.
  • NMI (NMI-EP1): Fixed an issue where a type error would occur if no related transaction is present and no extra data is set for a credit card connector. The expected data type is an array; if no data is available, an empty array is now used.
  • Worldline (ING-EP6): Fixed an issue that could cause successful refunds to remain stuck in a pending state.

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

API

Added

  • Transaction API: The "account closed" error for PCI adapters has now been mapped to error code 2001 in IXOPAY and treated as a hard decline.

Features

Changed

  • Alerts: Instead of sending out separate emails for each alert, email notifications are now sent out periodically. These emails will collect all alerts received over a time period in a single email. The default time period is 5 minutes, but can be configured individually for each notification category.

Added

  • Provider Settlement: Added a new feature to allow dummy settlement files to be created in order to test various post-processing features. The "Test Settlement" option is accessible from the "Provider Settlement" page. This page has been reworked and the UI has changes as a result. A new permission, postprocessing.provider-settlement.create, has been added. This permission must be enabled in order to access the "Create Settlement", "Upload Settlement File" and "Test Settlement" actions. The old permission, postprocessing.provider-settlement.settlement-upload, has been removed. If this permission was previously active, the new permission will be active by default.

Fixed

  • Job Configuration: Fixed an issue where two Save buttons were displayed when editing job configurations.
  • Transaction List: Ignore tenant name in the transaction list if only the "Include Sub-Tenants" checkbox was checked.
  • UI Navigation: Fixed an issue where styling was not applied to conflicted transactions after applying a filter.
  • UI Navigation: Fixed issues with sorting the transaction list by cardholder, first 6-8 digits, last four digits and card type. The table can no longer be sorted by card level, card bank and card country.

Adapters

Changed

  • Neteller (NET-EP1-NET): Added support for payouts.
  • Paynetics (PNE-EP1-CC): A new data fetcher setting, "Split settlements by PayCurrency", is now available. If enabled, settlements are split by currency and the PayCurrency is used as the SettlementCurrency.
  • Skrill (SKR-EP1-SKR): Added support for payouts.

Added

  • JCC Payment Systems (JCC): JCC Payment Systems leads Cyprus' payment-processing sector, supporting merchants and financial institutions for nearly 30 years.

Fixed

  • Adyen (ADY-EP3): Disabled refunds for the Multibanco payment method, as refunds are not supported for this payment method.
  • Braintree (BRA-EP1):
    • Fixed an issue that would result in an error if the customer was empty in a transaction.
    • Fixed an issue that occurred if the public or private key were null values.
  • China UMS (UMS-EP1):
    • Fixed an issue where white space was included in requests when no customer name is provided.
    • Fixed the mapping of callback data in the extraData field.
    • Fixed an issue with integer values in the extraData. Integer values are now converted to strings.
  • Klarna (KLW-EP1): When creating a session, the merchant_reference2 field is now also included. This provides additional information for identifying the transaction.
  • Straight2Bank Pay (STRAI-E01): Fixed an issue that would occur if the encryption key and payload were missing. The system now checks whether these values are present, and a correspoing error is returned if this is the case.

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.