The tour operator's guide to Yoco

Yoco processes payments for the large majority of the South African tour operators we talk to — not because it's the only option, but because it's the one built for how small businesses here actually get paid: a card tapped at the meeting point, a payment link sent in WhatsApp, a QR code stuck to the counter of a kayak shed in Hout Bay. This guide walks through exactly what Yoco charges, how and when the money actually lands in your account, what happens when something goes wrong, and how to connect it to a booking system so none of it requires you to sit at the Yoco Portal manually chasing transactions.

If you're comparing Yoco against PayFast, Stripe, or PayPal, we've covered that ground already in our payment gateway comparison. This piece assumes you've picked Yoco, or are close to it, and goes deep on the mechanics — the fees, the settlement calendar, the reconciliation habit, and the integration options — that actually determine whether Yoco is a smooth part of your operation or a source of monthly bookkeeping pain.

What Yoco actually charges

Yoco's pricing is unusually simple for a South African payments provider, which is part of why it's become the default for small tour operators. There's one transaction rate, no monthly account fee, and no minimum volume commitment. The only real cost decision is which acceptance device (if any) you buy for in-person payments.

The flat rate is deliberate — Yoco doesn't run tiered volume discounts the way PayFast does above R250,000/month, and it doesn't charge more for card-not-present transactions the way some legacy processors do. For a tour operator running, say, R150,000/month through Yoco Online payment links, the fee comes to roughly R4,425 — no monthly account fee stacked on top, no terminal rental, no annual contract.

How settlement and payouts actually work

"Next business day" is the headline, but the mechanics matter more than the slogan once you're relying on that cash to pay guides and suppliers on a schedule.

• Daily batching.Yoco batches all transactions from a given business day and initiates the payout the following business day. There's a cutoff — typically mid-afternoon — after which a transaction rolls into the next day's batch instead.
• Weekend and public holiday handling. Transactions taken on a Saturday or Sunday batch together and settle on the next business day — usually Monday, or Tuesday after a public holiday Monday. If most of your tours run on weekends, build this into your cash flow expectations rather than assuming same-day-of-week settlement every time.
• Bank processing time. Yoco initiates the EFT the next business day, but your own bank can add a few hours before it reflects, particularly with smaller or co-operative banks. Budget for funds landing by end of day rather than first thing morning.
• New account ramp-up.The first few weeks after account verification sometimes carry a shorter settlement hold while Yoco establishes a transaction pattern for risk purposes. This normalises quickly and isn't something most operators notice past month one.

The practical upshot for tour operators: next-business-day settlement means a Tuesday booking funds a Wednesday guide payment. That's the entire reason Yoco has become the default over PayFast's weekly batch cycle or PayPal's 21-day new-account hold — for a business paying casual guides and drivers weekly or per-tour, settlement speed is a cash flow feature, not a nice-to-have.

Reconciliation — the habit most operators skip

Yoco's dashboard (the Portal) gives you a transaction ledger, but it doesn't automatically match transactions to specific bookings unless you build that link yourself. Operators running Yoco standalone — generating payment links manually and pasting them into WhatsApp — end up doing this matching by hand at month-end, and it's the single biggest source of "where did this R850 come from" confusion we see.

Three habits fix this without needing new software:

1. Put the customer's name or booking reference in the payment link description every time — Yoco supports a reference field, and skipping it is the number-one cause of unmatched transactions.
2. Export the Portal ledger weekly, not monthly. A weekly export surfaces problems (a refund that didn't process, a duplicate charge) while the booking is still fresh in memory.
3. If you're on a booking platform, connect Yoco via API/webhook rather than generating links manually — every transaction then already carries the booking ID, and reconciliation becomes a non-event instead of a monthly chore.

Refunds and disputes

Tours get cancelled — weather, illness, a no-show, a genuine operator error. Yoco processes refunds from the Portal dashboard with no refund fee, and funds typically reflect back to the customer's card within 5 business days. Partial refunds (useful for a group booking where two of six people cancel) are supported the same way.

Disputes — a customer formally contesting a charge with their bank rather than requesting a refund from you — are uncommon for tour operators. Across the Booking·Tours operator base, disputes sit under 0.3% of transactions, well below the retail or e-commerce average, because a tour booking usually comes with a clear WhatsApp paper trail describing exactly what was purchased. When a dispute is raised, Yoco notifies you and gives you a window to submit evidence — the WhatsApp confirmation thread, the booking record, and proof of service delivery are normally enough to win it.

Integrations — from manual links to a wired-up flow

There are three levels of "using Yoco" for a tour business, and most operators move up this ladder as booking volume grows:

Level 1: Manual payment links

You open the Yoco Portal, create a payment link for the exact tour and price, and paste it into a WhatsApp reply by hand. Works fine under roughly 10 bookings a week. Above that, the manual step becomes the bottleneck — and the reason replies slow down at exactly the moment a customer's intent to book is highest.

Level 2: Templated links per tour

You pre-generate a payment link per tour/date combination and keep a spreadsheet of them to copy-paste. Faster than Level 1, but breaks the moment availability changes — you can send a valid-looking link for a slot that's already sold out.

Level 3: API-connected, availability-aware

Your booking platform holds the live availability, generates a Yoco payment link only for open slots, holds the slot for a short window once quoted, and auto-confirms via Yoco's payment webhook the instant the customer pays. This is how Booking·Tours' AI WhatsApp host operates — the AI drafts the reply, checks real availability, generates the Yoco link, and the booking confirms itself the moment the customer taps pay. No one touches the Yoco Portal for day-to-day bookings; it becomes purely a settlement and reconciliation record.

If you're currently on FareHarbor or a similar platform and paying a percentage commission on top of your payment processing fees, it's worth comparing the total cost — we break this down in detail in our FareHarbor alternative guide. Stacking a booking platform's commission on top of Yoco's 2.95% is a materially different cost structure than a flat-fee platform that uses Yoco natively.

Yoco vs. a traditional bank card machine

Most South African banks still offer merchant card machines, and it's worth knowing the comparison rather than assuming Yoco wins by default.

The bank machine can occasionally win on the headline transaction rate at very high volumes with a negotiated rate, but by the time you add the monthly rental and the slower online payment story, Yoco is cheaper and faster for the volumes most independent operators run — which is why it's become the default rather than the exception.

What this costs on a real month

Take a mid-size operator running R180,000 in bookings a month, split 70% WhatsApp payment links and 30% in-person card taps at the meeting point:

R5,310 on R180,000 is 2.95% blended, exactly as advertised, with no separate monthly account fee to add on top and no minimum-volume penalty if a slow month drops revenue. That predictability is worth something on its own — it's one line in your P&L, not three.

FAQ