Face Verification
Face Verification runs server-side face checks with AWS Rekognition. One node, two operations you can combine: validating that a selfie contains a single clear face, and comparing the selfie against the photo on the ID document with a configurable similarity threshold. Unlike Liveness Verification it is synchronous — the result is immediate, with no microsite and no session.
Compare operations record a Verification (type face, provider aws) bound to the selected identity, so KYC queries it alongside liveness and signing. The node's response variable holds the verification ID (a string), never the raw provider response.
Configuration
| Option | Description |
|---|---|
operation | validate-selfie, compare-with-id, or both |
selfieImageVariable | Variable holding the selfie image (from an Ask File node) |
idImageVariable | Variable holding the ID document photo (compare operations) |
selectedIdentityKey | Identity the verification is bound to (compare operations) |
similarityThreshold | Minimum similarity percentage to pass (default 80) |
responseVariable | Where to store the verification ID |
storeInPackage | Create an audit record with operation, similarity and threshold |
testMode | Returns a passing result without calling AWS |
Output Handles
| Handle | When |
|---|---|
| Success | All requested checks passed |
| Error | A failed or rejected check, unreadable images, or configuration errors |
Things to Know
Rejected routes through Error. A comparison below the threshold records a rejected verification and takes the Error handle, leaving a notice with the reason (for example similarity 72.3 below threshold 80).
Collect the images first. Use Ask File nodes earlier in the flow to capture the selfie and the ID photo into variables.
No Uanataca equivalent. Selfie-versus-document comparison is a new capability; it does not replace liveness, it complements it.