Prerequisites
- provider contract
- sandbox/production separation
- receiver ID and test approval
Peppol · partner
Peppol via partner provider
The Peppol strategy separates validation, preparation, partner transmission and status feedback.
Data flow
- Dynafis validates
- provider transmits
- status/webhook is returned
Limitations
- Dynafis does not claim own access point
- live sending requires credentials
Test path
- create sandbox transmission
- check idempotency and status
Formats and authentication
Peppol BIS Billing 3, UBL 2.1
provider credentials reference
Support through the Dynafis API/integration channel. Production use only where status is supported.