2 posts tagged with "Risk Engine"

Gateway API​

Fixed​

• Provisioning API: Fix an issue where the callback notification format 3-512 (JSON, SHA512-enforced) was rejected by createConnector and updateConnector requests.

Gateway Features​

Changed​

• Login: Improve error messages when adding a new multi-factor authentication method.

Added​

• Post Processing: Add a new settlement export column fees:vat:aggregation that aggregates all mapped provider VAT fees of a transaction into a single amount.

Removed​

• Network Tokenization: Remove Network Token Metadata field (to be re-introduced in a future release).

Fixed​

• Hosted Payment Pages: Fix an issue where selecting Set as preferred payment instrument did not mark the stored payment instrument as preferred in certain scenarios.
• Post Processing: Fix net and fees total amount calculations in CAMT.053 settlement exports for transactions in different currencies.
• Risk Engine: Fix an issue where the Riskified device fingerprinting script did not load for payment.js integrations.
• User Management: Fix an issue where the Invitations tab could fail to load for administrators with access to a large number of merchants.

Gateway Adapters​

Changed​

• Adyen (ADY-EP4): Add mapping of additional card data fields from webhooks for unknown transactions.
• dLocal (DLO-EP1-CC):
  • Add a new configuration setting Expose Installment Interest to include the installment interest amount in installment options responses.
  • Add a new configuration setting chargeArgentinaInUsd to process USD transactions for Argentina.
• EBANX (EBA-EP1-PIX,EBA-EP1-UPI): Add support for cancelling Pix Automático and UPI Autopay enrollments via Deregister transactions.
• EBANX (EBA-EP1-UPI): Add support for the new payment method UPI Autopay, including enrollment with an initial payment and recurring debits. UPI Autopay is a feature of India's Unified Payments Interface (UPI) that lets customers authorize automatic recurring debits from their UPI-linked bank accounts.
• NaverPay (NAV): Add support for automated settlement data retrieval and processing.
• Paynetics (PNE): Add support for the new settlement report flow covering posting, payout, and chargeback reports.
• Stripe (STRV2): Add an optional webhookSecret configuration setting to verify the signature of incoming webhooks.

Fixed​

• Adyen (ADY): Fix an issue where outgoing callback notifications for chargeback transactions contain the wrong adapter reference ID.
• Dimoco (DIM): Fix an issue where authorization rows with a matching transaction row caused duplicate reconciliation entries.
• dLocal (DLO-EP1-PIX): Fix an issue where enrollments (register) did not support both fixed and variable subscription amounts in all enrollment flows.
• PayPal (PPA):
  • Fix settlement report processing for refunds with currency conversion.
  • Fix an issue where settlement files without a bank reference ID could not be parsed.
• Redsys (RED-EP1-CC): Fix a 3DS issue where transactions failed with a repeated order number error when the 3DS method completion arrived after the challenge had started.
• Stripe (STRV2-EP2-ACH): Fix an issue with recurring debit transactions.
• VoltUnifiedGlobalPayments (VUGP): Fix an issue where callback notifications with an unexpected status format caused processing to fail.

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​

• 3DS: Rolled back changes that removed 3DS postback data for merchants using external MPI.
• Transaction details: The payment token is now included in the customer profile data in callbacks and API status calls.

Added​

• Post Processing: The filter in the Collect All Transactions (in period) Post Processing collecting step now supports filtering adapter errors and internal errors by the date on which their status changed.
• Provider settlements and Reconciliation: Added a new tab to the conversion rate system settings that allows deviation tolerances to be defined for currency pairs per tenant. This is then used to verify settlements rather than the tenant's global tolerance or default tolerance (0.02%).
• Settings: Added a new project setting, Postback: Include Basic Auth header, which allows a header to be sent for basic-auth postback. This setting is also available as a global connector setting.

Fixed​

• Account Updater: Fixed an issue where only one level of sub-tenants were filtered. Fixed an issue that would cause an error when changing the master tenant in the detailed view.
• Customer profile: Fixed an issue that triggered an error when creating a customer profile via the API's customerProfileData field without setting any customer data in the transaction.
• Pay-by-Link: Fixed an issue that would result in an empty redirect URL. Fixed an issue with redirects to expired pay-by-link transactions without an error URL that would cause an exception. The correct page is now displayed.
• Pay-by-Link: Fixed an issue that caused all pay-by-link transactions to be withRegister transactions. It is now possible to choose whether the transaction should be a withRegister transaction or not using the with Register (Store Payment Instrument for Card-on-File payments) checkbox.
• Post Processing: Fixed an issue that would cause an error for sub-tenants when attempting to select job configuration templates created at the parent provider level if no fee entities were available in the template.
• Risk Engine: Fixed an issue with the Count of different credit cards of same device risk rule if no customer or browser data is available.

Adapters​

Changed​

• checkout.com (CHE-EP1-CC): The AVS and CVV results are now added to the extraData in callbacks if available in the response.
• DPO Pay (PAYGA-PYGT-PMR): Added support for the USSD payment method.
• eMerchantPay (EME): Added support for chargeback reasons, which are now forwarded to merchants.
• Nuvei (NUV): Updated the Westpac settlement handling.
• Paysafecard (PSC): Added support for payouts.
• Redsys (RED-EP2-BIZ): Added support for refund transactions.

Added​

• Nuvei (NUV-EP1-CC): Added support for chargeback notifications from Nuvei.

Removed​

• Bank of America (BOFA-EP1-ACH): The Addenda row was removed from the NACHA file when using the WEB format, as it is not required.

Fixed​

• Nuvei (NUV-EP1-CC): Fixed issues with the references to related transactions, which should either contain the Nuvei transaction ID, the transaction ID of the previous 3DS request, or the transaction ID of the authorized payment.
• Nuvei (NUV): To handle issues with settlements, a new optional configuration setting has been added for the reconciliation data fetcher ID, which checks whether the system needs to wait for the CB report for the same date when retrieving settlements.
• PPRO (PPR-EP1): Fixed an issue with settlements, that is caused by PPRO sometimes providing multiple files with the initial file only containing volume data, and subsequent files containing the actual transaction settlement data. A new option is now available in the data fetcher configuration, Only retrieve settlements if all fees and volume files are present that checks whether all settlement files are present before retrieving and processing the files.
• Valitor (VALIT-EP1-CC): Fixed an issue related to duplicate transaction IDs issued by Valitor that would cause refunds to be ignored in settlements due to another transaction having the same ID.
• Volt (VOL-EP1): Fixed an issue with Volt settlement files caused by the formatting of the CSV data.

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.