Eventually Ticketing
Checkout & Payments

Set up the checkout bridge page for standalone paid checkout

Paid checkout from a standalone Eventually event link (/e/your-event-slug) works automatically for sites with an embedded Eventually widget, with no dedicated bridge page needed. When a buyer selects tickets on a standalone link, their selection is transferred into your Squarespace cart through a page on your own site that already carries the widget, then forwarded to checkout. A dedicated bridge page remains available as an optional override.

How automatic checkout bridging works

If your Squarespace site has the Eventually widget embedded, paid checkout from a standalone /e/ link requires no setup. When a buyer selects tickets, Eventually hops through a page on your own domain that already carries the widget, adds the tickets to your Squarespace cart, and forwards the buyer to checkout.

The automatic destination is used only when the embedded page is verified and matches the host of the Squarespace product URL. If no verified embedded page matches, checkout keeps the existing product-page fallback and the buyer selects tickets again.

A page carrying your calendar is checked the first time it is opened, so the first buyer on a standalone link can use the automatic handoff instead of falling back to the product page.

Set up a dedicated bridge page (optional)

A dedicated bridge page remains supported and takes precedence over the automatic route. Use one if you intentionally want checkout to pass through a specific page on your site.

  1. In Squarespace, create a new blank page. A name like Ticket Checkout works; the name is internal and only matters for your own reference.

  2. Add a Code block to the page and paste the bare Eventually loader:

    <script src="https://app.eventuallyticketing.com/widget.js"></script>

    This is the only script the bridge page needs. The full widget embed with data-widget-id is not required for the bridge: the bare loader detects the checkout handoff automatically.

  3. Keep the page public. Do not password-protect it or set it to private: the bridge only works if buyers can reach the page without logging in.

  4. Move the page to the Not Linked section in Squarespace so it does not appear in your site's navigation menu, but remains accessible at its URL.

  5. Save and publish the page, then copy the page's URL path (for example, /ticket-checkout).

The bridge page must be live and publicly accessible before the bridge can be activated. A missing, password-protected, or broken bridge page causes buyers to fall back to the Squarespace product page instead of reaching checkout.

Activate the bridge

After your bridge page is live, share the page's URL path with our support team. We configure the bridge for your site and verify the end-to-end checkout flow. There is no self-service setting in your dashboard to enable the bridge; we complete the activation after confirming your page is live.

How the checkout handoff works

When a buyer selects tickets on a standalone paid event link, Eventually creates a single-use checkout token valid for 15 minutes. The buyer is briefly redirected to the bridge or embedded page, where a full-screen Adding your tickets panel covers the page while the selected tickets are added to the Squarespace cart and the buyer is forwarded to checkout.

The token is single-use: once the handoff completes, the same link cannot be used again. If a buyer refreshes the page, uses the back button, or waits longer than 15 minutes, the token is consumed or expired and the buyer is sent to the Squarespace product page instead of checkout. On the product page, they can select tickets again and purchase normally.

Verify your bridge page

Verify the bridge by starting from a standalone paid event link (/e/your-event-slug) and selecting tickets. You should see the full-screen Adding your tickets panel, then be forwarded to Squarespace checkout.

Opening the bridge page URL directly in your browser shows a blank page: with the bare loader and no checkout token, it has nothing to hand off. A direct visit only confirms that the page is public and contains the loader script. If the page does not load at all, confirm the Code block with the loader script is present and the page is published.

Was this helpful?
Was this helpful?