# Terms and Conditions | OnArrival > The current OnArrival Travel terms covering platform access, accounts, travel services, booking, pricing, payments and consent. Read the full conditions. Source: https://www.onarrival.com/terms --- [← Home / Legal](https://www.onarrival.com/) Legal · Terms # Terms*of service.* Terms for using OnArrival APIs, embedded products, accounts and partner-powered travel services. v3.0 · Legal framework The same terms, both sides Before you read ## At a *glance* Company OnArrival Travel Technology Private LimitedSection 1 Version v3.0 Document hierarchy Order of precedenceSection 1.3 Related documents [Privacy Policy](https://www.onarrival.com/privacy) and [Data Processing Addendum](https://www.onarrival.com/dpa) Length 8 sections, about 6 min read ## Before you use the platform These terms form a binding agreement with OnArrival Travel Technology Private Limited. They apply across cloud SaaS, private deployments, white-label experiences, BYOS connections, APIs, SDKs and booking services. Service-specific annexes, a signed MSA, DPA or order form may take priority under the document hierarchy below. Section 01 ## Agreement formation and legal framework Using the platform can create an electronic contract with OnArrival Travel Technology Private Limited ### 1.1 The platform covered - Cloud-hosted multi-tenant SaaS. - On-premise and VPC deployments for enterprise data-residency needs. - White-label web and mobile micro-frontends. - BYOS connections for partner-controlled GDS, NDC or hotel supply. ### 1.2 How acceptance occurs - Registering an account or profile. - Clicking “I accept”, “I agree” or an equivalent affirmative control. - Generating an API key or integrating an SDK. - Completing a booking or payment transaction. - Continuing to use the Services after receiving notice of a terms change. ### 1.3 Document hierarchy The order of precedence is: service-specific annexes; enterprise MSA for private deployments; DPA; these general terms; then the privacy policy. Cookie, developer, BYOS and deployment documents operate alongside that hierarchy. **Important.** A signed order form, MSA, DPA or service annex may contain the binding commercial and service-specific commitments for a particular customer. Section 02 ## Definitions and interpretation The terms cover a B2B2C technology ecosystem, not only a consumer booking website. ### 2.1 Services and platform - Travel content, booking, payment, user-management, analytics and reporting technology. - White-label and embedded products, APIs, SDKs, webhooks, sandbox environments and support. - Security, authentication, authorisation and integration infrastructure. ### 2.2 Who uses it - Business Partners: travel agencies, fintechs, enterprises, marketplaces and travel-management companies. - Developers integrating APIs, SDKs and webhooks. - End Consumers using travel services through a Partner’s branded experience. - Platform Administrators responsible for OnArrival operations. ### 2.3 Bookings and suppliers A Booking includes confirmed flights, accommodation, ground transport, travel protection or experiences. Suppliers include airlines, hotels, transport providers, insurers and activity operators. Their content, availability, rules and fulfilment obligations remain relevant to the resulting reservation. ### 2.4 Content and confidential information These definitions distinguish OnArrival content, supplier content, user-generated content and dynamic pricing or availability. Intellectual property includes software, documentation, trademarks, trade secrets and technical methods. Confidential information includes non-public technical, business, user and strategic information. Section 03 ## Eligibility and capacity The person accepting these terms must have the legal and organisational authority to do so. ### 3.1 Individuals - The minimum age for independent contracting is 18. - People aged 16–18 require verifiable parent or guardian consent. - Identity, legal capacity and authority may be verified where necessary. ### 3.2 Business Partners - Valid business registration, tax standing and required travel or financial-services licences. - Authority for the representative to bind the organisation. - Financial, insurance, technical and security capability appropriate to the intended use. - Compliance with consumer, travel, payment, tax and data-protection rules in each operating market. ### 3.3 Developers and professionals Technical users are expected to follow documentation, rate limits, security requirements and privacy obligations. Travel-industry users remain responsible for licences, professional standards and coverage required by their jurisdiction. Section 04 ## Account management Account access is a security boundary and may be monitored, limited, suspended or terminated. ### 4.1 Registration and verification - Identity, email, phone, address or business verification may be requested. - Partner accounts may require corporate documents and risk assessment. - Travel profiles may contain passport, visa, payment, preference and emergency-contact information. ### 4.2 Your security responsibilities - Protect credentials and authentication factors. - Review account activity and report suspected unauthorised access promptly. - Keep devices and software reasonably secure and current. - Exercise care when accessing the Services over public networks. ### 4.3 Monitoring and review OnArrival may use automated and manual review for fraud, sanctions, abuse, rate limits, performance, high-value activity, complaints or security incidents. ### 4.4 Suspension and termination - Breach of these terms, suspected fraud, a security threat, legal requirements or payment disputes may justify restriction. - Where legally and practically possible, notice and an appeal path may be provided. - Existing bookings, refunds and legally required records may continue after account closure. Section 05 ## Service scope and functionality OnArrival supplies travel infrastructure and the operating services described in the applicable commercial documents. ### 5.1 Core technology - Travel content and availability APIs. - Booking lifecycle, payment and user-management APIs. - SDKs, webhooks, documentation, sandbox and usage monitoring. - Configurable white-label experiences, SSO and partner workflow integration. ### 5.2 Partner implementation and support - Technical onboarding, configuration, testing, certification and launch support. - Account management, technical support and performance review. - Analytics concerning revenue, customer journeys, supplier performance, operational health and fraud. ### 5.3 Travel operations Travel operations include booking fulfilment, payment handling, disruption management, customer-support escalation, itinerary organisation, alerts, document services, insurance and concierge capabilities where those services are enabled for the Partner. ### 5.4 Enterprise capabilities Corporate policy, approval, expense, budget, analytics and duty-of-care functions may be included in the relevant solution. Availability and commitments depend on the contracted product and deployment. Section 06 ## Booking terms and responsibilities The customer relationship and the technical fulfilment layer are intentionally separated. ### 6.1 Partner responsibilities - Own the primary customer relationship and present appropriate consumer terms. - Provide privacy notices and obtain required consents. - Collect accurate traveller details and explain documentation requirements. - Handle first-line customer support and escalate fulfilment issues to OnArrival. - Collect payment where the Partner commercial model assigns that role to it. ### 6.2 OnArrival responsibilities - Operate the contracted technology and supplier connections. - Process booking, confirmation and payment actions securely. - Maintain OnArrival technical references while supporting Partner-branded confirmations. - Provide the agreed technical and escalation support. ### 6.3 Traveller information - Names must match official travel documents. - Travellers remain responsible for passport, visa, health and entry requirements. - Special assistance, accessibility and medical needs should be declared accurately and early. - Electronic tickets, vouchers, changes and cancellations are delivered or handled through the configured Partner channels. ### 6.4 Special booking categories Group travel, corporate travel and unaccompanied minors may carry supplier-specific deposits, policies, approval, documentation, guardian-consent, service and safety requirements. **Supplier terms still matter.** Availability, cancellation, change, refund, baggage, check-in and fulfilment rules may come from the airline, property, insurer or other underlying provider. Section 07 ## Pricing and payment Prices can change with live supply, tax, currency and supplier policy; the payable total should be disclosed before commitment. ### 7.1 Price components - Base fare or rate. - Taxes, statutory fees and supplier surcharges. - OnArrival or Partner service and convenience fees where applicable. - Payment-processing, currency-conversion and optional-service charges. ### 7.2 Dynamic pricing Demand, season, market conditions, live availability, supplier revenue-management rules and limited promotions may change the offered price. Revalidation may be required before confirmation. ### 7.3 Payment architecture - Payment Service Providers, banking partners and regional methods may process the transaction. - Tokenisation, 3D Secure or other authentication may apply. - OnArrival stores limited payment-token metadata rather than full card credentials. - Settlement commonly flows to suppliers or through a PSP, with OnArrival not merchant of record in most jurisdictions. ### 7.4 Regional and enterprise features Regional features include Indian UPI, wallet, net-banking, GST and RBI tokenisation requirements; international card, PSD2/SCA and local-payment support; and enterprise tools such as corporate cards, credit terms, consolidated billing and budget controls where contracted. Section 08 ## Communication and telephone consent These terms cover consent for booking, support, payment, operational and opted-in promotional communications. ### 8.1 Channels and purposes - Telephone calls, SMS, email, WhatsApp, push notifications and other electronic channels. - Confirmations, changes, cancellations, travel updates and disruption messages. - Support, service, payment, refund, invoice and platform notices. - Promotional or loyalty communications where the person has separately opted in. ### 8.2 DND / NDNC clause The current source states that providing a telephone number constitutes consent for OnArrival, its Business Partners and authorised providers to make relevant service and transactional communications even where that number appears on an Indian DND or NDNC registry. It says that consent remains for the relationship and 180 days after deactivation or last interaction. ### 8.3 Withdrawal Promotional and marketing consent may be withdrawn through the opt-out supplied in a communication or by contacting hello@onarrival.travel. Necessary transactional and service communications are handled separately. **Read this clause carefully.** The DND/NDNC language is reproduced in substance from the currently published source. Applicable law and regulator rules govern whether and how any consent can override registry preferences. Questions about the terms ## Ask about the terms for your business. For a binding customer-specific version, request the applicable order form, MSA, DPA and service annexes from OnArrival. [Contact the OnArrival team](https://www.onarrival.com/company#contact) [Read the Privacy Policy](https://www.onarrival.com/privacy)