Skip to main content
Finnish Trust Network (FTN) lets eligible users verify their identity with a Finnish bank identity or supported mobile certificate. Use the Finnish Trust Network API to start bank authentication from your own application without a workflow. FTN also runs inside Didit’s ID Verification workflow step, using wallet identifier ftn and country code FIN. For the hosted integration described below, use the same session creation, session results and webhooks as your other Didit workflows.
Finnish Trust Network is available for Finland. Enable ftn in your workflow’s accepted wallets for FIN. The published price is $0.25 per completed verification. See wallet coverage and pricing for all supported wallets.

​
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:
An unavailable wallet rejects the workflow save. See workflow feature configs for the full API contract and console configuration 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 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. To send users to Finnish Trust Network first and show document capture only after a failure, set document.fallback_only to true. See Offer document capture only as the 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.25 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 for current billing rules.
Last modified on October 28, 2026