Event-level setup
Use a supported gateway configuration for a specific event when the account or market differs.
Best for event-specific payment operations
Event payment processing
Connect ticket sales to the payment setup your event uses
Route 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.
Stripe, Razorpay, and Tap Order-linked payment state Event-level finance view
Your supported gateway account
Keep the event connected to the processor account your team controls
Configure supported credentials at the event or organization level and keep sensitive values masked in normal organizer responses.
Event-level override
Event payment options 
Credentials masked
Save changes Organization-level setup
Reuse 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.
Choose the Current Gateway Path That Fits the Event Market
EventHex has active payment flows for Stripe, Razorpay, and Tap; the attendee checkout follows the gateway configured for the event.
Stripe
Use the supported Stripe checkout and webhook path for the configured event account.
Razorpay
Use Razorpay paths for relevant India-first payment experiences, including supported hosted or SDK handoffs.
Tap
Use Tap for supported GCC/MENA currency and payment-source flows.
Need another gateway?
Bring the provider and required checkout model to the demo so the EventHex team can scope what would need to be built.
Attendee checkout, payment status & approval
Keep payment state connected to the ticket order
Attendee checkout
Keep the payment handoff connected to the ticket order
The configured event and gateway determine the payment path; the attendee does not choose between processors during checkout.
Proceed to Pay Payment status
Give operations a payment record they can act on
Review the payment state beside the order instead of reconciling a separate attendee list against processor emails.
Price and registered state Approval-led payment paths
Keep payment state aligned with registration approval
When the ticket flow requires review, the order can carry approval and capture context so operations can see what still needs a decision.
Approval and capture context
Organizer-managed refunds
Process a full or partial refund from the order context
Let an authorized organizer choose the amount, send the request through the supported provider path, and retain the history beside the original payment.
Book a Demo01
Full refund
Return the remaining eligible value for the order.
02
Partial refund
Refund a smaller amount without exceeding the paid balance.
Refund order #ORD-4821
Refund amount
120.00QAR
Full Partial
03
Remaining-balance guard
Cap another refund at the order total minus earlier refunds.
04
Attendee notification
Use the configured refund communication after the organizer action.
Event Finance View
By gateway and status Orders grouped Provider context kept Event finance view
Review revenue and refund context by currency, status, and gateway
Use the event-level finance view to move from individual orders to an operational summary for the finance team.
- Gross collectedReview captured value for the selected event context.
- RefundedSee returned amounts without treating gross sales as retained revenue.
- Fees and taxKeep estimated gateway fees, platform-fee context, and recorded tax visible as separate fields.
- Estimated net payoutReview the calculated event view by currency, status, gateway, and provider before comparing it with processor records.
Keep an offline payment option separate from gateway automation
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.
-
Online gateway payment
Provider confirmation and webhook paths update the order through the supported integration.
Automated provider path -
Manual or offline payment
The organizer provides instructions and remains responsible for confirming receipt outside EventHex gateway automation.
Organizer-verified path
Manual/offline payments are not automatically reconciled and cannot use the same in-product provider refund path.
Keep processor responsibilities clear
EventHex connects the event order to supported gateway flows while the selected payment provider handles its own checkout, methods, settlement, and account requirements.
-
01
Masked credentials
Keep stored credential values out of normal organizer responses.
-
02
Provider checkout
Use the active integration path for the selected gateway.
-
03
Provider settlement
Treat payout timing and account status as processor-specific.
-
04
EventHex order state
Use EventHex for the event order, ticket outcome, refund action, and finance context it records.
Continue into the job that owns the detail
Payments sit between ticket selection and the financial documents or attendee outcomes that follow.
Event Ticketing
Configure ticket price, capacity, sale windows, discounts, and access rules.
Event Registration
Choose the form or checkout journey that creates the paid order.
Invoicing and tax
Collect billing details and generate an order-linked PDF invoice with configured tax lines.
Event Check-In
Use confirmed attendee records and QR tickets at arrival.
Which payment gateways does EventHex support today?
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.
Can we use our existing gateway account?
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.
Does EventHex always charge zero platform fees?
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.
Can organizers issue refunds?
Authorized organizers can initiate full or partial refunds for supported online gateway payments, up to the remaining refundable balance.
Can EventHex accept manual or offline payments?
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.
Where can finance teams review event payments?
The event Finance view aggregates gross collected, refunds, estimated fees, tax, and estimated net payout by available currency, status, gateway, and provider context.
Map your event payment setup
Bring your gateway and finance workflow to the demo
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
