ID-Rights

Get started
Step 1
Step 2
Step 3
ID-Rights APIs
Overview
Country specific information
Service access
Key Util
Operational information
Web service functions
1. Signing Rights
2. KYC/AML support
3. Audit Trail
4. Black/White List
Data elements
Error response
Role codes
Denmark
Finland
Norway
Sweden
Company form codes
Denmark
Finland
Norway
Sweden
Test Data
Error codes
Release notes
Contact us

Service access

​​ID-Rights is accessible through both Internet and an Extranet to Nets. A customer test environment is always available as long as you are a customer. At this page you find information about the URLs and IP addresses to the service and how to get your own test and production setup.​​

 

Access Endpoint

The different URLs  to customer test and production: 

Interface
Customer testProduction
ID-Rights
https://order.id-rights-preprod1.nets.eu/id-rights/app
https://order.idrights.nets.eu/id-rights/app

The different IP addresses to the service:

InterfaceInternetExtranet
ID-Rights (customer test)

91.102.28.54:443

193.161.30.231:443

ID-Rights (production)
91.102.28.97:44391.102.26.181:443

Legacy endpoint

The production endpoint order.id-rights.nets.eu (91.102.27.90) will stop working after 15th December 2024. Please make sure to use the new endpoint order.idrights.nets.eu (91.102.28.97).

TLS Security

​

The communicat​​​ion with ID-Rights is secured using HTTPS. The server certificate used is issued under one of the following Root CAs:​

Make sure that both these root CAs are trusted in your applications.

ID-Rights only supports TLS 1.2 in the communication.

Test and production configuration

To use the ID-Rights service, a customer needs its own test and production configuration to use the service.

Note: The demo app available in the get started guide will give you access to a common test configuration. This is predefined and can be used to try out the service. It is however recommended to get your own test configuration when you develop and test your own applications.

Test

To setup your test configuration, follow the below steps:
  1. Contact Nets support to request a test access.
  2. Fill out the information requested from Nets support and return to the given address. This includes:
    Info about your organisation.
    The service(s) to use.
  3. Generate a certificate request (*.p10 file) for signing and SSL client authentication and return to the given address. The KeyUtil tool may be used to generate this.
  4. Nets support will set up your test configuration and give you the needed credentials (MerchantID and certificate).

Production

To setup your production configuration, follow the below steps:

  1. Contact Nets support to request a production access.
  2. Fill out the information requested from Nets support and return to the given address. This includes:
    Info about your organisation.
    The service(s) to use.
  3. Generate a certificate request (*.p10 file) for signing and SSL client authentication and return to the given address. The KeyUtil tool may be used to generate this.
  4. Nets support will set up your test configuration and give you the needed credentials (MerchantID and certificate).

Incident and change notifications

Nets sends out e-mail and SMS notifications to customers during on-going incidents and e-mail notifications in case of customer affected changes. Customers are added to our notification lists upon customer test and production configuration. To receive e-mail and/or SMS notifications, send your contact details to our support using the Contact us form.

Nets also sends out monthly SLA reports. If you as a customer wants to receive the report, send your contact details to support using the above form.