Identification Process

Identification Endpoint

POST https://api.sandbox.billit.be/v1/einvoices/registrations/{RegistrationID}/identification

📝 Precondition

You must have an active registration, the entity must be created. When the entity is active, you have a RegistrationID. Create it with:

POST https://api.sandbox.billit.be/v1/einvoices/registrations

If you skip or fail this step, calls to /identification will return 404 Not Found or 401 Unauthorized.

🔑 Path Parameters

Name	In	Type	Required	Description
`RegistrationID`	path	string	yes	The ID obtained from the initial registration.

🛠️ Request Body

{
  "IdentificationProviderTC": "ItsMe",
  "RedirectURL": "https://your.app/after-id-check"
}

Field	Type	Required	Description
`IdentificationProviderTC`	string	yes	Which identity-provider Terms & Conditions you require (e.g. `"ItsMe"`). (Later more options then will be supported).
`RedirectURL`	string	yes	Where Billit will send the user after the identity check, with two extra query parameters.

⚠️ IMPORTANT

You have 5 minutes to complete the check from the moment you POST.

If the session expires or the user abandons, you must re-POST (no resume).

Itsme on Sandbox versus Itsme on production

Environment	Itsme Use
Billit Production	Normal use of Itsme
Billit Sandbox	The normal Itsme app is for production and cannot be used for testing on the Billit Sandbox. In order to use Itsme for testing, the following procedure can be applied: https://partner-support.itsme-id.com/hc/en-us/articles/360052052054-How-to-download-the-itsme-E2E-mobile-app. This includes install of another app and whitelisting at Itsme.

✅ Successful Response (200 OK)

{
  "RedirectURL": "https://idprovider.com/start?session=abc123"
}

Field	Type	Description
`RedirectURL`	string	Full URL where you must now redirect your customer (HTTP 302 / meta).

Next steps:

Issue an HTTP redirect (302) to the returned RedirectURL.
Customer (authorised user of the entity) completes the identity flow with the provider.
Provider redirects back to Billit; Billit will automatically validate internally.

🔄 Final Callback to Your App

After the provider flow, Billit:

Validates the incoming request.
Determines success or failure.
Redirects the user’s browser to your RedirectURL, appending:

?registrationID={RegistrationID}&success=true|false

Example of result:

https://your.app/after-id-check?registrationID=42&success=true

https://your.app/after-id-check?registrationID=42&success=false

Note: Always read both registrationID and success query params—without them you won’t know the outcome.

Next action:

status = success : identification is done, ready to set up integration and/or start sending..
status = false : identification needs to be relaunched.