Check the border before the trip is approved.
Business trips get booked late, route through cities nobody planned to stop in, and often need a different class of visa than a holiday to the same place. SimpleVisa answers the document question inside your trip request, files the application for the traveler, and shows the travel manager who is still missing something.
The approval screen says what each leg needs.
The same request your approver already opens, with a document line per leg and per passport. Approve it knowing the trip is legal, and the applications start the moment it clears.
The assumptions a holiday checker makes do not survive a work trip.
Leisure travel is booked months out and flies point to point. The whole party usually carries the same passport. None of that is reliably true of a supplier audit in Delhi with a colleague from the Madrid office.
The trip is next Tuesday
Approval to departure is often days. A requirement answered at booking is worth little if the document takes a week, so the processing window sits next to the requirement and the approver can see whether the date holds before anyone books.
The stop nobody counted
A connection that stays airside usually needs nothing. Leave the airport, collect a bag or change terminal in the wrong country and it becomes a visa. Every leg is resolved with its layover duration and airside flag as inputs.
Business is a different document
A destination that waves a tourist through can require a business visa, an invitation letter, or a permit for anything that looks like paid work. The trip purpose feeds the answer alongside the passport and the route.
One trip, four nationalities
Teams travel together and rarely share a passport. Each traveler on the request gets their own answer, and the request is only clear once the last of them is.
190+ destinations carry requirement data and 80+ are processed end to end. Where a destination still needs a consulate appointment and a physical passport, the screen says so and we do not take the order. See what is covered →
Three moments, one set of answers.
Corporate travel has no single moment of truth. There is the request, the call to the service centre, and the Monday morning when someone asks who is where.
The trip request
Elements drop the requirement check into your OBT or your approval screen. A platform that renders its own interface calls the Requirements API instead. Median response is 380 ms, fast enough to sit inside the page load.
See the requirements endpoint →The service centre
Agents file for the traveler during the call, inside the mid-office record or CRM they already have open. They sign in once, to your tool, and the order carries their name and team.
How phone orders work →The travel manager's view
Every application with its status, its government reference and which traveler is still holding it up. Filter it, export the month for the client's report, and give the seat to whoever needs it; seats are free.
See the partner console →The agent surface is Desk Embedded, mounted in your own portal, and the traveler-facing pieces are Elements. Both run on the same requirement engine, so the approver and the agent never read different answers.
Approval answers the budget question. It rarely answers the border one.
Duty of care is the employer's obligation to look after the people it sends abroad, and ISO 31030, the travel risk management guidance published in 2021, is the shape most corporate policies are now written to. Nobody gets certified against it. It asks that a trip be assessed before it is approved and that someone own the risk in writing.
Entry permission is one of the few travel risks with a documentary answer. Either the traveler holds the right document for that passport and that route, or they do not, and the difference is knowable on the day the request is raised. A trip approved without that check leaves the risk sitting with whoever approved it.
When something does go wrong months later, what you want in front of you is a file, not somebody's memory of an email.
Passport scans stay out of your stack and your client's.
Travelers upload documents into our frame and they post straight to us. Your booking tool keeps a route, an email address and a reference. Applications and documents are held in the EU under GDPR, so a corporate security questionnaire gets answered from what we already publish.
Read the trust center → for hosting, subprocessors, retention and the DPA.
In corporate travel the traveler rarely pays, and that decides the model.
A leisure booking ends with a card. A business trip ends on the client's account, inside the invoice your finance team already sends every month. Two of our three models are built for that, and the third is for platforms running their own gateway.
The usual fit for a TMC
$29 per application wholesale, $24 above 100 a month, $19 above 500. You are the merchant of record, so you set the line the client sees and bill it the way you bill everything else. Consular fees pass through at cost, seats are free, and the Network add-on is $29 per branch per month if your offices settle separately.
When the traveler pays
Some programmes let travelers buy their own document and expense it. SimpleVisa is then the merchant of record, the traveler pays a $39 service fee, and you take a share of it on volume terms. No invoice line to build, no reconciliation.
For the booking platform itself
The licence puts the whole flow on your own gateway and your own brand: $5,000 a month minimum, drawn down against $12 an application. Requirements lookups come with it once applications process through us. Standalone, the Requirements API is $500 a month.
Volume terms, add-ons and the full rate card are on the pricing page.
What programme managers ask first.
Can we check requirements without sending applications through you?
Yes. The Requirements API is $500 a month on its own, and free once applications process through SimpleVisa. The lookups are funded by the applications either way, which is why the standalone price exists.
A visa is approved. Does that guarantee entry?
No, and nobody can promise it; the officer at the border decides. What a document check removes is the avoidable failure: the wrong class of visa, a transit stop nobody priced, a passport that misses the destination's validity rule.
Who chases a traveler who has uploaded nothing?
We do. They get the emails, the console shows them as outstanding, and your agent can file on their behalf from the desk and send the traveler a link for the parts only they can supply.
How does the fee reach the client's invoice?
On Desk you charge the client, at whatever price you set, on the invoice you already send. Refunds and traveler support on that model sit with you as merchant of record, while the government submission, the document chase and the status reporting stay with us.
See it against a real itinerary.
Give us the destinations and passport mix of one client and the demo runs on their actual requirements and processing windows, with your desk rate applied to the invoice they would get. Or open a sandbox and check a route yourself in ten minutes.