back to overview
For enterprise·9 min read

How EOR platforms can offer same-week global visa appointments without building the infrastructure

The gap between 'hire anywhere in 48 hours' and the reality of 8-week visa wait times. How Deel-style platforms can close that gap by embedding appointment booking via API, and what the integration looks like from the product and engineering sides.

The gap between your SLA and reality

8–14 wks
UK visa queue from India / Nigeria
VFS Global, 2026 — frequently cited on Reddit
48 hrs
EOR promise to customers
'Hire anywhere in 48 hours' — the category tagline
1
Single point of failure
Visa appointment is the only step you can't automate — until now
$1.5M
Cost to build this in-house
3-year TCO for 1 engineer maintaining a scraper

Every EOR and global mobility platform has the same unresolved contradiction in their product: the marketing says "hire anywhere in 48 hours." The reality is "hire anywhere in 48 hours unless your new employee needs a UK, Schengen, or US visa, in which case expect 8–14 weeks for an appointment alone."

This gap is not a secret to your customers. It is the moment in every enterprise sales call where someone asks the question you don't have a satisfying answer to: "What happens to our timelines when the candidate needs a visa?" The current answer — "we help facilitate the process" — is a polite way of saying "it depends on a portal we can't control."

The visa appointment is the one step in global hiring that has resisted automation because it requires navigating government portals with hostile anti-bot defenses, managing 2FA in real time, and reacting to slot availability windows that last under ten seconds. The rest of the EOR workflow — contracts, payroll, benefits, tax — has been productised. Visa appointment booking has not. Until that changes, "48 hours" is a number that applies to everything except the part your customers care about most.

The three integration paths — and which one actually ships

Option
Reality
Build in-house
2–3 engineers, 4–6 months, $200–300k
Breaks on every portal update; 1 FTE ongoing forever
Partner with a visa agent
Human-operated, no API, no SLA
No webhook, no status endpoint, no programmatic control
Embed via API (Opaige)
REST + webhooks, days to integrate
Portal changes absorbed; SLA-backed; scales with volume

The in-house path is the natural CTO instinct — and the most expensive mistake a mobility platform can make. A visa-booking script is not a standard integration. It is an adversarial automation problem against portals that actively try to break you, with a quarterly maintenance cadence and a legal compliance surface. Most teams that have tried it have quietly abandoned the effort six months in.

Partnering with a visa agency gives you human operators, not infrastructure. There is no API for you to call. No webhook for you to subscribe to. No SLA with contractual teeth. You are outsourcing a problem, not solving it.

Embedding via API is the path that actually closes the product gap — and the only one that lets you make a credible promise to enterprise customers about timelines.

What the integration looks like in practice

1
POST /bookings — submit the hire event
When your platform triggers a new-hire flow that requires a visa, your backend calls POST /bookings with the candidate's applicant data, destination country, visa type, and preferred date window. You receive a booking ID.
2
Subscribe to booking:status_changed webhook
Your webhook endpoint receives real-time state transitions: CREATED → AUTHENTICATING → CHECKING_AVAILABILITY → SLOT_FOUND → OTP_REQUIRED → CONFIRMED. Each event carries the booking ID and current state — enough to update your own workflow UI without polling.
3
Candidate receives OTP prompt in your UI
When the portal asks for 2FA, the booking:otp_required event fires. Your platform surfaces the OTP input in your existing candidate onboarding UI. Candidate submits in under 90 seconds. No redirect to a third-party interface.
4
booking:confirmed fires with appointment details
Date, time, centre, reference number. Your platform marks the visa step complete, continues the onboarding workflow, and sends the candidate their appointment confirmation. From your product's perspective, this step is now as deterministic as generating a contract.
5
GET /bookings/:id/evidence for compliance records
For regulated industries, GET /bookings/:id/evidence returns screenshots, DOM snapshots, and portal-issued PDFs. Your platform stores them against the hire record for audit purposes.

The product pitch that becomes possible

What you can say in the next enterprise sales call
'Our platform submits the visa appointment request on day one of the hire. You receive a webhook when the appointment is confirmed — typically within 72 hours for corridors with availability. Your candidate receives their appointment reference in the same onboarding portal where they signed their contract.' That is a product capability. 'We help facilitate the visa process' is not.

The competitive moat for EOR and global mobility platforms in 2026 is not payroll localisation or benefits compliance — every serious player has solved those. The moat is the speed and reliability of the last mile: getting the candidate into the destination country without the months of uncertainty that currently define the visa experience.

The platform that closes this gap first owns the enterprise segment for talent-scarce corridors — UK, Schengen, and Canada are the three that enterprise customers ask about most in 2026. All three are bookable via Opaige today.