Travel payments glossary

Gateway timeout

When a payment gateway fails to respond within the expected time window during processing.

Plain-English definition

A gateway timeout is the situation where a payment gateway fails to respond within the expected time window during a transaction. The merchant system does not know whether the payment was approved, declined or never reached the acquirer. Handling timeouts safely requires idempotency keys, retry logic and reconciliation against the acquirer’s record so duplicates are not charged and successful payments are not lost.

Why it matters in travel

Gateway timeouts on a busy departure day, mid-campaign or during a flash sale can leave deposits in limbo — booked from the customer view but unrecorded from the merchant view. Resolving them by hand is operationally expensive and can lead to either duplicate charges or lost bookings.

A single gateway timeout on a £4,000 deposit is not a technical anomaly — it is a customer who is now uncertain whether they have booked a holiday. Without idempotent capture and reliable reconciliation against the acquirer record, the resolution often involves either charging the customer twice or losing the booking entirely, and either outcome usually surfaces as a complaint.

The travel businesses that survive their busiest day are the ones that designed the gateway-timeout case into the system from the start. Idempotency keys, retries, automatic reconciliation against acquirer state and clean customer messaging turn the case into an exception that resolves itself. Without those mechanics, a flash sale can produce more refunds than bookings.

How felloh helps

felloh handles timeout cases automatically with idempotent capture, retries and reconciliation against acquirer state, so the booking either settles cleanly or surfaces as a single, actionable exception.

Connect the dots.

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