THE LINUX FOUNDATION PROJECTS

Location Verification

API Description
Use Cases
  • Fraud Prevention in location-dependent Transactions: Banks, fintechs and other digital service providers can verify whether a user’s device is within an expected area before approving sensitive actions such as card payments, cash withdrawals, account changes or high-risk transactions. A location mismatch can trigger step-up authentication, manual review or rejection of the transaction.
  • Validation of app-reported GPS Information: Applications can compare a claimed or device-reported GPS location with an independent network-based verification signal. This can help identify inconsistent location information before enabling location-dependent features or services.
  • Connected and validated Delivery Services: Delivery platforms can verify whether a courier or recipient device is within an expected delivery area before confirming a handover, activating a service or completing a location-sensitive workflow.
  • Smart Mobility and zone-based Operations: Mobility providers can verify whether a user or connected asset is within an expected operational area before activating rental, access or automated workflow functions. This can support use cases such as shared vehicles, bikes, airport operations or controlled service zones.
  • Location-based digital Content and Services: Media, entertainment, gaming, hospitality and event applications can verify whether a user is within an authorised zone before enabling regional content, premium experiences or location-specific features.

See also at GSMA:

Benefits
  • Independent network-based Verification: Enables applications to validate an expected or claimed device location using information available to the mobile network, without relying exclusively on device-reported GPS data or IP-based location inference.
  • Reduced Location Fraud Risk: Helps identify inconsistencies before approving location-dependent transactions, granting access or enabling sensitive services.
  • Context-aware Service Control: Allows developers to activate, restrict or adapt digital services based on whether a device is within an expected geographical area.
  • Location Freshness Control: Enables API consumers to specify the maximum accepted age of the location information used for the verification.
  • Developer-friendly Integration: Provides a standardized CAMARA interface that can be integrated into existing fraud-prevention, delivery, mobility and location-based service workflows.
  • Operational Efficiency: Helps automate location-dependent decisions and reduce manual verification processes.

API Portfolio: Location Services

[icon color=”accent-color” size=”tiny” icon_size=”” image=”fa-file”] Sub Project Wiki: Device Location
(incl. how to meet the team)

[icon color=”accent-color” size=”tiny” icon_size=”” image=”fa-file”] API Wiki: Device Location

[icon color=”accent-color” icon_size=”” size=”tiny” image=”fa-github”]API Repository: Device Location

API Repository Status: Incubating

API Status: Stable

[icon color=”accent-color” size=”tiny” icon_size=”” image=”fa-list”]API Version(s) and Release Date(s):

  • v0.2.0 (27.02.2024), second alpha version
  • v1.0.0 (10.09.2024), Fall24 meta-release
  • v2.0.0 (10.03.2025), Spring25 meta-release
  • v3.0.0 (16.09.2025), Fall25 meta-release

API availability: Information which APIs are available in which country and network, and how to get access can be found on the GSMA public launch status page.

Be part of a collaborative community driving the future of global Telco APIs.

Join Today