Prevent tampering with client-side geocoding results

We are building a service that uses location-based pricing. The user can input an address and s开发者_开发百科ee prices in his area as determined by various server-side algorithms. It is then possible to order items based on these prices.

I'm trying to figure out if there is a way we can use client-side geocoding in this scenario (to avoid hitting Google Maps API usage limits), e.g. the user enters his address and the browser fetches the geocode result using the JS library and includes it in the form submission. The problem is that the user could tamper with the form submission and potentially place orders to his address for prices that apply to a different set of coordinates.

I'd like to hear your suggestions about how I can secure this. For example, it would be amazing if the geocode result could be signed somehow to verify that it hasn't been tampered with?

---

Never trust data created clientside. Anything you can do client side, they can.

---

If you want the client machine to do the request, you are going to be a bit limited in the security aspect of this, as it would all be javascript, and a malicious user could inspect the script and see what you are doing. Therefore even attempts at "securing" it would be limited in success.

My only recommendation would be to do a "final validation" serverside just as the user is submitting their results. This should reduce the API hits on your server side, but will keep the security 100% valid.

---

If the data's stored on the users' machine, they can do what they want with it. You might be able to encrypt it or something, or maybe store an ID to a table of geodata (like a zip code, but make up your own similar system) or a hash of the geodata or something, but whatever's stored on their machine is theirs.