Flix consolidates chargebacks onto Payrails, pulling disputes out of its PSP portals

Payrails and Flix announced on 12 August 2026 that Flix will run its payment disputes through Payrails Chargebacks, consolidating dispute handling across its payment stack instead of managing chargebacks separately in each payment service provider's portal. The product reviews transaction types and reason codes to assemble supporting evidence such as delivery confirmation and 3D Secure authentication records, presents chargeback volume in a dashboard that flags which disputes are worth contesting, and applies rules-based auto-refund logic to straightforward cases while routing complex disputes to shared queues with the transaction context attached.

Alexandru Dorobantu, head of payment ecosystem at Payrails, framed disputes as primarily an operations problem, particularly in travel; Krystyna Savotchenko, head of fraud prevention at Flix, cited faster response times, lower manual effort and revenue protection as the business scales. Travel merchants are the stated target case because high order values and long lead times between booking and travel leave dispute evidence scattered across several PSP portals under tight representment deadlines.

Payment orchestration was sold on routing and redundancy, and both have commoditised fast; what a multi-PSP merchant genuinely cannot solve on its own is the operational surface — reconciliation, reporting and disputes — that fragments once with every acquirer added. Winning the dispute layer at a merchant like Flix matters more than the revenue on it, because the module sits between the merchant and each acquirer's own dispute tooling and makes the orchestrator, not the acquirer, the system of record for chargebacks.

Travel is the sharpest version of the problem, with long gaps between authorisation and delivery, and it is a segment where European acquirers have historically defended share on service rather than price. For acquirers the read is that another piece of the merchant relationship moves up the stack to a vendor that is PSP-agnostic by design.

Whether Payrails names further enterprise travel accounts on the dispute module, whether acquirers respond by opening their own dispute APIs to orchestrators rather than losing the interface, and whether recovery-rate numbers are ever published against the manual baseline.

• thepaypers.com