Stripe: Travel & Leisure Fraud Attempts Hit 4-Year High; Radar Blocks $3 Billion
Key point
Stripe data analysis reveals that fraud attempts in the travel and leisure industry reached a four-year high, with Radar blocking over $3 billion.
Details
According to Stripe's data analysis, fraud attempts against travel and leisure businesses reached a four-year high over the past year. The analysis covered over 200,000 active travel and leisure businesses on Stripe, noting an increase in new tactics such as booking hijacking, hotel impersonation, and phishing kits as a service. Advances in AI technology have enabled convincing fraud campaigns and the large-scale generation of synthetic identities, making detection more difficult.
Regional Fraud Trends and Radar's Performance
By region, fraud attempts surged more than five times year-over-year in APAC and EMEA, while LATAM saw a 37% increase. In contrast, North America was an exception, showing a decrease in fraud attempt rates. Stripe's AI-powered fraud prevention product, Radar, responded to these threats by blocking over $3 billion in suspicious fraudulent payments from travel and leisure merchants over the past year.
Key Fraud Types and Response Cases
Fraud in the travel industry occurs primarily in four areas. First, bookings and ancillary service purchases using stolen cards. Second, the abuse of promotional benefits through multi-account creation using bots. Third, post-trip disputes where refunds are attempted after service usage. Fourth, multi-account abuse via login signals.
In real-world cases, Radar's effectiveness was clear. Oasis Hotels in Mexico applied additional authentication when the booker's name did not match the cardholder's name via Radar, reducing the fraud dispute rate by 90% within six months. SiteMinder, a hotel commerce platform operating in 150 countries, reduced fraudulent payment volume by 61% and fraudulent bookings by 27% with Radar adoption. Early detection is a key strategy that significantly reduces principal losses and subsequent processing costs incurred after payment completion.
This summary was generated automatically by AI. Check the original for the author's claims and context. Copyright belongs to the original author.
Our guide explains how the AI works. Report summary errors, attribution issues, or removal requests via Contact.