Partner Operations Guide
GNet Platform
How We Work With Partners
How We Work With Partners
GNet is the execution layer — not the commercial layer. Contracts, vetting, SLA discussions, and pricing negotiations happen directly between operators, outside of GNet. Once that groundwork is done, GNet handles the electronic trip exchange — efficiently, at scale, in real time.
All vetting, SLA discussions, contract signing, and pricing negotiation happen directly between the two companies — outside GNet. GNet doesn't facilitate or replace this step.
Click "Add Partner" to send a connection request. Partner receives email + in-app notification. They must explicitly accept or decline — not automatic. Both sides need verified GNet Connect accounts.
One-time setup: agree on vehicle type mapping so both systems speak the same language (e.g. "Luxury Sedan" = same class on both ends). After that, trips can flow.
You can search the full network and connect with operators you've never worked with before. GNet Connect's verified documents help you feel confident — but your own due diligence still applies.
Operators across 80+ countries available on GNet Connect for discovery and connection.
Submit a standard trip payload via the GNet Platform API with reservationType: "QUOTE". GNet routes it to the partner's rate engine. No reservation is created on either side.
The partner's system responds with a totalAmount. Most mature platforms (LimoAnywhere, FASTTRAK) handle this natively. Others use GNet's GRate or LimuRate engines.
To convert the quote to a real booking, resubmit the same payload — same requester GNet ID and same requester reservation number. The reservation lifecycle begins: CONFIRMED → ASSIGNED → EN_ROUTE…
Quotes require an established partner connection. The receiving partner needs a customer account number to process the quotation.
No system-level TTL. In practice the gap between quote and booking is typically just a few minutes. Re-quote if meaningful time passes.
Provider marks trip as COMPLETE. If the provider hasn't done so within 24 hours, GNet auto-marks it COMPLETE.
The provider must still submit CLOSE with final charges. GNet does not force this step — it waits for the provider to input and close the trip.
When a requester pushes a change (e.g. pickup time), the driver can respond with ACKNOWLEDGED — you receive this via webhook as confirmation the update landed.
Each extra is delivered as a structured item in the fees webhook payload:
Each item: type · currency · description · amount
Any chauffeur update triggers a new webhook callback with the replacement driver's name, phone number(s), ID, and profile picture. Not just the initial assignment.
GNet transmits what the provider reports — it doesn't adjudicate. Any discrepancy between GNet-reported charges and a final invoice is resolved bilaterally between the two operators.
The requester provides a credit card. The provider charges per transaction or on a set interval (weekly, monthly). Simple to set up, no manual invoicing overhead.
Weekly, bi-weekly, or monthly invoice batches between partners. Standard for high-volume relationships where batching transactions is more efficient for both sides.
GNet has no payment rails. No predetermined payment rules for marketplace vendors. All settlement is agreed and managed directly between the two operators.
If a provider requires advance payment for a booking, that conversation happens between the two operators. The trip proceeds through GNet regardless of the payment arrangement.