Features
Changed
- Post Processing Jobs:
- The Collect Transactions by Uploaded CSV File post-processing job now allows multiple fields (
arn
,uuid
, andadapterTxid
) to be mapped. Previously, only thearn
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.
- The Collect Transactions by Uploaded CSV File post-processing job now allows multiple fields (
- 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.
- Fixed an issue that would cause the status of a transaction to be set to
- 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.