...
This way, familiar tools and flows will be used helping to reduce any news to learn, while using appropriately pragmatic workflows in the back-office involving both OpenPeppol and GENA association representatives as required.
The process consists of a formal sign-up (steps 1+2) and configuration in your infrastructure.
...
Sign-Up request
A dedicated type of eB2B Sign-Up request is available at the Peppol Service Desk page.
...
Once this stage is completed, follow-up requests are used to go through the more technical next steps.
Request eB2B Certificates and validate initial implementation
The certificate issue process follows the same pattern as the OpenPeppol PKI procedure.
Request Test eB2B Test Certificate
Complete initial Testbed testing (e.g. eB2B connectivity of the Access Point)
Request eB2B Production Certificate
As separate ticket is used in each stage, assigned to the “eB2B Domain” to distinguish from other requestsIn particular, signing the “Peppol Service Provider Agreement” (SPA) with the “Enhanced B2B Domain” option, with OpenPeppol, will be required.
Note: as of 05/2025, a specific “EB2B certificate” is not required anymore; your regular Peppol AP certificate is used to establish your identity as AP operator.
System Configuration
Depending on your infrastructure, configure required flows in Peppol “Test” (SMK) and production.
See also Building an eB2B endpoint for some generic thoughts.