We use a few small files called cookies. They keep you signed in, remember the area you chose and show prices in your own money. We do not use them for ads or tracking. What each one does
Global payment rails · Multi-currency
OpenDinkers is booking software, not a payment processor. We never touch, hold or route a player's money. What a player pays goes straight to the host's own payment account, or is handed over in person at the court.
Each host picks which of these they accept, so what one host takes is not what another takes.
Players pay the way they already pay for everything else at home. The host is paid in their own currency, into their own account. Each host picks which methods they accept, so this is what a host in each region can switch on.
A host connects the payment account they already have and keeps the whole relationship with it. Nothing is routed through us on the way.
Straight into the host's account
What a player pays clears into the host's own account. There is no balance of ours in between, so there is nothing for us to release.
From the player's payment to the host's account, OpenDinkers is the software that arranges the booking. It is never the party holding the money.
A host switches on the ways they want to be paid and enters their own credentials for each one. Nothing is switched on by default.
The player sees what that court accepts and pays it directly, or arranges to pay in person when they arrive.
We never touch, hold or route the money. There is no platform balance, so there is no payout of ours to wait for.
Players pay into the host's own account. OpenDinkers never holds your takings, so there is no schedule to wait on.
Direct to the host
A host links the payment accounts they already have and enters the credentials each one needs. Where the money lands after that is between the host and that provider.
We store no bank account and no card number
A booking has one payer and one amount, in the court's own currency. What the court charges is the host's number, and we do not add to it.
Priced by the host, in the host's currency
The host writes their own cancellation and bad weather terms. When a booking is cancelled we work out what is owed from those terms and list it for the host to send back.
Not a certificate. Four things about the way the product is built.
A card is entered on the payment provider's own checkout, never on a page of ours. The secret half of each key a host gives us is held in the database's own secret store, not beside the rest of the row.
Row-level security is on every table, and on the files as well. A booking, its payment reference and any proof uploaded against it are readable by that player and that host. Apart from our own small team, who can look a booking up to help with a problem, nobody else can read them.
A court's cancellation terms are shown to the player before they book, then copied onto the booking itself. A host editing them later cannot change what was already agreed.
Most hosts start with a chat thread, a screenshot and a notebook. This is what changes when the booking, the terms and the payment sit in one place.
| What is at stake | With OpenDinkers | By chat message |
|---|---|---|
| Who holds the money | Nobody. The host is paid directly | The host, with no record of what was agreed |
| Ways to pay | 7 to pick from, chosen by each host | Whatever the host can arrange in the thread |
| Two people booking one slot | Refused by the database, not by a person reading a list | Whichever message the host notices first |
Connect the payment accounts you already have, or simply be paid in person at the desk. OpenDinkers never takes custody of a court fee.
The same arrangement, the same keys, the same direct settlement. A player who pays in person hands the money to the host at the desk instead.
The host owns the keys
A host enters their own credentials for each method. A player's payment is handled by that provider and never reaches us.
The wallets and card checkouts people here already use, plus paying in person at the court desk for the players who prefer it.
Wallet or in person
A transfer lands in the host's own wallet. A payment made in person is handed to the host at the court, and the booking shows that this is how the player chose to pay.
A card or wallet payment confirms the court as soon as the provider says it cleared. Transfers and payments in person wait for the host. Either way the player gets a notice in the app, and by email and push where those are on.
We work out the refund. The host sends it.
We hold no player money at any point and no host takings at any point. There is no balance of ours that anybody has to be paid out of.
| Cancellation terms | Written once, shown before booking, copied onto it | Argued again every time |
|---|
