Payments · Events
A white-label registration and payment platform used for events at the top of their disciplines — including a World Rally Championship round and Tour de France events — that collects money by card online and by cash at physical payment-network counters, then reconciles both rails automatically against registrations.
Athletes pay however is convenient to them — card or cash at a counter — and organizers get registrations reconciled against payments automatically, instead of chasing down unmatched cash payments by hand.
// the problem
Organizers needed athletes to be able to pay for event registrations either by card online or in cash at a physical counter, with both routes ending up correctly matched to a registration without anyone manually checking payments against sign-ups.
// engineering
Athletes pay online by card, or in cash at a physical payment-network counter using a printed voucher with a barcode. Both routes update the same registration record, so an organizer never has to know which rail a given athlete used.
A scheduled job retrieves settlement files from the payment network over FTP and matches each payment to its registration automatically, including partial payments tracked to completion, without anyone keying a payment in by hand.
Organizers build their own registration form per event, choosing the fields they need. A road race asks for a shirt size and an emergency contact; a rally stage asks for a competition licence, a vehicle class and a co-driver; a cycling event asks for a team and a category. All of it runs on one platform, with no separate deployment per event type.
Group registrations, discount coupons, a full email sequence — pending, partial, accepted, rejected, reminders — check-in by hash on race day, results with split times, and organizer dashboards all run on top of the same registration and payment state.
// result
Organizers ran registration and payment for events at every scale, from local road races to a World Rally Championship round and Tour de France events, with athletes paying on either rail, cash counter settlement files pulled and reconciled automatically on a schedule, and partial payments tracked through to completion, alongside group registration, coupons, check-in and results.
Cash paid at a payment network’s counter and cards paid online land in the same reconciliation job, matched against registrations from a settlement file pulled over FTP on a schedule.
Event-driven backend · Scheduled batch jobs · Relational database · FTP file ingestion · Frontend application layer
Tell us what you're building. You'll leave with an honest opinion, even if it's "you don't need us."
Reference calls with past clients are available under NDA during evaluation.