We offer four primary services:

• Verification: Verify user identities with national eIDs for KYC compliance, fraud reduction, and secure login.

• Digital signatures: Securely collect legally binding electronic signatures with signing flows customized to match your brand.

• Age verification: Verify your customer's age online when selling age-restricted products like alcohol and tobacco.

• Caller authentication: Verify callers with agent-initiated eID authentication. 

 We support all major electronic identities across Europe and the Nordics:

• MitID (Denmark)

• MitID Erhverv (Denmark)

• BankID (Sweden)

• Freja eID (Sweden)

• BankID (Norway)

• Vipps MobilePay (Norway)

• Finnish Trust Network (FTN) (Finland)

• iDIN (Netherlands)

• Personalausweis (Germany)

• OneID (UK)

• Samleikin (Faroe Islands)
  
  

Missing an eID on the list? Contact us!

Learn more about eIDs → 

 Our platform is built by developers, for developers:

• Simple documentation and a growing list of SDKs

• Access to all eIDs through a single integration

• Customizable flows that you can tweak to match your brand

• Instant support directly from developers via Slack
  

All of this at a fair, competitive price. (Plus a free test environment that you can use without credit card or time limits.)

Learn how you can switch to Idura →  

 Idura supports the following signature levels:

• Simple Electronic Signatures (SES) via Drawable

• Advanced Electronic Sealing (via Idura Signatures)

• Qualified Electronic Signatures (QES) in Norway (via Norwegian BankID)

1. Create a free test account
2. Set up your domain
3. Set up your application
4. Test your selected eIDs
5. To go into production, upgrade to a paid plan

Learn more in our documentation →

1. Choose your preferred payment plan
2. Provide your credit card details
3. Apply for and get the needed eID certificates
4. Set up your application in production
5. Go live!

The timeline depends on which eIDs you need.

Some eID providers are approved instantly through Idura, while others require a separate registration that may take up to 10 business days. 

You pay a monthly platform fee, plus a per-usage fee for each eID (varies per eID).

See our pricing pages for details.

For complex projects, a one-time onboarding fee may apply. After onboarding, you only pay the subscription and eID provider fees.

There is no onboarding fee for self-service credit-card subscriptions.

Your subscription renews automatically at the end of your billing period (monthly or yearly).

You can cancel at any time to stop it from renewing.

Yes!

Annual plans also grant a 10% discount.

Enterprise customers can request invoicing as a flexible payment option.

Yes!

We offer enterprise plans for both Idura Verify and Idura Signatures.

Enterprise plans include:

• Customizable product features and integration options

• Tailored commercial advice

• Sales-assisted purchasing

• Formal SLA options

• Flexible invoicing options

• Demo availability
  

Contact a digital identity expert → 

We currently have the following certifications:

• MitID certification (ISAE3000 format)

• FTN certification

• NSIS certification (ISAE3000 format)
  
  

We also issue an audit report in ISAE 3000 format for our Information Security Management System as a whole.

In our Trust Center you can also find a mapping of MitID controls to ISO27002.

See more in our Trust Center →

Yes!

Our integration gives you access to all supported eIDs across different countries and products.

You choose which eIDs to offer and each eID has its own associated transaction fee.

Idura uses existing standards like OpenID Connect (OIDC) and CIBA.

This means you can integrate using widely available tools and libraries, without any specialized API knowledge.

We guarantee a monthly uptime of at least 99.5% on our standard plans and 99.9% for enterprise customers.

In the exceptional case of scheduled maintenance, we'll communicate it at least 24 hours in advance. (Scheduled maintenance is not our standard practice and has never yet been necessary.)

You can monitor our system status in real time:

See Idura Service Status here →

Idura can use browser language preferences or authentication parameters like ui_locales, where supported:

• MitID: Danish, English

• Norwegian BankID: Norwegian Bokmal, English

• Swedish BankID: Swedish, English

• Finnish Trust Network: Finnish, Swedish, English

• iDIN: Dutch, English

• Personalausweis: German, English

• Freja eID: Swedish, English

Note: The underlying eID provider controls parts of the authentication experience, so language availability may vary.

Idura provides SDKs and integration guides for a wide range of platforms.

• Frontend and mobile: React, JavaScript, Vue.js, React Native, Expo, Kotlin (Android), Swift (iOS)

• Backend: Node.js (Express), PHP, ASP.NET Core

• CMS: WordPress

• Idura Signatures SDKs: Node.js (@criipto/signatures), Python (criipto-signatures), C# (Criipto.Signatures)
  

For Idura Signatures languages with no SDK, the API endpoint returns its schema on a GET request, and a codegen tool can generate a typed client from it.

See our documentation →

Idura Signatures produces documents in the PAdES-LTA standard.

PAdES-LTA is designed to support long-term validation of electronic signatures in PDF documents.

The law requires online retailers to implement a digital age verification systes to ensure customers are either 16 years old (for beverages with alcohol content between 1.2% and 16%) or 18 years old (for beverages above 16% alcohol content, tobacco, tobacco substitutes, and herbal snoking products).

This aligns online sales with existing in-store age verification requirements. 

Yes, our Caller authentication product lets you verify your users' identities when talking to them on the phone.

We faciilitate Swedish BankID phone authentication via the CIBA flow.

Learn more in our docs → 

Yes!

We support both the BankID app and file-based BankID.

On mobile, we can also redirect users directly to the BankID app without a QR code to scan. 

You have two options:

1. Match users by their social security numbers (if you have those on file)

2. Ask users to do a double authentication to combine the old login with the new BankID one. 

BankID with biometrics has the second-highest level of assurance and covers almost all authentication cases.

If you need the highest level of assurance, you'll have to upgrade to BankID High.