PSD2 (Payment Services Directive 2)

Why it matters in travel

PSD2 affects travel-payment design across the UK and EU — when SCA applies, when exemptions can be used, how open-banking payments are presented, and where chargeback liability lands. Compliance is not optional and it changes how payment funnels are built.

For a UK or EU travel business, PSD2 is the regulatory backbone that decides which authentication exemptions are available, which open-banking flows are possible, and which payment data has to be shared with licensed third parties. The implementation choices made under PSD2 affect everything from conversion rate to chargeback liability to fee profile.

The travel businesses that engage with PSD2 proactively turn the regulation into commercial advantage — using open banking for cost savings, using authentication exemptions for conversion, using AISP data for reconciliation. The businesses that meet PSD2 only as a compliance burden miss the upside the regulation built in for businesses willing to use it.

How felloh helps

felloh handles PSD2 SCA, exemptions and open-banking flows inside the booking-level picture so travel businesses can meet the rules without rebuilding their payment stack for each market.

The pay checkout handles SCA exemptions correctly across markets, with the dashboard’s Transactions view recording the exemption claim, authentication method and outcome against the booking. Open-banking flows via Crezco and AISP-driven account information run through the same regulatory framework, with consent and authorisation evidence captured at each step.

For travel businesses operating across UK and EU markets, PSD2 stops being a per-market integration project. The exemption logic, the authentication flow and the open-banking consent management are all unified, and compliance evidence is part of the same booking record.