Overview

Creates a pending post-booking extra-charge batch for an existing flight booking and returns an opaque chargesId. When the batch is paid with TRANSACTION_ID, also creates a PaymentIntent (transactionId + secretKey) when usePaymentSdk is true.

Payment methods

• Credit-line booking — CREDIT (default) bills the credit line; TRANSACTION_ID creates a Stripe PaymentIntent so the passenger pays (requires usePaymentSdk: true)
• Stripe booking — TRANSACTION_ID (requires usePaymentSdk: true)
• WL / CMI booking — MANUAL (system admin / operations only): nothing is captured; support collects the payment outside LiteAPI and marks it paid with PUT /extra-charges/charges

The chosen method is returned in paymentTypes and recorded in chargesId.

Access

Requires Flights API access. Post-booking extra charges are not enabled by default — contact the LiteAPI support team to request access.

When to Use

• Attach fees after confirmation (seat change, baggage, admin adjustment)
• Obtain a Stripe client secret so the customer can confirm payment before POST .../extra-charges/charges

What You Get

• chargesId — Opaque token required by /extra-charges/charges (do not re-send charge lines)
• paymentTypes — The method chosen for this batch (CREDIT, TRANSACTION_ID or MANUAL)
• transactionId / secretKey — Present when the batch is paid with TRANSACTION_ID and usePaymentSdk is true
• Existing extras totals plus pending batch totals

Constraints

• Booking status must be CONFIRMED or PENDING_CONFIRMATION
• All lines in one request must share the same currency
• Payment method on /charges must match the method chosen here