Silent Verification
Silent Verification lets you approve a returning, previously validated user without friction: no capture screen is shown. Unico's technology approves the transaction when the signals collected in the background are enough.
It is not a separate product: it is an extra step on top of the same transaction creation flow described in Payment transactions and Credit card Onboarding. Collecting signals with the SDK and sending that same external key when creating the transaction is what makes a silent approval possible.
- Silent Verification applies when there's enough history for Unico's technology to approve through signals.
- When that isn't possible, the transaction falls back to the standard visual flow instead. This can happen, for example, the first time a given identity is seen on the network.
Silent Verification uses the Capture SDK's Silent Revalidation flow to collect device and behavior signals in the background, without opening a camera. The guides below assume the SDK is already installed and configured for your platform; if you are starting from scratch, begin with SDKs and Tools. The collection has two calls:
initializeSDK— call it as early as possible, before the user is identified: on Android and iOS, at app launch; on the Web, on the same page wherestartSilentValidationwill run. It starts the collection in the background.startSilentValidation— call it with theexternalUserIdat the moment of the action (checkout, card registration). It associates the collection already in progress with the identified user and sends it.
Follow the Silent Revalidation guide for your platform:
Step 3 of those guides creates a process with POST /processes/v1 and reads silentAuth.result. In Card Not Present Verification, you create the transaction instead, as described in Step 2 below.
Minimum SDK versions:
| Platform | Minimum version |
|---|---|
| Android | io.unico:capture 6.13.0 |
| iOS | 3.3.0 |
| Web | unico-webframe 3.28.3 |
Create the transaction after startSilentValidation completes. There is no fixed wait: the earlier initializeSDK runs, the less the user waits at this point. If the call fails, handle the error as described in the SDK guide for your platform. A collection is valid for up to 5 minutes after it is sent, and each collection serves one validation; in a new journey, the collection may need to be loaded again.
externalUserID is optional — but without it, Silent Verification cannot happen for that transaction. When creating the transaction — via Payment transactions or Credit card Onboarding — send the exact same externalUserID used in the SDK, inside additionalInfo:
{
"additionalInfo": {
"externalUserID": "YOUR_EXTERNAL_USER_ID"
}
}
The externalUserId used in the collection (startSilentValidation) and the additionalInfo.externalUserID sent in the transaction must be identical, character by character. Any difference — case, whitespace, formatting — means the backend cannot match the collection to the transaction, and the transaction follows the standard visual flow.
Omitting it doesn't cause any error — the transaction is still created normally, it just always follows the standard flow with visual friction.
If the transaction qualifies and is silently approved, no further action is needed:
{
"id": "6ab1771e-dfab-4e47-8316-2452268e5481",
"status": "approved"
}
Otherwise, the response includes a link to complete the standard visual flow, exactly like a transaction created without Silent Verification:
{
"id": "6ab1771e-dfab-4e47-8316-2452268e5481",
"status": "waiting",
"link": "https://aces.so/example",
"token": "eyJhbGciOiJIUzI1NiIsInR5cC[...]Ok6yJV_adQssw5c"
}
A transaction can also come back as fast-inconclusive: a final status with no link, returned when the validations determine that biometric capture is not required. For the other statuses, see Controlling the experience and Enumerated for the full list.