The visa sale is already happening. It just isn't yours.
Your customer books a flight, then goes looking for the entry document that flight needs. Today that search ends on a site you have never heard of, at a price you would never charge. Put the visa on your own confirmation page and take a share of the fee on every application.
The same card sits on the confirmation page, in the confirmation email and in manage-my-booking. It is the highest-intent moment you own, and most OTAs leave it blank.
Every traveler who needs a document goes and finds one.
The purchase happens either way. The only open question is whether it happens on a page with your name on it, and whether anyone in your company can see it when it does.
Into a search box
Your confirmation email says nothing about entry documents, so the traveler types the destination and the word visa into Google. The first things they see are ads.
Whatever the first ad charges
Intermediaries commonly charge a large multiple of the government fee. US Customs and Border Protection publishes a standing warning that it works with no third-party ESTA site and cannot vouch for what those sites charge or how they handle a passport.
Your support inbox
A week later the traveler cannot name the site they used. They can name the company that sold them the flight, and that is who gets the email about the charge, the missing approval and the refund.
None of it appears in your ancillary report, because none of it ran through you. The cost lands in support volume and in the reviews your brand team reads on Monday.
Sell it inside the flow, or sell it after the booking.
Most OTAs end up running both. One catches the traveler while their card is still out; the other catches everyone who was not ready to think about paperwork on the day they booked.
Requirements and checkout on your own pages
A requirements check on the passenger step for the exact passport and route being booked, then a visa checkout the traveler never leaves your site for. It is a script tag and a div, and it reads the itinerary you already have.
How the booking flow works →A visa storefront on your own address
A hosted checkout at visa.yourbrand.com, linked from the confirmation email, manage-my-booking and the pre-trip reminder. Nothing to build and nothing to release: the brand studio sets the logo, colours and typeface, and it is live the same day.
See the post-booking route →Both run on the same platform and report into the same console, so you can turn the storefront on this month and add the in-flow components whenever your release train has room. The component library is documented under Elements, the storefront branding under white label, and both endpoints under the API reference.
A $39 service fee, shared, on traffic you have already paid for.
Every application carries a $39 service fee on top of the consular fee. Your share of it is set in your agreement and rises with volume. The consular fee itself is passed through at cost, so the traveler pays the government exactly what the government asks.
How the money moves
The traveler pays us
On Revenue share SimpleVisa is merchant of record. The charge, the refund and the chargeback sit on our licence.
We do the work
Document validation, government submission, chasing the traveler whose photo came back rejected, and live chat when they ask where their visa is.
You get a statement
Your share closes into a statement with the per-order detail behind it: traveler, document, nationality, destination and the split.
"We like their professional team and easy to integrate API. After several years of partnership, we are very pleased with the service and revenue generated."
An ancillary line nobody can report on does not last.
Commercial needs attach rate, finance needs a statement it can invoice against, CS needs to answer a traveler without emailing us. All three sign into the same console, and seats are free.
One screen for every order and every payout
Every application your storefronts and components produce lands in one list, filterable by route, brand and channel, exportable for any month. Statuses update live, so the question "where is this application" stops being an email to us.
Look inside the partner console →Your security review stays short
Passport images and biometric photos go straight from the traveler to us. Your booking system holds a route, a name and an email address, which is what it held before you added visas. There is no new data store for legal to sign off.
Read the trust center →What commercial teams ask first.
If yours is not here, book a demo and bring the awkward one.
What do we earn on an application?
The service fee is $39 on top of the consular fee. Your share of it is agreed up front and rises with volume, and it applies to every application, including the ones a traveler starts on the storefront three weeks after booking. Consular fees are passed through at cost and never marked up.
Who talks to the traveler when something goes wrong?
We do. On Revenue share SimpleVisa is the merchant of record, so refunds and chargebacks come to us, and the traveler reaches our live chat from the application they filed. Your CS team can still see the whole file in the console.
Which destinations can you actually process?
Requirement data covers 190+ destinations, transit stops included, which is where thinner tools quietly fail. 80+ destinations are processed end to end today.
Can we be the merchant of record instead?
Yes, on the Platform licence: $5,000 a month minimum drawn down against $12 per application, running on your gateway and under your brand. Most OTAs start on Revenue share and move once the volume makes that arithmetic work.
See what the visa moment is worth on your routes.
Create an account and the storefront, the sandbox keys and the console open in minutes. Or send your top international routes to a demo and we will come back with the volume and the share.