SSMARTVERIFYDOCUMENTATIONOpen portal ↗
GuideServicesAPIPoliciesChangelog
Guide / lifecycle

Request lifecycle

Understand what happens between submit and report, including states that must not be retried.

The controlled path

SmartVerify validates the request, records purpose and authority, reserves credits, calls the configured upstream adapter server-to-server, then normalises the result.

01

Validated

Malformed input, missing authority or insufficient credits stops before an upstream call.

02

Reserved

A credit reservation and idempotency key bind the attempt.

03

Processing

The adapter is waiting for or handling a provider response.

04

Completed or reviewed

A report is available, or manual_review needs a human.

Never retry manual_review

A timeout or uncertain charge state is not proof that no lookup occurred. Keep the same idempotency key, inspect history and contact support. Do not create a new key.

manual_review

Pause automation and follow your approved escalation path.

Credit semantics

Validation failures should not consume a provider lookup. A no-record result may still be chargeable according to the configured service.