Booking Widget Changelog¶
Release notes for the HGN Booking Widget.
1.1 — 3 September 2026¶
The widget now runs on the same platform as the rest of Himalayan Guardian, sharing one booking flow with HGN's own public booking page.
Your integration does not change. The embed URL keeps the same shape, your slug and publishable key are unchanged, and no code edit is required.
Corrections to the 1.0 documentation¶
Payment verification endpoint was wrong
Widget 1.0 documented GET https://book.hgn.com.np/api/public/book/payment-status/{paymentRef} for verifying payments from a custom result page. That URL has never existed and returns 404.
If you built a custom result page against it, your verification has been failing and customers have been seeing a neutral "we are confirming your payment" state instead of a confirmation. The working procedure is in Payment Verification.
- Multi-traveller bookings cannot currently be verified from a custom result page. A booking with more than one traveller creates an order group whose payment reference does not resolve to a single order. The HGN hosted result page handles this correctly.
- Footer copy was never configurable. The 1.0 docs listed it as a dashboard setting; it is not. The widget footer is a single line crediting Himalayan Guardian as the insurer.
mode=fullis no longer load-bearing. It stays in the embed URL for compatibility and is now ignored. Your agency is identified by thepkalone.
Changed¶
- The post-payment result page is now HGN's standard hosted page rather than a per-agency branded one, when no
return_urlis configured. Your branding still applies throughout the booking flow itself. To control the final screen, set areturn_urlto a page on your own domain. - Embedding pages must be served over HTTPS. The widget previously allowed any origin to frame it. Plain-HTTP pages — including
http://localhostduring development — are now refused. See Local testing for the approaches that work. - The publishable key is now shown in the dashboard, under Booking Widget › Settings. You no longer need to request it by email once it has been issued.
- The Embed URL now requires an issued publishable key before it appears. Previously the dashboard could generate a URL without one, which loaded a widget that could not identify your agency.
- Primary colour is validated for contrast before it saves. Colours that are too light, too dark, or that no readable text colour sits on are rejected with an explanation.
1.0 — 28 August 2026¶
First release of the agency integration.
- Full-page iframe embed at
book.hgn.com.np/<slug>?mode=full&pk=<key> - Complete booking flow: trip details, traveller profiles and documents, plan selection, terms acknowledgement, and payment
- Branding managed from the HGN dashboard — logo, primary colour, and footer copy apply automatically with no code changes
- Payment routing through CyberSource for card payments and Fonepay for QR payments
- HGN hosted payment result page, branded per agency, covering success, failed, cancelled, and expired states
- Optional custom return URL via the
return_urlparameter - Public payment status endpoint for server-side verification on custom result pages
- English language support
Related¶
- Integration — the current integration procedure
- Portal changelog