iVisa Merged into HelloGov: What OTAs and Airlines Should Watch in the Partner-Network Push

In July 2026, HelloGov AI, Inc. and Document Advisor, Inc. (iVisa) completed a merger and now operate under the HelloGov brand. Company materials frame it as a combined consumer passport-and-visa platform, and leadership has been explicit about growing a global commercial partner network: airports, pre-check apps, passport-photo channels, retailers, and travel brands.

This post is a factual ops briefing for OTAs, airlines, and travel tech. It is not legal advice. Claims below are labelled confirmed (primary company pages) or reported (trade and contributor coverage that cites the companies).

Confirmed (primary sources)

From iVisa’s merger announcement and HelloGov’s merger page.

Partner and white-label surface

HelloGov’s Enterprise Partnerships page positions the B2B offer as follows.

Visa catalogue language on the same page: tourist visas across 100+ destinations, “built on thirteen years of iVisa application data.”

We did not treat older HelloGov “partner with us” commission figures as current. The historic partner recruitment URL returned a 404 on 6 October 2026, so this note states no revenue-share term.

Reported

Label these as reported. They are not SimpleVisa fact-checks.

iVisa’s own news article carries NewsArticle schema with datePublished 2026-08-20 (UTC). Trade and contributor amplification clustered later in September. For SimpleVisa, this is an industry briefing, not a same-day government-rule news hit.

What it means for travel sellers

1. Destination and product coverage. The combined story is U.S. passport fulfilment plus a global visa and ETA catalogue. It is not a new government programme. For OTAs and airlines evaluating vendors, ask how passport SKUs and visa or ETA SKUs share status, refunds, and support SLAs, especially if a passenger needs both for one itinerary. Company materials stress a single trip-document funnel. An RFP should test that claim end to end.

2. White-label vs API. HelloGov’s public partner pitch is a hosted, co-branded white-label: fast attach, partner brand, vendor-run compliance. That sits in the same shopping basket as other white-label visa processors. On the public pages we reviewed, it does not spell out a carrier-grade fulfilment API (eligibility write path, idempotent submit, webhooks into a PSS or CRM). When you compare vendors, separate the questions below.

Use our decision guides when you run that comparison: API vs white-label and eVisa API for OTAs and airlines.

3. Distribution footprint. The partner-network language targets where intent already exists: airport, pre-check, photo retail, the airline journey, and large digital-identity brands. For OTAs, that means more ancillary competitors at adjacent touchpoints (CLEAR, airport retail, photo chains) as well as other OTAs. For airlines, a co-branded passport or visa attach on manage-my-booking or partner sites is a familiar pattern. Stress-test brand control, data residency, and who owns the refused-application conversation.

4. Scope beyond travel. Business formation and tag-and-title are on the HelloGov roadmap. That is useful context for long-term vendor lock-in and brand strategy. Travel teams should keep the RFP scoped to travel-document eligibility, apply, pay, and status.

OTA and airline checklist

If your partnerships or product team is refreshing the visa ancillary shortlist after this consolidation, we can walk through API versus white-label against your top corridors. Start from the API vs white-label guide or request a readiness call when you have corridors and a target go-live.

Further reading: eVisa API for OTAs and airlines and Merchant of record, explained for travel teams.

Industry briefing for travel businesses. Not legal advice. HelloGov and iVisa are private companies. They are not government agencies. Governments issue passports, visas, and entry decisions. Volume and “largest” claims above are the companies’ own statements unless noted otherwise.