# FINMA online identification

Turn on FINMA online identification (Circular 2016/7) on the Identity Document step for onboarding by Swiss financial intermediaries. It is the electronic-copy route (Rz 32–37.1) with a chip read instead of a bank transfer (Rz 33.1), or, with Accept the Swiss e-ID on, the E-ID route (Rz 44.1–44.4): valid credential from a trusted issuer, holder binding, liveness, a selfie matched to the e-ID portrait and the address check. Until the federal E-ID launches only swiyu beta credentials exist; they are always held for review (`FINMA_EID_BETA_CREDENTIAL`). The age-only e-ID is refused. The workflow must have Require NFC chip, Liveness Check, Face Match and Proof of Address (or the setting that accepts digital address evidence). Video identification, the QES route and the bank-transfer route are not offered. Your institution keeps its own duties: its risk policy, the approval of higher-risk relationships, the equivalence judgement for digital address evidence and archiving.

| What the profile checks | Reason code when it holds | Default |
| --- | --- | --- |
| A verified chip (passive authentication against the CSCA list; active authentication where the chip offers it). Documents without a chip are never approved by machine | `FINMA_CHIP_NOT_VERIFIED` | Review (or decline) |
| The selfie against the chip portrait (the face match) and, recorded separately, against the printed portrait | `FINMA_PORTRAIT_MISMATCH` | Review (or decline) |
| At least two security features drawn at random per session from those that ran for the document (seed and results in the report) | `SECURITY_FEATURES_INSUFFICIENT`, `SECURITY_FEATURE_FAILED` | Review (or decline) |
| MRZ decoded, check digits and printed data compared; your `expected_details` compared. QR-code documents are not supported yet | `FINMA_MRZ_NOT_CROSSCHECKED` | Review (or decline) |
| Residential address: proof of address, or digital address evidence if your workflow accepts it | `FINMA_ADDRESS_UNVERIFIED` | Review (or decline) |
| PEP or sanctions hit, or a FATF call-for-action country (document, nationality or IP): approval needs a second reviewer | `FINMA_HIGHER_RISK` | Review only |
| E-ID route: credential validity, trusted issuer or holder binding not established | `FINMA_EID_NOT_VERIFIED` | Review (or decline) |
| E-ID route: a swiyu beta credential (not a proof of identity) | `FINMA_EID_BETA_CREDENTIAL` | Review only |

Digital address evidence (Rz 37.1) is supporting evidence only: the address country (from the proof of address, else `expected_details.address_country`) is compared with the IP country of the captures, and for Switzerland and Liechtenstein the postal code and locality (`address_postal_code`, `address_locality`) are checked against swisstopo's official directory of localities. It counts as the address check only when the workflow's accept digital address evidence setting is on (off by default).

Read the identification record with `GET /v1/verifications/{id}/finma-record` (scope results:read) or download it on the verification page. It lists each requirement with its margin number, the evidence and the outcome, the security-feature selection, the beneficial owner declaration, timestamps and reviewer actions, and is signed like the result. The signed result carries `finma` (holds, security features, address method, whether a second reviewer is required).

### Beneficial owner declaration

Add the Beneficial Owner Declaration step (it needs Email or Phone Verification). After verifying their contact, the person declares whether they are the beneficial owner of the assets; if not, they give the beneficial owner's name, birth date, nationality and address. They sign the declaration with a one-time code sent to the email or phone they just verified, and the time, IP address and user agent are recorded (Rz 48). The signed result carries `beneficial_owner` (state, whether the person is the beneficial owner, when and how it was confirmed); the beneficial owner's details are in the FINMA record and the dashboard. An unconfirmed declaration holds the verification with `BENEFICIAL_OWNER_NOT_CONFIRMED`; a third-party beneficial owner holds it with `BENEFICIAL_OWNER_THIRD_PARTY` (review by default; may be set to approve). Webhooks stay identifiers-only: read the result or the record after `verification.completed` or `verification.review_required`.