Skip to main content
When background verification can’t complete on its own — typically because the customer is on Wi‑Fi, a VPN, or a connection where the network identity isn’t recognized — the journey usually breaks and the business loses both visibility and revenue. Authmatech Stuck+ keeps those customers in view and helps you reconnect with them, so the ones who almost made it through still do.

​
When Stuck+ activates

Stuck+ is your fallback path whenever Verify returns validNumber: false or the SDK can’t produce a proof (for example sdk_no_he_result on Wi‑Fi). Instead of dropping back to an SMS OTP, you surface a Stuck+ unlock and Authmatech still works to confirm the customer’s identity.

​
What you can do with the API

All Stuck+ endpoints live under /v1/api/me/stuck-plus/** and use the standard X-API-KEY + X-CLIENT-ID headers.
ActionEndpoint
Overview of stuck sessionsGET /v1/api/me/stuck-plus/overview
List stuck sessionsGET /v1/api/me/stuck-plus/sessions
Inspect a session’s journeyGET /v1/api/me/stuck-plus/sessions/{sessionId}/journey
Reveal the confirmed identity (consumes credits)POST /v1/api/me/stuck-plus/sessions/{sessionId}/reveal
Reset a sessionPOST /v1/api/me/stuck-plus/sessions/{sessionId}/reset
Recover historical sessionsPOST /v1/api/me/stuck-plus/backfill
Audit who revealed whatGET /v1/api/me/stuck-plus/reveals
reveal decrypts and returns the confirmed mobile identity for a stuck session and consumes credits. Every reveal is recorded in the reveal audit so you keep a clear trail of who accessed what and when.

​
A typical recovery flow

1

Detect the stall

Background verification fails or the SDK can’t enrich. Show the customer a Stuck+ unlock instead of an OTP.
2

List stuck sessions

Your operations tooling polls GET /v1/api/me/stuck-plus/sessions to see customers who became stuck and their journey context.
3

Reveal when justified

For a session worth recovering, call reveal to obtain the confirmed identity and reconnect with the customer — within your own policy and consent rules.
4

Backfill history

Use backfill to bring older stuck sessions into Stuck+ so nothing high-value is lost.

​
Configuration

Stuck+ behavior (such as retention and reveal policy) is configured per account. Admins manage it via the dashboard; the effective configuration is also reachable through the dashboard Stuck+ config endpoints. Talk to sales@authmatech.com to enable Stuck+ or adjust limits.
Stuck+ never downgrades a customer to an SMS OTP. When a customer submits their number through the unlock, Authmatech still confirms their identity over the network.