Skip to main content

Gateway — v25.16

Gateway API​

Fixed​

  • Provisioning API: Fix bug where an auto-generated shared secret on connector creation returned a value longer than the actual stored one.

Gateway Features​

Changed​

  • Risk Profile: Update Forter risk engine to use Dispute API (v10.1).
  • Risk Profile: Add configurable Forter risk engine 3DS recommendations with an option to adjust 3DS requirements for transactions based on those recommendations.

Added​

  • Fee Management: Add new fee constraint 3DS (options: any or inhouse) which allows setting fees based on the 3DS environment used for a transaction.
  • Fee Management: Improve the transactionSubType constraint by showing any as the default option.
  • Transaction Details: Add viewing of fraud tags in the Transaction Details page for merchant users. Enable with the frontend.transaction.tag.show permission. Admin users have the transaction.tag.show permission enabled by default.
  • Transaction List: Add the Advanced Filter with a simplified set of filter options for merchant users in the Transactions view. It can be enabled with the frontend.transaction.advanced-search permission.

Fixed​

  • Risk Profile: Fix an edge case where transaction risk data couldn't be stored.

Gateway Adapters​

Changed​

  • dLocal (DLO-EP1-VPAY): Enable V Pay for Paraguay.
  • JPMorganChase (CHA):
    • Add new setting to select report type: Funded Transaction Fee Details (FTI) or Settlement Details (PE).
    • Add new setting to specify settlement retrieval type: Polling-Based Retrieval or Notification-Based Retrieval.
  • Nuvei (NUV-EP1-PSE): Update documentation for payment method PSE.

Fixed​

  • JPMorganChase (CHA): Fix several issues with notification handling and settlement file retrieval.
  • MultiSafepay (MUL-EP1): Attempt to retrieve the scheme reference identifier from the initial MultiSafePay transaction if it was missing in order to facilitate recurring transactions.

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.