Event-level connection
Use Stripe credentials for one event when its account, market, or commercial setup differs.
Stripe integration for events
Connect Stripe to your event ticket checkout
Use a supported Stripe account for paid registration, keep the Stripe handoff tied to the EventHex order, and manage payment and refund state from the event workflow.
- Stripe account
- Order-linked status
- Full or partial refunds
- ConfigureCredentials
- PriceEvent currency
- Provider handoff
- ConfirmPayment result
- DeliverTicket outcome
- ReviewRefund and finance
Use Stripe at the level that matches your event portfolio
EventHex can resolve a supported Stripe configuration from the event or the organization before checkout begins.
Specific event Repeat portfolio Organization-level connection
Reuse the organization's supported Stripe configuration across events that select Organization Payment.
Public and secret keys are write-only or masked after save; exact account requirements remain provider-specific.
Connect the account before tickets go on sale
Choose the gateway
Select Stripe in the supported payment settings.
Add credentials
Enter the supported publishable and secret-key values; saved secrets are not displayed back in normal settings responses.
Confirm event currency
Choose an event currency supported by the active Stripe path and your account.
Test the paid journey
Run the event's own checkout and confirmation path before launch.
Keep Stripe connected to the ticket order
The event configuration determines the gateway; the buyer continues through the Stripe path tied to that order.
Keep buyer, ticket, amount, currency, and recorded tax context together.
EventHex creates the Stripe checkout session for the order and sends the buyer to the provider-hosted payment step.
Confirmation and webhook paths update the EventHex order with the provider result.
Use the confirmed order for registration outcome, ticket delivery, and invoice handling.
International event payments
Use Stripe where the event and account setup align
Stripe can be a strong fit for international conference and corporate ticket sales, but actual currency and payment-method availability comes from the connected account and market.
01
Conference ticket sales
Run the supported paid checkout for a conference using its configured event currency.
02
Agency portfolios
Use organization settings where the same Stripe account supports multiple client events.
03
Cross-border buyers
Confirm the account's supported currencies and methods before promising them on the event page.
Give the event team a payment record it can act on
Handle a Stripe refund from the order context
Authorized organizers can request a full or partial refund through the supported provider path.
Refund eligibleOrder balance verifiedFull amountFull refund
Return the remaining eligible paid amount
Issue the full refund from the connected order context while keeping the original payment and its event record together.
Partial refund
Return only the amount the buyer needs
Enter a smaller value when only part of the order should be returned, without losing the payment’s surrounding context.
Partial amountEnter a smaller valueRefund queuedBalance guardRemaining refundable totalWithin limitBalance guard
Protect the paid total before issuing a refund
Prevent requests above the paid total minus earlier refunds so the event team stays within the refundable balance.
Recorded outcome
Keep the result beside the original payment
Record the refund outcome against the event payment so finance and operations can trace what changed.
Recorded outcomeLinked to the orderPayment updatedMove from one Stripe order to the event-level picture
EventHex keeps the provider and order state available to the Finance view, where teams can review gross, refunds, recorded fees, tax, and estimated net payout by the available filters.
Order detail
Investigate one buyer or refund.
Event summary
Review the selected event across orders.
Processor record
Use Stripe as the source for account settlement and provider-specific charges.
Use Stripe without rebuilding the event workflow
-
01
International conferences
Connect the event's Stripe path without separating payments from ticket orders.
-
02
Corporate events
Use paid tickets or access products with the organization's supported setup.
-
03
Associations
Keep member-event payments and refund history tied to the registration.
-
04
Event agencies
Choose event- or organization-level configuration based on the client account model.
Know what EventHex manages and what stays with Stripe
Event operations
Gateway configuration, event order, registration outcome, refund action, and the finance context EventHex records.
Event operations Processor account
Stripe account status, hosted payment experience, available methods, processing charges, disputes, and settlement schedule.
Processor account EventHex does not replace the Stripe Dashboard or control processor settlement timing.
Continue into the page that owns the next decision
Event Payment Processing
Compare the supported gateway paths and event-level finance workflow.
Explore Event Payment ProcessingEvent Ticketing
Configure ticket price, capacity, sale windows, approvals, and discounts.
Explore Event Ticketing
Event Registration
Choose the form or checkout journey that creates the order.
Explore Event Registration
Invoicing and tax
Collect billing details and create an order-linked invoice with configured tax lines.
Explore Invoicing and taxCan we use our existing Stripe account?
Yes, EventHex supports Stripe credentials at event or organization level. Confirm which model fits your account structure during setup.
How should we review payment costs?
Review the EventHex plan, any configured platform fee, and the Stripe charges that apply to your account and market before launch.
Can organizers issue refunds?
Authorized organizers can request full or partial refunds through the supported Stripe path, up to the remaining refundable amount.
Which currencies and payment methods are available?
They depend on the connected Stripe account, event currency, market, and provider configuration. Validate the target checkout before launch.
How does payment confirmation reach EventHex?
The active Stripe confirmation and webhook paths update the event order so the ticket workflow can continue.
