inDrive-style Fare Marketplace — Custom-Built for Your Market

Two drivers answer the fare proposal; only one can receive the ride

A passenger proposes a fare, receives two counteroffers and selects one as the phone loses connectivity. The second driver changes their price while the first driver accepts another booking. A list of prices cannot resolve this moment. The product needs a current trip request, an identifiable offer, an available driver and one durable commitment that both parties can recover when their screens reconnect. That agreement is the centre of a negotiated-fare marketplace.

An inDrive-style app lets passengers propose journey terms and choose among eligible driver responses rather than accepting an opaque automatic assignment. This is independently branded software, not another platform’s network, proprietary code, licences or support service. Buyers need to decide where negotiation is permitted, which obligations the operator holds and how the accepted terms survive pickup, journey changes and payment disputes. Attractive prices alone do not establish a viable local mobility operation.

Separate a fare suggestion from a passenger proposal

The official inDrive passenger walkthrough describes proposing a fare and choosing a driver response using price, vehicle and rating information. It is a reference for the interaction model, not a specification of your launch market’s fare rules or a guarantee of lower prices. State which information is advisory and which amount becomes part of the accepted trip.

If the interface suggests an amount, explain the relevant assumptions and whether the passenger may change it. Avoid calling a recommendation a guaranteed final price. Validate permitted amounts, currencies and disclosed charge components before broadcasting the request. Toll treatment, waiting charges and payment method should not remain hidden until the driver arrives. A participant must be able to read the same terms on the offer screen and on the confirmed trip receipt.

Attach every counteroffer to a request version and an expiry

A passenger changes the destination after three drivers have responded. Those responses belong to the earlier journey, not the revised route. Preserve request versions and expire or reconfirm affected offers under the agreed rule. Each counteroffer needs its driver, amount, currency, applicable terms and validity time. Keep withdrawn, expired, selected and rejected responses distinguishable so a returning participant does not mistake old interest for present availability.

Use the server’s acceptance decision rather than a device countdown as the authority. A delayed push notification can arrive after an offer expires; opening it must show the current status instead of silently selecting another price. Keep the original response in restricted history for disputes. Test a destination edit, an expired counteroffer and an out-of-order message with the passenger and driver screens open together. The buyer should see exactly why the old response cannot be committed.

Make passenger selection a single ride commitment

Two quick taps or a retried request must not reserve two drivers. At selection, recheck the offer version, validity, driver eligibility and availability before creating one commitment identifier. Close competing offers only after the selection succeeds. If the chosen driver is no longer available, explain the failure and return the passenger to current choices rather than substituting a provider or increasing the fare without approval.

The driver also needs an unambiguous distinction between responding to a request and being selected for it. Define whether their response reserves capacity and for how long; competing requests must use the same availability rule. After reconnecting, both participants should recover the same selected vehicle, journey and fare. Rehearse simultaneous selections and duplicate network retries. A successful animation is not enough if the operations console contains two accepted trips for one passenger request.

Compare drivers without turning the cheapest offer into a safety claim

Price is one selection input, not a measure of professional suitability. Show the vehicle facts, relevant driver eligibility and rating context that the operator can substantiate. Explain sorting and any sponsored placement. Do not imply that a paid provider tier certifies safer conduct or that a high rating replaces local checks. Drivers need enough journey information to respond responsibly without unnecessary access to the passenger’s identity or private routines.

Define what competing drivers can see about each other’s offers. An unrestricted bidding feed can encourage pressure, harassment or coordinated conduct. Review offer limits, withdrawal rules and report handling for the launch market. Keep repeated declined bids distinct from misconduct evidence; not every negotiation failure deserves an account restriction. Operators should explain the basis of a decision and allow appropriate review rather than presenting an unexplained score as proof of fairness.

Protect pickup details before a driver has a confirmed reason to use them

Broadcasting a precise home address to every nearby bidder can disclose more than the negotiation needs. Decide which approximate route information is sufficient before selection and when exact pickup details become available. Restrict telephone numbers, location history and personal notes by participant role. Sensitive details should not leak through notification previews, public ratings or support exports. Retention and lawful access requirements need review for each operating market.

After cancellation, remove access that is no longer needed while preserving restricted evidence required for a legitimate investigation. A driver should not keep live location access because they once submitted an offer. Distinguish a passenger’s manually chosen pickup point from GPS position and show uncertainty where relevant. Test a withdrawn response, a blocked account and a completed ride against location permissions. Privacy failures are difficult to repair after personal data has already been distributed.

Confirm the selected driver and vehicle at pickup

The official inDrive passenger safety guidance advises checking driver and vehicle details and sharing trip information with a trusted contact. These are useful preparation references, not evidence that your app includes that company’s safety team or guarantee. Define your operator’s own incident channels, responsibilities and limits before offering safety controls.

A passenger who sees a different vehicle needs a clear way to stop the pickup and report the mismatch. Preserve the selected vehicle record and the driver’s current eligibility status rather than overwriting them with a later profile edit. The driver also needs a reviewed response to an unexpected passenger or unsafe pickup situation. Document when local emergency services should be contacted. Software can surface information and route reports; it cannot replace emergency responders or guarantee safe travel.

A destination change needs a new agreement, not an edited receipt

An extra stop changes travel, waiting and cost after the fare has already been agreed. Create an amendment with the requested change, revised terms and explicit participant acknowledgement. Preserve the original agreement and the amendment history. Decide what happens if the driver declines or the passenger refuses the revised amount. The interface must not treat a chat message as automatic consent to a new charge.

Use the same amendment rule for pickup changes that materially affect the journey. An operations agent should not rewrite the accepted fare merely to make a disputed receipt match someone’s recollection. Authorized adjustments need a reason, actor and financial consequence, while the original record remains available. Rehearse a rejected extra stop and a disconnected device during amendment acceptance. Buyers should inspect recovery from disagreement before adding more ride categories or complex itinerary options.

Cancellation fees must follow disclosed events and evidence

An unselected offer, a selected driver cancellation and a passenger no-show are different outcomes. Define any applicable fee, grace period, arrival evidence and exception review before commitment. Negotiation timeout should not look like an accepted ride cancellation. A location estimate alone cannot establish that a driver reached the agreed pickup or waited under the stated terms. Keep both participant accounts and relevant event times available for review.

Assign disputed cancellation handling to an accountable queue. Record who requested cancellation, what each participant saw and whether payment was attempted. Prevent automatic fees from being repeatedly issued by duplicate events. Where safety concerns caused the cancellation, keep incident investigation separate from charge resolution so a refunded fare does not close the report silently. Do not copy another platform’s fee amounts or imply universal rules across jurisdictions and operating categories.

Settle the accepted fare without hiding cash or provider uncertainty

Choose the supported payment method explicitly. Cash collection needs an agreed receipt and dispute process; an app cannot prove physical payment from a driver’s button alone. Digital payment needs provider access, authorization rules and reconciliation. Present the passenger total and driver proceeds with the agreed platform charges and taxes. Do not describe an attractive reference commission as an offered commercial term or assume every provider permits the planned transport model.

Connect payment attempts to the ride commitment and preserve pending, acknowledged, failed and unresolved outcomes. If a callback is missing, inspect the provider result before creating another charge. Completion and successful collection are separate facts. Restrict refunds, manual credits and fare corrections to approved staff with traceable reasons. Demonstrate a duplicated callback, an ambiguous payment and an amended fare so the operator can reconcile the ride without altering its negotiation history.

Review fare conduct and transport permissions before opening a city

Participant-led pricing does not remove driver licensing, operating authority, insurance, accessibility or fare-regulation obligations. Qualified reviewers should assess the proposed model for the target market before launch. Scope minimum permitted offers, vehicle categories, working arrangements and required disclosures from that review. A software feature list is not a legal approval, and an identity check is not proof that the driver may operate the proposed service.

Compare a Bolt-style mobility operating model when automatic assignment or multiple transport categories better fit the business. Do not add negotiation just because another brand uses it. The choice changes response times, availability commitments, price communication and support workload. Keep the first release within a service zone and category the operator can supervise, then evaluate expansion using actual exceptions rather than a promise of instant marketplace liquidity.

Rehearse a disputed selection before signing off the marketplace

Illustrative screens explain the intended passenger and driver surfaces; they do not prove a working driver network, permitted payment integration or ready emergency operation. Request a controlled walkthrough with sample offers and sandbox services. Change a destination after responses arrive, select an expired bid, interrupt connectivity and trigger simultaneous acceptance. Confirm which offer survives, what each participant sees and who resolves the exception.

Buyer acceptance should also cover vehicle mismatch, an unapproved extra stop, a safety cancellation and an uncertain charge. Inspect keyboard access, readable mobile comparisons and protection of pickup details. Require a scope that distinguishes configured components, new engineering, third-party dependencies and operator responsibilities. The acceptance evidence should show agreement recovery and payment accountability, not only a moving vehicle icon or a grid of attractive prices.

Bring your fare policy and one disputed-ride example to a negotiated-fare marketplace scope discussion. Agree source ownership, integration rights, operational review and handover access in the applicable contract.

Use the delivery process to set checkpoints for offer integrity, pickup rehearsal, privacy review and support training before launch.