Travel payments glossary

Tokenisation

Replacing card data with a non-sensitive token that can be used in its place.

Plain-English definition

Tokenisation is the practice of replacing sensitive card data with a non-sensitive token that can be used in its place for future transactions, while the underlying card number is held only in the secure vault of a tokenisation provider. Tokens can be merchant-specific, scheme-issued (network tokens), or wallet-based, and they significantly reduce PCI DSS scope for the merchant.

Why it matters in travel

Tokenisation is the foundation of reliable deposit-then-balance, instalment, recurring and on-tour payment models in travel. Without tokens, every later capture risks being blocked by an expired card or a changed account number; with tokens — especially network tokens that update automatically — capture rates stay high.

For a tour operator with six months between deposit and balance, tokenisation is what makes the balance capture actually work. Cards get reissued, accounts get closed, expiry dates roll over — and without network tokens that update automatically, the failure rate on balance captures climbs into the single-digit percentages on long-lead bookings. That is real revenue at the supplier-payment deadline.

Tokenisation also keeps PCI scope contained as the business grows. Every channel that touches the same token instead of the raw card number is a channel that does not enter the cardholder data environment. The cost of tokenisation per transaction is a fraction of the cost of carrying the scope it removes.

How felloh helps

felloh tokenises card data at the booking level so deferred capture, instalments and ad-hoc top-ups all work reliably without keeping raw card data inside travel-business systems.

Connect the dots.

See how payments, settlement, refunds and reporting evidence connect around every booking.