Skip to main content

Gateway — v26.16

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.

Payments Intelligence — June-2026

IXOPAY Payments Intelligence​

Analytics​

Added​

  • Switch views in Analytics between PSP (original) values, PSP (unified/ mapped) values and enriched-BIN values

PSP and Partner Integrations​

Added​

  • TokenEx customers can now explore the Payments Intelligence solution with TokenEx demo data
  • Configure InterChange++ model for Stripe reports in Settings
  • Organization level API keys are now supported for Stripe connections for accounts that have multiple merchants under an organization
  • Organization level accounts are now supported for PayPal connections
  • Webhooks based tables are now supported in the Snowflake data sharing for Stripe connections

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.

Payments Intelligence — July-2026

IXOPAY Payments Intelligence​

IXO AI​

Added​

  • Search for detailed transaction events, chargebacks and fees with dynamic filters on key values, now through the IXO AI chat interface
  • Forecast KPI performances with IXO AI - view future performance of sales, authorization rates, fees and chargebacks basis 90-days historical data.

Changed​

  • IXO AI charts include a summary-title with clear reference to metrics visualized
  • Updated UI of IXO AI chat interface (thought-logs, source pills, landing page, starter prompts pills, and prompt field)

Snowflake Data Schema​

Added​

  • Users accessing Snowflake Data Schemas can view and query additional Stripe data-tables for checkout-sessions, account, credit_note, and payment-methods

User-Experience and Interface​

Changed​

  • Updated UI for Account Settings, Merchant Settings, Security in User profile
  • Updated User disclosures, AI Assistant disclosures and privacy guide
  • Updated UI for time-frame settings (including comparison with previous period) in Dashboard and Analytics pages
  • Rebranded MFA app to IXOPAY Payments Intelligence (formerly Congrify)
  • Updated UI for side-bar menu

Partner and PSP Integrations​

Fixed​

  • Enabled status view of TokenEx connection on Settings->PSP Connection, for existing TokenEx customers

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.

Payments Intelligence — August-2026

IXOPAY Payments Intelligence​

IXO AI​

Added​

  • Search for multiple Transaction and Payment Reference IDs through IXO AI and Transactions page filters
  • Search fee allocation rules applied and actual fee allocations on transaction-level, now through the IXO AI chat interface
  • Explore and analyse detected Anomalies on authorization rates, fees, chargebacks, sales, and refunds, now through the IXO AI chat interface
  • Discover customer-level KPIs (sales, fees and profitability, across PSPs for single customers) in a PII compliant manner
  • Monitor the ingestion status of PSP Reports processed in the IXOPAY Payments Intelligence platform, now through the IXO AI chat interface

Changed​

  • Explore detailed fee breakdowns, by scheme and interchange fee descriptors, now through the IXO AI chat interface.

Fixed​

  • Schedule analysis in IXO AI can be triggered on request in addition to the scheduled run (i.e. before the next scheduled time)

PSP Integrations and Onboarding​

Added​

  • USIO (PSP) integration enabled with USIO Payments 2.0 Web API
  • Detailed user-guide on onboarding as a new Customer and adding PSP Connections
  • Merchant Admins can request a custom PSP connection directly through the PSP Connections Settings, and share credentials securely on the IXOPAY platform
  • Create advanced JOINS across multiple PSP reports while mapping to unified reports

Changed​

  • Read clear instructions to go-live on the platform

Analytics and Platform​

Changed​

  • View share of Sales by percentage as per the dimension filters in the Fees section of Analytics
  • Extended time-frames for Ingestion Monitoring
  • Enabled download, filtering and adding dimensions in Analytics - Decline Retry Analysis section
  • Notifications for planned maintenance to the IXOPAY Payments Intelligence platform with affected time-windows

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 — v26.15

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.