I want to make a ticket selling platform and allow customers to create their events and sell tickets

Yes — you can absolutely build a multi-organizer ticket-selling platform on WordPress + Tickera, where each organizer manages their own events, sells tickets under their own brand, receives payouts directly to their own account, and you collect a configurable platform fee on every sale. The architecture is WordPress Multisite + Tickera (network-activated) + Stripe Connect. Here’s the full step-by-step setup.

The architecture in one paragraph

You run a WordPress Multisite network. Every organizer is given their own subsite (a subdomain like concerts.your-platform.com or a subdirectory like your-platform.com/concerts/). Tickera is network-activated, so each subsite is a fully-featured Tickera installation isolated from every other organizer’s data. Stripe Connect is configured at the network level — each organizer connects their own Stripe account once, and from then on every ticket sale automatically routes the buyer’s payment to the organizer’s account, with your configurable platform fee skimmed off the top. Check-ins work per subsite via Checkinera. Customers see one unified platform; behind the scenes, each organizer’s environment is private and self-contained.

Step 1 — Enable WordPress Multisite

Multisite is built into WordPress core but has to be explicitly turned on by editing your wp-config.php and .htaccess files. The official guide is the canonical reference: Create a Network — WordPress.org. If you’re not comfortable with the wp-config edit, your hosting provider’s support team almost certainly knows the drill.

Choose between:

• Subdomain network — organizer.your-platform.com. Visually cleaner per-organizer URLs. Requires DNS wildcard configuration.
• Subdirectory network — your-platform.com/organizer/. Simpler DNS but the URLs look like paths.

Once Multisite is on, you have a “Network Admin” dashboard above the per-site admin, where you control the whole platform.

Step 2 — Create a subsite for each organizer

In the Network Admin → Sites → Add New, create one subsite per organizer. Each subsite is, from the organizer’s perspective, almost exactly like a standalone Tickera-powered website. They log in to their dashboard, they only see their events, attendees and orders, they have their own Tickera settings.

Network Admins (you) decide:

• Which organizers get subsites
• Which plugins each subsite can use
• Which themes are available
• Per-site capabilities and quotas

If you want the organizer’s dashboard to feel like part of your platform — custom colours, branded login screen, welcome message with onboarding links — see our blog post on branding the WordPress dashboard. A little branding goes a long way toward making the platform feel professional.

Step 3 — Network-activate Tickera

Network-activate Tickera (and any add-ons you want available across the platform — Seating Charts, Custom Forms, CSV Export, etc.) so they’re available on every organizer subsite. Each organizer then has the full Tickera toolkit:

• Create and manage events
• Configure ticket types and pricing
• Track orders and attendees
• Customize ticket PDF templates
• Export reports
• Use whichever add-ons you’ve enabled

Each subsite stores its own event data in its own database tables. There’s no cross-contamination.

Step 4 — Set up Stripe Connect for payments

This is the piece that makes the platform commercially viable. The Stripe Connect add-on handles three things in one:

• Direct payouts — when a buyer pays for a ticket on an organizer’s subsite, the funds settle to that organizer’s connected Stripe account, not yours.
• Automatic platform-fee skim — you configure a percentage (or flat amount) per transaction; Stripe Connect deducts that and routes it to your account before the rest is paid to the organizer.
• Automated KYC / verification — Stripe handles the legal “this organizer is a real business that can receive payouts” verification, with no manual work on your side.

Stripe Connect is available in most countries worldwide, which makes it the natural choice for almost every multi-organizer platform. Each organizer connects their own Stripe account from inside their subsite’s Tickera settings. After that, every ticket sale is routed automatically — no manual reconciliation, no monthly invoices, no chasing payouts.

For the underlying Stripe model and what it enables, the Stripe Connect docs are the canonical reference: stripe.com/docs/connect.

Step 5 — Check-ins via Checkinera (per organizer)

Even though every organizer operates inside the same Multisite network, Checkinera works exactly as it would on a standalone Tickera site for each of them.

In their subsite, each organizer goes to Tickera → Settings → API Access to:

• View their existing API keys
• Create new API keys for Checkinera
• Find the login URL for the Checkinera mobile app

The login URL reflects how you’ve structured the network:

• Subdomain-based: organizer.your-platform.com
• Subdirectory-based: your-platform.com/organizer/

Organizers (and their staff) use that URL + their API key to log into the Checkinera mobile or web app. From there, the check-in flow is identical to a standalone Tickera setup:

• All event data is pulled from that organizer’s subsite
• Only that organizer’s tickets can be scanned
• Check-in logs stay isolated per subsite
• Multiple devices can scan simultaneously in real time

The isolation is automatic — staff at one organizer’s event can’t accidentally scan another organizer’s tickets.

Step 6 — Guide organizers through their workflow

Each organizer manages everything from inside the WordPress admin area of their subsite — creating events, setting prices, configuring capacity, tracking sales, exporting attendee lists, customizing emails and templates.

A few practical onboarding notes:

• Tickera does not currently support front-end event creation, so organizers always work from the WP dashboard. Once they learn the layout, it’s intuitive.
• If you want to make the dashboard feel less generic-WordPress and more “your platform,” use the branding techniques mentioned in Step 2 — colours, welcome notes, helpful onboarding widgets.
• Consider creating a short internal docs page or onboarding video for organizers covering: how to create an event, how to add ticket types, how to set up their Stripe Connect, how to check in attendees.

Step 7 — What customers actually see

To the public, your platform looks like one unified ticket-selling website. Customers can:

• Browse events across all organizers (you control the directory page on the main site)
• Pick an event they want
• Choose their ticket types
• Complete checkout with Stripe

Tickera handles email notifications, ticket generation, and attendee records automatically on whichever subsite the event lives on. Funds split between the organizer (via Stripe Connect) and your platform account in the same transaction. No batched payouts, no end-of-month reconciliation chores.

Why this beats a multivendor plugin

A common alternative path is to use a WooCommerce multivendor plugin (Dokan, WC Vendors, WCFM, etc.). Don’t. Tickera doesn’t integrate with those — they’re built around the WooCommerce product structure, and Tickera’s event/ticket model doesn’t fit. The Multisite approach gives you:

• Real data isolation per organizer (their own database tables)
• Real payment routing (Stripe Connect, not commission-skim-in-WooCommerce)
• Real ticketing depth (seating charts, custom forms, check-in apps, all working per organizer)
• A battle-tested architecture (WordPress.com itself runs on Multisite at huge scale)

See our full answer on WooCommerce multivendor for the long version.

Wrapping up

WordPress Multisite + Tickera + Stripe Connect is a complete, proven recipe for a multi-organizer ticket-selling platform. Each organizer gets their own private, fully-capable Tickera environment; you keep network control and earn a commission on every ticket. Custom onboarding, theme refinements, network-level reporting — all entirely possible. Reach out to our support if you need help architecting the specifics for your platform’s launch.

Related questions

• Does Tickera work with WooCommerce multivendor systems?
• Does Tickera take a percentage of sales?
• Where is my event and customer data stored?