Collecting tournament entry fees over Venmo is not a payments problem. The money moves fine. It is a record problem: entries arrive in one place and money arrives in another, so the only way to know who has actually paid is for one person to sit down and match two lists by hand. At ten teams that is twenty minutes. At forty teams with deposits, withdrawals and multi-team clubs, it is most of a Sunday — and it is the job nobody volunteers for twice.
Here is where it breaks, and what replaces it.
Why does Venmo break at more than a handful of teams?
Because a payment app has no idea what a division is.
A Venmo transaction knows an amount, a sender and a note. It does not know which event, which division, which team, whether that was a deposit or a balance, or whether the person sending it is the head coach or a parent paying on their behalf. Every one of those facts has to be reconstructed by a human reading a feed.
The specific failures, roughly in the order directors hit them:
- A payment arrives with no usable note. "Baseball" from a name you do not recognise.
- A club enters three teams and sends one lump sum. Now you are doing arithmetic to work out which teams are covered.
- Somebody pays the wrong amount and nobody notices until the event.
- A team withdraws and the refund is a manual transfer with no record attached to anything.
- A parent pays from a personal account and the event's money is now mixed with somebody's rent.
- You need to know the total collected and the only way to get it is to add up a feed.
None of these is Venmo being bad at its job. It is a peer-to-peer payment app being used as an accounts receivable system.
What does a real entry-fee flow look like?
Payment happens at the moment of entry, not as a separate request afterwards. That is the whole difference.
- A coach enters the team — division, contact, roster — and pays in the same session.
- The entry is not complete until payment clears. There is no state where a team is in your schedule but not in your ledger.
- Paid/unpaid is a field on the entry, visible to you and your staff without anyone reconciling anything.
- Deposits are a partial payment against the same record, with the balance and its due date attached.
- A refund is recorded against the entry, so the withdrawal and the money agree.
- The money lands in your own account and settles to your bank.
That last point is worth being precise about. On our platform, we take 0% of your registrations — you keep your own payment processor, so your card fees are whatever Stripe charges you, same as anyone. We just do not add a platform cut on top. That is a control argument, not a savings one: entry money never sits with us, you own the merchant relationship, and you can leave with it.
How does this compare to what you run now?
| Venmo / Zelle / cash | An entry-fee flow | |
|---|---|---|
| Record of who paid | A feed you read | A field on the entry |
| Links payment to a team | You do, by hand | Automatically, at entry |
| Deposits and balances | Tracked in your head or a sheet | A partial payment with a due date |
| Refunds | A manual transfer | Recorded against the entry |
| Chargebacks and disputes | Limited recourse on P2P | Normal processor dispute handling |
| Who else can see it | Whoever has your phone | Your staff, by role |
| Reconciliation | Manual, every week | None |
| Total collected | Add up a feed | A number |
| Card fee | None on personal; 1.9% + $0.10 on a Venmo business profile | Whatever your own processor charges you |
Note the last row honestly: a personal Venmo account is the cheapest way to collect money that exists, and moving off it will cost you more in fees, not less. What you are buying is the record. If somebody tells you online registration will save you money on payment fees, check the arithmetic — for most events it will not.
What about deposits, refunds and rainout credits?
These are the three that expose whether your system is real.
Deposits. Publish the deposit amount, the balance, and the date the balance is due. A deposit with no recorded due date is a balance you will chase in the week you have least time.
Refunds. Publish the withdrawal date after which money is not coming back, before entries open. Then hold it. The policy is not for the teams who read it — it is so you have something to point at when you are tired and it is Thursday.
Rainout credits. Decide before the season whether a washed-out event produces a refund, a credit to a future event, or nothing, and whether that differs by how much play happened. A credit is usually better for both sides: the team keeps their money in your ecosystem and you keep your cash flow. But it has to be written down in advance — the rainout post covers the whole decision tree.
Who eats the card fee?
Three options, all legitimate, and you should pick deliberately rather than by default.
- You absorb it. Simplest, and the entry fee already has it priced in. Most events do this.
- You pass it on as a separate line at checkout. Transparent, but it is friction at exactly the wrong moment.
- You offer a discount for ACH or check. Rewards the cheaper rail without penalising anyone.
Whichever you choose, put it in the entry fee arithmetic rather than discovering it later — processing is a real line in what an entry fee has to cover.
What records do you need afterwards?
More than a feed, and the time to decide this is not in January.
At minimum you want, per event: total collected, per-team amounts, refunds issued, and the date each payment cleared. If your event sits under a nonprofit, your board or treasurer needs that in a form they can audit, and a Venmo history is not it. If it is a business, that is your revenue record for the year.
The practical test: if somebody asked you today what your last event collected, net of refunds, could you answer in under a minute? If the answer is "I would have to go through and add it up," the record is the thing to fix, not the payment method.
Questions directors ask
Is it actually against the rules to use Venmo for entry fees?
No. A Venmo business profile is a legitimate way to take payment and charges 1.9% + $0.10 on direct and QR payments. The problem with a personal account is not legality — it is that event money mixes with your own, there is no record a treasurer can audit, and a team gets no receipt. That becomes a real problem the first time a payment is disputed.
Can we keep taking checks?
Yes, and plenty of events should — clubs with a treasurer often prefer them and there is no card fee. The thing to fix is not the rail, it is that a check needs to update the same paid/unpaid field everything else reads from, rather than living in a separate note.
What happens to our money on your platform?
It never touches us. Entry fees go into your own Stripe account and settle to your bank on your schedule. You own that merchant relationship and can take it elsewhere.
Will moving online save us money?
No, and we would rather say that now. A free form and a personal payment app is the cheapest thing you will ever run an event on. What you are buying is the record, the schedule and a site teams can find. Our pricing is here, including where a flat fee costs more than a percentage.
What is the smallest useful change?
Put entry and payment in the same step, even if you change nothing else. Almost every problem on this page descends from those two being separate.
Related: how to run a 60-team tournament covers the other six jobs this one sits inside, and collecting dues without chasing is the same problem for a club season. More for tournament directors.