In development. This is on the roadmap and not available yet. The guide is here so it is ready the day it ships.
Integrations & API

Selling tickets from inside your own website

Put a BrightStar ticket widget on your own site so buyers never have to leave it to check out.

4 min readUpdated 2026-07-29

If you already have a website your audience trusts — the retreat page they landed on from a friend's recommendation, the kirtan community site they check every week — sending them somewhere else to buy a ticket costs you people. Every click away from your own domain is a chance for someone to get distracted, lose confidence, or simply not follow through. The BrightStar embed solves this by putting the ticket selection and the payment step directly on your page. The buyer never leaves your site to check out. Behind the scenes, the order still lands in your BrightStar dashboard exactly like any other sale, so you're not running two separate systems to track who bought what. Installation itself is minimal: a script tag and a container element, both copied from the Embed tab on your event. There is nothing to build and no server work on your side.

What the embed actually is

The widget loads a small script from BrightStar and asks for the current state of your event — which ticket types exist, what they cost, and what's still available. It renders a purchase form directly in the space you've given it on your page, sitting inside your layout rather than opening a separate checkout window.

Payment runs through the same Stripe path as checkout on BrightStar itself, so card handling, receipts, and payouts behave identically whether someone bought from your site or from your BrightStar event page. That matters practically: you don't need a second payment processor, and your accounting doesn't split into two systems depending on where the sale happened.

Because the widget reads live event data rather than a copy you pasted in once, changing a price or closing a ticket type in your dashboard updates the widget on your site immediately, with no further action from you. If you sell out an early-bird tier the night before a sound healing evening, your website reflects that the next time anyone loads the page.

Domains and access

The embed is tied to your BrightStar account and to the specific domains you name, which is what stops your event's checkout from being reproduced on a site you don't control. If someone copied your widget code onto their own page, it simply wouldn't load your event, because that domain isn't on your registered list.

This is worth thinking through before you install anything. Add every domain you actually publish from, and don't forget any staging site you use to check how the widget looks before it goes live. A staging environment that isn't registered behaves the same as any unregistered site: nothing loads.

Embedding is part of BrightStar's Elevate plan rather than the free Seva plan. Everything else about the sale — the platform fee per ticket, the processing fee charged once per order, and how payouts reach you — works exactly the way it does for a sale made directly on BrightStar. The embed changes where the buyer sees the form, not how the money moves.

Give the container element a sensible minimum height in your own stylesheet. The widget sizes itself to its contents, and a container that starts at zero height can make the page jump as it loads — visitors notice that kind of shift, especially on mobile, and it can read as a stalled or broken page in the second before the form appears.

Getting it onto your page

Installing the embed doesn't require a developer, a build step, or anything on a server you manage. The whole process happens on the Embed tab of your event and inside whatever page editor you already use.

  1. 1Open the Embed tab on your event inside BrightStar.
  2. 2Copy the script tag BrightStar generates for that event.
  3. 3Copy the container element alongside it.
  4. 4Paste both into the page on your own site where you want the ticket form to appear.
  5. 5Load the page — the widget pulls your event's live ticket data automatically.

What happens after someone pays

When a buyer completes checkout through the embed, the order is recorded in your BrightStar dashboard the same way any other order is — there's no separate list to check for embedded sales versus sales made on your BrightStar event page. Whoever is watching the dashboard for check-in at the door, or building a run sheet for a retreat, sees one combined picture of who bought what, regardless of which page they bought it from.

That matters most at the moments where accuracy is non-negotiable: a kirtan door checking names against a list, a festival gate scanning tickets, a retreat check-in matching arrivals to room assignments. None of that has to know or care whether the original sale happened on your site or BrightStar's — the data is the same either way.

Which plan you need

Embedding tickets on your own site is part of BrightStar's Elevate plan. If your event is on the free Seva plan, you can still sell tickets — buyers are directed to your BrightStar event page instead of a form embedded on your own domain, and you can link to that page from anywhere on your site.

The fees involved in a sale don't change based on where the buyer checks out. The platform fee per ticket and the processing fee charged once per order apply the same way, and payouts follow the same path, whether the sale happened through the embed or directly on BrightStar.

Common questions

Does the buyer leave my website to pay?

No. The BrightStar embed renders the ticket selection and the payment step on your own page, so the buyer completes the purchase without navigating away. The order still appears in your BrightStar dashboard alongside orders made on the BrightStar event page.

Read more

This is the core reason to use the embed instead of just linking out: every extra click or page load between someone deciding to buy and completing payment is a chance for them to reconsider, get distracted, or lose trust in an unfamiliar domain. Keeping the whole transaction on your page removes that friction while still recording the order normally.

What do I have to add to my site to install the embed?

A script tag and a container element, both of which BrightStar generates for you on the Embed tab of your event. You paste them into your page. There is no server-side code to write and nothing to keep in sync by hand.

Read more

Because there's no server work, you don't need ongoing developer support to keep the embed running — the script pulls fresh event data on its own. The only maintenance on your side is making sure the domain hosting the page stays registered on your BrightStar account, since that's what the widget checks before it will load.

If I change a ticket price, do I have to update my website?

No. The BrightStar widget reads your event's live data every time it loads, so price changes, sold-out ticket types and newly added tickets appear on your site automatically.

Read more

This live-data behavior is what makes the embed safe to leave alone once it's installed. You can close a ticket type minutes before a kirtan evening starts, or raise a price after an early-bird window ends, and the change appears on your own site the next time the page loads — without you touching the embed code again.

Is the embed available on the free plan?

Embedding is part of the Elevate plan. Events on the free Seva plan sell through their BrightStar event page, which you can link to from your own site instead.

Read more

If you're on Seva, the simplest path is a clear link or button on your site pointing to your BrightStar event page, so visitors still buy through a page you control the entry point to. Upgrading to Elevate is what adds the option to keep the entire purchase form on your own domain instead.

Can someone copy my embed code onto a different website?

The embed is restricted to the domains registered on your BrightStar account, so a copy of the snippet placed on an unregistered site will not load your event. Add every domain you intend to publish from, including staging.

Read more

This protection exists specifically so someone can't lift your working checkout and place it on a site you have no relationship with, which would make it harder for you to control pricing accuracy or trust the traffic buying your tickets. Registering every domain you publish from, including staging, is what keeps the widget working where you expect it to.

Do the fees change when I sell through the embed?

No. The platform fee per ticket and the processing fee charged once per order apply the same way whether a ticket is bought through the embed or directly on your BrightStar event page, and payouts follow the same path.

Read more

The embed only changes where the buyer sees and fills out the purchase form — it doesn't introduce a separate fee structure or a different payout schedule. This is worth confirming before you assume embedding tickets is either more expensive or a way to avoid the fees that apply to a normal BrightStar sale.

Ready to get started?

Create your first event on EveryEvent Rio de Janeiro — it’s free.