Pricing Table

Use this method for Stripe’s actual stripe-pricing-table embed. It does not apply to arbitrary pricing pages or custom call-to-action links. For an anchor or form calling your checkout backend, use Server-Side Checkout.

Install the ordered scripts

1. Open Settings → Website integration → Pricing Table.
2. Copy your merchant’s installation snippet, which contains LiftVector first at https://static.liftvector.app/script/liftvector.js, then Stripe’s https://js.stripe.com/v3/pricing-table.js loader, both using defer. Preserve the merchant, provider, and method attributes.
3. Replace Stripe’s default async loader with that ordered pair. Load each script only once, with LiftVector on referral landing pages and pages that hand off to checkout.
4. Keep your existing stripe-pricing-table element, its pricing-table-id, and its publishable-key from Stripe.

LiftVector supplies the captured token through the element’s client-reference-id. Stripe carries it into the Checkout Session’s client_reference_id. No checkout backend change or data-liftvector attribute on the embed is required.

Existing references and dynamic tables

Leave client-reference-id absent so LiftVector can supply it. Existing merchant references are preserved, including empty or equal values. Resolve conflicts with any order or customer reference; do not combine it with the token.

Tables added later or updated with a different ID or publishable key are supported in the ordinary document. Changes are processed asynchronously: let the component finish loading before choosing a plan. Embeds inside another iframe or a shadow root are outside this integration’s scope.

Only script-owned references are refreshed or cleared as the captured candidate changes or expires. Missing capture must leave normal checkout available. Subscription renewals use the established financial association; they do not require another browser token or a new Checkout Session.

Verify a plan selection

Follow a current affiliate link and select a plan in the real Stripe table. Exercise dynamically inserted tables too if your website uses them. For a sandbox-connected merchant, complete a sandbox purchase. Inspect the resulting Session’s reference and collected payment, then check the sale, affiliate attribution, and expected commission in LiftVector. Inspecting the embed attribute alone is not enough.

Record merchant confirmation after setup, and use troubleshooting if the provider or financial result is missing.