Skip to content

Sell tours direct, without the cut

Book tours and activities direct in stablecoins, paid to your Paymos balance at checkout — the booking is yours before the group sets out, and no one can claw it back once the experience has run.

Sell tours direct, without the cut

Where small-operator margin disappears under booking platforms

Why does a sold-out tour still net the operator so little?

Four ways platforms and card rails thin out tour revenue before you've paid the guides — the marketplace cut, the fee on direct, the weather refund dispute, and the exchange-rate loss charged twice.

The experience marketplaces price commissions high

GetYourGuide now defaults to a 25–30% commission and Viator runs 20–25%, with card processing layered on top. On a typical day tour, that's roughly a fifth to a third of the price gone to the platform before the operator pays guides, venue, insurance, and inventory. Small-tour operators routinely report net margins under 10% after platform fees and direct costs. The flywheel works for the marketplace; the operator's economics are squeezed.

And the card fee stacks on the bookings you DO drive direct

For every guest you pull off the OTA to your own booking page you save the commission, then immediately pay the card processor. On a standard 2.9% + $0.30, a $99 tasting costs about $3.17 to accept — roughly 3% effective. Far better than 25%, but still a real bite in a business where the operator's net was already thin.

A weather cancellation can come back as a chargeback

Tour and experience acquiring sits in the elevated-dispute tier. Weather forces a cancellation, you offer a reschedule or partial refund per your terms, and the guest disputes at the card anyway. The up-to-120-day dispute window means a spring booking can chargeback months later — long after you've paid guides for the rescheduled date and committed to inventory. Acquirers price this with surcharges and case-by-case reserves on smaller operators.

International tourists get hit by the exchange rate twice

A boutique operator in Cape Town booking US, German, and Australian tourists pays a processor 1–2% in currency-conversion margin on every transaction — and the guest separately pays their own bank's 1–3% foreign-transaction fee. Two layers of conversion loss on the same booking, and you field the "why is my statement higher than the price" complaint. (Side-by-side in Pricing.)

How direct bookings work in stablecoins

What changes when the booking settles in stablecoins?

Sell the tour direct on a wallet, not a platform, and four things go the operator's way.

A weather refund is your call — no chargeback path

A stablecoin payment has no chargeback mechanism. Once the guest signs the transfer, there is no panel to override your written weather-cancellation policy. Reschedule, partial refund, full refund — all on your terms and your timeline, not the card network's dispute clock. The issuer's habit of siding with the cardholder — the reason this category runs high-dispute on cards — never gets a vote here.

The money is yours the same day, not on an OTA hold cycle

The platforms hold operator payouts on weekly-to-monthly cycles, often tied to tour completion. On Paymos the guest pays and the funds land in your Paymos balance within seconds of confirmation. For an operator paying guides on tighter cycles than the platform pays you, you stop financing the float and become cash-positive within the same booking cycle.

Tourists worldwide pay, with no currency conversion on either side

Price the tour in a dollar stablecoin and each guest abroad pays the same stablecoin they already hold — no currency-conversion margin for you, and no foreign-transaction fee for the tourist. No surprise "why is my statement higher" support email, and the booking that used to fail on a foreign-card decline now confirms in seconds.

Roughly $0.99 to accept a $99 tour, not $3.17

That same $99 tasting costs about $0.99 to accept on Paymos instead of roughly $3.17 on a card processor — and you keep the difference on every booking, with no per-transaction minimum, no high-risk surcharge, and no separate currency-conversion charge. Full rate card in Pricing below.

Experience flows on stablecoins today

What experience patterns run cleanly on a wallet?

Four flows from working operators and marketplaces — single ticket, deposit-plus-balance, milestone, and platform billing.

Single-ticket tasting tour — Hosted Checkout

For a tasting tour, issue the ticket invoice from the booking system. The guest pays from their wallet, and confirmation secures the place before the group departs. The sale does not incur a marketplace commission.

Private guided day-tour with a deposit — Hosted Checkout

A private guided day-tour where you take a deposit at booking and the balance on the morning. The guest signs the deposit today and the balance when it's due — two clean separate payments, no mid-tour card hold to dispute and no surprise balance-charge complaint after the day is done.

Bespoke multi-day expedition — Payment Link milestones

A bespoke multi-day expedition billed in stages — a slice at booking, more a month out, the balance on arrival. You send a payment link from your CRM at each milestone and the client signs each as it falls due. No card on file to expire across a long-lead booking, and each milestone is final once it confirms.

Operator-platform subscription — monthly renewal invoice

A calendar SaaS for indie operators charging a monthly subscription. Each cycle your system issues a renewal invoice the operator pays from their wallet — no card on file to expire and no involuntary churn. The subscription just renews on its own rhythm.

Tours and experiences on stablecoins

Frequently asked questions

How does same-day operator payout work compared to an OTA hold cycle?
The guest pays, the transfer confirms on Base or Polygon in a couple of seconds, you receive an HMAC-SHA256 webhook with the settlement event, and the funds are in your Paymos balance the same minute as the booking. The big platforms hold operator payouts on weekly-to-monthly cycles with completion-confirmation conditions. The difference matters most for operators paying guides on weekly cycles: instead of financing platform float, you're cash-positive within the same booking cycle.
What happens with weather-cancellation refunds, including same-day cancel-and-reschedule?
Weather-cancellation refunds are governed entirely by your written weather policy, and on the wallet rail you keep all of the operator-side decision power. A typical outdoor operator runs three branches: same-day weather cancellation (full refund or free reschedule, guest's choice), partial-weather operation (tour runs with modifications, no refund), and an operator-initiated reschedule for safety (full credit toward another date). Each branch is an explicit policy outcome — your booking system picks the branch, optionally fires an outbound refund transfer from your Paymos balance, and emails the guest the result. No chargeback panel can override your weather policy after the fact. On the Paymos side, the fee applies only to the tour payment that actually settled — issuing a weather refund doesn't add a charge on top.
Can we run a multi-operator marketplace and split payment to operators?
Yes — the server-side API supports marketplace-shape flows. The guest pays the platform invoice, your platform treasury receives the stablecoin, and you initiate outbound transfers to operator wallets per your rev-share contract (commonly 80/20 or 85/15 in the experience-marketplace space). No Stripe Connect per-operator KYC contract and no platform-account-holder regulatory ladder. Operator onboarding is just a wallet address — they're already self-custodial.
How does this work for operators in countries with weak card-acquiring?
This is most relevant for operators in LATAM, MENA, Southeast Asia, and parts of Africa, where local card-acquiring rates run high and onboarding takes weeks. The wallet rail bypasses local acquiring entirely — operator onboarding is near-instant, settlement is global, and you can keep a stablecoin treasury or convert to local fiat on an OTC desk schedule. The infrastructure-arbitrage advantage is real for non-EU/US operators.
Does this work for very small add-on experiences like food-tour stops?
The cost math works, but the UX math is tighter. At very low ticket prices, the wallet sign-and-pay flow adds friction the conversion rate can struggle to absorb. Offer wallet as an option, not a default, and let the customer pick. For impulse-buy add-ons, instant-card UX often still wins; for planned higher-value experiences, wallet conversion is clean.
Which networks fit the tour-ticket range best?
For lower-priced tickets, Base and Polygon dominate — fees under a cent make per-booking economics work. For higher-value private tours and bespoke expeditions, Ethereum picks up trust share. USDT-TRC20 is widely held among tour bookers in Egypt, Morocco, and similar MENA destinations — letting those tourists pay without an international-card decline is the realistic local pattern. Let the guest pick at checkout; they know which wallet has balance.

Honest disqualifier

When NOT to use Paymos for tours and experiences

Four operator profiles where the platform or the terminal still wins.

The marketplace's search results are your only storefront

If GetYourGuide or Viator delivers nearly every guest, the commission is your entire acquisition budget — and switching payment rails recovers none of it. Paymos cuts the cost of the bookings you drive yourself: your site, your socials, your repeat guests. Until that channel exists, the platform fee is the price of being found.

You need bookings split automatically between operators

Paymos settles each booking whole, into one treasury wallet. A marketplace that needs every payment divided at the source — operator share here, platform fee there, instantly — is describing Connect-style sub-accounts, which this rail doesn't have. You can pay operators yourself with batch transfers to whitelisted wallets, but the splitting logic and its bookkeeping live on your side.

You sell by the pier, in cash, with no booking page

A walk-up tour business running on cash and a local card terminal has no online checkout for Paymos to improve. The wallet rail starts paying off the day you take your first direct online booking — before that, there is nowhere to plug it in. A basic booking page comes first; the rail question comes second.

Impulse add-ons at single-digit prices

A $9 food-stop add-on sells in the three seconds the guest is already excited, and any extra screen kills it. A wallet payment is a deliberate act, and deliberation is what an impulse buy can't survive. Let cards carry the add-ons and bring the wallet out for the planned, higher-ticket experiences where its economics actually show.

Pricing

1.0% per settled booking. No OTA commission, no exchange-rate margin

Same rate for the $99 tasting and the $5,000 bespoke expedition — about $0.99 on a $99 tour versus roughly $3.17 on a 2.9% + $0.30 card processor, before any currency conversion. High-volume tier at 0.3% on request. No high-risk acquiring surcharge.

See pricing

Keep the margin on every booking you drive direct