Settle tonight's covers tonight.
Restaurants and hospitality operators (MCC 5812) run on daily cash and thin margins, yet card settlement lands in a later batch and staff are paid out of the float in between. On-chain settlement, final once confirmed, puts the day's takings in your hands on the day.
The problem is the gap between paying and travelling.
Yesterday's takings arrive tomorrow
Card settlement runs on the acquirer's batch cycle, so the cash for tonight's service turns up after the produce order it was meant to pay for. On a thin margin that float is expensive.
Smart-contract vault settlement on Base L2, final after the required network confirmations — the day's payments land as they confirm, into a wallet you control.
No-shows and disputed event deposits
Deposits for large bookings and private events are taken weeks ahead, which puts them in the acquirer's dispute window and makes them a reserve candidate in a category already watched for no-show disputes.
No card-network chargebacks on the on-chain leg, and settlement treated as final after the required network confirmations, so a deposit you have taken is a deposit you have.
Paying shift staff out the same night
Rotating shift rosters mean many small payouts, each with its own bank cut-off, funded from money that has not settled yet.
Settlement reaches your wallet that same night, so staff are paid out of money that has already landed — a USDC transfer from your own wallet, with no bank cut-off to plan around.
One payment, settled to a wallet you control.
Create the booking or bill link
Set the fixed amount for the deposit, the event bill or the table, and add your booking reference.
Guest pays their way
Card or crypto on a hosted checkout. Card availability depends on the buyer's location, currency, and available checkout providers. Card-funded payments are handled upstream by integrated global on-ramp bridges — card data never reaches your floor.
Split contract routes the payment
Shares are fixed in bps when the contract is deployed: your share and the platform fee. Every payment follows them exactly, verifiable on a public block explorer.
USDC lands in your vault
Smart-contract vault settlement on Base L2, final after the required network confirmations, into a wallet you control — available the same night for the morning's suppliers and the people you pay.
Where we can onboard you today.
Category
MCC 5812 and 5814 are supported categories in this group. Your declared category is checked at signup.
Jurisdictions we cannot serve
We cannot onboard merchants operating from comprehensively sanctioned jurisdictions. A US state stays open when at least one checkout partner still serves buyers there. We do not hold ourselves out as licensed anywhere.
Wallet addresses you'll be paid to are checked against sanctions lists when you enter them, and re-checked every day after that.
What restaurants & hospitality merchants ask first.
Is this for the till, or for bookings and events?
Bookings, event bills and deposits are the strongest fit today, because each one is a fixed-amount link you create and send. It sits alongside whatever you use at the counter rather than replacing your point-of-sale hardware.
A party cancelled. Can they claw the deposit back through their bank?
Not on the on-chain leg. Zoyn does not reverse a settled payment, so your cancellation terms decide what the party gets back and when — and you send that refund yourself, from your own wallet, with no card-scheme dispute fee attached.
How does paying staff work?
Outside Zoyn — you pay staff yourself, from your own wallet, on your own schedule. Zoyn is a payment-link platform and is not in that flow; what it changes is that the night's takings are settled and available before the pay run, instead of sitting in an acquirer's batch.
Looking for a different sector? See every supported industry.
Put the day's takings in the day's account.
Create a booking link, take the deposit, and settle before service starts.