Prepare to Join Roksnet
Understand what your organization needs and what happens from Organization Identification to operational data exchange through the Roksnet Framework.
✧ Public sector organization? Let’s discuss pricing and get you a better deal ✧
Understand what your organization needs and what happens from Organization Identification to operational data exchange through the Roksnet Framework.
You can use this page to understand the complete path through Organization Identification, secure Self-Service access, Trust Services, Member Directory activation, Security Server setup and certificates, Subsystem registration, and the provision or consumption of data services. Your organization completes each part when it becomes relevant; not everything must be ready on the first day.
First, you select an available Organization Identification method. You then complete the application for the selected method and provide the required organization information. After the application is submitted, Roksnet reserves a Member Code and processes the application using that method.
Use a SWIFT or SEPA bank transfer from an account that enables Roksnet to verify your organization. This route is also available to organizations in the EU and Japan.
If your organization is established in the European Union, you may instead submit an application bearing its qualified electronic seal.
If your organization is established in Japan, you may instead complete the Declaration of Accession through the applicable notarial or apostille route.
Have your organization’s legal name, address, country, organization type, national registration identifier, registering or establishing authority, and the information or documents required for the applicable route ready.
Your organization obtains Roksnet Framework Membership and becomes a Roksnet Member. The reserved Member Code becomes its active Roksnet identity. Membership in the Member Directory and other Roksnet Services are activated separately.
Your organization’s Administrator verifies the required organization-controlled email address and mobile phone number, creates a password, configures authenticator-app 2FA, and confirms the applicable Roksnet Framework documents through the authenticated account. Your organization then provides its general contact and profile information.
Your Administrator needs an organization-controlled email address and mobile phone number, access to an authenticator application, and your organization’s general contact and profile information.
Your organization can securely administer Membership, services, billing, and technical registrations in Self-Service.
Your organization submits a completed Roksnet Trust Services Application signed by an Authorised Signatory acting on its behalf, together with a current registration or establishment document issued by the relevant register or authority. Roksnet reviews the application and may request additional information.
Note: The service relationship supports authentication, organizational signing, certificate validation, and timestamping required for X-Road use within the Roksnet Framework.
You will need an Authorised Signatory and a current registration or establishment document that confirms your organization’s name, registration identifier, and issuing authority.
Your organization can order the certificates and supporting Trust Services required during Security Server setup.
Your organization provides the billing information required for the paid service, reviews the applicable pricing, and activates Membership in the Member Directory. Its Member identity is registered in the Roksnet DEV and PROD environments, and your organization controls the visibility of its profile.
Membership in the Member Directory is a separate paid service. Activation registers your organization’s Member identity; Security Server and Subsystem registrations are completed separately.
Your organization’s Member identity is registered in both Roksnet environments and can serve as the basis for later Security Server and Subsystem registrations.
Your organization orders Security Server registration capacity and provides a supported server. Your technical team installs X-Road, imports the Roksnet configuration anchor, and generates the required certificate signing requests.
Your organization submits the technical certificate requests through Self-Service. Your technical team installs the issued certificates, configures the supporting services, and submits the Security Server registration request from the Security Server.
Your organization will need infrastructure it hosts or controls, technical administration capability, the applicable DEV or PROD configuration, registration capacity, certificate orders, key protection, network configuration, monitoring, backups, and ongoing Security Server operation.
Your Security Server is registered in the selected environment and can establish authenticated, signed, and encrypted X-Road connections.
Your organization orders Subsystem registration capacity. Your technical team defines the required Subsystem identities, adds each participating information system as a Security Server client, and submits the registration request from the Security Server.
Identify the information systems to connect, their intended Subsystem codes and environments, the required registration capacity, and responsibility for each integration.
The registered Subsystem can receive access to data services or publish data services through your organization’s Security Server.
To consume data services: your organization agrees on access with the service provider, which grants your registered Subsystem access to the relevant REST/OpenAPI or SOAP/WSDL data services.
To provide data services: your technical team connects the backend and publishes X-Road-compatible data services. Your organization grants access to approved consumer Subsystems.
Note: Data travels directly between participating Security Servers. The Member Directory distributes the configuration and registration information required for the exchange but does not store or proxy the exchanged payload.
Identify the intended use case, participating information systems, expected counterparties, required data services, access decisions, and operational responsibility. These details may be refined during implementation and do not prevent registration.
Your organization can begin operational data exchange after the required registrations and access arrangements succeed, the integration is configured, and the first exchange completes successfully.
Organization Identification and Framework Membership administration, Self-Service, the Member Directory, registration processing, and the Roksnet Services separately activated or ordered by your organization.
Its Security Server and connected systems, private keys, integrations, access and counterparty decisions, exchanged data, and compliance with applicable law and accepted Roksnet documents.
Membership, Trust Services, Security Server registration capacity, and Subsystem registration capacity are separate services. Review current fees and binding documents before starting.
Start by identifying your organization. Other services and technical work follow later when they become relevant.
Start now
View Pricing Plans
Questions about our services? Our team is here to help you get started.