@v-office/website-sdk 2.5.1 → 2.7.0

package/dist/cli.mjs

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import { Pt as defineWebsiteSDKOptions, t as createWebsiteSDK } from "./client-C5ojrNQA.mjs";
+import { Pt as defineWebsiteSDKOptions, t as createWebsiteSDK } from "./client-45_ofP_d.mjs";
 import { SearchSearchSortSchema } from "@v-office/sdk-core";
 import { Console, Effect, FileSystem, Layer, Option, Path, Schema, Stdio, Terminal } from "effect";
 import { Command, Flag } from "effect/unstable/cli";
@@ -16,7 +16,7 @@ var CLICheckFailed = class extends Error {
 const toCLIError = (message, cause) => cause instanceof Error ? new CLICheckFailed(`${message}: ${cause.message}`, { cause }) : new CLICheckFailed(message, { cause });
 //#endregion
 //#region package.json
-var version = "2.5.1";
+var version = "2.7.0";
 //#endregion
 //#region src/cli/output.ts
 const toJson = (value) => Effect.try({

package/dist/{client-C5ojrNQA.mjs → client-45_ofP_d.mjs}

@@ -21,7 +21,7 @@ const toV9Options = (options) => ({
 });
 const defineWebsiteSDKOptions = (options) => options;
 //#endregion
-//#region src/payment/submit-payment-option.ts
+//#region src/payment/browser.ts
 const getBrowser = () => Effect.gen(function* () {
 	const globals = globalThis;
 	if (globals.document === void 0 || globals.window === void 0) return yield* Effect.fail(new CoreSDKError({
@@ -40,6 +40,83 @@ const toPaymentSubmissionError = (cause) => cause instanceof CoreSDKError ? caus
 	message: "Payment submission failed.",
 	cause
 });
+//#endregion
+//#region src/payment/stripe-checkout.ts
+/**
+* vOffice `initStripePayment` returns only `sessionId` and `accountId`, never the
+* Checkout Session URL, so the session has to be opened with Stripe.js. Sessions are
+* created on connected accounts, which is why the platform publishable key is combined
+* with the reservation's `accountId`. Remove this module once vOffice returns the URL.
+*/
+const STRIPE_PUBLISHABLE_KEY_TEST = "pk_test_62sy8HrukNuTd7ko6lZcyJcv00CtNmm5oo";
+const STRIPE_PUBLISHABLE_KEY_LIVE = "pk_live_lHTr8iFxjPqtC0aYmkQYZuzZ00qtUAATYP";
+/**
+* Must stay the unversioned bundle. Stripe gates `redirectToCheckout` behind a per-version
+* feature flag that is on from the `clover` (2025-09-30) release train onwards, so pinning a
+* version such as `https://js.stripe.com/clover/stripe.js` makes the method throw on call.
+*/
+const STRIPE_JS_URL = "https://js.stripe.com/v3/";
+let stripeJs;
+const getStripeConstructor = () => globalThis.Stripe;
+const createStripeJsLoader = (document) => new Promise((resolve, reject) => {
+	const alreadyLoaded = getStripeConstructor();
+	if (alreadyLoaded !== void 0) {
+		resolve(alreadyLoaded);
+		return;
+	}
+	const script = document.createElement("script");
+	script.src = STRIPE_JS_URL;
+	script.async = true;
+	script.addEventListener("load", () => {
+		const loaded = getStripeConstructor();
+		if (loaded === void 0) {
+			reject(/* @__PURE__ */ new Error("Stripe.js was loaded but window.Stripe is unavailable."));
+			return;
+		}
+		resolve(loaded);
+	});
+	script.addEventListener("error", () => {
+		reject(/* @__PURE__ */ new Error("Could not load Stripe.js."));
+	});
+	document.head.appendChild(script);
+});
+const loadStripeJs = () => Effect.gen(function* () {
+	const { document } = yield* getBrowser();
+	const pending = stripeJs ?? createStripeJsLoader(document);
+	stripeJs = pending;
+	return yield* Effect.tapError(Effect.tryPromise({
+		try: () => pending,
+		catch: toPaymentSubmissionError
+	}), () => Effect.sync(() => {
+		if (stripeJs === pending) stripeJs = void 0;
+	}));
+});
+/** A `cs_test_` session can only be opened with the test key, `cs_live_` only with the live key. */
+const toPublishableKey = (sessionId) => sessionId.startsWith("cs_test_") ? STRIPE_PUBLISHABLE_KEY_TEST : STRIPE_PUBLISHABLE_KEY_LIVE;
+const redirectToStripeCheckout = ({ accountId, sessionId }) => Effect.gen(function* () {
+	const createStripe = yield* loadStripeJs();
+	const stripe = yield* Effect.try({
+		try: () => createStripe(toPublishableKey(sessionId), accountId === void 0 ? void 0 : { stripeAccount: accountId }),
+		catch: toPaymentSubmissionError
+	});
+	const redirectToCheckout = stripe.redirectToCheckout;
+	if (typeof redirectToCheckout !== "function") return yield* Effect.fail(new CoreSDKError({
+		source: "core",
+		operation: "paymentSubmission",
+		message: "This Stripe.js build no longer provides redirectToCheckout, so a Checkout Session cannot be opened from its session id. This payment option requires a checkout session URL from vOffice."
+	}));
+	const { error } = yield* Effect.tryPromise({
+		try: () => redirectToCheckout.call(stripe, { sessionId }),
+		catch: toPaymentSubmissionError
+	});
+	if (error !== void 0) return yield* Effect.fail(new CoreSDKError({
+		source: "core",
+		operation: "paymentSubmission",
+		message: error.message ?? "Stripe rejected the Checkout redirect."
+	}));
+});
+//#endregion
+//#region src/payment/submit-payment-option.ts
 const submitFormPost = (option) => Effect.gen(function* () {
 	const { document } = yield* getBrowser();
 	yield* Effect.try({
@@ -83,10 +160,14 @@ const submitPaymentOptionEffect = (option) => {
 		case "form_post": return submitFormPost(option);
 		case "stripe_checkout":
 			if (option.url !== void 0) return redirectTo(option.url);
+			if (option.sessionId !== void 0) return redirectToStripeCheckout({
+				...option.accountId === void 0 ? {} : { accountId: option.accountId },
+				sessionId: option.sessionId
+			});
 			return Effect.fail(new CoreSDKError({
 				source: "core",
 				operation: "paymentSubmission",
-				message: "Stripe Checkout requires a checkout session URL. The current payment option only contains session metadata."
+				message: "Stripe Checkout requires a checkout session URL or session id. The current payment option contains neither."
 			}));
 		default: {
 			const runtimeKind = option.kind;
@@ -4686,7 +4767,7 @@ const parseV9SearchCursor = (cursor) => Effect.gen(function* () {
 	return page;
 });
 const loadV9SearchRuntime = Effect.tryPromise({
-	try: () => import("./search-9yzAqHCg.mjs"),
+	try: () => import("./search-wcoZw2rt.mjs"),
 	catch: (cause) => new CoreSDKError({
 		source: "v10",
 		operation: "v9.search.runtime",

package/dist/index.mjs

@@ -1,4 +1,4 @@
-import { $ as SetupResponseSchema, A as ErgoPolicyNumberRequestSchema, At as selectInsurancePaymentEffect, B as QuotePricesResponseSchema, C as ErgoAddressSchema, Ct as getStartDateSelectedAvailabilityEffect, D as ErgoCreatePreContractRequestSchema, Dt as searchEffect, E as ErgoCommonFieldsSchema, Et as removeAdditionalServiceEffect, F as OnOfficeUnitSchema, G as RegionListResponseSchema, H as QuoteServiceSchema, I as PaymentScheduleItemSchema, J as ServiceBeonDataSchema, K as RoomImageSchema, L as PaymentScheduleSchema, M as ErgoTripAndCustomerRequestSchema, Mt as submitPaymentOption, N as FacilityListResponseSchema, Nt as submitPaymentOptionEffect, O as ErgoPersonSchema, Ot as selectCancellationPolicyEffect, P as OnOfficeUnitCollectionResponseSchema, Pt as defineWebsiteSDKOptions, Q as SetupDataSchema, R as QuoteLineSchema, S as DocumentTypeSchema, St as getRentalsEffect, T as ErgoBookRequestSchema, Tt as quoteEffect, U as RawObjectResponseSchema, V as QuoteSchema, W as RawVofficeObjectSchema, X as ServiceLimitSchema, Y as ServiceImageSchema, Z as ServiceListResponseSchema, _ as DocumentResourceResponseSchema, _t as bookInsuranceEffect, a as makeV0OpenApiClientFetchLive, at as UnitIdsResponseSchema, b as DocumentStatusUpdateRequestSchema, bt as getFiltersEffect, c as V1OpenApiClientError, ct as UnitOfferSchema, d as ApiEnvelopeBaseSchema, dt as V1_BASE_URL, et as TileCollectionResponseSchema, f as CalendarDaySchema, ft as V1_OPERATIONS, g as DocumentCollectionResponseSchema, gt as bookEffect, h as CustomerUnitSummarySchema, ht as addAdditionalServiceEffect, i as V0OpenApiClientError, it as TravelInsuranceBookingStoreRequestSchema, j as ErgoReadPreContractRequestSchema, jt as submitContactEffect, k as ErgoPlanSearchRequestSchema, kt as selectInsuranceEffect, l as makeV1OpenApiClientFetchLive, lt as UnitResponseSchema, m as CurrentMemberResponseSchema, mt as decodeV1OperationResponse, nt as TileTagSchema, o as makeV0OpenApiClientLive, ot as UnitListItemSchema, p as CalendarResponseSchema, pt as VideoResponseSchema, q as SearchPropertiesResponseSchema, r as V0OpenApiClient, rt as TravelInsuranceBookingSchema, s as V1OpenApiClient, st as UnitListResponseSchema, t as createWebsiteSDK, tt as TileSchema, u as makeV1OpenApiClientLive, ut as UnitServicePriceSchema, v as DocumentResourceSchema, vt as clearAdditionalServicesEffect, w as ErgoBankSchema, wt as getTermsAndPrivacyPolicyEffect, x as DocumentSummarySchema, xt as getInitialAvailabilityEffect, y as DocumentStatusSchema, yt as createInsurancePreContractEffect, z as QuotePricesPayloadSchema } from "./client-C5ojrNQA.mjs";
+import { $ as SetupResponseSchema, A as ErgoPolicyNumberRequestSchema, At as selectInsurancePaymentEffect, B as QuotePricesResponseSchema, C as ErgoAddressSchema, Ct as getStartDateSelectedAvailabilityEffect, D as ErgoCreatePreContractRequestSchema, Dt as searchEffect, E as ErgoCommonFieldsSchema, Et as removeAdditionalServiceEffect, F as OnOfficeUnitSchema, G as RegionListResponseSchema, H as QuoteServiceSchema, I as PaymentScheduleItemSchema, J as ServiceBeonDataSchema, K as RoomImageSchema, L as PaymentScheduleSchema, M as ErgoTripAndCustomerRequestSchema, Mt as submitPaymentOption, N as FacilityListResponseSchema, Nt as submitPaymentOptionEffect, O as ErgoPersonSchema, Ot as selectCancellationPolicyEffect, P as OnOfficeUnitCollectionResponseSchema, Pt as defineWebsiteSDKOptions, Q as SetupDataSchema, R as QuoteLineSchema, S as DocumentTypeSchema, St as getRentalsEffect, T as ErgoBookRequestSchema, Tt as quoteEffect, U as RawObjectResponseSchema, V as QuoteSchema, W as RawVofficeObjectSchema, X as ServiceLimitSchema, Y as ServiceImageSchema, Z as ServiceListResponseSchema, _ as DocumentResourceResponseSchema, _t as bookInsuranceEffect, a as makeV0OpenApiClientFetchLive, at as UnitIdsResponseSchema, b as DocumentStatusUpdateRequestSchema, bt as getFiltersEffect, c as V1OpenApiClientError, ct as UnitOfferSchema, d as ApiEnvelopeBaseSchema, dt as V1_BASE_URL, et as TileCollectionResponseSchema, f as CalendarDaySchema, ft as V1_OPERATIONS, g as DocumentCollectionResponseSchema, gt as bookEffect, h as CustomerUnitSummarySchema, ht as addAdditionalServiceEffect, i as V0OpenApiClientError, it as TravelInsuranceBookingStoreRequestSchema, j as ErgoReadPreContractRequestSchema, jt as submitContactEffect, k as ErgoPlanSearchRequestSchema, kt as selectInsuranceEffect, l as makeV1OpenApiClientFetchLive, lt as UnitResponseSchema, m as CurrentMemberResponseSchema, mt as decodeV1OperationResponse, nt as TileTagSchema, o as makeV0OpenApiClientLive, ot as UnitListItemSchema, p as CalendarResponseSchema, pt as VideoResponseSchema, q as SearchPropertiesResponseSchema, r as V0OpenApiClient, rt as TravelInsuranceBookingSchema, s as V1OpenApiClient, st as UnitListResponseSchema, t as createWebsiteSDK, tt as TileSchema, u as makeV1OpenApiClientLive, ut as UnitServicePriceSchema, v as DocumentResourceSchema, vt as clearAdditionalServicesEffect, w as ErgoBankSchema, wt as getTermsAndPrivacyPolicyEffect, x as DocumentSummarySchema, xt as getInitialAvailabilityEffect, y as DocumentStatusSchema, yt as createInsurancePreContractEffect, z as QuotePricesPayloadSchema } from "./client-45_ofP_d.mjs";
 import { AdditionalServiceLimitExceeded, CoreSDKError, CoreSDKError as CMSError, GuestQuoteSchema, InvalidAdditionalServiceQuantity, LocaleSchema, SearchSearchFieldOrderBySchema, SearchSearchFieldSortSchema, SearchSearchInputSchema, SearchSearchOutputSchema, SearchSearchPriceSortSchema, SearchSearchRandomSortSchema, SearchSearchRatingSortSchema, SearchSearchSortSchema, SearchSortDirectionSchema, UnknownAdditionalService, validateContactSubmitInput } from "@v-office/sdk-core";
 //#region codegen/v9/heuristic-generation/public-api.ts
 const customDataAttribute = (name) => name;

package/dist/instructions/CHANGELOG.md

@@ -4,6 +4,7 @@ This file is the versioned changelog index for the website SDK instructions.
 
 ## Versions
 
+- `versions/2.6.0/CHANGELOG.md`: `@v-office/website-sdk` 2.6.0 release notes.
 - `versions/2.5.0/CHANGELOG.md`: `@v-office/website-sdk` 2.5.0 release notes.
 - `versions/2.4.3/CHANGELOG.md`: `@v-office/website-sdk` 2.4.3 documentation release notes.
 - `versions/2.4.2/CHANGELOG.md`: `@v-office/website-sdk` 2.4.2 release notes.

package/dist/instructions/MIGRATION.md

@@ -4,6 +4,7 @@ This file is the versioned migration index for the website SDK instructions.
 
 ## Available Guides
 
+- `versions/2.6.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.5.x to 2.6.0.
 - `versions/2.5.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.4.3 to 2.5.0.
 - `versions/2.4.3/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.4.2 to 2.4.3.
 - `versions/2.4.2/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.4.1 to 2.4.2.

package/dist/instructions/README.md

@@ -1,6 +1,6 @@
 # Website SDK Instructions
 
-These instructions describe `@v-office/website-sdk` 2.5.0.
+These instructions describe `@v-office/website-sdk` 2.6.0.
 
 Use this directory as the consumer-facing reference for the package:
 
@@ -15,6 +15,7 @@ Use this directory as the consumer-facing reference for the package:
 - `document-structured-json.md`: `sdk.static.documents.getTermsAndPrivacyPolicy` and structured document JSON rendering rules.
 - `CHANGELOG.md`: versioned changelog index.
 - `MIGRATION.md`: versioned migration index.
+- `versions/2.6.0/`: 2.6.0 release notes and 2.5.x-to-2.6.0 migration guide.
 - `versions/2.5.0/`: 2.5.0 release notes and 2.4.3-to-2.5.0 migration guide.
 - `versions/2.4.3/`: 2.4.3 documentation release notes and migration guide.
 - `versions/2.4.2/`: 2.4.2 release notes and 2.4.1-to-2.4.2 migration guide.
@@ -68,4 +69,4 @@ website-sdk --backend v10 search --locale de-DE --query "adults=2"
 website-sdk --backend v10 search --locale de-DE --query "adults=2" --sort '{"by":"field","orderBy":{"label":"ASC"}}'
 ```
 
-Config file examples in these docs use the flat `WebsiteSDKConfig` shape introduced in 2.0.0 and kept in 2.5.0. v10 config additionally requires `searchEndpoint` as of 2.5.0.
+Config file examples in these docs use the flat `WebsiteSDKConfig` shape introduced in 2.0.0 and kept in 2.6.0. v10 config additionally requires `searchEndpoint` as of 2.5.0.

package/dist/instructions/booking.md

@@ -100,6 +100,13 @@ Sample:
           "provider": "adyen",
           "label": "Credit card",
           "url": "https://checkout.example.com"
+        },
+        {
+          "kind": "stripe_checkout",
+          "provider": "stripe",
+          "label": "Credit card",
+          "sessionId": "cs_live_a1Upmvi1v62AdILeDZl4l",
+          "accountId": "acct_1MpAB7AFrTg9gw7b"
         }
       ]
     }
@@ -113,13 +120,42 @@ Payment option variants:
 - `bank_transfer`: display-only payment details.
 - `redirect`: redirect the browser to the payment URL.
 - `form_post`: submit a generated HTML form, currently used for PayPal-style flows.
-- `stripe_checkout`: redirect to Stripe Checkout when a `url` is present.
+- `stripe_checkout`: open Stripe Checkout. Emitted on `v9` only.
+
+## Payment Submission
+
+Use `sdk.live.booking.submitPaymentOption(option)` or the top-level `submitPaymentOption(option)` export for every option except `bank_transfer`, which is display-only. Submission requires a browser environment and fails outside one.
+
+Render a button for every submittable option. Do not gate rendering on `url`: a `stripe_checkout` option is submittable as soon as it carries a `sessionId`.
+
+Stripe Checkout is opened one of two ways:
+
+- When the option has a `url`, the browser is redirected to it.
+- Otherwise the SDK loads Stripe.js from `https://js.stripe.com/v3/` and opens the session with `sessionId`, passing `accountId` as the connected account. The vOffice platform publishable keys are built in, and test (`cs_test_`) and live (`cs_live_`) sessions are handled automatically, so Stripe needs no configuration.
+
+Stripe.js is fetched on first use and reused afterwards, and an existing `window.Stripe` instance is reused when the page already provides one. A failed load is retried by the next submission instead of being remembered, so a guest can retry a Stripe payment without reloading the page. Sites with a Content-Security-Policy must allow `script-src https://js.stripe.com` and `frame-src https://js.stripe.com https://hooks.stripe.com`.
+
+Booking creation and payment are separate steps. When a payment option is on screen the reservation already exists, so present a submission failure as an unpaid booking rather than a failed booking:
+
+```ts
+try {
+  await sdk.live.booking.submitPaymentOption(option);
+} catch (error) {
+  showPaymentFailure({ bookingNumber: booking.bookingNumber, error });
+}
+```
+
+## Payment Return
+
+Online payment providers return the guest to a URL derived from `relativeRedirectUrl`. Stripe returns to that path with `payment=stripe&success=true` after payment and `payment=stripe&cancel=true` after cancellation, so the path must exist in your site and should read those query parameters.
+
+`relativeRedirectUrl` is supplied before the reservation exists, so the return URL cannot carry the booking number or guest token. Persist whatever the return page needs, for example in `sessionStorage`, before submitting a payment option.
 
-Use `sdk.live.booking.submitPaymentOption(option)` or the top-level `submitPaymentOption(option)` export for non-bank-transfer payment options in a browser environment.
+A successful return means the provider sent the browser back, not that the payment has settled. Confirmation reaches vOffice through the provider's webhook.
 
 ## Configuration
 
-Booking requests are rate-limited to one backend request per second with a queue size of five. `v9` books through the v0 `book` action and can initialize Stripe payment data. `v10` books through GraphQL and initializes Adyen redirect payment options.
+Booking requests are rate-limited to one backend request per second with a queue size of five. `v9` books through the v0 `book` action and initializes one Stripe Checkout Session per payment schedule option when the property has Stripe enabled. `v10` books through GraphQL and initializes Adyen redirect payment options.
 
 ## CLI Usage
 

package/dist/instructions/versions/2.6.0/CHANGELOG.md

@@ -0,0 +1,28 @@
+# Changelog: 2.6.0
+
+Release date: 2026-07-27
+
+This release makes v9 `stripe_checkout` payment options submittable. The vOffice `initStripePayment` action returns only session metadata, so `submitPaymentOption` now opens the Checkout Session with Stripe.js when the backend omits the session URL. Config, service calls, and output types are unchanged.
+
+## Added
+
+- `submitPaymentOption` and `submitPaymentOptionEffect` now complete `stripe_checkout` options that carry only `sessionId` and `accountId`. Previously these options failed with "Stripe Checkout requires a checkout session URL".
+- Stripe.js is loaded from `https://js.stripe.com/v3/` on first use and reused for later submissions. A failed load is not kept, so the next submission retries it. An existing `window.Stripe` instance is used when the page already provides one, so no second script tag is added.
+- The vOffice Stripe platform publishable keys are embedded in the SDK. Stripe Checkout requires no consumer configuration.
+
+## Changed
+
+- `stripe_checkout` submission prefers the Checkout Session `url` and only falls back to Stripe.js when it is absent. Once vOffice returns the URL, the SDK uses it without a further release.
+- The publishable key is selected from the session id, so tenants in Stripe test mode (`cs_test_`) and live mode (`cs_live_`) both work without configuration or environment detection.
+- Stripe sessions are created on connected accounts, so the option's `accountId` is passed to Stripe.js as `stripeAccount`.
+- The failure raised when a `stripe_checkout` option carries neither a URL nor a session id now names both.
+- Browser access helpers used by payment submission moved into an internal module shared by redirect, form-post, and Stripe submission. This is internal only and does not change the public API.
+
+## Migration Impact
+
+- Consumers that hid Stripe payment options because `url` was missing can render them again. Gate the button on the option being present rather than on `option.url`. See `versions/2.6.0/MIGRATION.md`.
+- Sites with a Content-Security-Policy must allow `script-src https://js.stripe.com` and `frame-src https://js.stripe.com https://hooks.stripe.com`.
+- Payment submission remains browser-only and still fails outside a browser environment.
+- Stripe.js is fetched at submission time, so payment submission can now fail from a blocked or unavailable third-party script. Treat that as a payment failure, never as a booking failure: the reservation already exists when payment options are shown.
+- No config, option, or output type changes. v10 Adyen `redirect` flows and all `bank_transfer` and `form_post` flows are unaffected.
+- Stripe removed `redirectToCheckout` from its versioned Stripe.js release trains (`clover`, 2025-09-30, and later) and from the published `stripe-js` types. The method is still implemented in the unversioned `https://js.stripe.com/v3/` bundle that the SDK loads, which is why this fallback works. It is a bridge until vOffice returns the session URL and is expected to be removed afterwards. Should a future Stripe.js build drop the method entirely, submission fails with a message naming the missing session URL.

package/dist/instructions/versions/2.6.0/MIGRATION.md

@@ -0,0 +1,74 @@
+# Migration: 2.5.x to 2.6.0
+
+This guide covers upgrading `@v-office/website-sdk` from 2.5.0 or 2.5.1 to 2.6.0.
+
+2.6.0 changes no config, no service call, and no output type. The only change is that `stripe_checkout` payment options can now be submitted on the v9 backend. If your site does not offer Stripe, upgrading requires no work at all.
+
+## What Changed
+
+vOffice's `initStripePayment` action returns only `sessionId` and `accountId`, never the Checkout Session URL. Because `submitPaymentOption` redirected exclusively to a session URL, Stripe payment options could never be completed and failed with "Stripe Checkout requires a checkout session URL".
+
+2.6.0 keeps the URL redirect as the preferred path and adds a fallback: when a `stripe_checkout` option has a `sessionId` but no `url`, the SDK loads Stripe.js and opens the Checkout Session with it. This is the same mechanism the classic non-SDK vOffice websites use.
+
+The fallback is self-retiring. When vOffice starts returning the session URL, the option gains a `url`, the URL redirect wins, and Stripe.js is never loaded. No SDK release is needed for that transition.
+
+## Remove Stripe Workarounds
+
+Sites that hid the Stripe button because no URL was present should now render it. Gate on the option existing rather than on `option.url`:
+
+```ts
+// Before: Stripe options were unusable, so they had to be hidden
+const payable = option.kind !== "stripe_checkout" || option.url !== undefined;
+
+// After: every submittable option can be submitted
+const payable = true;
+```
+
+Sites that implemented their own Stripe.js bridge with a publishable key can delete it, along with the key configuration. The SDK carries the vOffice platform keys and selects between test and live based on the session id, so a tenant in Stripe test mode and a tenant in live mode both work from the same build.
+
+## Content-Security-Policy
+
+Stripe.js is fetched from Stripe at submission time. If your site sets a CSP, allow:
+
+```
+script-src  https://js.stripe.com
+frame-src   https://js.stripe.com https://hooks.stripe.com
+```
+
+Without these directives the script is blocked and Stripe submission fails. Other payment kinds are unaffected.
+
+## Error Handling
+
+Payment submission can now fail for new reasons: Stripe.js could not be loaded, the loaded Stripe.js build does not provide the Checkout redirect, or Stripe rejected the redirect. All surface as a `CoreSDKError` with `operation: "paymentSubmission"`, the same as existing submission failures.
+
+Offering a retry is worthwhile for these failures. A failed Stripe.js load is not remembered, so the next submission fetches the script again and can succeed without a page reload.
+
+The booking already exists by the time payment options are rendered, so a submission failure must never be presented as a failed booking:
+
+```ts
+try {
+  await sdk.live.booking.submitPaymentOption(option);
+} catch (error) {
+  // The reservation is created. Show the booking number and offer bank transfer.
+  showPaymentFailure({ bookingNumber: booking.bookingNumber, error });
+}
+```
+
+Submission is still browser-only and fails outside a browser environment, unchanged from earlier versions.
+
+## Payment Return
+
+Unchanged from earlier versions, but worth confirming while testing Stripe end to end. The SDK derives the Stripe success and cancel URLs from the `relativeRedirectUrl` passed to `sdk.live.booking.book(...)` and appends `payment=stripe&success=true` or `payment=stripe&cancel=true`. That path must exist in your site and should read those query parameters.
+
+Note that `relativeRedirectUrl` is supplied before the reservation exists, so the return URL cannot contain the booking number or guest token. Persist anything the return page needs, for example in `sessionStorage`, before submitting the payment option.
+
+A `success=true` return means Stripe sent the browser back, not that payment has settled. Payment confirmation reaches vOffice through Stripe's webhook.
+
+## Recommended Steps
+
+1. Upgrade to `@v-office/website-sdk` 2.6.0.
+2. Remove any conditional that hides Stripe payment options when `option.url` is missing.
+3. Remove a site-level Stripe.js bridge and its publishable key configuration if you added one.
+4. Add the Stripe CSP directives if your site sets a Content-Security-Policy.
+5. Confirm payment submission errors are presented as payment failures with the booking number, not as booking failures.
+6. Smoke-test one booking against a Stripe test tenant and one against a live tenant, checking that Checkout opens and that the configured return path handles both `success=true` and `cancel=true`.

package/dist/{search-9yzAqHCg.mjs → search-wcoZw2rt.mjs}

@@ -1,4 +1,4 @@
-import { n as stable_filters_default } from "./client-C5ojrNQA.mjs";
+import { n as stable_filters_default } from "./client-45_ofP_d.mjs";
 import { a as searchQuery, c as VofficeUnitDataFieldSchemas, m as parseVofficeUnitData, n as toImages, r as toAddress, t as toRentalHighlights } from "./to-rental-highlights-CxWlq76f.mjs";
 import { CoreSDKError, STABLE_SEARCH_INPUTS, collectQueryParameters, daysBetweenLocalDates, expandCustomAttributeFilterCompositions, parseChildrenAges, parseOccupancyCount, parseQueryParameters, toCustomAttributeFilterLabel, toFormattedSearchPrice, toIsoDateFromPeriodQueryDate, toQueryString, toStableSearchInputBackendQueryKeys, toStableSearchInputParameterValues, toStableSearchInputQueryKeys, toUnusedFilterKeys } from "@v-office/sdk-core";
 import { Effect } from "effect";

package/instructions/CHANGELOG.md

@@ -4,6 +4,7 @@ This file is the versioned changelog index for the website SDK instructions.
 
 ## Versions
 
+- `versions/2.6.0/CHANGELOG.md`: `@v-office/website-sdk` 2.6.0 release notes.
 - `versions/2.5.0/CHANGELOG.md`: `@v-office/website-sdk` 2.5.0 release notes.
 - `versions/2.4.3/CHANGELOG.md`: `@v-office/website-sdk` 2.4.3 documentation release notes.
 - `versions/2.4.2/CHANGELOG.md`: `@v-office/website-sdk` 2.4.2 release notes.

package/instructions/MIGRATION.md

@@ -4,6 +4,7 @@ This file is the versioned migration index for the website SDK instructions.
 
 ## Available Guides
 
+- `versions/2.6.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.5.x to 2.6.0.
 - `versions/2.5.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.4.3 to 2.5.0.
 - `versions/2.4.3/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.4.2 to 2.4.3.
 - `versions/2.4.2/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.4.1 to 2.4.2.

package/instructions/README.md

@@ -1,6 +1,6 @@
 # Website SDK Instructions
 
-These instructions describe `@v-office/website-sdk` 2.5.0.
+These instructions describe `@v-office/website-sdk` 2.6.0.
 
 Use this directory as the consumer-facing reference for the package:
 
@@ -15,6 +15,7 @@ Use this directory as the consumer-facing reference for the package:
 - `document-structured-json.md`: `sdk.static.documents.getTermsAndPrivacyPolicy` and structured document JSON rendering rules.
 - `CHANGELOG.md`: versioned changelog index.
 - `MIGRATION.md`: versioned migration index.
+- `versions/2.6.0/`: 2.6.0 release notes and 2.5.x-to-2.6.0 migration guide.
 - `versions/2.5.0/`: 2.5.0 release notes and 2.4.3-to-2.5.0 migration guide.
 - `versions/2.4.3/`: 2.4.3 documentation release notes and migration guide.
 - `versions/2.4.2/`: 2.4.2 release notes and 2.4.1-to-2.4.2 migration guide.
@@ -68,4 +69,4 @@ website-sdk --backend v10 search --locale de-DE --query "adults=2"
 website-sdk --backend v10 search --locale de-DE --query "adults=2" --sort '{"by":"field","orderBy":{"label":"ASC"}}'
 ```
 
-Config file examples in these docs use the flat `WebsiteSDKConfig` shape introduced in 2.0.0 and kept in 2.5.0. v10 config additionally requires `searchEndpoint` as of 2.5.0.
+Config file examples in these docs use the flat `WebsiteSDKConfig` shape introduced in 2.0.0 and kept in 2.6.0. v10 config additionally requires `searchEndpoint` as of 2.5.0.

package/instructions/booking.md

@@ -100,6 +100,13 @@ Sample:
           "provider": "adyen",
           "label": "Credit card",
           "url": "https://checkout.example.com"
+        },
+        {
+          "kind": "stripe_checkout",
+          "provider": "stripe",
+          "label": "Credit card",
+          "sessionId": "cs_live_a1Upmvi1v62AdILeDZl4l",
+          "accountId": "acct_1MpAB7AFrTg9gw7b"
         }
       ]
     }
@@ -113,13 +120,42 @@ Payment option variants:
 - `bank_transfer`: display-only payment details.
 - `redirect`: redirect the browser to the payment URL.
 - `form_post`: submit a generated HTML form, currently used for PayPal-style flows.
-- `stripe_checkout`: redirect to Stripe Checkout when a `url` is present.
+- `stripe_checkout`: open Stripe Checkout. Emitted on `v9` only.
+
+## Payment Submission
+
+Use `sdk.live.booking.submitPaymentOption(option)` or the top-level `submitPaymentOption(option)` export for every option except `bank_transfer`, which is display-only. Submission requires a browser environment and fails outside one.
+
+Render a button for every submittable option. Do not gate rendering on `url`: a `stripe_checkout` option is submittable as soon as it carries a `sessionId`.
+
+Stripe Checkout is opened one of two ways:
+
+- When the option has a `url`, the browser is redirected to it.
+- Otherwise the SDK loads Stripe.js from `https://js.stripe.com/v3/` and opens the session with `sessionId`, passing `accountId` as the connected account. The vOffice platform publishable keys are built in, and test (`cs_test_`) and live (`cs_live_`) sessions are handled automatically, so Stripe needs no configuration.
+
+Stripe.js is fetched on first use and reused afterwards, and an existing `window.Stripe` instance is reused when the page already provides one. A failed load is retried by the next submission instead of being remembered, so a guest can retry a Stripe payment without reloading the page. Sites with a Content-Security-Policy must allow `script-src https://js.stripe.com` and `frame-src https://js.stripe.com https://hooks.stripe.com`.
+
+Booking creation and payment are separate steps. When a payment option is on screen the reservation already exists, so present a submission failure as an unpaid booking rather than a failed booking:
+
+```ts
+try {
+  await sdk.live.booking.submitPaymentOption(option);
+} catch (error) {
+  showPaymentFailure({ bookingNumber: booking.bookingNumber, error });
+}
+```
+
+## Payment Return
+
+Online payment providers return the guest to a URL derived from `relativeRedirectUrl`. Stripe returns to that path with `payment=stripe&success=true` after payment and `payment=stripe&cancel=true` after cancellation, so the path must exist in your site and should read those query parameters.
+
+`relativeRedirectUrl` is supplied before the reservation exists, so the return URL cannot carry the booking number or guest token. Persist whatever the return page needs, for example in `sessionStorage`, before submitting a payment option.
 
-Use `sdk.live.booking.submitPaymentOption(option)` or the top-level `submitPaymentOption(option)` export for non-bank-transfer payment options in a browser environment.
+A successful return means the provider sent the browser back, not that the payment has settled. Confirmation reaches vOffice through the provider's webhook.
 
 ## Configuration
 
-Booking requests are rate-limited to one backend request per second with a queue size of five. `v9` books through the v0 `book` action and can initialize Stripe payment data. `v10` books through GraphQL and initializes Adyen redirect payment options.
+Booking requests are rate-limited to one backend request per second with a queue size of five. `v9` books through the v0 `book` action and initializes one Stripe Checkout Session per payment schedule option when the property has Stripe enabled. `v10` books through GraphQL and initializes Adyen redirect payment options.
 
 ## CLI Usage
 

package/instructions/versions/2.6.0/CHANGELOG.md

@@ -0,0 +1,28 @@
+# Changelog: 2.6.0
+
+Release date: 2026-07-27
+
+This release makes v9 `stripe_checkout` payment options submittable. The vOffice `initStripePayment` action returns only session metadata, so `submitPaymentOption` now opens the Checkout Session with Stripe.js when the backend omits the session URL. Config, service calls, and output types are unchanged.
+
+## Added
+
+- `submitPaymentOption` and `submitPaymentOptionEffect` now complete `stripe_checkout` options that carry only `sessionId` and `accountId`. Previously these options failed with "Stripe Checkout requires a checkout session URL".
+- Stripe.js is loaded from `https://js.stripe.com/v3/` on first use and reused for later submissions. A failed load is not kept, so the next submission retries it. An existing `window.Stripe` instance is used when the page already provides one, so no second script tag is added.
+- The vOffice Stripe platform publishable keys are embedded in the SDK. Stripe Checkout requires no consumer configuration.
+
+## Changed
+
+- `stripe_checkout` submission prefers the Checkout Session `url` and only falls back to Stripe.js when it is absent. Once vOffice returns the URL, the SDK uses it without a further release.
+- The publishable key is selected from the session id, so tenants in Stripe test mode (`cs_test_`) and live mode (`cs_live_`) both work without configuration or environment detection.
+- Stripe sessions are created on connected accounts, so the option's `accountId` is passed to Stripe.js as `stripeAccount`.
+- The failure raised when a `stripe_checkout` option carries neither a URL nor a session id now names both.
+- Browser access helpers used by payment submission moved into an internal module shared by redirect, form-post, and Stripe submission. This is internal only and does not change the public API.
+
+## Migration Impact
+
+- Consumers that hid Stripe payment options because `url` was missing can render them again. Gate the button on the option being present rather than on `option.url`. See `versions/2.6.0/MIGRATION.md`.
+- Sites with a Content-Security-Policy must allow `script-src https://js.stripe.com` and `frame-src https://js.stripe.com https://hooks.stripe.com`.
+- Payment submission remains browser-only and still fails outside a browser environment.
+- Stripe.js is fetched at submission time, so payment submission can now fail from a blocked or unavailable third-party script. Treat that as a payment failure, never as a booking failure: the reservation already exists when payment options are shown.
+- No config, option, or output type changes. v10 Adyen `redirect` flows and all `bank_transfer` and `form_post` flows are unaffected.
+- Stripe removed `redirectToCheckout` from its versioned Stripe.js release trains (`clover`, 2025-09-30, and later) and from the published `stripe-js` types. The method is still implemented in the unversioned `https://js.stripe.com/v3/` bundle that the SDK loads, which is why this fallback works. It is a bridge until vOffice returns the session URL and is expected to be removed afterwards. Should a future Stripe.js build drop the method entirely, submission fails with a message naming the missing session URL.

package/instructions/versions/2.6.0/MIGRATION.md

@@ -0,0 +1,74 @@
+# Migration: 2.5.x to 2.6.0
+
+This guide covers upgrading `@v-office/website-sdk` from 2.5.0 or 2.5.1 to 2.6.0.
+
+2.6.0 changes no config, no service call, and no output type. The only change is that `stripe_checkout` payment options can now be submitted on the v9 backend. If your site does not offer Stripe, upgrading requires no work at all.
+
+## What Changed
+
+vOffice's `initStripePayment` action returns only `sessionId` and `accountId`, never the Checkout Session URL. Because `submitPaymentOption` redirected exclusively to a session URL, Stripe payment options could never be completed and failed with "Stripe Checkout requires a checkout session URL".
+
+2.6.0 keeps the URL redirect as the preferred path and adds a fallback: when a `stripe_checkout` option has a `sessionId` but no `url`, the SDK loads Stripe.js and opens the Checkout Session with it. This is the same mechanism the classic non-SDK vOffice websites use.
+
+The fallback is self-retiring. When vOffice starts returning the session URL, the option gains a `url`, the URL redirect wins, and Stripe.js is never loaded. No SDK release is needed for that transition.
+
+## Remove Stripe Workarounds
+
+Sites that hid the Stripe button because no URL was present should now render it. Gate on the option existing rather than on `option.url`:
+
+```ts
+// Before: Stripe options were unusable, so they had to be hidden
+const payable = option.kind !== "stripe_checkout" || option.url !== undefined;
+
+// After: every submittable option can be submitted
+const payable = true;
+```
+
+Sites that implemented their own Stripe.js bridge with a publishable key can delete it, along with the key configuration. The SDK carries the vOffice platform keys and selects between test and live based on the session id, so a tenant in Stripe test mode and a tenant in live mode both work from the same build.
+
+## Content-Security-Policy
+
+Stripe.js is fetched from Stripe at submission time. If your site sets a CSP, allow:
+
+```
+script-src  https://js.stripe.com
+frame-src   https://js.stripe.com https://hooks.stripe.com
+```
+
+Without these directives the script is blocked and Stripe submission fails. Other payment kinds are unaffected.
+
+## Error Handling
+
+Payment submission can now fail for new reasons: Stripe.js could not be loaded, the loaded Stripe.js build does not provide the Checkout redirect, or Stripe rejected the redirect. All surface as a `CoreSDKError` with `operation: "paymentSubmission"`, the same as existing submission failures.
+
+Offering a retry is worthwhile for these failures. A failed Stripe.js load is not remembered, so the next submission fetches the script again and can succeed without a page reload.
+
+The booking already exists by the time payment options are rendered, so a submission failure must never be presented as a failed booking:
+
+```ts
+try {
+  await sdk.live.booking.submitPaymentOption(option);
+} catch (error) {
+  // The reservation is created. Show the booking number and offer bank transfer.
+  showPaymentFailure({ bookingNumber: booking.bookingNumber, error });
+}
+```
+
+Submission is still browser-only and fails outside a browser environment, unchanged from earlier versions.
+
+## Payment Return
+
+Unchanged from earlier versions, but worth confirming while testing Stripe end to end. The SDK derives the Stripe success and cancel URLs from the `relativeRedirectUrl` passed to `sdk.live.booking.book(...)` and appends `payment=stripe&success=true` or `payment=stripe&cancel=true`. That path must exist in your site and should read those query parameters.
+
+Note that `relativeRedirectUrl` is supplied before the reservation exists, so the return URL cannot contain the booking number or guest token. Persist anything the return page needs, for example in `sessionStorage`, before submitting the payment option.
+
+A `success=true` return means Stripe sent the browser back, not that payment has settled. Payment confirmation reaches vOffice through Stripe's webhook.
+
+## Recommended Steps
+
+1. Upgrade to `@v-office/website-sdk` 2.6.0.
+2. Remove any conditional that hides Stripe payment options when `option.url` is missing.
+3. Remove a site-level Stripe.js bridge and its publishable key configuration if you added one.
+4. Add the Stripe CSP directives if your site sets a Content-Security-Policy.
+5. Confirm payment submission errors are presented as payment failures with the booking number, not as booking failures.
+6. Smoke-test one booking against a Stripe test tenant and one against a live tenant, checking that Checkout opens and that the configured return path handles both `success=true` and `cancel=true`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@v-office/website-sdk",
-  "version": "2.5.1",
+  "version": "2.7.0",
   "description": "Website-facing SDK facade backed by @v-office/sdk-core",
   "bin": {
     "website-sdk": "./dist/cli.mjs"
@@ -41,7 +41,7 @@
   },
   "dependencies": {
     "@graphql-typed-document-node/core": "3.2.0",
-    "@v-office/sdk-core": "^1.6.1",
+    "@v-office/sdk-core": "^1.7.0",
     "effect": "4.0.0-beta.85",
     "graphql": "16.14.2",
     "yaml": "^2.9.0"