Platform integration

One integration. Every customer on Peppol. getpeppr handles identity verification, customer authorisation, and network delivery — your platform stays focused on your product.

Built for SaaS platforms

If your customers invoice their own clients, getpeppr lets your platform put every one of them on the Peppol network — through a single integration. You connect once with one master API key. From there you create a Peppol legal entity for each customer, send invoices on their behalf, and receive status webhooks.

We carry the hard parts: KYB verification against official business registries, customer authorisation, Peppol network registration, UBL generation, and BIS 3.0 compliance. Your platform never touches XML and never runs a Peppol access point.

Think Stripe Connect, for e-invoicing. Stripe connects platforms to payments for their merchants; getpeppr connects platforms to Peppol for their customers — you own the experience, we own the compliance pipe.

Create a customer's Peppol identity

curl https://api.getpeppr.dev/v1/legal-entities \
  -H "Authorization: Bearer sk_live_your_master_key" \
  -H "Content-Type: application/json" \
  -d '{
    "externalId": "customer_8412",
    "companyName": "Bright Health Ltd",
    "country": "GB",
    "address": { "line1": "10 King Street", "city": "London", "zip": "EC2V 8EA" },
    "identifier": { "scheme": "GB:VAT", "value": "gb123456789" }
  }'

What getpeppr handles

Every customer you onboard moves through the same managed pipeline. You drive it with simple API calls; we do the regulated work behind each step.

Identity verification (KYB) — each customer's legal identity is checked against the official business registry of their country before activation.
Customer authorisation — your customer attests, on a getpeppr-signed and audited page, that they authorise invoicing on their behalf. Required for production; captured as evidence.
Network registration — we register each verified, authorised identity on the Peppol network (SMP provisioning).
Validation & delivery — UBL 2.1 generation, Peppol BIS 3.0 business rules, and AS4 delivery to the recipient's access point.
Lifecycle webhooks — your platform is notified at each meaningful transition, so your UI stays in sync without polling.

You stay focused on your product. getpeppr carries the Peppol compliance burden — verification, authorisation evidence, and an audit trail for every action.

Master API keys

A standard getpeppr key manages one company's invoicing — it sends, and it reads back, only that company's documents. A master key manages many. It carries the standard scopes plus a legal_entities:* set, so a single key provisions, authorises, bills and reads for all your customers — with strict tenant isolation and a per-action audit trail.

Each customer is fully isolated. A master key only ever sees the customers it owns; anything else returns 404, never another platform's data.

Reading follows the same rule. Listing invoices, received documents or events with a standard key returns your own company's records only — a sub-tenant's document answers 404, the same as an unknown id. Use your master key to read across the customers you manage.

Master key scopes

// A master key carries the standard scopes, plus:
legal_entities:create     // provision a customer's Peppol identity
legal_entities:list       // list the customers you manage
legal_entities:attest     // request a customer's authorisation
legal_entities:send_as    // send invoices on a customer's behalf
legal_entities:archive    // off-board a customer

Country coverage

Before a customer goes live, getpeppr verifies their legal identity against the official business registry of their country. Registry coverage today:

Registry verification coverage by country
Country	Registry	Status
🇬🇧 United Kingdom	HMRC (VAT)	Contact support
🇫🇷 France	VIES (SIRENE / SIRET)	Live
🇩🇪 Germany	VIES (VAT)	Live
🇧🇪 Belgium	VIES (enterprise no.)	Live
🇸🇪 Sweden	Bolagsverket	Live
🇩🇰 Denmark	CVR (DanskCVRAPI)	Live
🇳🇱 Netherlands	KvK (OpenKvK)	Live
🇮🇪 Ireland	VIES (VAT)	Live
🇳🇴🇫🇮 Norway & Finland	—	Not yet verifiable

Coverage expands continuously. Tell us the countries your customers operate in and we'll confirm where we are — and what's next on the map.

Getting platform access

Platform integration runs under a platform agreement — the same footing every serious e-invoicing partner expects. Three steps to live:

1. Sign — we put a platform agreement in place (data processing agreement + order form).
2. Enable — we enable production platform access on your getpeppr account (the sandbox trial you may already be running stays as it is).
3. Generate — you create your master API key in the console and go live.

Platform pricing is published. Pilot (EUR 99/mo), Starter (EUR 199/mo), Growth (EUR 499/mo). Volume-based, built around the number of customers you onboard. Full breakdown on the pricing page.

Try it in sandbox first — free, no call, no agreement. Onboard a test customer, watch it settle, and send on its behalf, end to end — see Your first sandbox test. You can do it with a test identity on scheme 9915, which needs no real company, or against a real business registry if that is what you want to exercise. Attestation is the one part that is production-only, since it involves contacting your customer. The sandbox trial is self-service for an organisation admin: choose A platform for my customers when you sign up, or start the platform sandbox trial later from your console overview. The admin then creates the sandbox master key in the console; you provision a test customer and watch it move from verification to delivery.

Your First Sandbox Test