Travel payments glossary

Fraud detection

The process of identifying potentially fraudulent payments before or shortly after authorisation.

Plain-English definition

Fraud detection is the process of identifying potentially fraudulent payments before or shortly after authorisation, usually using a mix of rules and machine-learning models. Signals include device, behaviour, BIN, velocity, geolocation, AVS, CVC and authentication results. The output is a decision to approve, challenge, hold for review, or decline.

Why it matters in travel

Travel fraud has its own patterns: card testing on low-value deposits, account-takeover on familiar brands, friendly fraud post-trip. A detection layer that does not know about booking context — deposit versus balance, agency versus consumer, departure date — will either miss real fraud or block legitimate customers.

A generic fraud engine does not know that a £30 booking on a popular OTA is being card-tested, or that a high-value balance paid two days before departure is normal travel behaviour. Without travel context, the engine over-blocks or under-blocks — and either failure shows up as direct financial cost. The teams that get this right give the engine the booking context to work with.

The travel businesses with mature fraud-detection programs read outcomes back into the engine continuously: which blocks were right, which were wrong, which approvals turned into chargebacks. The businesses that set rules once and never revisit them quietly drift out of step with the threat model as fraud patterns evolve.

How felloh helps

felloh surfaces fraud signals alongside booking context so the next decision is informed by the whole picture, not just the payment in isolation.

Connect the dots.

See how payments, settlement, refunds and reporting evidence connect around every booking.