Skip to content

React checkout

Theming and hard floors

You can brand the embed. You cannot override buyer-protection hard floors.

Branding

Pass brand keys to AxynProvider's brand prop. The allowed keys are in THEMEABLE_BRAND_KEYS (src/theme/themeableKeys.ts). Other keys are dropped and reported through onBrandOverrideRejected. Prefer brand keys over forking components or overriding SDK CSS variables from host CSS.

<AxynProvider
  theme="dark"
  brand={{
    'color.cta.bg': '#7a1222',
    'color.cta.text': '#f2f3f0',
    'color.bg.elevated': '#1c1a1a',
    'font-family.sans': 'Georgia, serif',
  }}
>
  <TicketPanel ... />
</AxynProvider>

TicketPanel, HouseBrowser, and Stripe

The same keys restyle the ticket panel, the seat map, and the ticket-panel Stripe Payment Element. You do not need to set --axyn-ticket-* or --axyn-house-* yourself.

Brand keyTicket panel / seat mapStripe (ticket panel)
color.cta.bgPrimary button, your section and seats, section heat tintscolorPrimary, focus ring, tabs
color.cta.textPrimary button labelaccessibleColorOnColorPrimary
color.secondary.fgAccent text, links, focus outlines (falls back to color.cta.bg)—
color.bg.elevatedPanel surface (and inputs in light mode)Tabs in dark mode
color.bg.sunkenSunken wells (and inputs in dark mode)Input background, light tabs
color.bg.defaultSeat-map floor—
color.text.primaryBody text, hairlines, and seat tintscolorText
color.text.mutedSecondary textcolorTextSecondary
color.border.hairlineDividers and input borders—
color.status.cautionWarning text and fill—
font-family.sansPanel and seat-map fontfontFamily

Keys you leave out keep the AXYN default. Without a brand, nothing changes. Brand values apply in both light and dark mode. If you set color.bg.elevated, any surface keys you leave out (sunken wells, inputs, body and secondary text) are derived from your panel color, so a light brand still reads correctly under theme="dark".

The SDK keeps ticket-panel text readable (WCAG AA, 4.5:1):

  • No color.cta.text: the button label is chalk or ink, whichever has more contrast on color.cta.bg.
  • color.cta.text is only used when color.cta.bg is set, and is adjusted if it fails AA on it.
  • Body, secondary, accent, and warning text are adjusted until they pass AA on the panel.

These checks run on hex colors (#rgb, #rrggbb). Other formats, such as rgb(), are used as given, so check their contrast yourself.

Stripe renders in an iframe that cannot read CSS variables. Use literal colors (#hex, rgb(), hsl()) for the Stripe keys above. Values such as var(...) still style the panel, but Stripe keeps the AXYN default for them. A custom font only renders inside Stripe if it is installed on the buyer's device. Otherwise Stripe uses the next font in your stack.

Hard floors (non-negotiable)

RuleMeaning
TotalsDo not invent client-side totals that disagree with AXYN
FeesShow fee and price honesty constraints in buyer UI
Add-onsDo not hide the add-on skip path
PrivacyDo not hide the "Ticketing by AXYN · Privacy" notice

SDK tests cover re-skin integrity for these rules.

Every SDK checkout shows "Ticketing by AXYN · Privacy" under the pay or place-order button, linking to https://axyn.events/legal/privacy. It is AXYN's notice at the point of collection. No prop, slot, brand key or --axyn-* variable changes it: it inherits your checkout text color and uses fixed AXYN type size, so it always matches your branding without being removable. API-only integrations must show the same line (Required disclosure).

Next