2 posts tagged with "Alerts"

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 Settlements and Reconciliation: 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.

Features​

Changed​

• Connector Settings: Extend connector setting "Set Customer Identification if empty" with the "Pseudo Random" option, allowing for the generation of a random ID to be assigned as the customer identification when left empty.
• Multi-method connector: Redirect the customer to the appropriate URL when a redirect payment method is used without a payment template, preventing the "Unexpected redirect to payment page" error.
• Virtual Terminal: The delayed capture interval can be set in days to add more convenience for virtual terminal users.

Added​

• Fee Management: Add GST fee support in the fee engine. Configure and map the GST (a percentage of the surcharge fee) as a fee entity and include it in a connector's fee set.
• Post Processing Setting: Enable the "Reconciliation: Use reference merchant tx id for unknown transactions" setting for remote deregister and remote refund transactions.
• Job Configuration: Introduce the ability to split jobs by cardType.
• Provider Settlements and Reconciliation: Add the bank reference number as a new column in the "Recent Settlements" and "All Settlements" view, along with a filter option for bank reference number in the "All Settlements" view.
• User Management: Simplify admin user management by adding a new filter option in the "Tenant User" view to include sub-tenant users in your filter results.

Fixed​

• Alerts: Fix an issue causing resolved alerts to remain visible to users.
• Job Configuration: Fix job configuration setting "Display a negative total sum of the initial transaction amount plus fees" in order to handle negative net settlement refund amount.
• Risk Profile: Allow users with the permission riskcheck.riskruleset.edit to edit the score card for a risk profile, resolving the limitation of requiring riskcheck.riskruleset.archive permission.
• Transaction Details: Hide capture button for pre-authorize transactions that are already fully captured.

Adapters​

Changed​

• Adyen (Settlement): Add support for skipped settlement files.
• Adyen (ADY-EP3): Add metadata merchantTxId and additionalId1 to debit and preauthorize transactions.
• Bank of America (BOFA-EP1-ACH): Remove the redundant connector setting initialTransactionState.
• Braintree (BRA-EP2-AMX, BRA-EP2-CUP, BRA-EP2-DIN, BRA-EP2-DIS, BRA-EP2-JCB, BRA-EP2-MAS, and BRA-EP2-VIS): Add support for parsing the new disbursement settlement file format.
• Six (Settlement): Add configuration options for SFTP host and root directory.
• Straight2Bank Pay (STRAI-E01): Add a new connector configuration field, pspid, to enable PSP id overwriting for cases where clients receive this parameter from the PSP.
• Straight2Bank Pay (STRAI-E01): Add new transactional fee types, markup and markup_vat, to the SCB settlement handling.
• Valitor (VALIT-EP1): Improve handling of Valitor settlements for transactions with non-unique adapter transaction IDs or lifecycle transaction IDs.
• WorldPay (WOR-EP1-CAB): Add support for CB (Carte Bleu and Carte Bancaire).
• Worldline (ING-EP6): Improve settlement data handling by implementing the configuration option "Customized REGEX Pattern" in the Settlement Data Fetcher for better distinction.
• eMerchantPay (EME-EP3): Add the orgTerminal parameter received by postback to transactions for cases of missing responses due to time-outs.

Added​

• Adyen (ADY-EP3-AMX, ADY-EP3-CAB, ADY-EP3-CAR, ADY-EP3-CUP, ADY-EP3-DIN, ADY-EP3-DIS, ADY-EP3-ELO, ADY-EP3-HIC, ADY-EP3-JCB, ADY-EP3-MAS, ADY-EP3-TRO, and ADY-EP3-VIS): Add support for the incremental authorization transaction type in the Adyen Checkout service platform.
• PayU (PAU-E01): Added PayU Colombia.

Fixed​

• ATOM (ATOM-EP1-AMX, ATOM-EP1-DIN, ATOM-EP1-JCB, ATOM-EP1-MAS, ATOM-EP1-RUPAY, and ATOM-EP1-VIS): Fix settlement fee mapping to correct the net settlement amount calculation.
• First Atlantic Commerce (FAC-EP1-MAS and FAC-EP1-VIS): Refine adapter integration in combination with customer profiles to support follow-up transactions.
• Nuvei (NUV-EP1-AMX, NUV-EP1-CUP, NUV-EP1-DIN, NUV-EP1-MAS, and NUV-EP1-VIS): Fix issue causing follow-up void transactions to fail when the initial transactions experienced timeouts, that were later marked successful.
• PPRO (PPR-EP1): Ensure accurate handling of separate settlement files by eliminating unexpected NULL value for netSettlementAmount when only submitting a fee for a transaction without a net settlement amount.
• Worldline (ING-EP2-BTR): Fix failed refunds by adding the missing accountHolderName parameter.
• Worldline (ING-EP2): Improve refund processing by adding the iban parameter to the refund payload and enabling refund notifications.

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.