> ## Documentation Index
> Fetch the complete documentation index at: https://eurusys-6c0957fa.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Verification methods

> The verification methods you can enable for an API key, and what each one does.

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

| Method                 | Document    | Input                 | Biometric   |
| ---------------------- | ----------- | --------------------- | ----------- |
| `eid_manual`           | Emirates ID | Manual entry          | —           |
| `eid_manual_finger`    | Emirates ID | Manual entry          | Fingerprint |
| `eid_card_read`        | Emirates ID | Card read (DIP / TAP) | —           |
| `eid_card_read_finger` | Emirates ID | Card read             | Fingerprint |
| `eid_card_read_face`   | Emirates ID | Card read             | Face        |
| `passport_manual`      | Passport    | Manual entry          | —           |

<Info>
  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](/distribution/nexus-overview) and the [Android guide](/sdks/android).
</Info>

## 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 request                         | Resulting method       |
| ----------------------------------- | ---------------------- |
| `EmiratesIdManual` (no fingerprint) | `eid_manual`           |
| `EmiratesIdManual` + `fingerprint`  | `eid_manual_finger`    |
| `EmiratesIdCard` (no fingerprint)   | `eid_card_read`        |
| `EmiratesIdCard` + `fingerprint`    | `eid_card_read_finger` |
| `PassportManual`                    | `passport_manual`      |

See [Validation methods](/concepts/validation-methods) for the request fields, and [Biometrics](/concepts/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](/dashboard/api-keys), 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.

<Warning>
  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.
</Warning>