Booking, Payment & Order Confirmation
Required order lifecycle, idempotency, cancellation, and confirmation rules.
Authoritative booking sequence
- Query product in real time for the actual stay dates, room count and guest composition.
- Trial booking to check availability and the latest price.
- Collect final guest/contact details, then repeat Trial booking with the actual booking payload immediately before submission.
- Create order with a unique
coOrderCodeonly if the second trial succeeds. - When local payment succeeds or confirmation is needed, call Pay order.
- Receive the signed order-status webhook; use Query order details only as a low-frequency recovery path.
What must be preserved
| Item | Reason |
|---|---|
coOrderCode | Your unique order ID for idempotency and reconciliation. |
fcOrderCode | G-Link/FCG order ID returned by the platform. |
| Product, price and policy returned by the final trial | The data used to create the order must match current availability. |
request_id, trace_id, idempotency_key | Required to diagnose uncertain writes safely. |
Payment and confirmation
Order creation does not equal hotel confirmation. After Pay order, wait for the order-status webhook. Status 3 means confirmed and 4 means rejected; cancellation result statuses are 6 and 7. Do not announce a confirmed hotel booking to the traveller before the confirmation event or authoritative order result is received.
Cancellation
Call Cancel order for customer-initiated cancellation or an unpaid order according to your policy. For an already-confirmed booking, the platform validates the supplier cancellation terms before returning the result.
Updated about 4 hours ago
Did this page help you?