Technical Interface Specifications - Complete Peppol Implementation Guide - Peppol.now

Technical Interface Specifications

Complete technical documentation for implementing Peppol connections, from architecture to practical implementation and API integration

Peppol Architecture & Components

The Peppol network consists of various technical components that work together to enable secure and reliable document exchange. The architecture is based on a four-corner model with standardized interfaces and protocols.

Core Components

Access Point (AP)

  • AS4 protocol implementation
  • PKI certificate management
  • Message Level Response (MLR)
  • Message validation and routing
  • Start-AP and C2-C3 connectivity

Service Metadata Publisher (SMP)

  • Endpoint discovery service
  • Participant capabilities registration
  • Document type support
  • REST API interface
  • DNS-based or SML lookup

Service Metadata Locator (SML)

  • Central DNS-based registry
  • SMP lookup service
  • Participant registration
  • NAPTR DNS records
  • High availability setup

Security & Certificates

Peppol uses a robust PKI framework for end-to-end security of all messages and connections within the network. All communication is secured with industry-standard cryptography.

PKI Certificate Requirements • Peppol AP certificates issued by OpenPeppol CA
• X.509v3 certificates with specific extensions
• Minimum SHA-256 signing algorithm
• Certificate validation via OCSP
• Annual certificate renewal mandatory

Need help with complex certificate implementation? Use our certificate management expertise for secure PKI setup.
// Example AS4 message header structure 2024-01-15T10:30:00Z uuid:12345678-1234-5678-1234-567812345678 POP000001 POP000002

API Specifications & Endpoints

REST API Implementation

For integration with the Peppol network, various API endpoints are available. These follow RESTful principles and use standard HTTP methods for optimal interoperability.

SMP API Endpoints

GET/iso6523-actorid-upis::{id}
GET/services/{doctype}
PUT/servicegroup
DELETE/participant
GET/complete/info

Business Document API

POST/as4/send
GET/as4/status/{msgid}
GET/as4/mdn/{msgid}
POST/validate/document
GET/document/metadata
// Example SMP lookup request GET https://smp.provider.com/iso6523-actorid-upis::0106:12345678 Accept: application/xml // Response 0106:12345678

Transport Protocols

AS4 Profile Specifications • OASIS AS4 Profile of ebMS 3.0 Version 1.0
• SOAP 1.2 with WS-Security authentication
• Synchronous and asynchronous message exchange patterns
• Compression via AS4 compression feature
• Maximum message size: 100 MB (configurable per provider)

Need AS4 protocol implementation support? Benefit from our technical expertise for complex integrations.

Implementation Requirements

Technical Requirements

Minimum System Requirements

  • Java 11+ or .NET Core 3.1+
  • TLS 1.2 or higher mandatory
  • 4 GB RAM minimum
  • 10 GB disk space
  • 99.5% uptime SLA

Network Configuration

  • Public IP address required
  • Port 443 (HTTPS) open
  • DNS A/AAAA records
  • Firewall configuration
  • Load balancer support

Monitoring & Logging

  • Transaction logging (7 years)
  • Performance metrics
  • Error tracking & alerting
  • Audit trail compliance
  • GDPR compliant storage

Integration Steps

The technical implementation of a Peppol connection follows a structured process with clear milestones and test phases for optimal results.

1
Analysis Phase
Establish technical requirements and architecture design with stakeholder alignment.
2
Development
Implement API integration and configure message mapping according to Peppol standards.
3
Testing
Conformance testing via Peppol testbed and comprehensive quality control.
4
Certification
OpenPeppol compliance verification and obtain official approval.
5
Production
Execute go-live with real-time monitoring and 24/7 support activation.
Implementation Roadmap The complete implementation takes an average of 8-12 weeks, depending on the complexity of your current systems and the desired integration depth. During each phase, close collaboration with your technical team ensures knowledge transfer and continuity.

Want to optimize your implementation timeline? Plan your strategic implementation for minimal downtime and risks.

Need help with technical implementation?

Our technical experts are happy to help you with all aspects of your Peppol integration, from architecture design to production deployment and ongoing support.

Request Technical Advice Compare Peppol Service Providers

Peppol.now - Your guide in the world of electronic invoicing