One booking. The money lands in a wallet you control.
A booking is rarely one company's money. The payment goes to a wallet your platform controls, and it is yours once the network confirms it. Paying the other parties stays in your hands — transfers you send from your own wallet, on your own schedule. If your customer pays by card or bank transfer, the company that takes that payment sets any holds, reserves, disputes, fees, limits or delays on that side — not us.
The problems start when the money moves slower than the trip.
Collecting on behalf of everyone else
The usual pattern is that the platform collects the full booking, sits on it, and remits each party's share later. Holding money that belongs to an operator or a partner means float to manage, trust to maintain, and — depending on your business model and jurisdiction — obligations of its own to analyse.
The booking money goes to a wallet your platform controls, and it is yours once the network confirms it. Paying each party their share is a transfer you send from your own wallet, on your own schedule — Zoyn is not in that flow. If your customer pays by card or bank transfer, the company that takes that payment holds it first, on its own terms.
Reconciling lump settlements by hand
One booking often owes an operator, the platform, a guide, and a local supplier. When the money arrives as a single lump, that division happens days later, in a spreadsheet, and every correction is a manual transfer.
Once the network confirms the booking payment, the money is in your own wallet before you pay anyone — so you are paying out of money that has already arrived, not money you are still waiting for. Every payment in and every payment out is publicly verifiable on Base, and the dashboard exports the full history to CSV for your accountant.
Long fulfilment cycles get penalised
Travel is a long-fulfilment category on card rails: a deposit taken months before departure sits inside the acquirer's dispute window the whole time, and card acquirers commonly respond to that risk with rolling reserves held for months.
On-chain settlement is treated as final after the required network confirmations. Card- and bank-funded methods remain subject to provider reserves, holds, disputes, fees, and processing times.
Paying overseas operators and suppliers
A supplier abroad usually means a wire, a correspondent bank, a currency spread, and days of float between the traveller paying and the operator seeing the money.
Paying an overseas operator or supplier is a USDC transfer you sign from your own wallet. Timing remains subject to required network confirmations and network conditions.
From booking link to settled wallets.
Create the booking link
Set the amount and the booking reference. The link is yours to send from your platform's own flow — email, invoice, or checkout handoff.
The traveller pays a link
Card or crypto on a secure hosted checkout. The card company may ask a card payer to confirm some details or verify who they are — those checks belong to that company, not to Zoyn. A traveller paying from their own crypto wallet is asked none of it. The traveller never needs a crypto wallet or crypto knowledge to pay by card.
The money lands in your wallet
Once the network confirms the payment, the money arrives in a wallet your platform controls, in the currency set on the link — USDC by default. It gets there through a contract that pays your share and the platform fee in proportions fixed when it is set up, and publicly verifiable on Base.
Pay every party from your own wallet
Paying operator, guide and partner wallets is a USDC transfer you sign from your own wallet, on timing you control and subject to network conditions — Zoyn is not in that flow.
What we support — and what we check.
Category
Travel agencies, tour operators, and lodging (MCC 4722 and 7011) are supported categories on our published accept list. Your declared category is checked at signup, and every application is screened — a supported category is a prerequisite, not a promise of approval.
Restricted lines don’t ride along
Some categories are not supported at all — gambling and wagering among them — and are blocked at signup. If your platform bundles a restricted line into its packages, or your business sits adjacent to one, ask us before applying rather than assuming. The live accept list is public.
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.
Every wallet is screened
Beneficiary wallet addresses — your platform’s payout wallet and every payout recipient’s — are screened against an on-chain sanctions oracle when entered and re-screened daily thereafter.
Zoyn is a non-custodial software platform, not a payment processor or money transmitter, and does not provide legal or compliance advice. Whether your own platform has regulatory obligations for the way it handles bookings depends on your business — that analysis is yours and your counsel’s to make.
Running a single agency rather than a multi-party platform? The travel & tourism industry guide covers bookings that settle to one merchant, including deposits and refunds.
Zoyn is a non-custodial software platform — not a payment processor, payment gateway, money transmitter, or merchant of record. Funds settle on-chain directly to wallets the recipients nominate after required confirmations; Zoyn does not custody those settled funds. Checkout and on-ramp providers operate under their own terms before settlement.
Stop waiting on everyone's money.
Take the booking, settle after the required confirmations, and pay every party on timing you control, subject to network conditions, with a payout you sign. We screen every application.