Location check

Add Location Check to a workflow to confirm where the person is: in Switzerland for online gambling (Geldspielgesetz), at the delivery address for age-restricted deliveries, at a branch or a property. With the person's consent the browser shares the device's location once, before any other step, and secuveri checks it against the workflow's countries and, if you send one, the session's place. It runs alongside a person's verification: the workflow needs Identity Document, Liveness Check or Health Insurance Card too.

Countries and places

  • Countries: set location_countries on the workflow, {"mode": "allow", "countries": ["CH"]} or a block list. Borders come from swisstopo for Switzerland, Liechtenstein and the enclaves of Büsingen and Campione d'Italia (a few metres) and from Natural Earth elsewhere (up to about a kilometre), all looked up on our servers.
  • Place: send location_target with POST /v1/sessions: latitude, longitude, radius_m (25 to 100000, 200 by default) and an optional label. Turn on the step's Require target place option to refuse sessions without one.
  • A workflow needs countries, the Require target place option, or both.
curl
curl -X POST https://api-verify.secuveri.com/v1/sessions \
  -H "x-api-key: $SECUVERI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "workflow_id": "<your workflow>",
    "vendor_data": "order-1042",
    "location_target": { "latitude": 47.3769, "longitude": 8.5417, "radius_m": 150, "label": "Delivery address" }
  }'

What is checked

CheckReason codeDefault
Outside the countries, or farther from the place than its radiusLOCATION_MISMATCHDecline (or review)
The person did not share a location, or the device could notLOCATION_NOT_SHAREDDecline (or review)
Too vague (over 5 km) or too old (over 2 minutes), or a border or the radius's edge lies within the reading's accuracyLOCATION_UNCERTAINReview
Shared over Tor or a hosting network, as VPNs and proxies useLOCATION_ANONYMOUS_NETWORKReview
The IP country is none of the countries the device may be inLOCATION_IP_MISMATCHReview
The device's time zone has a UTC offset no zone of that country hasLOCATION_TIMEZONE_MISMATCHReview

Near a border the check counts every country within the reading's accuracy: someone in Kreuzlingen with a 500 m reading may be in Germany, so an allow list of CH holds the verification for review instead of approving it. An IP from any of those countries is consistent, so roaming and border networks do not count as a mismatch. A browser location can be faked with developer tools or a spoofing app; the IP country, the network and the device clock are second opinions, not proof.

What is kept

The reading itself is never stored or logged. The report keeps location_check: the decision and its reasons, the country, whether it was certain or which other countries were possible, the accuracy rounded to 10 m, an area rounded to two decimals (about 1 km, wiped with the other personal data), the distance to the place rounded to 10 m, and the IP country, network class and clock check. The place you sent is stored encrypted with the session and only its label, radius and the distance reach the report. The signed result (GET /v1/verifications/{id}/result) carries location_check without the area. The step is off unless a workflow lists it, and the person sees why it is asked and can decline.