A card-not-present (CNP) transaction is any card payment taken without the physical card being presented, including online purchases, phone bookings, payment links and email-based payments. CNP transactions are higher risk than chip-and-PIN because the merchant cannot rely on the card being physically inspected, so authentication, AVS and fraud checks carry more weight. CNP also carries more chargeback liability for the merchant in most scheme rules.
Travel payments glossary
Card-not-present (CNP) transaction
A card payment taken without the card being physically presented to the merchant.
Why it matters in travel
Most travel sales are card-not-present: customers book online, agents key in card details on the phone, deposits and balances are taken via emailed payment links. The CNP risk profile is the reason travel finance teams pay close attention to authentication, fraud signals and chargeback ratios — and why payment links with authentication evidence have largely replaced raw MOTO keying.
CNP transactions in travel carry higher chargeback liability and higher fraud risk than card-present transactions, which is why so much travel-payment design is really about turning CNP into something defensible. Authentication evidence, AVS results, CVC matches and behavioural signals all stack into the picture that decides whether a chargeback survives representment months later.
The travel businesses that handle CNP well treat every transaction as evidence to be preserved — every authentication, every signal, every booking event — so a dispute can be defended from the booking record. The businesses that do not treat CNP as evidence-led accept chargebacks they could have defended, because by the time the dispute arrives the underlying data is too fragmented to use.
How felloh helps
felloh treats CNP authentication, fraud signals and dispute history as part of the booking ledger, so the evidence the business may need to push back on a chargeback is available without rebuilding it from logs.
The Transactions view in the dashboard exposes CVC, AVS and 3DS outcomes against every CNP payment, and the Risk Analysis page surfaces the chargeback history at booking and portfolio level. Payment Links and the pay checkout move CNP card data through tokenised, hosted flows so the underlying card number never enters the operator’s environment.
For travel businesses where most sales are CNP, the practical effect is that representment goes from an investigation to a query. The evidence is preserved as routine, not assembled after the fact, so chargeback win rates reflect what actually happened rather than how well the operator scrambled for evidence.
Where this shows up in risk and disputes.
Card-not-present (CNP) transaction touches more than one workflow at felloh. Start with the pages most travel teams reach for next.
- Financial Control
Control refunds, exceptions, supplier exposure and payment risk against the same booking record.
Explore - Financial Protection Data
Authentication, settlement, protected funds and refund history kept with the booking for dispute defence.
Explore - Payment Optimisation
Acceptance, decline and authentication evidence so you can act on the patterns that matter.
Explore
More on payment risk and disputes.
Real-world context from the felloh team and customers, written for travel finance and operations.
UpdatesEnhance Your Payment Success with felloh's AI Decline Analysis for the Travel Industry
felloh's AI Decline Analysis surfaces real-time insight on why card payments fail and the best next step — for higher acceptance on travel bookings.
Read article
InsightsMinimising Payment Risks of phone payments: The Smart Way for Travel Merchants
Phone bookings are still essential in travel, but they carry payment-security risk. How to keep last-minute trips moving without exposing the business.
Read article
Connect the dots.
See how payments, settlement, refunds and reporting evidence connect around every booking.