Electronic COC Platform · XML signing & electronic seals

Connect XML signing to the complete eCoC workflow

eCoC XML signing binds a certificate's structured vehicle data to its signer or sealing organisation. Electronic COC Platform connects the validated XML, signing step and submission record so manufacturer teams can trace the file they actually sent.

Discuss XML signing integration

01

Confirm whose certificate will be used

A personal electronic signature and an organisation's electronic seal serve different identity purposes. Confirm the certificate holder, authorised operator and required signing profile with the selected channel. RDW currently specifies at least an advanced electronic seal; a qualified seal is allowed but is not mandatory for that requirement.

02

Protect the exact XML you intend to send

Complete data corrections before signing. Record which XML version was signed and verify that the signed output still matches the intended vehicle record. A PDF signature is not a substitute for signing the structured XML required by the receiving channel.

03

Planning an eCoC signing API integration?

Bring the source system, expected volume, certificate provider and target NAP to the technical review. We define how validated records enter signing, how results return to the vehicle record and how failures are handled. API availability, credentials and the exact interface are agreed for the manufacturer project; this page is not a public API specification.

Official references

Certificate requirements depend on the submission channel. Confirm the current requirements before ordering a certificate.

Updated: 30 September 2026

Frequently asked questions

Does signing the XML submit it to a NAP?

No. Signing and submission are separate steps. The signed XML must be sent through the configured manufacturer connection, and the resulting response must be checked.

Do you issue electronic seal certificates?

The platform manages the workflow around signing. Certificate procurement and identity verification are handled with the selected trust service provider.

Can ERP integration be included?

Yes, subject to the agreed implementation scope. Start with a sample data flow and define responsibilities for mapping, validation, signing and response handling.

Contact

Need a clear eCoC next step before you leave?

Tell us what you are trying to solve in one short message. Share your name and email; our team will respond directly with the right next step.

  • Short form
  • Direct team response
  • No certificate or private key request

Use the form here or open the full contact page for more context.

Open full contact page