> ## Documentation Index > Fetch the complete documentation index at: https://docs.didit.me/llms.txt > Use this file to discover all available pages before exploring further. # ID Verification Methods in the Console > Choose which of the three ID Verification methods each country may use, set the fallback switches, and read the method a session actually used. The [ID Verification](/core-technology/id-verification/verification-methods) step in a workflow has a **Countries** tab. That is where you decide, country by country, which of the three methods a person may use and what happens when a non-document method does not land. Everything on the tab writes the [`methods`](/management-api/workflows/feature-configs#ocr--id-verification) key on the ID Verification node — the console and the Management API are two views of the same object. ## Countries and allowed ID methods Open a workflow, select the **ID Verification** node, then **Countries**. Each country row shows the methods it accepts. Pick a country to open its editor. | Section | What it controls | Config it writes | | --------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | | **Document capture** | Whether a photographed document is accepted, plus the document types, subtypes and capture rules for that country | `document.enabled`, `documents_allowed` | | **Non-doc lookup** | Whether the non-document lookup is offered, how many answered attempts the user gets, and whether the workflow's later Liveness and Face Match steps are skipped after a portrait-backed match | `id_lookup.enabled`, `id_lookup.max_attempts`, `id_lookup.skip_liveness_and_face_match` | | **Wallets accepted** | Which digital ID wallets that country offers. An accept-list, not a ranking — the end user picks from what you tick | `wallet.enabled`, `wallet.providers` | | **Fall back to document capture when…** | One switch per failure mode | `id_lookup.on_partial_match`, `id_lookup.on_no_match`, `id_lookup.on_provider_error`, `wallet.on_failure` | A country where you turn every method off is rejected on save with **No method enabled — nobody can verify here**, because that configuration cannot verify anybody. ### Availability is server-driven The tab reads the same capability catalog the API validates against, so it can only ever offer you what the platform actually supports: * A method the catalog does not offer in that country is not shown as a choice. * A source or wallet the catalog marks **Coming soon** is listed so you can see the roadmap, but it cannot be switched on. * Wallet sign-in is switched on per environment. While it is off, every wallet reads **Coming soon** whatever the catalog says. ### Expected request and response **See details** on a lookup source or a wallet opens the expected request and response: what the end user is asked for, in plain language, and what the source returns. Each lookup source is named exactly — a government register in most countries, a credit-bureau or residential-records file in some — because that is what determines provenance and the consent regime. The end user never sees the response fields, the source name or the price. ### Bulk switches **Global settings** turns a method on in every country that supports it, so you do not have to walk 36 countries by hand. The per-country editor still wins: switch a method on globally, then turn it off for the one country where you do not want it. ## Prices on the tab Each method shows what it costs. Document capture is \$0.15 with the first 500 checks each month free. Non-document methods are priced per country and per wallet, and any price the pricing catalog has not published yet is labelled a placeholder on the tab rather than presented as a quote. The tab also spells out the billing consequence of each fallback switch, so the cost of a configuration is visible before you save it: * A registry that answered bills the lookup — a match and a no match both count — and the document capture then bills on top when the user falls back. * A lookup that never returned is not billed, so an outage costs you the document price only. * Turn a fallback off and those users are declined; nothing further is billed. * An abandoned or failed wallet sign-in is not billed. ## Reading a session The **ID Verification** block on a session detail carries a chip for the method that produced it and a second chip for its [assurance tier](/core-technology/id-verification/verification-methods#assurance-tiers): **Document / Documentary**, **Non-doc lookup / Data match**, or the wallet's name with **Cryptographic**. A session that fell back from a non-document method to document capture reads as a **Document / Documentary** session. The API does not yet record the method that was tried first on a successful fallback — [`fallback_from`](/reference/data-models#id-verification) is populated only when the country's switch was `decline` and the session was declined — so the console has nothing to draw a "tried this, then that" trail from. To see which non-document method was attempted, use the checks list on the session. Below the chips, each method shows its own evidence: * **Document** — unchanged: the front, back and selfie images, quality scores, extracted fields and warnings. * **Non-doc lookup** — a **Registry comparison** listing every compared field with what the user provided, what the source held, and a **Match**, **Partial** or **No match** result, plus the source name, the time it was checked and the attempt count. A source that did not answer appears as its own row with an error rather than a field verdict. Where the source returned a portrait, that portrait and the user's selfie are shown side by side with the face score. * **Wallet** — the **Credential** card: the wallet, its issuing authority, the credential type, the level of assurance it asserted, when it was verified, whether the signature checked out, and the attributes the wallet shared. Where a source or a wallet shares no portrait, the panel says so instead of leaving an empty frame: there is nothing to face-match, and Liveness and Face Match run as their own steps if the workflow has them. ## Related * [ID Verification methods](/core-technology/id-verification/verification-methods) — the three methods, fallback and billing * [Non-document lookup](/core-technology/id-verification/non-doc-lookup) — per-country fields and consent * [Digital ID wallets](/core-technology/id-verification/digital-id-wallets) — per-wallet attributes and assurance * [Workflows](/console/workflows) — building and publishing a workflow * [Workflow feature configs](/management-api/workflows/feature-configs#ocr--id-verification) — the same settings through the API