Skip to main content

Verify Learner Identity with BankID - Article

Understand the optional BankID identity-verification connection, choose checkout or training-page verification and distinguish identity status from learning evidence.
Updated: 14 Nov 2026
5 min read

Summary

Some training processes need an additional identity check when a person purchases or accesses training. The optional BankID connection supports a configured digital-identity provider and a selected verification point. Plan that point, the profile evidence and the learner’s supported provider route before enabling the requirement.

Use this article to:

  • Choose checkout or training-page verification
  • Understand provider activation and identity fields
  • Configure the relevant Activity requirement
  • Verify the actual learner journey and reporting evidence

Choose the identity question you need to answer

A training provider may need to check the identity of a purchaser or establish the identity associated with access to a particular training. Those are different moments in the journey. The connection offers BankID verification type to determine whether verification is used during checkout or on training pages.

Identity verification is not a learning result. It does not show that a person understood a procedure, attended an Event or passed an assessment. Keep the identity requirement alongside the Training Activity’s own enrollment, access and completion requirements.

Establish the supported identity-provider setup

Ask Eurekos to confirm activation, the supported provider and the setup appropriate for your audience. The identity-service configuration can expose regional methods such as Norwegian/Swedish BankID or Danish MitID through its configured provider service. The methods a learner actually sees depend on that application’s configuration; do not promise every method to every audience.

Where delegated, the configuration is under Settings → Third party integrations → BankID. It uses OpenID Connect Discovery Document, Client ID, Client secret and BankID verification type. Request SSN/NNIN, where configured, controls requesting the identification number from the provider.

Coordinate identification-number handling and reporting with the organization’s identity and information owners. Do not collect the value merely because the provider can supply it, and do not expose it in screenshots or general support correspondence.

Distinguish provider verification from profile maintenance

When the feature and profile fields are enabled, the profile can include BankID and BankID verified. Authorized administrative roles can maintain the configured fields; other roles can have view-only access. The permitted maintenance scope still matters.

A status set manually is not the same event as a learner completing the provider’s verification journey. The access flow can rely on the verified checkbox in either case. Define who may maintain it and what evidence the process needs; do not describe every checked value as proof that a provider check just occurred.

Configure the relevant Activity requirement

Platform verification typeActivity featureLearner experience
Verification on checkoutRequires BankID validation in the Price featureVerification is required before the applicable checkout/enrollment can proceed
Verification on training pagesRequires BankID validation in Registration detailsThe learner completes identity verification before accessing the relevant training content

The platform-level choice determines where the Activity option is available. Configure the requirement on the intended Training Activity rather than assuming enabling the provider makes every training require identity verification.

For checkout, the self-enrollment/price flow presents Requires valid BankID and Verify your BankID when the person is not already verified. The learner selects a supported provider, completes its authentication and returns to checkout to continue the normal enrollment process.

For training-page verification, the learner can see Verify your identity with BankID and Verify with BankID before entering the learning content. Successful provider verification returns the person to the normal training route. Verify direct links as well as the ordinary overview route when testing the intended access boundary.

Explain the result and evidence

Successful verification can update the profile’s BankID verified state and, where requested, the BankID identification value. A previously verified user can continue without repeating the check.

The Progress report can include BankID verified and the identification value when the relevant request setting permits it. Use the report only for the evidence the process actually records. It does not establish a new digital-signature, assessment or attendance event merely because the identity fields are present.

Plan support for a learner who lacks the required regional identity method. Confirm the organization’s intended route before making a training mandatory for that audience; an unsupported identity prerequisite can block an otherwise eligible learner.

Verify the configuration

Scenario or checkExpected result or evidence
An unverified learner reaches the selected verification pointThe intended identity prompt appears
The learner completes an available provider methodReturn to the correct checkout or training route and intended profile update
A previously verified learner returnsThe previously verified user can continue without repeating verification
The learner does not complete verificationThe applicable checkout or training access remains blocked
A direct training link is usedThe intended verification boundary is still enforced
Reporting is reviewedIdentity fields reflect the actual configured collection and maintenance process

Troubleshooting

ProblemWhat to check
BankID settings are absentOptional activation and delegated configuration access
Requires BankID validation appears in the wrong expected featurePlatform verification type: checkout uses Price; training pages use Registration details
A learner sees no suitable identity methodProvider application configuration and the audience’s supported regional method
A previously verified user is not prompted againCheck the profile’s verified state and whether verification is required for this enrollment
A report shows no identification numberRequest SSN/NNIN configuration and the actual supplied profile evidence
A checked status is being treated as a new provider eventDistinguish manual profile maintenance from completed provider verification

Third Party Integrations

FAQ