INTRODUCTION
Booking an auto or a cab through Rapido has become an everyday part of urban life for students, working professionals or just anyone in a hurry. With just a few clicks on the smartphone, reaching a destination has become faster than ever. Yet legally, that tap may mark the formation of a binding contract. The Indian Contract Act, 1872[1], enacted in the pre-digital era, continues to govern such app-based transactions.
This blog argues that while booking a Rapido ride broadly satisfies the formal essentials of a valid contract under the Indian Contract Act, the platform’s claim of being a mere “intermediary” complicates issues of privity, liability, and enforceability. The real legal tension lies not just in the contract formation, but in determining who bears responsibility when things go wrong.
SECTION I: PARTIES INVOLVED IN A RAPIDO BOOKING
At first instance, booking a Rapido ride seems to be a simple bilateral transaction between the passenger and the driver. However, a closer legal examination reveals a more complex triangular relationship among the parties.
The contractual framework of a Rapido ride is triangular in nature, involving the user, the platform and the Captain. Determining the nature of the obligations between these parties is crucial to understanding liability under contract law.
Let’s assume a person X wants to reach a destination. So, X opens the Rapido app and enters the destination she wants to reach. X here is the User, and the app is the intermediary and finally, the driver transported to the destination is the “Captain” (as Rapido likes to refer to it).
Interestingly, Rapido, under its terms and conditions, claims to be an intermediary and not a direct service provider. An intermediary is someone who facilitates the main supply of goods or services between two other parties, in this case, the User and the Captain. By doing so, Rapido tries to limit its contractual liability by suggesting that the actual contract exists only between the passenger and the driver.
This claim by Rapido raises the question of privity of contract, which, under Indian Contract law, restricts the enforcement of contractual rights and obligations to the parties to the contract. The classic principle laid down in Dunlop Pneumatic Tyre Co. Ltd. v. Selfridge & Co. Ltd.[2] establishes that a stranger to a contract cannot sue upon it.
If Rapido is truly an intermediary, then liability should lie only between passenger and captain. However, Rapido exercises considerable control over the transaction through the determination of fare, service guidelines and it can also penalise or deactivate bike captains for non-compliance. This suggests that Rapido’s role goes beyond the role of a mere facilitator and may resemble an agency relationship under Section 230 of the Indian Contract Act[3], which suggests that an agent acting for a disclosed principal is generally not liable, unless circumstances indicate otherwise. The degree of control exercised by Rapido invites scrutiny into whether captains act independently or on behalf of the platform.
Hence, a Rapido booking represents a contractual relationship different from the traditional notions of a bilateral contract and challenges the traditional understanding of privity inviting courts to examine the economic reality behind digital platforms like these.
SECTION II: OFFER, ACCEPTANCE AND CANCELLATION
Section 2(a)[4], 2(b)[5] of the Indian Contract Act 1872, a contract is formed only when there is a valid offer and an unconditional acceptance. In the context of Rapido, when a passenger enters the pickup and drop locations, views the option of vehicles and estimated fare, the platform merely displays the potential terms and conditions of the ride. This mere display doesn’t constitute an offer; instead, it amounts to an invitation to offer, inviting the passenger to make the offer. This principle is widely renowned in the case of Pharmaceutical Society of Great Britain v. Boots Cash Chemists[6].
Furthermore, the offer is made when the passenger selects all the desired terms and clicks the “Book Ride” option, expressing a clear intention to avail of the service. At this stage, the offer is open for acceptance or cancellation, and does not constitute a binding contract.
The acceptance takes place when the Captain accepts the ride request through the application. Under Section 7 of the Indian Contract Act[7] the acceptance must be absolute and unqualified. Hence, once the Captain accepts the request and the same is communicated to the passenger via the app, a legally enforceable contract is formed.
In the context of app-based ride bookings, communication occurs through digital networks that may occasionally experience latency. Suppose a Captain accepts a ride, but due to network delay the confirmation does not immediately reflect on the passenger’s screen. During this delay, the passenger may cancel the request, believing it remains unaccepted. If confirmation has not been effectively communicated due to a network delay, it may be argued that no binding contract has yet arisen.
However, another perspective considers that once acceptance is registered on the platform’s server, which operates as the common digital interface for both parties, communication may be deemed complete. In such cases, the platform’s internal system logs could determine the precise moment of contractual formation.
Unlike traditional contracts governed by the postal rule, digital contracts involve instantaneous communication. Courts in India have recognised the binding nature of electronic contracts. In Trimex International FZE Ltd. v. Vedanta Aluminium Ltd.[8], the Supreme Court held that even in the absence of a formal signed agreement, a concluded contract may arise through electronic communication if essential terms are agreed upon.
Section 5 of the Indian Contract Act[9] deals with the issue of revocation of the offer before its acceptance is complete. If a passenger cancels the ride before acceptance is made by the Captain, the cancellation would amount to a valid revocation of the offer. However, if the Captain has already accepted the ride, then any subsequent cancellation, whether by the passenger or Captain, would lead to breach of contract, subject to the terms and conditions of Rapido. The platform imposes cancellation charges as a mechanism to compensate for such a breach. While the Indian Contract Act[10] allows parties to revoke offers before acceptance, post-acceptance cancellation raises questions of liability, damages and fairness, especially in these digital contract settings.
SECTION III: CONSIDERATION, CAPACITY, CONSENT AND LEGALITY
The Indian Contract Act requires lawful consideration under Section 2(d)[11] to form a valid contract. A Rapido booking satisfies this requirement as the passenger agrees to pay the fare in exchange for transportation service provided by the Captain.
The element of Free Consent under Section 13[12] of the Act is fulfilled through user assent by selecting all the options; however, the unequal bargaining powers between the user and the platform, unlike the traditional system, raise concerns regarding meaningful consent.
Further, Rapido clearly states in its terms and conditions that both the passenger and the driver must be of majority age and possess the capacity to contract, as mandated by Section 11[13]. The platform, as stated in the General Covenants section of its Terms and Conditions for Users (Auto and Cab), clearly indicates that users must be at least 18 years of age and not restricted by any legal, regulatory, judicial, quasi-judicial, or other authority from accessing the platform.
Lastly, the contract must have a lawful object under Section 23[14] and in jurisdictions where such bike taxis are restricted, the legality of such contracts may become questionable and render them void. Examples of such instances include Delhi, Maharashtra, Karnataka, and Assam, where Rapido’s bike taxi services have faced bans or temporary suspensions for various reasons, including violation of the Motor Vehicles Act[15].
Together, these elements demonstrate that while a Rapido booking broadly complies with the essentials of a valid contract, its enforceability remains dependent upon various regulatory compliances and fair contracting practices.
BEYOND FORMATION: THE REAL LEGAL QUESTION
The formation of a contract in a Rapido booking is relatively straightforward under classical contract principles. The more complex issue concerns allocation of liability.
Is Rapido merely a facilitator? Or does its algorithmic control, pricing authority, and disciplinary power transform it into a principal?
As gig-economy platforms expand, courts may need to reconsider whether the traditional intermediary shield adequately reflects modern economic realities. Consumer protection law, competition law, and labour law may increasingly intersect with contract doctrine in resolving such disputes.
CONCLUSION
The Indian Contract Act, 1872[16] was enacted long before the creation of app-based services; however, its foundational principles continue to govern modern digital transactions. Booking a Rapido ride is an example of how traditional contract law adapts to technological evolution, highlighting the Act’s[17] continuing relevance in the digital age.
However, the true legal complexity lies not in contract formation but in platform accountability. The intermediary model challenges traditional doctrines of privity and agency, while cancellation mechanisms test principles of damages and fairness.
As digital marketplaces evolve, Indian courts may be called upon to refine contract law doctrines to ensure they align with technological and economic realities. The tap of a button may appear simple, but legally, it may carry consequences far deeper than users imagine.
Author(s) Name: Namya Agrawal (Hidayatullah National Law University, Nava Raipur, Chhattisgarh)
References:
[1] Indian Contract Act 1872
[2] Dunlop Pneumatic Tyre Co Ltd v Selfridge & Co Ltd [1915] AC 847 (HL)
[3] Indian Contract Act 1872, s 230
[4] Indian Contract Act 1872, s 2(a)
[5] Indian Contract Act 1872, s 2(b)
[6] Pharmaceutical Society of Great Britain v Boots Cash Chemists (Southern) Ltd [1953] 1 QB 401
[7] Indian Contract Act 1872, s 7
[8] Trimex International FZE Ltd v Vedanta Aluminium Ltd (2010) 3 SCC 1
[9] Indian Contract Act 1872, s 5
[10] Indian Contract Act 1872
[11] Indian Contract Act 1872, s 2(d)
[12] Indian Contract Act 1872, s 13
[13] Indian Contract Act 1872, s 11
[14] Indian Contract Act 1872, s 23
[15] Motor Vehicles Act 1988
[16] Indian Contract Act 1872
[17] Indian Contract Act 1872
