Catch fraud before it becomes a chargeback
Fraud rules you can turn on, tune and own — across 3DS, card, customer, device, location and velocity signals, with every decision attached to the booking.
The challenge.
Travel is one of the most-targeted card-not-present categories. Bookings are high-value, the delivery window is long, the merchandise is liquid — and most fraud tools were not built for any of that.
Travel-specific fraud profile
High average values, long booking-to-travel windows, and routes that fraudsters cluster around. A generic fraud model is the wrong tool for the job.
Blanket rules cost real bookings
Tightening every dial blocks paying customers as well as fraud. Loosening them lets the chargeback ratio climb. Calibration is the work.
Generic processors leave you with the bill
When fraud lands, the chargeback is the merchant's problem — and the evidence to defend it has to be reconstructed under deadline. Most fraud rules sit too far from the booking record to help.
How Fraud Shield decides.
Each transaction runs through six categories of signal and the rules you have enabled. The outcome — allow, review or block — and the signals behind it are recorded against the booking so the decision can be defended later.
Gather the signals
3DS, card, customer, device, location and velocity in one picture.
Apply your rules
Turn on the rules that match your risk profile.
Decision and evidence
Allow, review or block — with the reasoning kept.
What you can configure.
Six signal categories, each carrying its own rule library, each rule individually switchable and tunable.
3DS
Decline-velocity thresholds, step-up triggers, authentication-outcome rules.
Card
BIN-level controls, issuer-country logic, card-type permissions.
Customer
Profile-based rules across new and returning customers.
Device
Device fingerprinting, proxy / VPN / Tor detection.
Location
Card-vs-IP geography, high-risk and medium-risk country lists, English-speaking allow lists.
Velocity
Limits per card, IP, device and email across configurable windows.
How felloh helps.
Fraud Shield runs inside the felloh payment flow rather than as a disconnected bolt-on, so every signal, rule and decision lives on the same booking-level ledger as the payment itself.
Fewer false positives
Rules tuned to your real customer profile, not a generic model.
Stronger representment
Authentication outcome and fraud signals already attached when a chargeback lands.
One picture, not two
Fraud, payment and reporting evidence all sit against the same booking record.
How travel businesses think about fraud.
See how this works around your bookings.
Bring one payment, reporting or cash-position problem. We will show how felloh connects the booking-level money trail behind it.
Book a walkthrough