sajn ID - Identity Verification

sajn ID enables secure identity verification using Swedish BankID, allowing you to verify the identity of individuals before granting access to services or completing transactions.

Overview

sajn ID provides two verification methods:

SSN-based verification: Verifies both identity and Swedish personal number (personnummer)
Name-based verification: Verifies identity and name match without requiring SSN

How It Works

Verification Lifecycle

Status	Description
`CREATED`	Verification created but not sent
`SENT`	Verification sent to recipient
`OPENED`	Recipient opened verification link
`VERIFIED`	Successfully verified
`FAILED`	Verification failed
`EXPIRED`	Verification link expired
`CANCELED`	Verification was canceled

Creating a Verification

Creating a verification through the API immediately sends it to the recipient over the chosen channel. There is no create-without-send step.

SSN-Based Verification

Verify both identity and SSN:

{
  "fullName": "John Doe",
  "ssn": "197001011234",
  "email": "[email protected]",
  "channel": "EMAIL",
  "reference": "customer_onboarding_123"
}

Name-Based Verification

Verify identity without SSN requirement:

{
  "fullName": "John Doe",
  "email": "[email protected]",
  "channel": "EMAIL",
  "reference": "age_verification_456"
}

Delivery Channels

EMAIL

Send verification link via email:

{
  "channel": "EMAIL",
  "email": "[email protected]"
}

SMS

Send verification link via SMS:

{
  "channel": "SMS",
  "phone": "+46701234567"
}

API-created verifications use EMAIL or SMS. The channel field returned by the API may also be IN_APP for verifications delivered inside the sajn app.

Verification Data

After successful verification, retrieve the BankID response data:

{
  "id": "verify_123",
  "status": "VERIFIED",
  "fullName": "John Doe",
  "verifiedAt": "2024-01-15T10:30:00Z",
  "data": {
    "completionData": {
      "user": {
        "personalNumber": "197001011234",
        "name": "John Doe",
        "givenName": "John",
        "surname": "Doe"
      },
      "device": {
        "ipAddress": "192.0.2.1"
      }
    }
  }
}

Sensitive information like SSN is encrypted and only accessible to authorized users.

Use Cases

Customer Onboarding

Verify customer identity during account creation:

{
  "fullName": "John Doe",
  "ssn": "197001011234",
  "email": "[email protected]",
  "channel": "EMAIL",
  "reference": "account_signup"
}

Age Verification

Verify age without collecting SSN:

{
  "fullName": "John Doe",
  "email": "[email protected]",
  "channel": "EMAIL",
  "reference": "age_check"
}

Contract Signing Prerequisites

Verify identity before allowing document signing:

{
  "fullName": "John Doe",
  "ssn": "197001011234",
  "email": "[email protected]",
  "channel": "EMAIL",
  "contactId": "contact_123",
  "reference": "pre_signing_verification"
}

Linking to Contacts

Link verifications to existing contacts:

{
  "fullName": "John Doe",
  "email": "[email protected]",
  "channel": "EMAIL",
  "contactId": "contact_123"
}

This creates an audit trail connecting the verification to the contact’s profile.

Audit Logs

Every verification includes a complete audit log:

{
  "audits": [
    {
      "type": "ID_CREATED",
      "createdAt": "2024-01-15T10:00:00Z"
    },
    {
      "type": "ID_SENT",
      "createdAt": "2024-01-15T10:01:00Z",
      "data": {
        "channel": "EMAIL"
      }
    },
    {
      "type": "ID_OPENED",
      "createdAt": "2024-01-15T10:15:00Z",
      "ipAddress": "192.0.2.1"
    },
    {
      "type": "ID_VERIFIED",
      "createdAt": "2024-01-15T10:30:00Z"
    }
  ]
}

Expiration

The identity check and its verification link expire after a set period (default: 7 days from creation). Set a custom expiration with expiresAt when creating the verification — it must be in the future:

{
  "expiresAt": "2024-01-22T23:59:59Z"
}

The current expiration is returned as expiresAt on the verification object.

Billing

Creating a sajn ID verification counts toward your monthly sajn ID quota and is billed according to your plan.

Each successful verification is tracked as a billable event, regardless of whether it completes successfully or fails.

Security Considerations

Token security

Verification tokens are single-use and expire after completion or timeout.

SSN encryption

SSNs are encrypted at rest and only accessible to authorized users with proper permissions.

Audit trail

Complete audit logs track every step of the verification process for compliance.

BankID security

Leverages BankID’s robust security infrastructure for identity verification.

Best Practices

Reference IDs

Always include a reference to link the verification to your workflow

Set Expiration

Use expiresAt to control how long the verification link stays valid

Appropriate Method

Use SSN-based only when legally required; prefer name-based for privacy

Use Webhooks

Subscribe to ID events instead of polling for a better user experience

Next Steps

Identity Verification Guide

Step-by-step guide to implementing ID checks

API Reference

Explore the sajn ID API

​sajn ID - Identity Verification

​Overview

​How It Works

​Verification Lifecycle

​Creating a Verification

​SSN-Based Verification

​Name-Based Verification

​Delivery Channels

​EMAIL

​SMS

​Verification Data

​Use Cases

​Customer Onboarding

​Age Verification

​Contract Signing Prerequisites

​Linking to Contacts

​Audit Logs

​Expiration

​Billing

​Security Considerations

​Best Practices

Reference IDs

Set Expiration

Appropriate Method

Use Webhooks

​Next Steps

Identity Verification Guide

API Reference

sajn ID - Identity Verification

Overview

How It Works

Verification Lifecycle

Creating a Verification

SSN-Based Verification

Name-Based Verification

Delivery Channels

EMAIL

SMS

Verification Data

Use Cases

Customer Onboarding

Age Verification

Contract Signing Prerequisites

Linking to Contacts

Audit Logs

Expiration

Billing

Security Considerations

Best Practices

Next Steps