We are the merchant of record. You never become a travel agency.
Adding flights sounds like an integration problem. It is not. Every path in hands you a business you did not ask to run.
You get the inventory, and the role with it. You become the seller of record: you take the payment, you carry the chargeback, you answer the phone when a flight is cancelled at 2am, and you meet the consumer-protection obligations that come with selling travel.
Fast to ship, and it costs you the thing you were trying to protect. Your user leaves your product at the exact moment they spend money, lands on someone else's brand, and you earn a thin slice of a transaction you no longer control or see.
Supplier contracts, accreditation, a settlement bond, payment infrastructure, refund logic, fraud controls, ticketing operations. All of it before you sell your first seat, and none of it is the product your company is for.
This is a legal position before it is a technical one. GoGlobe holds the supplier relationships and sells the ticket. Your product holds the customer.
Corporate is priced by agreement, not from a table. We size the deal against your volume and vertical, and you get one contract covering flights, hotels and everything around them.
Business identity and ownership are checked once. We then switch on your account, your booking seats, your API access and SSO if you use it.
Put travel in your product with a widget, a branded page or a deeper integration. Every booking is attributed to you automatically and appears in your dashboard against its own reference.
| Direct supplier | Affiliate links | GoGlobe Corporate | |
|---|---|---|---|
| Time to launch | 6–12 months | 1 day | 1–2 weeks |
| Merchant of record | You | Them | GoGlobe |
| Chargeback exposure | Yours | None | GoGlobe's |
| IATA accreditation | Required | Not required | Not required |
| Settlement bond | Required | Not required | Not required |
| User stays in your product | Yes | No | Yes |
| Refunds and support | Yours | Theirs | GoGlobe's |
| Ongoing operations cost | High | None | None |
Your rate is agreed per contract rather than taken from a published table — either as a share of the margin we earn, or as a percentage of booking value where that is easier for you to model.
As many of your people can book as need to. Seats are the people who book; the travellers they book for are unlimited on every plan.
Production API keys alongside the widgets, so you can build the search and results experience yourself and hand over only at checkout.
SAML and OIDC, so your staff sign in with the identity provider you already run and joiners and leavers are handled where you already handle them.
Reference, route, value, what you earned and where it stands — filterable by date and type, and exportable as CSV whenever you need to reconcile.
Earnings are released once verification is approved and paid out to your own account by SEPA transfer. Not vouchers, not points, not credit against future travel.
The terms that actually affect what you earn, stated plainly rather than buried.
What you earn is a share of what we earn, so there has to be something to share. A booking made outside your integration earns nothing.
Where a rate is agreed as a percentage of booking value, it is paid up to the net margin that booking actually produced. We never pay out more than a booking earned, and a thin-margin fare pays less than the headline rate.
If a booking is cancelled, refunded, charged back or no-showed, the margin goes with it and the accrual is reversed on your next statement.
Business identity and ownership are verified, and the destination account must belong to your company. Earnings accrue from the first booking and are released in full once that is approved — nothing is forfeited by the wait.
You build and test against sandbox credentials where no real booking is made. Sandbox activity is recorded and is worth exactly zero, by design.
What you receive is income or a cost reduction depending on your treatment, and VAT may apply. Amounts are gross. Take your own advice — we cannot give it.
We will scope the integration, agree the commercial terms and give your engineers a sandbox key before anything is signed.