Configure a Peppol participant SMP record and verify AS4 connectivity before go-live

domain: docs.peppol.eu · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Register your Peppol Participant Identifier (ISO 6523 scheme + value, e.g., 0088:GLN) with your certified access point provider, which registers it in the SML
  2. Confirm the SMP record by querying the SML DNS: resolve b-{MD5(participant-id)}.iso6523-actorid-upis.acc.edelivery.tech.ec.europa.eu
  3. Retrieve the SMP service metadata endpoint from the DNS response and GET /{participantId}/services/{documentTypeId} to confirm supported document types
  4. Obtain the recipient's Peppol PKI certificate from the SMP endpoint metadata and verify it chains to the Peppol PKI root
  5. Send a test AS4 message to the OpenPeppol conformance endpoint, confirming signed and encrypted payload delivery via HTTPS

Known gotchas

Related routes

Register as a Peppol AS4 access point and obtain production certificates from OpenPeppol
peppol.eu · 5 steps · unrated
Look up a Peppol participant's capabilities via SMP (Service Metadata Publisher) before sending an invoice
peppol.org · 6 steps · unrated
Build and transmit a Peppol BIS Billing 3.0 invoice XML document and deliver it via an accredited access point using AS4 messaging
peppol.org · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans