Partner register โ Quickstart¶
Register a first service and download its certificates in about ten minutes. This page follows a verification service, the most common case. Issuers follow the same path with a few more fields: see Issuance service.
1. Get access¶
You sign in to the register with your Playground account, the GitLab account of the playground (tools.playground.france-identite.gouv.fr/gitlab). Your organisation's partner group gives you access: every member of the group manages the organisations bound to it.
- You already have a GitLab account? Your playground GitLab account works. Open the partner space and choose Continue with Playground.
- No account yet? Request access from the France Identitรฉ team. Give the name of the group you want for your organisation (for example
acme, created asplg/partners/acme) and the name and email address of each person who will register your services. Onboarding is done every day.
Pick English in the header if you prefer: the register remembers it in your browser.
2. Create your organisation¶
The first time you sign in, the partner space asks you to create your organisation.

- Fill in the Legal name, an optional Trading name (shown to users), the 9-digit SIREN number and the Establishment address. The address is never published.
- Give a Registration contact email address.
- Click Create the organisation.
Your organisation's identifier in the register is FR-RCS.Sandbox.B.<SIREN>. The register does not check what you declare: being registered here does not prove an identity. See Organisation and team for teams that manage several organisations.
3. Register a verification service¶
Your dashboard now shows a Getting started checklist and the three kinds of service. Follow the steps below. Use the arrows, the dots or your keyboard's arrow keys to move through them.

Start from the dashboard
The checklist shows where you are. Scroll to Declare your first service and choose Verify data: your service requests data from the wallet.

Describe the service
Enter the Service name, as users will see it, the Service address and the address of your Privacy policy (it must start with https://). The wallet shows these to the user. Click Continue.
Say who queries the wallet
Keep Our service, directly: your service signs its own requests. This step only appears when an intermediary is registered; choose A registered intermediary if a provider queries the wallet for you. See Intermediaries.
Choose an attestation
Under Add an attestation, pick one of the attestations that registered issuers deliver, then click Add. The list is the attestation catalogue.

Tick only the data you need
Tick the data items your service needs, for example family_name, given_name and birth_date. The wallet warns the user about any request beyond what you declare here.
Explain why
In Why is this data needed?, write the purpose in one sentence. The wallet shows it to the user when you request the data. Click Continue.
Let the sandbox prepare your certificates
Keep The sandbox prepares everything: the register generates the key and the access certificate, and you download a .p12 file. To keep your own key, choose I use my own keys and upload a CSR: see Certificates. Click Continue.
Review and register
Check the summary, tick I confirm that this information is accurate for this test environment, then click Register the service. The service is published, its access certificate is issued, and a registration certificate is issued for the intended use.

Your service is registered
The page lists what is left to do, and below it Your files, ready to install. You can come back to these files at any time from the service's Certificates tab.
4. Install the certificates¶

| File | What it is | Where it goes |
|---|---|---|
access.p12 |
Your service's access key and access certificate (WRPAC), with its chain. Protected by the Password of the .p12 files shown above it. | The service that signs your presentation requests. |
<service>-<intended use>.jwt |
The registration certificate (WRPRC) for this intended use. | Attached to each presentation request. |
To read the .p12 file with OpenSSL, or extract PEM files for tools that cannot read .p12:
Your verifier signs each OpenID4VP request with the access key, puts the access certificate in the x5c header, and attaches the registration certificate. See Use your certificates for the details.
Sandbox keys stay in the sandbox
With The sandbox prepares everything, the register keeps a copy of your keys so you can download them again. Never use this option for a production service: use your own keys there.
5. Check the publication¶
Open the service from the dashboard (Manage the service). On its Overview tab, under Your service publication, click Check publication. Present in the trust publication means a wallet looking your service up in the register finds it.

Your service also appears in the public register, with its purpose and the data it requests.
6. Test with a wallet¶
| Wallet | Checks the register? | Use it to |
|---|---|---|
| Registry build of the EU reference wallet | โ | Check that your request is signed with a registered access certificate and stays within your registration. |
| France Identitรฉ Partenaires | ๐ง planned | Test your flow end to end with the French wallet. It does not check the register yet. |
See Test your registration for what each wallet shows, and what a lookup in the register does and does not prove.
Next steps¶
- Add more intended uses, or change one: Verification service.
- Issue attestations: Issuance service.
- Query the wallet for clients: Intermediaries.
- Fetch your registration certificates automatically: APIs and automation.
Something not working? See Troubleshooting, or contact anthony.carmoy@interieur.gouv.fr.