No booking platform can natively integrate every bank, acquirer, and payment processor on the planet — there are simply too many, each with its own API and quirks. That's the problem Spreedly solves. Through a single Spreedly connection, TicketingHub can route your payments to more than 100 international payment gateways, so you can keep the merchant account and banking relationship you already have and still take payments directly inside your booking widget.
What is Spreedly?
Spreedly is a payment orchestration platform: a secure layer that sits between a software product like TicketingHub and the world's payment gateways. When a customer pays, their card details are captured and tokenised by Spreedly over securely encrypted connections — so sensitive data is never exposed — and the transaction is routed to the gateway of your choice. One integration on our side unlocks over 100 processors on yours, without configuration time or clunky workarounds.
Why this matters for tour and attraction operators
- Keep your bank: if you already have a merchant account with a specific acquirer — often with negotiated rates — you can keep it and still use TicketingHub.
- Operate where Stripe can't: Stripe has country limits and is not currently fully supported in some markets (for example Egypt, Pakistan, and Turkey). Spreedly opens up local and regional gateways in those markets.
- Pay in the widget: guests enter card details directly in the TicketingHub booking widget — no redirect to a third-party payment page.
- No extra platform cost: TicketingHub covers the Spreedly costs as part of the integration.
How the integration works
From your guest's point of view, nothing unusual happens: they pick a tour, enter card details in your booking widget, and get a confirmation. Behind the scenes, Spreedly tokenises the card, routes the charge to your connected gateway, and the funds settle into your own merchant account. TicketingHub never stores or accesses card data at any point.
On the money side, this works like our other invoiced gateways: your gateway pays you directly, and TicketingHub invoices its fees separately for reconciliation — unlike Stripe, where fees are deducted automatically per transaction.
Who uses it
Operators in markets Stripe doesn't fully cover
A tour company in Cairo or Istanbul still needs slick online card payments. Via Spreedly, they connect a regional gateway that works with their local bank, and their TicketingHub widget takes payments just like an operator in London or New York.
Larger attractions with an existing acquiring deal
Attractions processing serious volume often have hard-won rates with a specific acquirer. Spreedly means switching to TicketingHub doesn't mean renegotiating payments: the existing gateway plugs straight in, and finance keeps the reporting relationships they know.
Multi-country operators mixing gateways
A brand running tours in several countries can route each region through the gateway that suits it best — one that handles local cards and currencies well — while all bookings land in the same TicketingHub dashboard.
How to connect a gateway through Spreedly
- Check that your gateway appears in Spreedly's supported gateway list at spreedly.com/connections.
- Ask TicketingHub support for the connection requirements for that gateway — the required credentials differ per provider.
- In the dashboard, go to your supplier name → Settings → Integrations → Payment Providers.
- Find Spreedly, select Activate, and follow the provider-specific instructions supplied to you.
- Make a low-value test booking, confirm the order is paid in TicketingHub, and check the transaction in your gateway's dashboard.
Use only credentials from the gateway account you control — never example credentials from generic developer documentation. Sandbox availability varies by gateway, so confirm testing options with your provider or TicketingHub support first.
