Skip to content
Safety & Security

Passport-checked sellers. Encrypted payments. Payment held until the name change.

Every ticket is checked against its booking, and every seller's passport name must match it, before the ticket goes on sale.

01

Identity checked - every seller.

Every seller verifies a valid passport through Sumsub, and the name on it must match the name on the booking. The passport's name is kept on the account and cannot be changed.

  • ✓Passport check
  • ✓Name matched against the booking
  • ✓Expired passports cannot publish new tickets
Identity · Step 1
Passed
✓
Passport · checked
processed by Sumsub
✓
Name match
passport name = booking name
✓
Expiry
checked at every publish
02

Booking checked - every ticket.

Before a ticket goes on sale TKTZ retrieves the booking from the operator's system and checks it is confirmed, one-way, for one adult and leaves in time. Every ticket on sale is checked again every day.

  • ✓Booking retrieved from the operator's system
  • ✓Confirmed, one-way, one adult, leaves in time
  • ✓Every ticket on sale checked again every day
Booking check · Step 2
Daily
✓
Booking · retrieved
from the operator's system
✓
Rules · checked
confirmed · one-way · one adult
✓
Departure · in time
checked again every day
03

Seller paid after the name change.

When a ticket sells, TKTZ keeps the buyer's payment until the airline confirms the name change, then pays the seller's linked PayPal account. No wire transfers to chase. PCI-DSS-aligned end-to-end.

  • ✓Card data tokenised - TKTZ never sees the raw PAN
  • ✓Seller paid after the airline confirms the name change
  • ✓Buyer pays through one of our regulated partner gateways
Payment · Step 3
PCI-DSS
Payout destination
PayPal
the seller's linked PayPal account
Buyer pays through partner gateway
Ticket transferred to buyer
Seller paid to PayPal

Questions about security?

We answer security questions personally. Partners can request a full compliance brief on request.