Payment Initiated
Called by the client immediately BEFORE it mounts the payment element.
This is what stops a re-prebook from stranding a payment. LiteAPI cannot return a transactionId once a new prebook has replaced it, and a booking stays prebooked right through payment — so without this stamp the backend has no way to distinguish "the user is still choosing" from "the user has paid and we must not touch the transaction id". A browser refresh on the checkout URL is enough to lose the money otherwise.
Deliberately idempotent and deliberately not a state machine: it only ever moves payment_status from unset to processing. The real payment status arrives later from LiteAPI at /book and must win.
Request
- Base URLhttps://stardrift.ai (the document declares no server; this is the origin it was published from)
- URLhttps://stardrift.ai/hotel-bookings/{booking_id}/payment-initiated
- Authnone declared
Path parameters
Response
Successful Response
Changes
No recorded changes to this operation across all 34 revisions of this API.