Start with what the API actually verifies against
Before integrating, confirm what the provider's comparison is actually running against — a registry photo from an authoritative source, or only a photo the user submits themselves. The latter can confirm consistency but not independent identity.
Check the outcome model, not just the happy path
A good integration plans for all the real outcomes a face-verify call can return — match, no-match, a near-tie flagged for review, and a liveness failure — not just the success case.
Build idempotency and retries in from the start
Verification calls over mobile networks fail and retry more often than typical API traffic. Confirming the provider supports idempotency keys, and using them, avoids double-enrollment from a retried request.