To set up Stripe in Webflow Ecommerce for selling event tickets online, connect Stripe in Ecommerce > Payments, configure event products as no‑shipping orders, model dates/tiers with variants, enable web payments, customize checkout to capture attendee info, and brand order emails with event instructions before publishing. Stripe can also enable fast wallets like Apple Pay and Google Pay on supported devices, which helps conversion for time‑sensitive ticket drops.
TL;DV
Connect Stripe in Webflow Ecommerce settings, keep PayPal as an optional backup, and enable web payments to add Apple Pay/Google Pay via Stripe for faster checkout on eligible devices.
Create an “Event ticket” product, turn on variants for date/time or tier, and track inventory per variant to cap seats; mark the product as not requiring shipping to remove address and shipping steps.
Customize checkout to capture attendee details and brand the order confirmation page and emails with entry instructions, venue, and terms.
Prerequisites
Use a Webflow Ecommerce site plan so Payments, Checkout, Orders, and Emails are available for the project.
Plan to offer Stripe as the primary processor and optionally add PayPal to increase trust and acceptance in some markets.
Connect Stripe in Webflow
Go to Project Settings > Ecommerce > Payments, click Connect Stripe, sign in or create a Stripe account, and authorize access to link Webflow with Stripe.
After connecting, enable web payments so supported devices can use wallets like Apple Pay and Google Pay for a one‑tap ticket purchase flow.
Model the ticket product
Create a single “Event ticket” product and enable Product Options and Variants to represent date/time sessions or tiered tickets (e.g., GA, VIP) in one SKU.
Track inventory per variant so stock decrements as tickets sell and “Out of stock” appears when a session or tier sells out.
Mark the product as not requiring shipping so checkout omits shipping address/method for a smooth event‑ticket purchase flow.
Checkout fields for attendees
Use the Checkout page in Designer to add and style the built‑in fields, and consider a lightweight pattern to collect attendee names using the Additional Info field plus custom inputs mapped into it if multiple attendee details are needed.
Keep the form concise to reduce friction on mobile, especially when using accelerated wallets via Stripe.
Confirmation and emails
Customize the Order Confirmation page to show event details, house rules, and on‑site check‑in instructions right after purchase.
In Ecommerce Email Settings, brand customer emails and include what guests need at the door (order number, attendee name, event date/time, venue, and support contact); preview emails and resend when needed.
Payment experience and wallets
With Stripe connected, enable web payments so eligible browsers automatically surface Apple Pay or Google Pay, reducing steps and cart abandonment for flash ticket drops.
Keep SSL active and test checkout on mobile and desktop to confirm wallets appear as expected for supported devices and browsers.
Testing before launch
Place a low‑price test product or a temporary “hidden” ticket variant to run end‑to‑end checks on cart, checkout, emails, and order management without impacting real inventory.
Verify that orders for the ticket product skip shipping, that variant stock decrements correctly, and that emails carry all required event details.
Go‑live checklist
Confirm Stripe connection status, currency, and web payments in Payments settings, then publish the site.
Re‑QA checkout on the custom domain, validate email branding and content, and ensure inventory counts match venue capacity per variant.
Troubleshooting tips
If shipping fields appear, reconfirm the product is configured as not requiring shipping and that checkout conditional visibility is set accordingly.
If more attendee data is needed than default fields allow, apply the Additional Info pattern to capture structured attendee details at checkout without custom code backends.
Setup table (quick map)
| Area | What to configure | Why it matters |
| Payments | Connect Stripe and enable web payments; optionally add PayPal | Card processing plus Apple/Google Pay improves speed and trust for ticketing |
| Product | One ticket product with variants for dates/tiers | Clean catalog and easy management of multiple sessions/ticket types |
| Inventory | Track stock per variant | Prevent overselling and reflect “Out of stock” status accurately |
| Shipping | Set “doesn’t require shipping” | Removes shipping steps for a service‑like ticket purchase |
| Checkout | Style fields; add attendee details pattern | Collect the right info and minimize friction on mobile |
| Emails | Brand templates and include entry info | Clear, on‑brand instructions reduce support load |
Credits
Webflow Help Center: Payments, orders without shipping, checkout and email customization for Ecommerce.
Webflow University and Product Docs: Product variants, inventory tracking, and email management patterns for Ecommerce.
LitExtension: Practical overview of enabling Stripe and Apple/Google Pay in Webflow.
Author
Erik — leaning on Stripe for speed and global acceptance, the go‑to pattern is variants for sessions/tiers, tracked inventory to cap seats, no‑shipping checkout, and branded confirmations that hand attendees everything needed at the door.
