Refund_

Travel refunds are operationally heavy because supplier payments may already have been made, protection regimes may apply, cancellation terms may limit what is refundable, and the customer expectation may not match the actual policy. Refund decisions made without booking-level context are how disputes start.

A refund in travel is rarely just a reversal — it is a decision about supplier exposure, protection treatment and customer relationship at the same time. A refund issued before the supplier has been billed is straightforward; one issued after is a recovery problem that may not resolve cleanly. Without booking-level context, the decision is made on a phone call and revisited in the dispute team three months later.

The travel businesses that handle refunds well have the supplier, protection and policy context attached to the booking, so the decision is consistent regardless of which agent the customer reaches. The businesses that handle them badly have inconsistent answers, recovery problems with suppliers, and a chargeback rate that surprises them.

felloh keeps refund requests, approval evidence, payment history and booking context connected for clearer financial control, so refund decisions are made on the same picture finance, operations and customer support are looking at.

The Refunds view in the dashboard enforces a two-stage authorisation flow — initiation by one user, approval by another — with the underlying booking, supplier-payment status and policy context surfaced inline. Audit captures who initiated and who approved, and the Transactions view ties the refund back to the original payment.

For travel businesses where refund decisions used to depend on which agent picked up the call, the policy now applies consistently. The same evidence supports the customer-support answer, the finance reconciliation and the dispute defence months later if a chargeback follows.