Card scheme_

Scheme rules shape what travel merchants actually experience: which surcharge models are allowed where, how chargeback reason codes apply to non-refundable bookings, what evidence representment needs, and how authentication liability shifts work. A scheme rule change can ripple through pricing, dispute defence and operational workflows.

A scheme update — a new chargeback monitoring threshold, a tightened representment evidence requirement, a reclassified MCC — can land with weeks of notice and force a travel business to restructure its dispute response, its pricing or its compliance evidence. The schemes do not coordinate updates with travel-business operating cycles.

The travel teams that keep up read scheme bulletins as part of operating rhythm, brief the dispute and operations teams in advance, and adjust booking-level evidence collection so the new requirements are met before they are needed. The teams that do not keep up discover the change retroactively, often after a chargeback they could have defended is lost.

felloh surfaces scheme-driven costs, dispute outcomes and authentication evidence at the booking level so travel teams can manage the impact of scheme rules without standing up bespoke reporting.

The Merchant Acquirer view in the dashboard breaks out scheme fees against bookings; Decline Analysis filters by scheme so policy changes show up as visible shifts. Risk Analysis and Chargebacks roll up the dispute picture by scheme so scheme-monitoring thresholds are tracked in real time rather than discovered when the acquirer calls.

For travel finance teams adjusting to scheme rule changes — a chargeback monitoring threshold tightening, an authentication exemption changing — the new requirements land in the same dashboard the operations team already uses. No bespoke rebuild, no parallel reporting layer.