1. Make the entry offer clear
Before a driver pays, explain which event they are entering, the entry fee and what happens next. Put your refund policy where drivers can find it before checkout.
Give drivers one place to ask about a payment. Keeping those questions together helps staff avoid answering the same request in several conversations.
2. Stop matching payments by message history
A payment name may not look like a driver’s competition name. If staff have to compare screenshots, messages and entry lists, confirming a place becomes another manual task.
Keep the payment connected to both the driver and the specific event. For refunds, make sure staff can identify the original payment before reviewing the request.
3. Connect checkout to the entry
Payments & Refunds lets drivers open Stripe checkout from Discord. Each payment is matched to the driver and event, so staff spend less time working out who paid for what.
The module includes protection against duplicate checkouts on retries and configured free-entry promotions. Refund requests stay subject to staff review and your published policy.
It works with Applications & Event Registration and your own Stripe account. Guided setup includes a test payment and refund so your team can walk through the process before opening paid entries.
Before your next event
Readiness checklist
Tick these as you prepare, or print a copy for your team. This site does not save your ticks.
Keep the checklist
A simple copy for your team, ready to open in Google Sheets or Excel.
Common questions
Do payments go through our own Stripe account?
Yes. You provide the Stripe account used for entry checkout. The module connects those payments to the driver and event records.
Are refunds approved automatically?
No. Staff review refund requests according to your published policy. The module helps handle the payment workflow; it does not replace that decision.
