Overview

Create a temporary hold on the selected tour slot and a Stripe PaymentIntent for checkout.

When to Use

• Checkout start — After the user picks option, slot, and participants from booking-options
• Payment setup — Obtain transactionId and secretKey for Stripe SDK confirmation
• Hold window — Reserve inventory for ~10 minutes before book

What You Get

• Checkout context — tourId, optionId, dateTime, language, participants, and pricing echoed back
• Provider refs — cartId, experienceBookingId, providerBookingId, status, reservationExpiresAt
• Stripe fields — transactionId, secretKey, paymentTypes: ["TRANSACTION_ID"]

Quick Start

POST the same selection used for display pricing from booking-options with usePaymentSdk: true. Confirm payment with Stripe, then call POST /experiences/bookings.

Error codes

Product-operation codes are listed below. Shared authentication/access/rate-limit middleware can return common codes such as 401, 40301 or 4290. HTTP status and error code are separate; do not parse message text.

For 72001, requested/expected are customer SELL totals; do not apply markup or FX again. Inspect the code on HTTP 400, 409 and 422. A generic no-money error must not open price-change consent.