Electronic invoicing, hardened.

• Never persisted in the clear The .p12 exists on disk only inside a WPFE1 envelope encrypted with the signer’s public key.
• A WordPress breach leaks nothing usable The encrypted blob is meaningless without the signer’s private key, which WordPress never holds.
• The signer keeps no secrets at rest Decryption happens in memory for the length of a single request; no key material is written or cached.
• Auditable code The signer is a small, readable service that self-verifies every signature before releasing it.
• Verifiable, not just promised Run as a shared signer in an AWS Nitro Enclave, the cryptographic hash of its image proves exactly which code handles your data — and that code stores nothing and does nothing beyond signing.

The leverage of a shared signer: one hardened instance, serving many stores, deployed as an AWS Nitro Enclave or similar trusted execution environment. Remote attestation publishes a cryptographic hash of the enclave image, so anyone can verify the exact audited binary before trusting it — and by verifying the code, you verify the promise: the attested image neither stores nor processes the data fed to it beyond producing the signature.

1. 1

   The order completes in WooCommerce and the plugin drafts a factura with the buyer data you configured.

2. 2

   You review the parties and DIR3 codes — the autocomplete and relation finder fill the OC-OG-UT triplet for you.

3. 3

   You sign; the signer verifies its own output before anything leaves the service.

4. 4

   You export the signed XML or the VeriFactu-style PDF with the official QR.

5. 5

   You submit to FACe or register the record with VeriFactu, and keep the CSV receipt on the invoice.