Skip to main content
The confirmation mode controls the contact identity step inside a verification. It does not change the organization boundary or the bank account details you send; it changes how the individual is confirmed. For most first integrations, start with kyc.

​
Decision table

ModeUse whenContact stepMain trade-off
kycYou want ezyshield to establish the contact’s identity.The contact provides identity details and completes a face scan.Strong default, but more work for the contact on the first verification.
biometricYour system already has a suitable government-issued portrait image.The contact completes a face scan against the supplied image.Faster for the contact, but your system must already handle the identity image correctly.
skipYou intentionally own contact identity assurance outside ezyshield.No ezyshield contact identity step.Lowest friction, but identity assurance is your responsibility.
If you are unsure, use kyc. You can still use attribution_id to link later verifications for the same payee, and ezyshield can reduce friction on later flows when previous identity evidence can be reused.

​
How the choice affects implementation

For kyc and biometric, you can either let ezyshield send the SMS or deliver the returned individual_confirmation_url yourself. For skip, no contact confirmation link is needed.
biometric requires individual_portrait_image. kyc and skip must not send that field.
Send a stable attribution_id when the payee exists in your system. It lets you retrieve related verifications and helps keep repeat verification history connected to the same record.

​
Mode guides

KYC verification

Best default when ezyshield should establish identity.

Biometric verification

Use when you already have a suitable identity portrait.

Skip contact confirmation

Use only when identity assurance is handled outside ezyshield.