Your product stopsat the terminal.

A ground transport partnership lets a company offer chauffeured transfers to its own customers as part of its own product, using RYDES supply, pricing and operations underneath. The partner controls the customer experience, the branding and usually the price, while RYDES fulfils the ride through licensed local operators in 1,200 cities. It differs from a business account, where an organisation books transport for its own staff or guests rather than selling it onward.

Six: a deep link to a branded page, a tracked referral or affiliate link, a white label booking flow in your brand hosted by us, a fully embedded API inside your own interface, loyalty earn and burn, and bundled benefits attached to a fare class, tier or card. Most partners start with a deep link and move to an embedded API once volume justifies the engineering.

Typically four to eight weeks for a standard embedded integration, and two to four for white label. A deep link can be live within days. Loyalty earn and burn typically takes six to twelve weeks because it involves your programme's own systems as well as ours. Sandbox credentials are issued the same week the agreement is signed.

You do. Customers who reach us through a partner are not added to our marketing, not sent promotional email, and not contacted after the ride for anything other than the ride itself. That is a contractual term rather than an assurance, because it is the first thing any serious partner asks and it should not rest on trust.

Either you take a share of each completed ride at retail pricing, or you buy at net rates and set your own price, keeping whatever margin you choose. Share is settled on a periodic statement with a machine-readable reconciliation file that matches it. Cancelled and no-show rides do not earn share, and equally are not charged to you. The rate is set out in your partnership agreement.

Yes, on white label and embedded models. Confirmations, notifications and travel documents can carry only your identity. The chauffeur arrives in business dress in an unbranded premium vehicle, so nothing about the ride itself contradicts your branding either.

Both. Earn attaches points to ground spend that was previously invisible to your programme because it happened at a kerb. Redemption lets members pay for a transfer in points, which is a genuinely useful low-tier redemption: it costs the programme far less than a seat, it is used on a day the member is already travelling, and it is remembered. Earn rates, redemption rates and eligibility are yours to set.

Quoting, availability, booking, amendment and cancellation, webhooks for chauffeur assignment and journey status, live tracking, and reconciliation. Fare components are broken out so you can display or repackage them as your product requires, and the cancellation window is returned on every booking.

Yes, a full test environment with deterministic scenarios covering the awkward cases: delayed and cancelled flights, no-shows, waiting overruns and failed payments. We would rather you build against those first than discover them with a customer in a car park.

Your choice. Our 24-hour dispatch can handle it directly, in your name if you prefer, with the outcome reported back to you. Or you can own first line and escalate to us, which some partners prefer where the ride is one part of a larger itinerary they are already supporting.

A periodic statement covering completed rides, fares, add-ons, cancellations and revenue share, with a matching machine-readable file so your finance team is not reconciling a PDF. Currency and period are agreed in the partnership agreement.

We receive the passenger details needed to deliver the ride and share them with the local operator only to the extent required to complete it. Ride data flows back to you. We do not market to your customers. Contractual data protection terms form part of the partnership agreement, alongside our published privacy policy.

We would strongly prefer it. One city or one route pair, real customers and real money, is enough to read conversion and attach rate while nothing is at stake. If the pilot works, coverage opens across the markets you want. If it does not, we would both rather find out after one city than after twenty.

Rarely, and never as an opening position. Category or market exclusivity can be discussed at meaningful committed volume, but it usually serves neither side: it constrains our coverage and it means you are carrying a commitment before you know whether the product converts. Prove it in one market first and the conversation becomes a real one.

Placement in your product, an idea of where your customers actually travel, a technical contact during integration and a finance contact who reads statements. On net rate models you also set the retail price. Beyond that, the supply, the fulfilment and the operations are ours.

No. If you run a licensed chauffeur company and want to receive bookings from RYDES rather than send them, you are looking for the supply side of the network. That is Drive with RYDES, where operators apply to join, keep their own brand and fleet, and take prepaid rides in their market.