The trip is paid for. The visa question is still coming.
Somewhere between the confirmation email and the airport, your traveler goes looking for what their passport needs. If that answer does not come from you, it comes from a search result. A visa storefront in your brand, linked from the pages they already open, keeps the moment inside your booking.
A travel documents card, next to seats and bags.
The traveler opens the booking they have already paid for. Their documents sit where the rest of the trip admin sits, answered per person: what this passport needs for this route, or that nothing is needed at all.
Four places the link earns its keep.
You do not need all four on day one. Each reaches the traveler at a different distance from departure, and each is a link plus, if you want it, a badge saying who needs what.
Confirmation page
The trip has just become real. Most travelers will not act yet, but they learn that you have an answer, and they come back for it.
Confirmation email
The most opened message you will ever send this traveler. Transactional mail is read at several times the rate of a campaign, and the visa line rides along with it.
Manage my booking
Travelers return here to move seats, add bags and re-read the times. A documents card sits inside that habit instead of asking for a new one.
Pre-departure reminder
The message with real intent behind it. Sent at the right distance from departure, it is the difference between a calm application and a rush.
The badge is what keeps the click honest. It answers per traveler: the one who needs nothing is told so and moves on, and the one who needs a visa hears it from you before a lookalike site marks the consular fee up and keeps the difference.
Send it early enough to be useful.
Visas carry two clocks: how long the government takes to issue one, and how long it stays valid once issued. Send the reminder too late and a routine application becomes a rush at the airport. Send it far too early and the document can expire before the trip starts. Build the schedule off the real median processing time for each destination rather than a round number.
Booked
Payment clears. The trip exists, the paperwork does not, and nothing on your side has changed.
Reminded
Your message goes out at a distance that suits the route: one link, and a badge saying who needs what.
Applied
The traveler fills in the form on your storefront. A specialist checks the file by hand before it reaches the government.
Approved
The document lands in the traveler's inbox. The order closes in your console with your share on it.
A visa storefront that wears your brand.
The same storefront that runs on 400 travel storefronts today. It covers 190+ destinations with requirement data and 80+ processed end to end.
Set the brand once, publish, done.
Logo, palette, typeface and corner radius come from one brand record in the studio, and that same record dresses the traveler emails. With the custom domain add-on at $250 a month, the storefront answers on your own address. Publishing is a button, not a release.
We take the payment, file the documents with the government and answer the traveler. No passport image ever reaches your systems.
Everyone can see where it is.
The traveler tracks their own application on the storefront and gets an email at every state change, which is why most visa questions never reach your support inbox. Your team watches the same orders in the partner console: reference, traveler, document, status, government reference and your share, exportable by month.
A support agent answers a traveler from the record, without opening a ticket with us.
See the partner console →You add a link. We carry the rest.
It costs nothing to start and needs no build. SimpleVisa is merchant of record on this model, and that single fact decides who carries what.
The payment, the filing, the traveler
We take the card, submit to the government, run live chat with the traveler and handle refunds and chargebacks. Your finance team receives a monthly statement and your support team's workload does not change.
How the three models price →Later than checkout converts less
A requirements check inside the booking flow catches the traveler while they are already buying, and it attaches better. Attaching after the booking asks for no engineering time at all. Most teams start here, watch the attach rate for a quarter, then move the check up the funnel.
Sell in the booking flow →What partners ask on the first call.
If yours is not here, the trust center covers data handling and the API reference covers everything a badge needs.
Does this need engineering?
Not for the link. You create the storefront in the console, pick the brand, and add an anchor to your confirmation page and your booking record. If you also want the badge to read from the real trip, one call per traveler returns what that passport needs for that route, transit stops included, at 380 ms on the median.
Whose brand does the traveler see?
Yours, on every screen and in every email. SimpleVisa appears once, named as merchant of record, because the card networks require the seller of record to be identifiable on the statement. Take the payment yourself on a Platform licence and that line goes away with it.
What if the traveler already has a visa?
Then the card tells them so and nothing is sold. The badge answers per passport and per route, so a traveler who is already covered gets one line confirming it and closes the tab. Being right when the answer is no is what makes the traveler believe you when the answer is yes.
Who answers traveler questions?
We do. On Revenue share SimpleVisa is merchant of record, so live chat, chasing a missing document, refunds and chargebacks sit on our licence. Your support team still sees every order in the console and can answer from the record.
Start with one link.
Create an account and a storefront exists in sandbox the same afternoon, ready to point at from your confirmation page. Or book a demo and we will walk the four touchpoints against your own post-booking journey.