# bindro — Club and travel sports tournaments > Bindro takes tournament entries by team for clubs and tournament directors: one coach pays for a squad in a single order, names the players on a roster afterwards, and each player under eighteen is countersigned by their own guardian through a link sent to the guardian's own address — an unsigned player is refused at the door rather than flagged in a report nobody reads. Waivers, proof of age, jersey sizes, requested divisions and published results are all handled. Brackets, schedules and scoring are not: bindro sells the entry and works the gate. It costs 2.5% + $0.99 per entry, charged once on the order. Canonical page: https://bindro.io/vertical/tournament-registration/ Reviewed: 2026-08-09 ## Facts - Inventory model: multi day agenda. - Pricing models: group rate, tiered. - Fees: 2.5% + $0.99 per paid entry; free tournaments cost nothing. - Payouts: one payout per event, released 2 days after that event's LAST session has ended (medium risk tier, 7.5% reserve). Never before delivery, and a tournament sold as a run of dates pays out once, after the final date. - Check-in: name list, works offline. Visitors can come back in: a scan after they were admitted reads as a re-entry rather than a used code, at whichever entrance they come back to, and says when they first arrived. A second scan within a few minutes of the first is still read as the same code presented twice, so a screenshot passed down the queue does not get anybody in. A scan at a later point on the route counts as progress along it, not as a return. The visit is counted once however often it is scanned. - Joining: free, alone, in minutes. No contract, no monthly fee and no card at signup. A payout destination is verified before the first payout, never before the first sale. - Booking fee default: the player pays it. A tournament can absorb it or split it per tournament; the fee itself does not change with the choice, only which side of the sale it comes from. - Overselling is structurally impossible: inventory moves only under a row lock inside the transaction that confirms the order, with a database constraint behind that as a backstop rather than as the mechanism. - The number this vertical is run on: Teams registered per event. Also tracked: division fill rate, withdrawal rate, waiver completion rate. The console computes the north-star figure and prints the arithmetic under it, beside this tournament's own funnel with the drop-off at each stage, where the traffic came from, refund, transfer, turnout, no-show, add-on and repeat rates each shown with its numerator and denominator, gross, fees and refunds per tournament, live remaining capacity during the tournament, and CSV exports of orders and players. A step the platform cannot observe says so rather than reporting a zero. - Data export: orders and players as CSV from the console at any time, behind a fresh one-time code. No export fee, no notice period, no lock-in. - Required before checkout, enforced on the money path: Youth sports participation liability waiver; Parent/guardian consent for players under 18; Certificate of public liability insurance. ## Not supported for this vertical - Brackets, schedules and scoring — there is no bracket generator, no fixture list, no court or field assignment, no seeding and no live scoring anywhere in bindro. Results are a table you type in yourself — division, rank, competitor, score — kept private until you publish them. If you draw brackets in a scheduling tool today, keep it: bindro takes the entries and works the gate. - A waiver typed by every player's family — the acceptance record names each player and the gate refuses one it does not cover, but the signature it carries is the one the payer typed at checkout, or the name typed on a place filled in later. It is not twelve families each shown the wording at their own link. The one per-family signing act is the guardian countersign for under-eighteens. If your insurer expects a form signed by each player's own household, collect those yourself. - Checking that a player is the right age for their division — the only age rule enforced on the money path is a floor of five years old, and this vertical's divisions are skill bands rather than age grades. Every date of birth is collected and kept, and no cut-off date is compared against it by anything. Age-grade eligibility is a human reading the roster. - Sending the host club or the facility their share — bindro works out each party's cut to the cent, freezes it onto the tournament's payout and names it on your money screen, but it holds no bank details for anyone except you. A split tournament therefore settles to nobody until that changes, and the console says so rather than reporting a transfer that never happened. You still pay the facility. - Collecting the balance of a payment plan automatically — you can publish a plan on the entry type and the deposit is taken at checkout, but bindro never charges the stored card for the rest of it. Off-session charging is armed by a separate switch that is set in no environment: a checkout happens with the payer watching and a sweep bills with nobody present. Collect the balance the way you collect anything else. - A team rate that prices itself — the roster is real, but the group price and its threshold live on the entry type and nothing in the product writes them, so a per-team discount cannot be published. What works instead is an entry type priced for a squad, an early-entry tier that closes on a date, or a promo code you give returning clubs. - A release ladder that hands over on its own — an early-bird entry type opens and closes on a date, and that much works. What is not here is the ladder proper: a wave selling out and announcing the next rung on the entry page, a fast-track type, or a price that varies by date. Price two entry types and close the first one. - A touchline sheet arranged around the fixture — emergency contacts and medical notes by division, by pitch, by kick-off. Those answers are collected, validated, held under their sensitivity class and readable in four places: the approvals queue before you take the money, the player’s own record afterwards, the players list your gate works from, and a column each in your own CSV of your own players. What nothing builds is the sheet for the Friday, so print that yourself from the export. - Selling a whole weekend day by day in the hosted checkout — the multi-day basket ships on the public JSON API, and the hosted entry page still sells one session per order. A Saturday-and-Sunday tournament is normally one entry covering the weekend; a day-by-day picker on the hosted page is not built yet. - A waiting list when the divisions are full — waitlists are not declared for this vertical, so a full division says "Divisions full" and stops rather than collecting addresses nobody calls back. Raising the cap or opening another division is one form, and it sells entries. - Handing a paid entry on — there is no ticket transfer for this vertical and no self-service move button. A coach can re-type a place on their own roster; a family cannot swap itself into another team and a club cannot sell its place on. Rolling an entry into next season IS covered, but as your act rather than theirs: you withdraw the team from the console and settle it as a credit, held against the captain's email for a future entry, and their places go back to the division the moment you do. - Sales tax on an entry fee — tax is configured as optional for this vertical and is not turned on, so nothing is calculated, itemised or held as a liability. Whether a youth sports entry is taxable where you run is a question for your accountant. - Checking the certificates you collect — the insurance certificate and the proof of age are uploaded before payment and retained, and nothing reads them. No expiry date is parsed, no document is matched against the date of birth on the form, and no team is ever suspended for a lapsed certificate. Watching for that stays with you. ## Questions the landing page answers - What should a tournament actually run on bindro, and what should stay where it is? - How does one coach's payment become twelve named, signed, admissible players? - How should entries be priced when a team rate cannot be published? - What happens to the entry money between checkout and the facility's share? https://bindro.io/vertical/tournament-registration/ ## Pages - FAQ (20 questions): https://bindro.io/vertical/tournament-registration/faq/ - bindro vs TourneyMachine: https://bindro.io/vertical/tournament-registration/compare/tourneymachine/ (reviewed 2026-08-09) - bindro vs SportsEngine: https://bindro.io/vertical/tournament-registration/compare/sportsengine/ (reviewed 2026-08-09) - bindro vs Exposure Events: https://bindro.io/vertical/tournament-registration/compare/exposure-events/ (reviewed 2026-08-09) - How to open entries for a weekend tournament without losing a division to a spreadsheet: https://bindro.io/vertical/tournament-registration/blog/opening-entries-for-a-weekend-tournament/ (reviewed 2026-08-09) - Waivers, guardian consent and the gate: what actually stops an unsigned player: https://bindro.io/vertical/tournament-registration/blog/waivers-guardian-consent-and-the-gate/ (reviewed 2026-08-09) - Divisions, eligibility and the age-grade check bindro will not do for you: https://bindro.io/vertical/tournament-registration/blog/divisions-eligibility-and-what-bindro-will-not-check/ (reviewed 2026-08-09) - Entry fees, facility splits and when the money actually lands: https://bindro.io/vertical/tournament-registration/blog/entry-fees-splits-and-when-the-money-lands/ (reviewed 2026-08-09)