Skip to main content

4 posts tagged with "Nexi Group"

View All Tags

Gateway — v.24.17

Features​

Changed​

  • Post Processing Setting: Added validation of custom parameters, it will now show an error when trying to save post processing job settings with invalid custom parameters.

Fixed​

  • Customer Profiles: Use the network token (dPAN) instead of the fPAN when a customer profile was created or updated from a network token registration.

Adapters​

Changed​

  • Valitor (VALIT): Added support for mapping Acquirer Reference Numbers (ARNs) in settlement processing.
  • Worldpay (WOR-EP1): Added support for account funding transactions (AFT).

Fixed​

  • GoCardless (GOC): Fixed an issue in settlement processing where missing links.payment or links.refund in a refund object would previously cause an error and stop transaction retrieval.
  • Klarna (KLW): Fixed Klarna settlement configuration to allow longer passwords via the KlarnaApiPassword field in the provider settlement data fetcher configuration. If no KlarnaApiPassword is set, the connector configuration password will still be used.
  • Nexi Group (NETS): Fixes a problem with the test-mode configuration setting which prevented retrieving settlements.
  • PayPal Complete Payments - PPCP (PPCP-EP1-PPE): Removed null values from the setup token call to prevent issues with the prepare-register call when shipping details are not provided.
  • PXP (PXP-EP1-INST):
    • Added missing adapter specific documentation.
    • Send initiatePaymentFromReferenceRequest.merchantTransactionId to the PSP to correctly link follow-up transactions with their initial transaction.
    • Fixed handling of responses of capture, refund, and void transactions.
  • Worldpay (WOR-EP5): Fixed the settlement amount calculation for refunds during settlement processing.

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

API​

Changed​

Fixed​

  • Pay-by-Link API: Fixed an issue that would prevent a pay-by-link transaction from being canceled if a failover occurred for the transaction.
  • Push API: Fixed an issue that would cause a type error if an empty body request was submitted in a Push API request.
  • Transaction API: Fixed an issue where invalid 3DS values (browserColorDepth, browserTimezone) sent to the API in transaction data would cause an error. These invalid values are now ignored.

Features​

Changed​

  • Connector Settings: The "Postback: Include 3DS Data" connector setting is now also available in the global settings.
  • Post Processing Jobs: Optimized the process of collecting transactions in post-processing jobs.
  • UI Navigation: Improved the parent tenant selection when creating a new tenant. By default, the current tenant is set as the parent tenant and the drop-down is now searchable.
  • UI Navigation: Updated risk logs so that they are loaded asynchronously. This improves the initial load time for the transaction details view. Risk data is now only loaded when expanding the view.

Added​

  • Connector Configuration: Added audit logs for the "Additional Configs" in the connector view.

Fixed​

  • Audit Log: Fixed an issue that would cause an error when accessing the audit log if the corresponding merchant cannot be found when checking access permissions.
  • Fee Management: Fixed an issue that would cause an error when changing the mapping to a different fee entity. The mapping for the old fee entity is now removed, and the mapping is set to the new fee entity.
  • Post Processing Setting: Fixed an issue with the "Create unknown transaction on connector with GUID" option for settlements that prevented unknown transactions in a settlement file from being added to the platform.
  • Provider: Fixed an issue that would occur when saving a connector configuration. Previously configured connectors that were assigned to the same provider were removed when the configuration was saved, with only the new configuration linked to the provider.
  • Provider Settlements and Reconciliation: Fixed an issue that would cause an error when trying to sort missing reconciliation data by merchant.
  • Risk Profile: Fixed an issue where saving a risk rule without entering parameter values would result in a type error.
  • Risk Profile: Fixed an issue that would cause an error when opening risk rules if the risk rule set ID referenced a risk rule set that does not exist. A 404 error is now displayed instead.
  • Transaction Processing: Fixed an issue caused by the platform attempting to collect 3DS information for Apple Pay transactions. The system now checks whether a transaction uses Apple Pay before collecting additional 3DS information.
  • UI Navigation: The loading page displayed for the collectMissing3DSecureData connector configuration was only displayed in English. The page is now displayed in the language of the transaction where available, with English as the fallback language.

Adapters​

Changed​

  • American Express (AMX-EP1-AMX): Added a new gateway connector configuration option, "Force System Generated STAN". This option can be used to force the system trace audit number (stan) to be generated by the IXOPAY platform and stored in the additionalId1 field. The following options are available to determine the format of the STAN:
    • "Yes - Uppercase characters only"
    • "Yes - Upper- and lowercase characters".
  • Banca Intesa (BAI-EP1): If the PSP includes the TRACEID in a transaction response, it is now included in the postback.
  • Braintree (BRA-EP1-BLI): Added support for partial refunds for the Blik non-redirect payment method.
  • Braintree (BRA-EP1-PPE): Added support for line items and a corresponding option, includeLineItems has been added to the connector configuration.
  • dLocal (DLO-EP1-CC): The merchantTransactionId is now passed to the vault, in order to pass it on to the PSP in refund requests.
  • HypYaad (HYP): Removed the mapping of payment references in settlement files, as this could lead to a single settlement file being split into multiple settlements.
  • Mastercard Payment Gateway Services (MPG, BAMI): Added support for the scheme transaction ID.
  • Nexi Group (NETS-EP1): Added support for specifying the language in the checkout payload for transactions. This ensures that the language field is included in the payload if it is included in the transaction's extra data.
  • PayPal (PPA-EP1-PPE): Added the isFinalCapture flag for capture transactions. If set to true, the capture is marked as final on the PayPal side and no further captures are possible.
  • Simulator: Added support for incremental authorization for simulated credit card transactions.

Added​

  • WavePay (WAV): The WavePay push adapter allows cash collection payments to be pushed to the IXOPAY platform to ensure that these transactions are also available within the system.

Fixed​

  • Afterpay (AFT): Fixed an issue with retrieving the minimum/maximum price, caused by a missing interface.
  • American Express (AMX-EP1-AMX): Fixed an issue that would cause an error if settlement files are not formatted correctly.
  • Braintree (BRA): If rows in a settlement file did not include a settlement date, the settlement date was previously taken from the first value found in the "Settlement Date" column of the file. However, this could result in the settlement date being incorrect. The behavior has therefore been changed to set the settlement date to the transaction's disbursement date instead.
  • Braintree (BRA-EP1-PPE): The merchantAccountId is now only passed to Braintree's JavaScript SDK if a value is present.
  • iyzico (IYZ):
    • Fixed an issue with that would cause the batch number to be set to the entire file name of the settlement file, rather than the initial numerical portion of the file name. This was caused by empty rows in the settlement file.
    • Fixed an issue that would cause some settlement files to be parsed incorrectly.
  • Khipu (KHI): Fixed an issue with retrieving the bank list, caused by a missing interface.
  • Klarna (KLW): Fixed an issue that would result in the error "Invalid Response" being returned for transaction without a body. An empty body is now handled correctly, with the HTTP error code being checked prior to parsing the response.
  • Mashreq (MASH-EP01): Fixed an issue where the status of successful transactions was not set correctly due to the status in the response not being formatted as expected.
  • Payabl (P21): Fixed an issue caused by the error code parameter being evaluated incorrectly.
  • Paymee (PAYME-EP1-CCRD): Fixed an issue where refund amounts would be sent with a varying number of decimal places, which could sometimes lead to errors. Refund amounts are now formatted consistently.
  • Trustly (TRU): Fixed an issue that would cause a generic payment error if the private key required to generate the signature was missing. The system now checks for its presence.

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

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.