Cross-border communications, operated end to end
One platform for every border your customers have to cross
JAP runs the lanes between markets: local numbers, messaging, voice, verification and roaming data across 190+ countries — bought as corridors, priced per interaction, and measured on the handset rather than at the gateway.
No minimum commitment · Sandbox keys issued at signup
Hub time
Interconnected with carriers, aggregators and OTT partners on five continents
Direct interconnects and audited wholesale partners, reviewed quarterly.
The platform
Six capabilities, one cross-border account
Every lane is bought, provisioned and billed in the same place. No separate vendor per country, no reconciliation project at month end.
Measured, not quoted
190+
Countries reachable
1,400+
Active corridors
98.4%
Handset-verified delivery
99.99%
Platform uptime, trailing 12 mo
The lanes
Bought by corridor, reported by corridor
Trailing-30-day figures from live traffic and probe SIMs held in the destination markets. The same table the network page publishes in full.
| Corridor | Markets | P95 latency | Verified delivery | Sample markets |
|---|---|---|---|---|
| APAC → North America | 21 | 1.9s | 98.9% | CN · SG · JP · KR · US · CA |
| North America → LATAM | 24 | 2.4s | 98.1% | US · MX · BR · CO · CL · AR |
| Europe → Middle East & Africa | 46 | 2.7s | 97.4% | GB · DE · AE · SA · NG · ZA |
| South & Southeast Asia → Gulf | 18 | 2.2s | 98.3% | IN · PH · ID · VN · AE · QA |
| Intra-Europe | 39 | 1.6s | 99.2% | DE · FR · ES · IT · NL · PL |
How a corridor works
From your API call to a handset in another country
The same four steps run whether the interaction is a text message, a voice leg, a WhatsApp template or a verification challenge.
Originate
You send one request with a destination and a channel preference. No per-country endpoint, no per-carrier credential to manage on your side.
Clear
We resolve the destination network, apply the local regulatory profile — sender registration, content rules, quiet hours — and pick a compliant lane.
Carry
The interaction crosses on a scored corridor. If quality drops mid-flight, the next-best lane takes over before your traffic notices.
Settle
Handset receipts, per-unit charges and a full corridor trace land in the console and on your webhooks, in one currency and one invoice.
Assurance
Crossing a border is a legal act, not just a network hop
Each destination has its own registration regime, consent rules and data expectations. We treat them as part of the product.
Registered before you send
Sender IDs, 10DLC brands and campaigns, short codes and per-country templates filed, renewed and tracked from one workflow.
Consent that survives an audit
Opt-in records, STOP and HELP handling, quiet-hour windows and suppression lists applied per destination, with an exportable trail.
Data handled per jurisdiction
Message bodies are processed transiently, metadata is retained on a published schedule, and transfers ride on standard contractual clauses.
Questions
What operators ask before they move a corridor
What exactly is a corridor?
A corridor is an origin–destination lane with a channel attached: for example, US → Brazil on SMS, or Singapore → Gulf on voice. You buy and monitor capacity lane by lane, because that is how quality, price and regulation actually vary.
Can I mix channels for the same user journey?
Yes. A single verification flow can start on a WhatsApp template, fall back to SMS and finish on a voice callback, with one request and one charge trail. Channel preference is a parameter, not a separate integration.
Do you own numbers in the destination markets?
We lease inbound numbers directly in most markets and through licensed partners in the rest. Numbers appear in your console with their capabilities and their local regulatory requirements attached.
How fast can a new corridor be opened?
Existing corridors are live the moment your account is approved. A destination we do not currently carry typically opens within one to three weeks, depending on the local registration regime.
How is delivery actually measured?
From handset delivery receipts on live traffic plus continuous probe tests against real SIMs in the destination market. Gateway acknowledgements are never reported as delivery.
Which currency do you invoice in?
USD by default, with EUR available on committed-volume accounts. Every cross-border charge is converted at the rate stamped on the interaction, so the invoice reconciles to the console line by line.
Move one corridor and compare
Open an account, point a single destination at JAP, and put our handset-verified delivery next to your current provider's numbers.
Median time from signup to first delivered interaction: under 20 minutes