Skip to main content
A verification method is a specific way of validating an identity. Methods are enabled per organization and assigned per API key — the SDK can only invoke a method that is enabled for the key it authenticates with.

Available methods

MethodDocumentInputBiometric
eid_manualEmirates IDManual entry
eid_manual_fingerEmirates IDManual entryFingerprint
eid_card_readEmirates IDCard read (DIP / TAP)
eid_card_read_fingerEmirates IDCard readFingerprint
eid_card_read_faceEmirates IDCard readFace
passport_manualPassportManual entry
Card-read and fingerprint methods require the corresponding hardware (a smart card reader and/or fingerprint sensor) and, on desktop, the matching signed services installed. See Get the SDK and the Android guide.

How methods map to SDK calls

The SDK exposes one validate entry point that takes a request object. The request shape plus whether you attach a fingerprint determines the method:
SDK requestResulting method
EmiratesIdManual (no fingerprint)eid_manual
EmiratesIdManual + fingerprinteid_manual_finger
EmiratesIdCard (no fingerprint)eid_card_read
EmiratesIdCard + fingerprinteid_card_read_finger
PassportManualpassport_manual
See Validation methods for the request fields, and Biometrics for attaching a fingerprint.

Viewing and using methods

In Operations → Methods you can see the methods enabled for your organization (read-only), along with their pricing. The set of enabled methods is configured for your organization by ICP during onboarding — enabling or disabling a method for the organization is not a client control. What you do control is scoping: when you create an API key, you choose which of your organization’s enabled methods that key may call. If the SDK invokes a method the key isn’t scoped to — or that isn’t enabled for your organization — the backend rejects the request.
Each successful verification draws against your organization’s wallet. Review pricing under Methods and your balance under Finance → Balance & Metering before running high-volume methods.