WPsigner is for everyday electronic signatures under the Electronic Transactions Act 1999 and state ETAs — B2B contracts, NDAs, HR acknowledgments — with identity, intention, consent, and audit evidence on your WordPress server. It is not for wills, many powers of attorney, or other instruments that still require wet ink or special formalities.
Australia · document check
Start with the required signature level—not the signing tool. This quick guide shows where a WPsigner SES workflow may fit and where it does not.
Is this instrument excluded from electronic execution, or does it still require wet ink or special formalities?
WPsigner may fit
If Commonwealth or state/territory ETA rules allow electronic form, WPsigner can support a simple electronic signature workflow with identity, intention, consent, reliability evidence, and audit trails.
Common SES use cases
Use a higher-assurance route
Australia’s ETA model is functional equivalence, not an eIDAS QES ladder. WPsigner is not a government-accredited certificate product. When wet ink or ETA exclusions apply, use the required formality instead.
Practical orientation only—not legal advice. The required signature level depends on the document, parties, and applicable law.
Under the Electronic Transactions Act 1999 (Cth) and matching state/territory ETAs, electronic signatures are recognised for most business documents when the method identifies the person, shows intention, is appropriately reliable, and has consent. SaaS envelope pricing and offshore storage rarely match that control on WordPress.
Commonwealth law treats a signature requirement as met when a method identifies the person and indicates their intention regarding the information — for example drawn/typed signatures, email attribution, OTP, or KYC when the risk warrants it.
The method must be as reliable as appropriate (or proven in fact), and for private parties the recipient generally must consent to the electronic method — express or inferred from conduct. Everyday B2B contracts, NDAs, and HR acknowledgments fit this model well.
Each state and territory has its own ETA with similar rules but different exemptions (wills, some powers of attorney, certain court or government forms). Self-hosting on an AU or NZ host keeps signed personal information under your Privacy Act / APP posture instead of a third-party US vault.
Send service agreements and accepted quotes from your site. Clients sign via a secure link — no WordPress account required.
Capture confidentiality and supplier paperwork with timestamps and attribution stored on your Australian (or chosen) server.
Collect handbook and policy acknowledgments with an audit trail your HR team can file under local retention practices.
Agencies and property teams running WordPress can standardise high-volume signing without per-envelope SaaS fees — confirm any state-specific formalities for regulated instruments.
Signed documents stay on your WordPress server. Host with Australian providers (e.g. SiteGround AU, BinaryLane, AWS Sydney) or wherever your stack already lives — you choose storage, backups, and access policy.
WPsigner captures signer identity signals, clear consent to sign, IP/device metadata, document hashes, and optional RFC 3161 timestamps in a tamper-evident audit trail — practical support for ETA-oriented reliability and attribution.
Plans start at $99/year with unlimited signatures on your licensed site. Predictable cost for Australian SMEs and agencies that sign regularly.
Upload the plugin, activate your license, and configure branding — no separate signing platform to host.
Add PDFs for contracts, NDAs, or consent packs. Place signature, date, and text fields where counterparties need to complete them.
Share a secure signing link by email. Download the signed PDF with its audit trail and retain it under your document policy.
Compatible: simple electronic signature (SES) workflows under the Electronic Transactions Act 1999 (Cth) and parallel state/territory ETAs — for most private and commercial documents where an electronic method may identify the person, show intention to approve, be appropriately reliable, and have consent. Typical fits include B2B contracts, proposals, NDAs, vendor onboarding, HR/policy acknowledgments, and many agency SOWs. You can strengthen reliability with email attribution, OTP, or optional KYC when the risk warrants it. WPsigner captures consent, IP/device metadata, document hashes, and optional RFC 3161 timestamps in a tamper-evident audit trail.
Not compatible / not a substitute for: (1) wet-ink signatures where the law or the instrument still requires a handwritten signature; (2) documents excluded from electronic execution under Commonwealth or state/territory rules — commonly certain wills, some powers of attorney, and specific court or government forms; (3) any government-accredited, court-certified, or statutory “special method” signature scheme; (4) eIDAS Qualified Electronic Signatures (QES) or EU written-form equivalence — that is an EU framework, not Australian ETA. If your document needs one of those, use the required formality instead of WPsigner.
No. Australia’s ETA model is functional equivalence, not an eIDAS-style SES/AES/QES ladder with QTSP accreditation. WPsigner is a self-hosted SES evidence tool for WordPress. It does not issue government-accredited certificates and does not claim court certification for every instrument.
WPsigner helps you operationalise ETA s.10 themes: identify the signer, indicate intention to approve, support appropriate reliability (or proof in fact), and record consent to the electronic method — plus retain tamper-evident evidence. Enforceability still depends on the document, parties, configuration, and any exemptions. This page is not legal advice.
No. Compatible for most everyday business contracts under ETA-style rules. Not for instruments that remain excluded or need wet ink / extra formalities (for example certain wills, powers of attorney, or specific court/government processes). Always check the specific instrument and applicable state/territory ETA before assuming electronic form is allowed.
Yes — because WPsigner is self-hosted. Signed files stay on your WordPress server. Choose an Australian host if data residency matters for your Privacy Act / APP programme. Data leaves the site only if you enable external storage, CRM, messaging, payments, or identity providers.
Plans start at $99/year with unlimited signatures on your WordPress site — far more predictable than per-envelope SaaS pricing for teams that send contracts regularly.
Choose an annual or lifetime license with unlimited documents and no per-envelope fees. Keep control of your data and signing workflows.