Live demo

Direct sales to travellers

B2C Travel Portal for Travel Agencies and OTAs

A B2C travel portal is the public booking site a travel agency or an OTA uses to sell flights, hotels, tours and cars direct to travellers. PHPTRAVELS licences that storefront once, with the source code. The B2C booking site is included on Startup, Agency and Enterprise.

  • B2C site on every licence
  • Flights, hotels, tours and cars
  • Your domain and your brand
  • Source code on every licence
Open the live demoSee licence pricing

Definition

What a B2C travel portal is

A B2C travel portal is the customer-facing booking website of a travel agency or an online travel agency (OTA). The traveller searches, compares and pays on the agency domain. The agency sets the markup, takes payment through its merchant account and issues the voucher. It is not a sub-agent desk, and it is not a marketplace that takes a cut of the booking.

PHPTRAVELS is self-hosted travel booking software on the Platform overview. The B2C booking site, the CMS, reports and supplier connectors ship on every licence, including Startup. The licence is a one-time payment. Hosting, supplier fees and optional add-ons are separate. The OTA page, Online travel agency software, stays on “online travel agency software”. This page stays on the B2C portal.

PHPTRAVELS has built this platform since it was founded in May 2014. The site states 4,800+ agencies and 5 million bookings, as of September 2026, and the pricing page states agencies in 100+ countries. About us introduces the company. Success stories shows agencies running the product. This page does not invent clients.

Logo and colours are applied on every plan. Startup is English and one currency, on one domain. Agency adds unlimited languages with RTL and stays on one currency and one domain. Enterprise adds unlimited currencies, unlimited domains, the B2B agents portal and removal of the Powered by link. A B2C portal that sells only to the public does not require Enterprise.

Who a B2C portal is forThree roles, one public site. The licence decides whether agent tools are included as well.

  • The traveller

    Searches flights, hotels, tours and cars, pays at checkout and receives a voucher on the agency brand. No agent login is required.

  • The travel agency

    Sells direct to the public from its own domain, with its markup and its merchant account. Startup or Agency is the published fit when there is no sub-agent network.

  • The OTA

    Runs the same storefront at a larger catalogue: several suppliers in one result list, languages from Agency, and more than one currency only on Enterprise.

Traveller path

Search, results, checkout, payment, voucher

One booking record. The traveller does not have to know which supplier answered the search.

  1. 01

    Search

    The traveller asks for a flight, a stay, a tour or a car. The portal queries the suppliers switched on for that module and waits on each connection on its own path.

  2. 02

    Results

    Fares and rooms come back as one list. The agency markup is already in the price the traveller sees: a fixed amount on Startup, or a fixed amount and a percentage on Agency and Enterprise.

  3. 03

    Checkout

    The traveller enters passenger or guest details and confirms the selection. The booking stays pending until payment returns a result the booking can act on.

  4. 04

    Payment

    Checkout uses the payment gateway whose credentials are stored in admin. The traveller pays the agency merchant account. Gateway fees are between the agency and that provider.

  5. 05

    Voucher

    The confirmation carries the agency brand and the supplier reference, so the desk and the supplier can find the same booking. The invoice follows the same record.

The wider booking product is Travel booking software. Commissioning the build as a project is Travel portal development. This page is the B2C storefront.

What it sells

Flights, hotels, tours and cars

These four modules are on the platform and are the products a B2C travel portal is expected to sell. Each one has its own page.

  • Flights

    Search, fare rules, PNR, ticketing, changes and refunds through the GDS agreement, plus NDC and low-cost content through a consolidator.

    Flights

  • Hotels

    Bedbank rates and direct hotel contracts in one stay search. When two bedbanks return the same room, the stays module maps them to one hotel record.

    Stays

  • Tours

    Activities and tickets from connected suppliers, plus tours the agency loads itself. The traveller books a departure, not a spreadsheet.

    Tours & activities

  • Cars

    Car hire from a connected supplier such as CarTrawler, shown in the same storefront as the flight or the hotel.

    Cars & transfers

Other modules, including cruises, transfers and visa, live on the Platform overview. They are not required to launch the B2C portal described here. Flight software in depth is Flight booking software. The hotel booking engine is Hotel booking engine.

Suppliers

GDS, NDC, LCC and bedbank suppliers

The licence includes connectors. It does not include the supplier contract, the credentials, or a promise that a named supplier will accept the agency. The agency signs, then switches the connector on.

Suppliers and gateways named on this page
  • Amadeus
  • Sabre
  • Travelport
  • Duffel
  • Hotelbeds
  • Viator
  • CarTrawler
  • Stripe
  • PayPal
  • Cashfree

The live list, including suppliers not named here, is the All integrations. This page does not freeze a supplier count.

Checkout

Payment gateways on a B2C portal

The traveller pays the agency merchant account. Ready connectors include Stripe payments and PayPal payments. Cashfree, Flutterwave and Paystack are on the same gateway list. Razorpay integration is not a ready connector. The live list is Payment gateway integration.

  • Stripe

    A ready card gateway. The agency opens the Stripe account, stores the credentials, and settlement stays with Stripe. The licence does not add a per-booking payment fee.

    Stripe payments

  • PayPal

    A ready wallet gateway on the same pattern: the agency’s PayPal account, the agency’s credentials, the booking confirmed when PayPal returns a result.

    PayPal payments

  • Razorpay

    An Indian gateway for cards, UPI, netbanking and wallets in rupees. It is not a ready PHPTRAVELS connector. The guide explains the payment flow and how a custom integration is scoped.

    Razorpay integration

  • Cashfree for India

    Cashfree is the ready gateway for India today. It is switched on in admin with the agency’s Cashfree account. Flutterwave and Paystack are the ready gateways the homepage hub shows for Africa.

    Payment gateway integration

A gateway that is not in the ready list can be added as a Custom API integration on the included source code, scoped in hours. How a gateway talks to the booking is Payment gateway API.

B2C, B2B, B2B2C

B2C versus B2B versus B2B2C

B2C, B2B and B2B2C are modes of one installation. The licence decides which modes are included. They are not three products with three contracts.

B2C, B2B and B2B2C against the published PHPTRAVELS licences
AreaB2CB2BB2B2C
Who booksThe traveller, on the public site.A sub-agent or reseller, with a login.Travellers and agents, from one installation.
Where it sits in the licenceThe B2C booking site is on Startup, Agency and Enterprise.The B2B agents portal is Enterprise only.The storefront is on every plan. Agent distribution is Enterprise.
MarkupFixed amount on Startup. Fixed amount and percentage on Agency and Enterprise.Agent tiers, each with a markup, on Enterprise.The same rules, in one admin.
Wallet and creditNo customer wallet on Startup. The wallet is on Agency and Enterprise.Agent credit limits and commissions are Enterprise.Customer wallet from Agency. Agent credit on Enterprise.
DomainOne domain on Startup and Agency. Unlimited domains on Enterprise.Often a separate host, which unlimited domains on Enterprise allows.Public site and agent site can share one licence on Enterprise.
Language and currencyEnglish and one currency on Startup. Unlimited languages with RTL from Agency. Unlimited currencies on Enterprise.The same plan rules. Agent statements follow the currency the plan allows.The same plan rules for both audiences.

Plan differences for markup, languages, currencies, domains and support are on Pricing. The page that covers B2C, B2B and B2B2C as one white-label portal is White label travel portal. The agent-network page is B2B travel portal.

Price

What a B2C travel portal costs

The B2C booking site is included on Startup, Agency and Enterprise. Each is a one-time licence. There is no monthly licence fee and no per-booking fee from PHPTRAVELS.

  • B2C is included on every plan

    The pricing matrix marks the B2C booking site as included on Startup, Agency and Enterprise. Buying Enterprise is not required to sell to travellers.

  • The one-time licence

    Startup, Agency and Enterprise are one-time licences. The amount for each plan is on the pricing page. It is not a subscription.

  • Hosting and suppliers, separate

    The portal runs on a server the agency controls. Shared hosting and a VPS are quoted on Shared hosting and VPS hosting. Supplier deposits and gateway fees are between the agency and those providers.

  • Add-ons are not in the three prices

    Native iOS and Android apps, and the JSON API, are add-ons on every plan. Their prices are not on the pricing matrix, so they are quoted when asked. Custom work is scoped in 8-hour blocks, paid in advance.

Startup

One-time licence

7 to 10 business days

B2C site, admin, CMS, reports, source code, self-hosted, one domain, English, one currency, fixed markup. No B2B portal, no wallet. The Powered by link stays. Updates can be bought separately.

Agency

One-time licence

Rush: 1 to 2 business days

Startup, plus the customer wallet, unlimited languages with RTL, and fixed and percentage markups. Still one currency, one domain, no B2B portal. The Powered by link stays.

Enterprise

One-time licence

Rush: 4 to 6 hours

Adds the B2B agents portal, removal of the Powered by link, code customisation, all themes, unlimited currencies and domains, lifetime updates and ongoing maintenance.

Compare the plansBook a scoping call

The amounts are on Pricing. Support first-response is 4 to 6 days on Startup, 2 to 3 days on Agency, and within 24 hours on Enterprise. App scope is on Mobile apps. Hours beyond the product are on Customization.

Before go-live

Launch checklist

The software part follows the setup window of the plan. Supplier contracts usually take longer than the installation, so start them first. Nothing here is a timeline this site does not publish.

  1. Confirm it is B2C

    Selling to travellers on one domain can start on Startup or Agency. Sub-agents, an unmarked storefront, more than one currency or more than one domain means Enterprise. Write that down before paying.

  2. Register the domain and point it

    Register the domain in the agency’s name and point it at the installation during setup. Startup and Agency are one domain. Enterprise is unlimited domains.

  3. Send the brand package

    Logo, colours and the name that should appear on vouchers and invoices. A custom branding package is on every plan. Removing the Powered by link is Enterprise only.

  4. Sign suppliers and store credentials

    Open or confirm the GDS, the NDC or low-cost consolidator, and at least one bedbank if the portal sells hotels. Enter those credentials in admin. The connector does nothing until the supplier has accepted the agreement.

  5. Set the markup

    Fixed markup on Startup. Fixed and percentage on Agency and Enterprise. The customer wallet, if stored balances are required, is Agency or Enterprise.

  6. Open the merchant account

    Apply to Stripe, PayPal, Cashfree or another ready gateway, finish their checks, and store live credentials only after a sandbox payment succeeds. Razorpay is a custom integration, not a switch in admin.

  7. Set SEO on the pages travellers land on

    In the CMS, set the slug, meta title and description for the home page and the main product pages, in each language the plan includes. Keep thank-you and test pages out of the sitemap.

  8. Walk one booking on the demo, then on the install

    Use the public demo to follow search, results, checkout, payment and voucher before buying. After setup, repeat that path on the agency domain with the agency credentials.

SEO and apps

SEO on the storefront, and the mobile add-on

The CMS module ships on every licence. Native apps do not. They are a separate add-on, with no price printed on the pricing matrix.

The CMS holds a meta title, a meta description, a clean URL slug and a social image for each page, and each language version keeps its own fields. A canonical URL can point a near-duplicate at the main page. Thank-you and test pages can stay out of search, and the rest can go on the XML sitemap.

The website is responsive on every plan. Native iOS and Android apps are the Mobile apps: the same installation, the same markups and the same bookings, built with the agency name and icon, and published on the App Store and Google Play. The app price is quoted when asked. It is not one of the three licence prices.

  • Clean URL slug

    A readable address per page and per language, edited in admin.

  • Meta title and description

    Written per page, with a preview of the search snippet, and separate fields per language.

  • Social image

    The picture and text shown when a page is shared. Each language can have its own.

  • Robots and sitemap

    Thank-you and test pages can be kept out of search. Other pages can be added to the XML sitemap.

Next step

See the B2C portal before you licence it

The demo is public. Licence amounts are on the pricing page. A call is for mapping suppliers and the commercial model onto a licence, and for quoting apps or hours where the standard product stops.

Bring the suppliers already in place and say whether the sale is to travellers, to agents, or to both. Talk to sales is that conversation. Contact us reaches the same team by email, phone and WhatsApp. The service menu that lists this page is Services.

Open the live demoView pricingMessage us on WhatsAppBook a call

Related reading

FAQ

Questions about a B2C travel portal

Short answers from the product as it is sold. Prices and setup times match the pricing page. The starting licence in the cost answer is Startup.

Talk to sales

Startup, Agency and Enterprise are one-time licences. The amounts are on the pricing page. The B2C booking site is included on all three. Hosting, supplier fees, mobile apps, the JSON API and custom hours are separate. There is no per-booking fee from PHPTRAVELS.

Platform setup is 7 to 10 business days on Startup, 1 to 2 business days rush on Agency, and 4 to 6 hours rush on Enterprise, including installation, configuration and testing. Supplier approval can take longer than setup. Custom development is extra and is scoped after the licence is in place.

A GDS is needed only for the GDS content the portal will sell. Amadeus, Sabre and Travelport connect through native adapters once the agency has an IATA or consolidator agreement. NDC and low-cost fares can come through consolidators such as Duffel, Kiwi and PKfare without a direct GDS contract. Hotels can come from a bedbank such as Hotelbeds. The licence does not include any of those contracts.

Yes. The site runs on the agency domain: one domain on Startup and Agency, unlimited domains on Enterprise. Logo and colours are applied on every plan. Removing the Powered by link is Enterprise. The agency registers the domain. The installation answers on it.

Yes. The full source code is included on every licence, and the installation is self-hosted, so bookings sit on the server the agency controls. Enterprise adds the right to modify that code and lifetime updates. Startup and Agency include the source; customisation rights and lifetime updates are Enterprise terms. Updates on Startup and Agency can be bought separately.

Ready connectors include Stripe and PayPal. Cashfree is the ready gateway for India. Flutterwave and Paystack are ready gateways on the homepage hub. Razorpay is not a ready connector; it can be added as a custom integration. The traveller pays the agency merchant account. PHPTRAVELS does not add a per-booking payment fee.

B2C is the public site where travellers search and pay. It is on every licence. B2B is the agent portal, with logins, credit and commissions, and it is Enterprise only. B2B2C is both, from one installation: the storefront on any plan, the agent tools on Enterprise. A business that only sells to the public does not need Enterprise for the B2C site.

Keep exploring

More from the platform