Skip to main content
Authmatech’s native mobile SDKs perform silent verification directly on the device, where they can route the header-enrichment request over the cellular connection for the highest match rates. The integration model mirrors the Web SDK: the SDK obtains an operator-signed proof and registers a session; your backend completes the verification with the server-side API key.
Native SDK packages are provisioned per integration. Contact sales@authmatech.com or your solutions engineer to get the iOS, Android, or Flutter package and credentials for your account.

​
The model

Regardless of platform, the flow is the same:
1

Initialize

Configure the SDK with your Client ID and a short-lived SDK token issued by your backend. The server API key is never embedded in the app.
2

Enrich over cellular

The SDK triggers header enrichment over the mobile data connection and receives an encrypted identity proof plus the operator id.
3

Register the session

The SDK calls POST /v1/api/sdk/session with the X-SDK-TOKEN and X-CLIENT-ID headers and gets back an sdkSessionId.
4

Verify on your backend

The app forwards the proof, operator id, and sdkSessionId to your backend, which calls POST /v1/api/verify with the X-API-KEY.

​
Advantages over the web flow

  • Higher match rates — native apps can prefer the cellular interface for enrichment even when Wi‑Fi is connected.
  • Richer device signals — platform, OS, model, and integrity flags (isRooted, isEmulator, app integrity) feed directly into Shield and Detect.

​
Fallback

As with the web flow, enrichment depends on a usable mobile network identity. When it isn’t available, route the customer to Stuck+ rather than back to an SMS OTP.

​
Available today

The browser SDK is published as authmatech-sdk-web and is the fastest way to integrate web and mobile-web flows. For native iOS, Android, and Flutter packages, reach out to your Authmatech contact.

Web SDK reference

Fully documented and available on npm today.