One system that takes entries, collects payment, checks people in and scores the competition.
Why this exists
Most events start with a Google Form and a bank transfer. It works until about forty entries, and then the questions start: who paid, who paid twice, which squad is short a player, and which of the three copies of the list is current.
| Form and spreadsheet | This system | |
|---|---|---|
| Taking payment | A bank transfer, then someone checks statements by hand | Card or online banking at the point of entry, matched to the entry automatically |
| Knowing who paid | Cross referencing a statement against a list | A paid or unpaid status on every row, updated by the gateway |
| Confirmations | Typed and sent one at a time | Sent the moment payment clears, with the reference on it |
| Chasing unpaid entries | Someone remembers to do it | A reminder sent from the entry itself |
| Refunds | A manual transfer and a note somewhere | Sent back through the gateway to the original card, recorded against the entry |
| Squad entries | One row per player, and no way to see the team | A manager registers the squad, players sit under the team |
| Check-in on the day | A printed list and a pen | Searched and ticked off at the counter, live |
| Scores and standings | A whiteboard, then a spreadsheet | Entered per match, standings recalculated immediately |
| Who changed what | Nobody knows | Every admin action logged with the account that did it |
End to end
From somebody pressing register to their name appearing in a results table. Nobody retypes anything at any point.
Fields follow the event: an individual entry, or a manager entering a squad. In game names, a team logo and paid extras appear only where the event asks for them.
Card or online banking on the gateway's own page. We never touch card details. The place is held when the money clears, not when the form is submitted.
A confirmation email goes out with a reference. The entry lands in your list as paid, and your seat count moves.
Checked in at the counter, drawn into fixtures, scored per match. Standings and the published results follow from the same record.
What is in it
They share a single participant record, which is the whole point. Check somebody in and the tournament module already knows they are present.
Entry forms that fit the event rather than the other way round.
Money in, money back, and a figure you can defend.
The list, and the things you need to do to it.
The counter on the day, not a printed list.
Draws, scores and a standings table that is correct.
Reaching people, and knowing what happened.
An entrant wants to be finished in two minutes. An organiser wants to know where things stand. Both are served from the same record.
Payment happens on the gateway's own page. What comes back to the system is a reference and a result, so there is no card number here to lose.
Roles decide what an account can reach. A referee entering scores cannot open the payment list, and a read-only account cannot move money.
Consent is recorded with the time and origin it was given. Identity numbers are treated as sensitive data, and our Privacy Policy says plainly what is collected and why.
Read the Privacy Policy and the Refund Policy for the detail.
No. They fill in a form and pay. There is no password, which removes the single most common reason somebody abandons a registration. Their reference is what identifies the entry afterwards.
Yes. Set the fee to zero and the entry is confirmed on submission with no payment step. You still get the list, the check-in and the reporting.
The event is set to manager mode. One person registers the team, names each player, and pays once for the squad. Players sit under the team, so you can see the team and its players without holding two lists.
Yes. Add-ons are defined per event and can have variants, such as jersey sizes. They appear as their own line before payment, and they are itemised in the takings so you know what was fee and what was merchandise.
Both payments appear against the entry with their own gateway reference, so the duplicate is visible rather than hidden in a bank statement. Refund it from the entry and the amount returned is recorded on the record.
The public pages carry your event name, poster and rules. Logos in the administration area are configurable. A fully separate look on your own domain is a larger piece of work; ask and we will scope it.
Yes. Participants and transactions export to CSV, so a sponsor report or a hand-off to a funding body does not need us. The data is yours.
Then use only registration. The modules share one record but you are not obliged to touch the ones you do not need.
Send us the format, the fee and the fields you need. We will set up the entry form and show you the whole path, including a real payment, before you commit to anything.