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
Supported payment gateways

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.

Attendee checkout
01Create the orderKeep buyer, ticket, amount, currency, and tax context together.
02Start the gateway handoffOpen the supported redirect, hosted, SDK, or provider flow used by that configuration.
03Receive the resultConfirm payment or update the order from the provider response and webhook path.
04Continue the journeyMove a successful order into confirmation, ticket delivery, and invoice handling.
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.

Payment status
GatewaySee which supported provider handled the payment. Amount and currencyKeep the paid value in the event's configured currency context. Captured or pending stateUnderstand whether the order is ready for the next ticketing action. Failure contextKeep an unsuccessful attempt separate from a completed order. Refund historySee refund activity and the amount still eligible for another refund. Order detailConnect the payment history to its buyer and tickets.
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-led payment paths
Registration submittedCreate the attendee and order context for review.
Payment authorization stateKeep the processor result and capture status visible to the workflow. Organizer decisionApprove or reject through the configured ticket process. Outcome messageContinue into the applicable ticket and payment communication.
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.

  • Full refundReturn the remaining eligible value for the order.
  • Partial refundRefund a smaller amount without exceeding the paid balance.
  • Remaining-balance guardCap another refund at the order total minus earlier refunds.
  • Attendee notificationUse the configured refund communication after the organizer action.
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.
Manual payment instructions

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.

Payment setup and trust

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.

Masked credentials

Keep stored credential values out of normal organizer responses.

Provider checkout

Use the active integration path for the selected gateway.

Provider settlement

Treat payout timing and account status as processor-specific.

EventHex order state

Use EventHex for the event order, ticket outcome, refund action, and finance context it records.

Event payment questions

What teams ask before connecting event payments

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