6 posts tagged with "guardian"

Guardian SDK v0.4.2 adds a diagnostics object to verify() and collect() results so you can see what the SDK observed during a transaction. It is additive and backward-compatible — a drop-in upgrade.

Guardian SDK v0.4.0 makes the SDK production-only. The environment option and the Environment type are removed, so the backend URL and all internal device-intelligence checks are now fixed to production and cannot be pointed at a non-production target. This is a small breaking change from v0.3.x.

Guardian SDK v0.3.1 is a bug-fix release. There are no API changes - it is a drop-in upgrade from v0.3.0.

Guardian SDK v0.3.0 moves authentication off the client. Your backend now mints a short-lived token (a GeolocationJwt) and passes it to the client - the API key never ships in your app or web bundle. This is a breaking change from v0.2.x.

Guardian SDK v0.2.1 adds a new collect() API for server-to-server device verification.

New: collect() method​

The SDK now supports two verification paths:

• verify() (existing) — SDK calls Surt directly, returns a risk decision to your app
• collect() (new) — SDK collects and encrypts device data locally with zero network calls to Surt. Your backend sends the encrypted payload to POST /geolocation/transactions/evaluate and receives the full risk assessment

This is useful when your backend needs to make the risk decision, when you want to combine device risk with your own business logic, or when compliance requires all third-party calls to originate from your infrastructure.

Available on all platforms: React Native, iOS, and Android.

Read the full guide

Surt developer documentation is now live.