EquaSign

EquaSign lets you send a document for electronic signature and collect a legally meaningful signature without leaving your WordPress site. It is built around a simple, honest promise: every completed signature produces a self-contained proof file that can be verified independently, offline, with no dependency on our servers. EquaSign implements a Simple Electronic Signature (SES) in the sense of the eIDAS regulation. It is designed for everyday agreements — quotes, mandates, consent forms, internal approvals, service contracts — where a clear, auditable record of who signed what, and when, is what matters. What it does

• Send a document (PDF) to a signer by email for signature.
• Verify the signer's access with a one-time code (OTP) sent over your site's email system.
• Let the signer review the document and apply a signature (typed signature rendered on the document).
• Seal the signed result and generate a proof file for the transaction.
• Keep a tamper-evident record: the proof is sealed with an Ed25519 cryptographic signature so any later modification is detectable.

Self-contained, verifiable proof The distinguishing feature of EquaSign is that the proof of a signature does not rely on our infrastructure to stay valid. Each proof bundle is cryptographically sealed and can be verified on its own, offline. Your evidence keeps its value even if you stop using the plugin. Works on its own EquaSign is fully functional on its own. Installing it, adding your document type and model, and configuring an email transport (see below) is enough to start collecting signatures. No account on any external service is required for the core signing workflow. Data ownership Documents, signer information and proof files stay in your own WordPress site's database and uploads. EquaSign does not send your documents, your signers' personal data, or the content of any transaction to us or to any third party. EquaSuite EquaSign is part of EquaSuite, a set of independent WordPress plugins that also work well together. EquaSign works perfectly well by itself; the rest of the suite is optional. A Pro version of EquaSign is available separately (distributed outside WordPress.org) and unlocks additional features. The free version shown here is complete for the core simple-signature workflow.

1. Upload the plugin to /wp-content/plugins/equasign, or install it from the WordPress plugin directory.
2. Activate the plugin through the Plugins screen in WordPress.
3. On first activation, review and accept the End User License Agreement when prompted.
4. Configure an email transport so EquaSign can deliver access codes and invitations (see the FAQ — "Do I need anything else to send emails?").
5. Open the EquaSign menu to create your first document type and model, then send your first document for signature.

Requirements

• WordPress 6.0 or later.
• PHP 7.4 or later.
• The PHP sodium extension is recommended (WordPress ships a pure-PHP fallback, so EquaSign also works without it; enabling the native extension is recommended for optimal security).
• A working email transport on your site (see the FAQ).

1.0.3

• Security hardening and WordPress.org coding-standards compliance: stricter input validation and output escaping, safer file-upload handling, and internal naming cleanup. No change to the signing, sealing, or proof workflow, or to your data.

1.0.2

• Build-derivation hardening: the free build no longer ships any code, flag, or wording for features it does not include. No change to the signing, sealing, or proof workflow, or to your data.

1.0.1

• WordPress.org review compliance: removed the Pro-feature upsell teasers, replaced the in-admin Pro installer with an outbound link, moved inline scripts and styles to the native enqueue functions, dropped the bundled translations (served by translate.wordpress.org), and added direct-access guards to the vendored files.

1.0.0

• First public release.
• Simple Electronic Signature (SES, eIDAS) workflow: send, verify by one-time code, sign, seal.
• Self-contained, offline-verifiable proof file sealed with an Ed25519 signature.
• Works without the native PHP sodium extension (WordPress pure-PHP fallback supported).
• Compatible with WordPress 6.0+ and PHP 7.4+.