FTN was established in 2017 and is managed by the Finnish Transport and Communications Agency Traficom. It replaced the previous identity service, TUPAS, which was phased out in 2019. Security was a key driver for forming FTN, as TUPAS, which had been operating for nearly 20 years, did not meet the new requirements under eIDAS, nor the more extensive new data privacy and protection regulations introduced in Finland.

Competition was another driver for forming the FTN. Under TUPAS, service providers needed a separate contract and a separate integration for each bank they worked with. Under FTN, a single standardised service contract and a single integration allows strong authentication service brokers to resell eID solutions in Finland, with a cap on transaction costs between the bank and eID broker.

Scrive offers access to FTN through an API as well as an integrated part of the eSign electronic signature service.

The Scrive eID Hub is an API that makes it easy for organizations and businesses to integrate FTN and other eIDs into their systems to authenticate their own customers and users. As an eID Hub customer, you sign one contract with Scrive and get access to all the eIDs Scrive supports, but you only buy the eIDs you need and only pay for what you use. This way you avoid having to sign a separate contract with each eID provider and do a separate integration for each.
Built for security, simplicity and scalability, eID Hub provides a single point of access for identity checks, customer onboarding, KYC compliance, secure sign-in and other authentication needs, thus streamlining their digital identity journey for all their markets.

FTN is already integrated into eSign, Scrive’s electronic signature service. eSign makes it easy to send, sign and manage documents on any device, helping businesses digitalise and automate their agreement signing processes. When eSign users send out documents for signature, they may want to add an extra layer of security to make sure only authorised parties can access and sign their documents. They can do this by requiring the signing parties to authenticate themselves, and one option is to use one of the many eIDs Scrive supports.