Airlines & Hospitality
Build travel payment flows with booking context, authentication, capture, cancellation, refund, and reconciliation controls.
Airlines and hospitality businesses combine high-value purchases, future fulfillment, itinerary or reservation changes, multiple services, and complex cancellation and refund rules. DEUNA connects the payment lifecycle to the booking context required by supported providers and operations teams.
Choose the supported order context#
Use the Airline order model for supported airline-specific fields. For lodging or another travel product, use the common order fields and only supported merchant-defined metadata; the airline schema does not create a public hotel reservation schema.
Keep the reservation system as the source of truth for room, stay, guest, rate, cancellation, and fulfillment details that do not have a documented first-class DEUNA field. Send only the context required by the configured payment, risk, or reconciliation flow.
Design for delayed fulfillment#
- Preserve the booking or reservation reference through authorization, capture, change, cancellation, refund, and dispute.
- Confirm whether the provider supports delayed capture, incremental or partial operations, void, and the required travel payment method.
- Reconcile an uncertain operation before retrying or releasing reserved inventory.
- Keep passenger and guest data to the minimum required fields and approved retention period.
- Test schedule or reservation changes, no-show, partial use, cancellation window, refund, chargeback, and provider outage scenarios.
Continue with Airline payments and orders, Provider capabilities, and Webhooks.