Payment API Guideline
Every product (hotel, flight, tour, attraction, transfer) is paid through the same
payment endpoint. Once a booking is confirmed you always continue with
/api/v1/unified-payment/request.
Payment Flow
Integration Flow
- Confirm the booking. The confirm response returns
invoice_no— keep it. - Call
/api/v1/unified-payment/requestwith thatinvoice_no. - Handle the response according to its
type(link,qr,prepayorform). - The gateway notifies our backend directly; you do not need to post the result to us.
- After the buyer returns to your site, read the final status with
/api/v1/unified-booking/result.
Important Notes
- The payment provider is not chosen at this step. It is fixed when the booking is
confirmed (
payment_methodin the checkout confirm payload) and is read back from the booking record here. - An unpaid booking is cancelled automatically after the hold window (30 minutes by default), so request payment right after confirming.
- Requesting payment again for the same booking is allowed while it is still unpaid — a new payment instruction is issued each time.