Event-level setup
Use a supported gateway configuration for a specific event when the account or market differs.
Best for event-specific payment operationsRoute paid checkout through Stripe, Razorpay, or Tap, use your supported gateway account, and keep payment, refund, tax, and estimated net-payout context connected to the event order.
Configure supported credentials at the event or organization level and keep sensitive values masked in normal organizer responses.
Use a supported gateway configuration for a specific event when the account or market differs.
Best for event-specific payment operationsReuse supported payment settings where the organization model allows shared configuration.
Best for repeat event portfoliosThis is bring-your-own account support for Stripe, Razorpay, or Tap—not a universal adapter for any gateway.
EventHex has active payment flows for Stripe, Razorpay, and Tap; the attendee checkout follows the gateway configured for the event.
Use the supported Stripe checkout and webhook path for the configured event account.
Use Razorpay paths for relevant India-first payment experiences, including supported hosted or SDK handoffs.
Use Tap for supported GCC/MENA currency and payment-source flows.
Bring the provider and required checkout model to the demo so the EventHex team can scope what would need to be built.
The configured event and gateway determine the payment path; the attendee does not choose between processors during checkout.
Review the payment state beside the order instead of reconciling a separate attendee list against processor emails.
When the ticket flow requires review, the order can carry approval and capture context so operations can see what still needs a decision.
Let an authorized organizer choose the amount, send the request through the supported provider path, and retain the history beside the original payment.
Use the event-level finance view to move from individual orders to an operational summary for the finance team.
For bank transfer or another manual path, EventHex can show organizer-provided instructions and record the order flow without pretending the platform verified the external payment.
Provider confirmation and webhook paths update the order through the supported integration.
Automated provider pathThe organizer provides instructions and remains responsible for confirming receipt outside EventHex gateway automation.
Organizer-verified pathManual/offline payments are not automatically reconciled and cannot use the same in-product provider refund path.
EventHex connects the event order to supported gateway flows while the selected payment provider handles its own checkout, methods, settlement, and account requirements.
Keep stored credential values out of normal organizer responses.
Use the active integration path for the selected gateway.
Treat payout timing and account status as processor-specific.
Use EventHex for the event order, ticket outcome, refund action, and finance context it records.
Payments sit between ticket selection and the financial documents or attendee outcomes that follow.
Configure ticket price, capacity, sale windows, discounts, and access rules.
Choose the form or checkout journey that creates the paid order.
Collect billing details and generate an order-linked PDF invoice with configured tax lines.
Use confirmed attendee records and QR tickets at arrival.
EventHex has active payment paths for Stripe, Razorpay, and Tap. Availability and payment methods still depend on the event currency, market, provider account, and integration setup.
You can configure your own supported Stripe, Razorpay, or Tap credentials. Another provider requires a separate scoping conversation; a generic any-gateway adapter was not verified.
Fee behavior depends on the subscription, gateway mode, and event configuration. Confirm the commercial setup for your account before relying on a zero-fee option.
Authorized organizers can initiate full or partial refunds for supported online gateway payments, up to the remaining refundable balance.
EventHex can present manual payment instructions and record the order path, but the organizer confirms receipt. It is not automatically reconciled or refunded through a gateway integration.
The event Finance view aggregates gross collected, refunds, estimated fees, tax, and estimated net payout by available currency, status, gateway, and provider context.
Show us the market, currency, ticket flow, supported provider account, refund process, and reporting needs for one event. We’ll walk through the matching EventHex path and call out anything that requires separate scoping.
Book a Demo