Platform branding
Set the name, logo and support contact your customers see when getpeppr asks them to authorise Peppol on your behalf.
Where your branding appears
Before a customer can go live in production, getpeppr asks them to confirm that you may register them on Peppol and send and receive invoices on their behalf. You start that step with the attestation endpoint. Your branding is what the customer recognises in two places:
- The authorisation email — your logo, “via” your display name, your name in the text, and your support email as the contact. Replies to the email go to your support email.
- The confirmation page — the getpeppr page the email links to, with your logo, your display name and your support email.
Some parts stay getpeppr's, so the customer can check who is asking. The email is sent from getpeppr <noreply@getpeppr.dev>, the confirmation page lives on console.getpeppr.dev, and the authorisation the customer gives names your company's legal name — the one confirmed on your Order Form or, failing that, on your production Legal Entity — never the display name.
Set up your branding
In the console, open Branding under Platform. The page is available to platform accounts. Every member of your organisation can see it; only organisation admins can change it or send a test email.
| Field | Rules |
|---|---|
| Display name | Required, 2 to 80 characters. Shown as “via your name” and in the email text. |
| Support email | Required, a valid address of up to 254 characters. Customers reach it by replying to the email or from the confirmation page. |
| Logo | Optional. PNG or JPEG, up to 512 KB. Each side between 96 and 4,096 px, and the longer side at most twice the shorter one. SVG is not accepted. |
| Default language | Not a setting yet. Each request is sent in the language your attestation request names, and in English when it names none. |
Save changes applies the branding to the next authorisation requests you issue. See when changes apply.
How your logo is stored
getpeppr hosts the logo itself, so the email and the confirmation page never load an image from a third-party site. Before storing it, getpeppr keeps only what is needed to display the image and removes everything else the file carries: camera and location data, author and comment fields, embedded thumbnails and colour profiles. The pixels are not changed.
- The logo is public. It is served from a getpeppr address that anyone with the link can open, because email clients load it without signing in. Upload only an image you are happy to publish.
- Colours. Removing the colour profile does not change the pixel values. A logo designed in a wide-gamut colour space, such as Display P3, can look slightly less vivid on some screens; a standard sRGB logo looks the same.
- Upload limit. An organisation can upload up to 20 logos per hour.
Preview and send a test
The Preview renders the real email and confirmation page with your current edits and a sample customer, before you save anything, in any language a request can currently be sent in. The language you pick stays in the page address, so a refresh or a shared link opens the page in it.
Send a test email sends that email to a member of your organisation with a verified email address, so you can check it in a real inbox.
- Saved branding. The test uses the branding you saved, not unsaved edits. Save your changes first.
- A link that cannot authorise. Its button opens a preview of the confirmation page, valid for 7 days, that cannot authorise anything.
- Language. The test uses the same language as the preview, and changing it in either place changes both; the email and its preview page use it. Only languages a real request can be sent in are offered.
- Limit. An organisation can send up to 5 test emails per hour.
When changes apply
The branding is fixed when an authorisation request is issued. The email and the confirmation page of that request keep the name, logo and support email it was sent with, even if you change your branding afterwards.