To collect tournament entry fees online, give each approved entry a stable team reference, request the agreed amount and match confirmed payment before you confirm the place. Keep payment status separate from eligibility and bracket acceptance. Money arriving does not by itself prove that a team belongs in the correct division.
This guide is for amateur team-tournament organizers who already manage applications, eligibility and draws separately. It covers the complete path from inviting entries to confirming paid teams, including duplicate payments and withdrawals. It does not turn a payment page into tournament-management software.
Decide whether collection needs to be inside registration
If you need automatic entry limits, division checks, seeding, draws and payments in one system, start with a tournament platform. PlayCompete describes integrated brackets, paid entries and divisions; SportyHQ offers online entries, custom questions, scheduling and event reporting. Evaluate their actual fit for your sport rather than moving only the payment step.
A separate payment link can fit a small event where you approve teams yourself and maintain a reliable entry register. Bank transfer with a clear reference can also work if manual reconciliation and your buyers' payment preferences suit it. The important choice is who is responsible for turning an application into a confirmed entry.
ClubPayHub's registration guidance illustrates the integrated alternative: a paid registration goes to checkout before being registered. In a separate-link workflow, you must maintain that connection yourself. Do not tell captains a place is automatic unless your actual process makes it so.
Publish the entry terms before asking for money
Your invitation should state the event and dates, divisions, team-size rules, eligibility review, entry fee and currency, included items, payment deadline and how a place is confirmed. Identify the organizer receiving the money and a contact for entry or payment questions.
Explain what happens if the event is cancelled, a team withdraws, a division does not fill or weather changes play. Set appropriate terms before accepting money; do not invent a universal right to retain the fee. Say whether a replacement team or entry transfer needs approval. Confirm any sport-specific requirements through your governing body.
For a hypothetical €120 team entry, say what the captain is purchasing. “€120 for one accepted team in [division] on [dates]” is clearer than “tournament payment.” State whether any applicable taxes are included. Do not quietly add a processing surcharge after the captain has accepted an all-in price.
Create one entry record before sending the link
Download the editable team-entry register and captain messages. It contains fictional workflow examples, not real teams or payments. Replace them with your own records and store access appropriately.
Assign a stable identifier such as CUP26-014. Record the team name, division, captain contact, agreed fee, payment deadline and eligibility decision. Track the payer separately: a sponsor or club treasurer may pay for a team without being its captain. Keep sensitive eligibility documents outside a payment ledger; store only what the collection task needs.
| Field | Why it matters |
|---|---|
| Entry ID and division | Connects the payer, team and intended competition |
| Eligibility decision | Records whether the organizer has approved the application |
| Fee due and payment deadline | Defines the specific request |
| Payment/request reference | Matches the collection to the entry |
| Confirmed received and transaction reference | Separates a request or screenshot from a payment record |
| Place confirmed on | Records the organizer's acceptance action |
| Refund/transfer decision | Keeps later changes visible without deleting history |
Choose a policy you can maintain. For example: approve eligibility and reserve a provisional place until a stated payment deadline, then confirm after checking payment. Do not request payment from a waitlisted team under a message promising a guaranteed place.
Send the captain a specific payment request
Use the agreed amount and include the entry identifier in the message and request description. An individual team request is easier to reconcile than an unexplained public link that accepts many payments. If you choose a reusable link, confirm how you will reliably identify each payer before sharing it.
Hello [captain], your team [name] has been approved for [division]. The entry fee is [amount/currency], covering [included items]. Please pay by [date/time/time zone] using [payment link]. This request is for entry CUP26-014 only. If someone else pays, ask them to use that reference and tell us their payer name through [contact].
We will confirm your place after matching confirmed payment to the entry. The provisional place and withdrawal terms are [link/attachment]. If the amount, division or team details are wrong, contact us before paying.
Do not send a second request simply because a payment is still processing. Check the original request first. A screenshot can help locate a transaction but should not be the only evidence used to confirm receipt.
Confirm paid teams before publishing the draw
Check the payment provider's confirmed status, amount and transaction reference. Match them to the entry ID. Then update the register and send a separate place-confirmation message. If collection succeeded but the wrong division was recorded, resolve eligibility before adding the team to the draw.
Before drawing groups, reconcile accepted entries against confirmed payments and any explicitly approved unpaid exceptions. Record who approved an exception and when payment is due. Avoid publishing payer names or payment references in a public bracket.
Handle exceptions without losing the original trail
| Situation | Collection action | Entry action |
|---|---|---|
| Payment pending | Check the existing transaction before requesting another payment | Keep the place provisional under the stated policy |
| Two people pay for the same team | Match both transactions; agree and process any necessary refund through the appropriate provider workflow | Keep one entry; do not create a second team |
| A club pays for several teams | Obtain the allocation across entry IDs and check the total | Confirm each eligible team separately |
| Team withdraws after payment | Apply the agreed terms and applicable rules; record any refund and unrecovered fees | Mark withdrawn; approve any replacement separately |
| Payment received after the place is released | Contact the payer and resolve the amount; payment alone does not restore capacity | Check availability before offering a place |
For example, if a fictional club sends €240 for two €120 entries, allocate €120 to each entry only after identifying both. Do not mark four entries paid because four teams share the same club name. The register is an allocation aid, not evidence that the payment occurred.
Use PayRequest for the agreed collection step
PayRequest payment links let you request a specific amount through a supported connected payment provider. Create the agreed team-entry request, send it with the captain message and reconcile confirmed payment against your register. Available methods depend on provider, account and country eligibility; verify your organization and event can use the selected provider.
Free supports payment links with a 2% standard payment fee, capped at €25 per transaction. Provider fees apply separately. Review plans and exceptions if you need additional capabilities. An entry fee is a payment; it is not a card security hold, and a recurring subscription is usually unnecessary for a one-off tournament.
PayRequest handles the payment step described here. Keep team eligibility, capacity, waivers and bracket management in your event process or specialist software. If you cannot maintain that handoff reliably, use an integrated registration system instead.
Create an account, finish setup, connect an eligible provider and prepare one entry request. Review the amount, reference and captain message before inviting teams to pay.
Editorial method: AI-assisted preparation and conceptual illustration; sources and workflow reviewed. All example teams, entries and amounts are hypothetical. No live registration, payment or refund test is claimed.


