Blog
Border rules change on a Tuesday. We write down what changed.
Coverage notes, product releases and the economics of selling travel documentation, written by the people who process the applications.
Coverage alerts
One email when a rule changes on a destination you sell. Not a newsletter.
ETIAS moved again. What it changes for anyone selling flights into Europe.
A new start window, a grace period that does most of the work, and one line in your booking flow that has to be right before the first traveler is turned away at the gate.
Product
Timatic and modern visa APIs: what each is for
The airline industry's compliance engine has done one job well since 1963. Knowing where that job ends tells you what to run beside it.
Revenue
Visa ancillary revenue: the complete guide
Seats and bags are saturated. The visa line is the rare ancillary with no cost of goods, no ops burden, and a traveler who is actively looking for help.
Product
Elements are free on every model, including the API
Why we stopped charging for the components that bring applications to us in the first place.
Coverage
Vietnam extended its e-visa. Read the fine print on entry dates.
The validity window moved. The entry date rule did not. That gap is where refusals happen.
Revenue
What a 4% attach rate looks like on 60,000 bookings
The arithmetic behind visa ancillary revenue, using the numbers we actually see.
Engineering
Idempotency keys, and the duplicate charge that never happened
How we made retrying an application POST boring, and why your integration should retry more.
Inside SimpleVisa
How three people track sixty governments
Sources, diffing and the weekly review that turns a circular into an API response.
Coverage
India e-visa processing times are back to normal
Two weeks of delays cleared. What we told partners while it lasted.
Product
Coverage alerts: pick destinations, get one email per change
Pick the destinations you sell and hear from us only when one of them changes.
Revenue
Merchant of record, explained for travel teams
Who the traveler is buying from decides whose logo goes on the checkout. Here is why.
Engineering
Six webhooks we send, three you should actually handle
Only three of them change what a traveler sees. Start there, add the rest later.
Coverage changelog
Rule changes, as we covered them.
Requirements update in the API the same day they land here; your integration keeps rendering whatever comes back. Every entry links the note that covers it.
See every destination→