

The API provides location accuracy based on the mobile network. This is not GPS, but location at the cell ID level. The accuracy is generally sufficient for proximity verification, allowing you to define security radii of 2 km or more, which are effective for detecting if the device is in the same city or neighborhood as the point of sale.
Yes. The use of the Device Location API is subject to strict privacy regulations and must comply with end-user consent requirements in each jurisdiction (GDPR, CCPA, etc.). It is fundamental that the institution obtains explicit and traceable customer consent for the use of their location data for security and anti-fraud purposes.
The verification radius is the parameter (in kilometers or meters) that you define in the query to establish the proximity tolerance. For example, a bank could use a 2 km radius for an ATM in a city, or a 500-meter radius for a retail store, based on its risk policy and desired accuracy.
Yes, as long as the device maintains an active connection to the operator's mobile network (which is what enables cell ID-level tracking). The API queries the operator's network, regardless of whether the end-user's internet connection is via mobile data or Wi-Fi.
Absolutely. In a pure online transaction, you can use the retrieval query to verify if the location of the customer's mobile device matches the billing or shipping address they have provided. If the device is located in a sensitive location (such as a prison) or a high-risk country, the transaction can be flagged for review or rejected.