> ## 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.

# Finnish Trust Network integration

> Configure Finnish Trust Network identity verification for Finland with Didit, including bank sign-in, workflow configuration, verified results and document fallback.

Finnish Trust Network (FTN) lets eligible users verify their identity with a Finnish bank identity or supported mobile certificate.
It runs inside Didit's **ID Verification** workflow step, using wallet identifier `ftn` and country code `FIN`.
You use the same session creation, hosted verification, session results and webhooks as your other Didit workflows.

<Note>
  **Coming soon in production; integration tested in sandbox.**
  Production activation is pending.
  The integration has passed a real sandbox bank sign-in.
  The configuration and user journey below apply once FTN is enabled in your environment.
  Production availability is shown in the [wallet coverage table](/core-technology/id-verification/digital-id-wallets#supported-wallets) and your console.
  Enable `ftn` only when it is marked `available` in the environment you are using.
</Note>

## User journey

1. The user chooses Finland and Finnish Trust Network from the identity methods your workflow accepts.
2. They select a participating bank or supported mobile certificate.
3. They authenticate with that service and authorize the identity verification.
4. They return to the Didit session, which validates the identity result and continues the workflow.

The person needs an active identity with the service they select and access to its authentication method.
They enter bank credentials and approval codes only in that service's authentication experience.
Didit does not ask for a bank password in its verification form.

The Didit method chooser and return screens use the session's branding and custom domain settings.
The selected bank or identity service controls its own authentication screens.

## Configure the workflow

Open your workflow's **ID Verification** step in the console, choose **Countries**, and open **Finland**.
Under **Wallets accepted**, enable Finnish Trust Network when available.
Keep document verification enabled if users should be able to use a document instead.
Save and publish the workflow before creating a new session.

The following is a `methods` configuration fragment, not a complete workflow request:

```json theme={null}
{
  "FIN": {
    "document": { "enabled": true },
    "wallet": {
      "enabled": true,
      "providers": ["ftn"],
      "on_failure": "fallback_to_document"
    }
  }
}
```

An unavailable wallet rejects the workflow save.
See [workflow feature configs](/management-api/workflows/feature-configs#ocr-/-id-verification) for the full API contract and [console configuration](/console/id-verification-methods) for the visual setup.

## Verified result

A completed FTN check returns a wallet verification result with `cryptographic` assurance.
The verified identity includes the user's name, date of birth and personal identifier when returned by the selected identity method.
FTN does not return a portrait.
Inspect the actual result rather than assuming every optional identity field is present.

The session's **Credential** card shows the selected wallet and its verified evidence.
See the [ID verification data model](/reference/data-models#id-verification) for the result schema.
Successful FTN authentication completes the ID Verification step; remaining checks still determine the session's final decision.
Keep separate liveness and face comparison steps configured when your workflow requires them.

## Cancellation and document fallback

If the user cancels, the request expires or verification fails, Didit applies the country's `wallet.on_failure` setting.
`fallback_to_document` starts document capture when document verification is enabled for Finland.
`decline` declines the ID Verification step.
A disabled document method cannot serve as fallback.

A redirect or a displayed bank chooser is not a successful identity verification.
Wait for the verified session result or webhook before granting access.
Handle duplicate webhook delivery using the same idempotent processing as the rest of your integration.

## Test and launch

Test the wallet in the environment where it is enabled.
Cover successful return, user cancellation, expiry, incomplete identity and document fallback.
Also test the devices and browser contexts your users rely on.
A simulated sandbox result does not prove a real bank authentication or production activation.

FTN costs **\$0.30 per completed verification** at the published base rate.
Cancelled, expired and failed wallet attempts do not incur a completed wallet verification charge.
A completed document fallback is charged separately under document verification pricing.
See [wallet pricing](/core-technology/id-verification/digital-id-wallets#pricing) for current billing rules.

## Related guides

* [Digital ID wallet coverage and pricing](/core-technology/id-verification/digital-id-wallets)
* [Smart-ID and Mobile-ID integration](/core-technology/id-verification/smart-id-mobile-id)
* [ID Verification methods](/core-technology/id-verification/verification-methods)
* [Webhook integration](/integration/webhooks)