3DS2 / 3D Secure 2

Why it matters in travel

Travel bookings are often high value and made across phone, web, agent screens and email links, so authentication needs to work without breaking the customer journey. A failed challenge mid-booking can lose a deposit, push the balance into manual chase work and create disputed-payment risk against a non-refundable supplier commitment. Done well, 3DS2 shifts chargeback liability away from the travel business while keeping cards behind authentication evidence the finance team can rely on at month end.

3DS2’s real win over 3DS1 is invisibility on low-risk transactions. A repeat customer paying a balance against a known booking should not have to authenticate at all — the data exchange behind the scenes can tell the issuer the transaction is safe, and the customer experiences a single click instead of an SMS code. That invisibility is what makes 3DS2 work for travel rather than against it.

The cost of 3DS2 done badly is conversion. A challenge presented as a redirect to an outdated branded form mid-booking will lose customers; the same challenge presented as a biometric prompt inside the customer’s banking app rarely does. Travel businesses that treat the authentication journey as part of the product experience capture more bookings than those that treat it as a compliance bolt-on.

How felloh helps

felloh keeps authentication, payment status and booking evidence connected, so finance and operations can see in one place whether a payment was authenticated, captured and matched to the right booking. When a challenge fails or a soft decline lands, the booking ledger surfaces it as an actionable exception rather than letting it disappear into an inbox.

In the felloh dashboard, the Transactions view records the 3DS outcome alongside the booking — authentication method, liability-shift status and the issuer that ultimately approved or challenged the payment. Decline Analysis groups failed authentications by issuer so you can see whether a particular bank is rejecting more than its share, and Risk Analysis rolls the picture up to portfolio level when chargebacks land.

The practical outcome is that the evidence to invoke a liability shift is already attached to the booking when a chargeback arrives. Representment becomes a query rather than an investigation, and the same authentication trail is available to customer support when a customer asks why their payment was challenged.