Gateway API​

Changed​

• Provisioning API: Update the business identification validation to accept Brazil's new alphanumeric CNPJ format.

Added​

• Transaction API: Add the adapterMerchantTransactionId field to record the PSP's merchant transaction identifier for transaction matching and reconciliation.

Gateway Features​

Changed​

• Post Processing Jobs: Add a preciseSettlementExchangeRate column with the unrounded settlement exchange rate to Write Customized Settlement CSV and Write Settlement CSV with Split Transaction Merchant.
• Post Processing Jobs: Add a Fee Conversion setting to Write Customized Settlement CSV that converts aggregated fee sums into the settlement currency, with matching currency columns for each fee aggregation.
• Risk Profile: Add support for reporting a specific cancellation reason to Riskified on void and refund requests.

Added​

• Audit Log: Add audit log entries for manually performed void, capture, and chargeback actions, including chargeback reversals.
• Connector Settings: Add a connector setting that lets you specify which customer fields are stored when a customer profile is created during transaction processing.
• Customer Profiles: Add support for sharing stored payment instruments with multi-method meta connectors and with wallet connectors using the same payment method.
• Risk Profile: Add a new risk rule that blocks payout transactions once their cumulative volume exceeds a configured daily, weekly, or monthly limit.
• Risk Profile: Add a per-rule setting to automatically void or refund a transaction that Riskified flags as declined, instead of requiring manual action.
• Transaction Details: Add the option to show which user manually created a transaction on the transaction detail page.

Fixed​

• Connector Configuration: Fix an issue where a connector's terminal could not be edited when the terminal ID contained special characters.
• Customer Profiles: Fix an issue where a deregister could point at the connector it was received on instead of the correct one.
• Fee Management: Fix an issue where gateway fees could display the wrong label.
• Post Processing Jobs: Fix an issue where SFTP export jobs rejected custom ports that were already approved for use.
• Risk Profile: Fix an issue where partial voids and partial refunds were reported to Forter as canceling the order instead of reflecting the remaining total.
• Risk Profile: Fix an issue where shipping cost data could be missing from Riskified risk checks run after the transaction was authorized.

Gateway Adapters​

Changed​

• checkout.com (CHE-EP2-CC): Add support for forwarding device fingerprint data via the extraData.device_session_id field for Debit, Preauthorize, and Register transactions.
• Dimoco (DIM): Add support for parsing Mastercard SAFE fraud advisory records from settlement files.
• Nuvei (NUV-EP1-WCP): Add an option to include additional customer details with WeChat Pay debit transactions.
• Worldline (ING): Add support for reading Visa TC40 fraud alerts from the daily fraud report file.

Added​

• Fiserv (FSV-EP1-CC): Fiserv Commerce Hub is a global payment processing platform from Fiserv, enabling secure Credit Card payments. The new adapter supports Debit, Preauthorize, Capture, Refund, and Register transaction types.

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 Features​

Changed​

• Data Export: Merge split payment data into the transaction's own row instead of writing a separate row per split.
• Transaction List: Show split payment details within the transaction's own row instead of separate rows.

Added​

• BI Data Source: Add the scheme lifecycle identifier and reference scheme lifecycle identifier as searchable fields in the Advanced Search.
• Risk Profile: Add Riskified's fraud decision result to the callback notification and transaction API response.

Fixed​

• 3-D Secure: Fix an issue where soft-decline 3-D Secure is not properly handled.
• Callback: Fix an issue where the chargeback amount in the callback notification was sent as a number instead of a string.
• Dashboard: Fix an issue where dashboard pivot table reports could return incomplete results.
• Hosted Payment Pages: Fix an issue where Content Security Policy headers could be added to Hosted Payment Pages responses for tenants that had not configured a policy.
• Provider Settlements and Reconciliation: Fix an issue where settlement amount calculations could use an imprecise exchange rate.
• Risk Profile: Fix an issue where item and browser data could be missing or incorrect in Riskified risk checks.
• Transaction List: Fix an issue where searching by Additional ID 1 or Additional ID 2 did not return matching transactions in the transaction list.

Gateway Adapters​

Changed​

• 2C2P (2C2P): Add an option to map the commission VAT amount as a dedicated commission-VAT fee instead of a scheme fee.
• checkout.com (CHE-EP2-CC): Add the Account Name Inquiry result to the callback notification for register transactions when enabled via the accountNameInquiryEnabled configuration.
• Dimoco (DIM): Add support for chargeback reversals.
• Klarna (KLW): Add a new data fetcher setting addNetSettlementAmountLineItem to enable actual-net-settlement-amount for settlements.
• Paynetics (PNE): Add support for CHB2 chargeback and reversal reconciliation, including RDR sub-type mapping.
• Stripe (STRV2-EP4-KBNPL): Add support for the new payment method Klarna. Klarna is a Swedish payment provider allowing customers to pay via invoice, direct debit, or installment-based financing at checkout.
• Worldpay (WOR-EP1-CC): Add support for the Mastercard Transaction Lifecycle Identifier (TLID) mandate for stored-credential transactions.

Added​

• du Pay (DUP): The du Pay push adapter allows cash deposits made at du Pay kiosks to be pushed to the IXOPAY platform, ensuring that these transactions are also available within the system.

Fixed​

• Dimoco (DIM): Fix an issue where chargeback settlements could be created from the wrong record.
• Stripe (STRV2): Fix an issue where StripeConnect platform credentials could fail to load.

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 API​

Fixed​

• Transaction API: Fix an issue where callback notifications for payments using an existing customer profile did not include the customerProfileData object.
• Transaction API: Fix processing error responses to include the transaction uuid and purchaseId, and the stored API response log entry to match the response sent.

Gateway Features​

Changed​

• Transaction Processing: Improve general error mapping for declines caused by deactivated network tokens for ISO adapters.

Added​

• Post Processing Jobs: Add an optional Account Name setting to the camt.053 settlement report exporter, used as a fallback when no merchant name is available.
• Risk Profile: Add the new external risk provider Riskified. Riskified is a real-time risk management solution that uses machine learning to detect fraudulent orders and protect against chargebacks.

Fixed​

• Hosted Payment Pages: Fix an issue where the payment form did not show an error message when tokenization failed.
• Transaction Details: Fix an issue where expanding the Transaction Tree panel could show a false session-expired message and reload the page.

Gateway Adapters​

Changed​

• Klarna (KLW): Add a line item with the actual net settlement amount of each payout to the retrieved settlement data.
• PayU (PAU-E01): Add support for card payments in seven additional LATAM markets: Argentina, Chile, Panama, Costa Rica, Guatemala, Honduras, and El Salvador.
• Stripe (STRV2): Add an optional connectedAccount setting to restrict the report to a single connected account.

Fixed​

• EBANX (EBA-EP1-PIX,EBA-EP1-UPI): Fix an issue where customers were not redirected back to the shop after completing a payment and status notifications were not received.
• Klarna (KLW): Fix issues where tokenization could fail and stored customer tokens could not be used for merchant-initiated transactions.
• Nuvei (NUV-EP1): Fix an issue where merchant-initiated preauthorize transactions using stored payment data could be declined.
• Stripe (STRV2): Fix an issue where the connected account payout reconciliation report could not be generated.
• Stripe (STRV2-EP2-ACH): Fix an issue where dispute notifications for ACH Direct Debit payments were not processed.

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

Gateway Features​

Changed​

• Post Processing Jobs: Add a credit card token type filter to Batch Less: Aggregate Transaction Values To Job Line Items strategy.
• Provisioning API: Add Network Token TRIDs to the listMerchants response.

Added​

• Hosted Payment Pages: Add possibility to manage and configure Content Security Policy (CSP) headers.
• Provider Settlement: Add automatic detection of second chargebacks when the first chargeback was already settled.
• Provisioning API: Add a new dedicated endpoint to configure and retrieve the multi-method routing configuration.

Fixed​

• Dashboard: Fix an issue where dropdowns in the dashboard did not work in Safari.
• Network Tokenization: Fix an issue where tokens stored during cross-merchant transactions with register were not marked active.
• Post processing: Fix the CAMT.053 settlement export to skip files with no reportable entries and to use fallback values for currency, account name, and booking date.
• Post processing: Fix the settlement net amount shown when the fee currency differs from the settlement currency.
• Provisioning API: Fix error responses to always return a consistent JSON format.

Gateway Adapters​

Changed​

• 2C2P (2C2P-EP1-CUP): Add UnionPay support as a dedicated UPOP payment method.
• 2C2P (2C2P-EP1-MACAU): Add support for the new payment method Macau Pass. Macau Pass is a widely used stored-value card and mobile payment service in Macau; customers complete the payment on a hosted page, with MOP as the supported currency.
• Adyen (ADY): Add support for handling chargebacks.
• Autopay (AUTO-EP1): Add handling of the scheme transaction identifier in callback notifications, storing it as the transaction's scheme reference.
• dLocal (DLO-EP1-CC): Add support for installments.
• EBANX (EBA): Improve callback notification and error handling for the Pix, Pix Automatico, and UPI payment methods with consistent status and error mapping.
• EBANX (EBA-EP1-PIX): Add support for the new payment method Pix. Pix is Brazil's instant payment system operated by the Central Bank of Brazil, allowing customers to pay in real time via QR code.
• NaverPay (NAV): Improve error mapping for failed transactions.
• Paynetics (PNE):
  • Add parsing of TRN2 transaction reports for reconciliation when the new report retrieval mode is enabled, replacing the legacy POF-based reconciliation.
  • Add support for chargeback handling.
• PayU (PAU): Add support for sending a merchant-provided tax amount with payment requests via a new configuration setting.

Fixed​

• Adyen (ADY): Fix callback handling for incremental authorizations.
• Adyen (ADY-EP2-SEP): Fixed an issue where recurring transaction were failing.
• EBANX (EBA-EP1): Fixed an issue where the adapter log captured the first partial refund ID instead of the current partial refund ID.

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.