ActiveLogin.Identity provides parsing and validation of Swedish identities such as Personal Identity Number (svenskt personnummer) and Coordination Number (samordningsnummer). Built on NET Standard and packaged as NuGet-packages they are easy to install and use on multiple platforms.
- 🆔 .NET parser for Swedish Personal Identity Number (Svenskt personnummer)
- 🐧 Cross platform: Targets .NET Standard 2.0
- ✔️ Strong named
- 🔒 GDPR Compliant
- 📆 Extracts metadata such as date of birth and gender
- 🔷 Written in F# and C# and works great with VB.NET as well
- ✅ Well tested
CI-builds from master of all packages are available in our Azure DevOps Artifacts feed.
| Project | Description | NuGet | Downloads |
|---|---|---|---|
| ActiveLogin.Identity.Swedish | .NET classes handling Personal Identity Number |  |
 |
| ActiveLogin.Identity.Swedish.AspNetCore | Validation attributes for ASP.NET Core. |  |
 |
| ActiveLogin.Identity.Swedish.TestData | Provides Swedish Identity Numbers test data. |  |
 |
ActiveLogin.Identity is distributed as packages on NuGet, install using the tool of your choice, for example dotnet cli:
dotnet add package ActiveLogin.Identity.SwedishPersonalIdentityNumber provides parsing methods such as PersonalIdentityNumber.Parse() and PersonalIdentityNumber.TryParse() that can be used like this:
var rawPersonalIdentityNumber = "990807-2391";
if (PersonalIdentityNumber.TryParse(rawPersonalIdentityNumber, out var personalIdentityNumber))
{
Console.WriteLine("PersonalIdentityNumber");
Console.WriteLine(" .ToString(): {0}", personalIdentityNumber.ToString());
Console.WriteLine(" .To10DigitString(): {0}", personalIdentityNumber.To10DigitString());
Console.WriteLine(" .To12DigitString(): {0}", personalIdentityNumber.To12DigitString());
Console.WriteLine(" .GetDateOfBirthHint(): {0}", personalIdentityNumber.GetDateOfBirthHint().ToShortDateString());
Console.WriteLine(" .GetAgeHint(): {0}", personalIdentityNumber.GetAgeHint().ToString());
Console.WriteLine(" .GetGenderHint(): {0}", personalIdentityNumber.GetGenderHint().ToString());
// IsTestNumber is an extension method from the package ActiveLogin.Identity.Swedish.TestData
Console.WriteLine(" .IsTestNumber(): {0}", personalIdentityNumber.IsTestNumber().ToString());
}
else
{
Console.Error.WriteLine("Unable to parse the input as a PersonalIdentityNumber.");
}The code above would output (as of 2018-07-23):
PersonalIdentityNumber
.ToString(): 199908072391
.To10DigitString(): 990807-2391
.To12DigitString(): 199908072391
.GetDateOfBirthHint(): 1999-08-07
.GetAgeHint(): 18
.GetGenderHint(): Male
.IsTestNumber(): True
The library can be configured to use different levels 'strictness' when parsing identity numbers. The different levels are:
- Off
- Ten Digits
- Twelve Digits
- Ten or Twelve Digits
By default 'Ten or Twelve Digits' is used but it can be overridden when calling Parse and TryParse, e.g.:
// this would fail since the input is not a 12 digit number.
PersonalIdentityNumber.Parse("990807-2391", StrictMode.TwelveDigits); For more information regarding StrictMode, see the FAQ.
Some data, such as DateOfBirth, Age and Gender can't be guaranteed to reflect the truth due to the limited quantity of personal identity numbers per day.
Therefore they are exposed as extension methods in the C# api and are suffixed with Hint to reflect this. They are also placed in a separate namespace ActiveLogin.Identity.Swedish.Extensions. In the F# api these functions are available in the ActiveLogin.Identity.Swedish.PersonalIdentityNumber.Hints module.
If used to validate input in an ASP.NET Core MVC project, the PersonalIdentityNumberAttribute can be used like this:
public class SampleDataModel
{
[PersonalIdentityNumber]
public string PersonalIdentityNumber { get; set; }
}The PersonalIdentityNumber attribute is available through a separate package:
dotnet add package ActiveLogin.Identity.Swedish.AspNetCoreCoordinationNumber provides parsing methods such as CoordinationNumber.Parse() and CoordinationNumber.TryParse() that can be used like this:
var rawCoordinationNumber = "680164-2395";
if (CoordinationNumber.TryParse(rawCoordinationNumber, out var coordinationNumber))
{
Console.WriteLine("CoordinationNumber");
Console.WriteLine(" .ToString(): {0}", coordinationNumber.ToString());
Console.WriteLine(" .To10DigitString(): {0}", coordinationNumber.To10DigitString());
Console.WriteLine(" .To12DigitString(): {0}", coordinationNumber.To12DigitString());
Console.WriteLine(" .RealDay: {0}", coordinationNumber.RealDay;
Console.WriteLine(" .GetDateOfBirthHint(): {0}", coordinationNumber.GetDateOfBirthHint().ToShortDateString());
Console.WriteLine(" .GetAgeHint(): {0}", coordinationNumber.GetAgeHint().ToString());
Console.WriteLine(" .GetGenderHint(): {0}", coordinationNumber.GetGenderHint().ToString());
// IsTestNumber is an extension method from the package ActiveLogin.Identity.Swedish.TestData
Console.WriteLine(" .IsTestNumber(): {0}", coordinationNumber.IsTestNumber().ToString());
}
else
{
Console.Error.WriteLine("Unable to parse the input as a CoordinationNumber.");
}The code above would output (as of 2018-07-23):
CoordinationNumber
.ToString(): 199908072391
.To10DigitString(): 990807-2391
.To12DigitString(): 199908072391
.RealDay: 7
.GetDateOfBirthHint(): 1999-08-07
.GetAgeHint(): 18
.GetGenderHint(): Male
.IsTestNumber(): True
Some data, such as DateOfBirth, Age and Gender can't be guaranteed to reflect the truth due to the limited quantity of personal identity numbers per day.
Therefore they are exposed as extension methods in the C# api and are suffixed with Hint to reflect this. They are also placed in a separate namespace ActiveLogin.Identity.Swedish.Extensions. In the F# api these functions are available in the ActiveLogin.Identity.Swedish.CoordinationNumber.Hints module.
If used to validate input in an ASP.NET Core MVC project, the CoordinationNumberAttribute can be used like this:
public class SampleDataModel
{
[CoordinationNumber]
public string CoordinationNumber { get; set; }
}The CoordinationNumberAttribute attribute is available through a separate package:
dotnet add package ActiveLogin.Identity.Swedish.AspNetCoreopen ActiveLogin.Swedish.Identity.FSharp
The PersonalIdentityNumber-module provides functions for parsing, creating and converting a PersonalIdentityNumber to its 10- or 12-digit string representation.
"990807-2391"
|> PersonalIdentityNumber.parse
|> function
| Ok pin ->
printfn "%A" pin
pin |> PersonalIdentityNumber.to10DigitString |> printfn "to10DigitString: %s"
pin |> PersonalIdentityNumber.to12DigitString |> printfn "to12DigitString: %s"
pin |> PersonalIdentityNumber.Hints.getDateOfBirthHint |> (fun date -> date.ToShortDateString() |> printfn "getDateOfBirthHint: %s")
pin |> PersonalIdentityNumber.Hints.getAgeHint |> printfn "getAgeHint: %i"
pin |> PersonalIdentityNumber.Hints.getGenderHint |> printfn "getGenderHint: %A"
// isTestNumber is an extension from the package ActiveLogin.Identity.Swedish.TestData
pin |> PersonalIdentityNumber.isTestNumber |> printfn "isTestNumber: %b"
| Error e -> printfn "Not a valid Swedish personal identity number. Error %A" e The code above would output (as of 2018-07-23):
{Year = Year 1999;
Month = Month 8;
Day = Day 7;
BirthNumber = BirthNumber 239;
Checksum = Checksum 1;}
to10DigitString: 990807-2391
to12DigitString: 199908072391
getDateOfBirthHint: 1999-08-07
getAgeHint: 18
getGenderHint: Male
isTestNumber: true
For more usecases, samples and inspiration; feel free to browse our unit tests and samples:
- C# ConsoleSample
- F# ConsoleSample
- ActiveLogin.Identity.Swedish.Test
- ActiveLogin.Identity.Swedish.AspNetCore.Test
The implementation is primarily based on the definition defined in Swedish Law:
But when there have been ambiguities we have also read more info and samples from these links from Swedish authorities:
Worth noticing is that the date part is not guaranteed to be the exact date you were born, but can be changed for another date within the same month.
The implementation is primarily based on the definition defined in Swedish Law:
But when there have been ambiguities we have also read more info and samples from these links from Swedish authorities:
In summary: According to these definitions a coordination number is the same thing as a personal identity number, but you add 60 to the day part.
There is one issue though, in reality Skatteverket themselves does not follow either the definition in law or the definition on their own website. When we looked into the dataset of official testdata we noticed three specific issues:
- There are cases when the month part (YYMMDD-IIIC) is set to 00
- There are cases when the day part (YYMMDD-IIIC) is set to 60 (Day would equal: 00)
- There are cases when the day part (YYMMDD-IIIC) is set to 89, 90 and 91 (Day would equal: 29, 30, 31) in a months where those dates do not exists. I.e. 29 and 30 in february (non leap year), 30 in february (leap year) and 31 in months that only have 30 days.
When we asked Skatteverket explicitly about this distinction between law/definition and reality we were given this explanation:
"A coordination can be issued even when the data (Date of birth) can not be confirmed. In this case, 00 might appear both for month and for day."
When asked for some public documentation on this, the closest thing Skatteverket has is the developer documentation for Navet.
In "Bilaga 7 XML-struktur" there is a definition under "5.1.2 Personid" that states that Month has a range of 00-12 and Day has a range of 60-91 (00-31 when subtracting 60).
We do not agree that it follows from Day has a range of 60-91 (00-31 when subtracting 60) that days in the range 29-31 are valid days for any month in the year. Skatteverket has not been able to present us with any official documentation to support their interpretation. Nevertheless we have decided to go with the less strict interpretation in our implementation simply because we want to avoid false negatives when parsing an identity number.
The library supports 'strict' and 'loose' parsing modes. In strict mode the client specifies the exact format they expect to be parsing, i.e. StrictMode.TenDigits, StrictMode.TwelveDigits, StrictMode.TenOrTwelveDigits. If the input string contains any additional characters or whitespace except digits and the optional delimiter (for 10-digit numbers) the parsing will fail. With the 'loose' parsing mode Off, any invalid characters will be removed from the input string, while still preserving digits and + when that applies.
- StrictMode.TenDigits
- YYMMDD-BBBC
- YYMMDD+BBBC
- YYMMDDBBBC
- StrictMode.TwelveDigits
- YYYYMMDDBBBC
- StrictMode.TenOrTwelveDigits
- Any of the above
StrictMode.Off would also support other variations such as
- YYMMDD BBBC
- YYYYMMDD-BBBC
- YYYYMMDD BBBC
- YYYY MM DD BBB C
- YY-MM-DD-BBBC
And basically anything else that can be cleaned and parsed :)
- YY: Year
- MM: Month
- DD: Day
- BBB: Birth number
- C: Checksum
As the definition of coordination number is very close to personal identity number, the section above applies to coordination number as well. StrictMode works in the same way as for personal identity numbers:
- StrictMode.TenDigits
- YYMMDD-IIIC
- YYMMDD+IIIC
- YYMMDDIIIC
- StrictMode.TwelveDigits
- YYYYMMDDIIIC
- StrictMode.TenOrTwelveDigits
- Any of the above
StrictMode.Off would also support other variations such as
- YYMMDD IIIC
- YYYYMMDD-IIIC
- YYYYMMDD IIIC
- YYYY MM DD IIIC
- YY-MM-DD-IIIC
But, as described in Exceptions to the definition, a coordination number can have 00 for month and 60 (00) for day. Also, for a coordination number we have an individual number instead of birth number.
- YY: Year
- MM: Month
- DD: Day
- III: Individual number
- C: Checksum
The Swedish word "personnummer" is translated into "personal identity number" by Skatteverket and that's the translation we decided on using as it's used in official documents.
Unfortunately the term "social security number" or SSN is often used even for a swedish personal identity number, even though that is misleading as a SSN is something used in the United States and should not be mixed up with a PIN.
To comply with GDPR and not no expose any real PINs, we are using the official test data for Swedish Personal Identity Numbers provided by Skatteverket.
If you need to use test numbers yourself, for example if you need to write tests using personal identity numbers, but want to avoid violating GDPR, we provide a nuget package with a simple api to get random test numbers or strings. You can also check if a personal identity number is a test number.
using ActiveLogin.Identity.Swedish.TestData;
var aTestNumber = PersonalIdentityNumberTestData.GetRandom();
aTestNumber.IsTestNumber(); // => trueusing ActiveLogin.Identity.Swedish.TestData;
var aTestNumber = CoordinationNumberTestData.GetRandom();
aTestNumber.IsTestNumber(); // => trueopen ActiveLogin.Identity.Swedish.TestData
let aTestNumber = PersonalIdentityNumberTestData.getRandom()
aTestNumber |> PersonalIdentityNumber.isTestNumber // => trueopen ActiveLogin.Identity.Swedish.TestData
let aTestNumber = CoordinationNumberTestData.getRandom()
aTestNumber |> CoordinationNumber.isTestNumber // => trueSome forms of a Swedish Personal Identity Number and Swedish Coordination Number depends of the age of the person it represents.
The "-" will be replaced with a "+" on January 1st the year a person turns 100 years old. Therefore these methods (.To10DigitStringInSpecificYear(...), .ParseInSpecificYear(...), .TryParseInSpecificYear(...)) exists to define at what year the the data should be represented or parsed.
Useful for parsing old data or printing data for the future.
Active Login is an Open Source project built on .NET that makes it easy to integrate with leading Swedish authentication services like BankID. In addition, Active Login also contain convenient modules that help you work with and handle validation of Swedish Personal Identity Number (svenskt personnummer).
In our Security Policy you can read about how to report a vulnerability, how to subscribe to security alerts and what packages we currently support.
We are very open to community contributions to Active Login. Please see our contribution guidelines before getting started.
Thank you to all who have and are contributing to this project!
The three primary ways to interact and stay updated with Active Login are:
Active Login is licensed under the very permissive MIT license for you to be able to use it in commercial or non-commercial applications without many restrictions.
All trademarks are the property of their respective owners.
Active Login is built on or uses the following great open source products:
Active Solution is the main sponsor of Active Login. Active Solution is located in Sweden and provides IT consulting with focus on web, Azure and AI.
Bright cloud solutions - System development that shines. Together, we create systems that will rocket your business.
And yes, we are hiring 👩💻 :)
https://www.activesolution.se/
If you need help with implementing Active Login, there are commercial support & training options available. See ActiveLogin.net for more details on how to get in touch with us 📞.