Advanced Electronic Signature: eIDAS Requirements and US Law

An advanced electronic signature is a category defined by the European Union’s eIDAS Regulation that must meet four technical conditions: it is uniquely linked to the signer, it can identify that signer, it is created using signing data the signer keeps under their sole control, and it is bound to the document in a way that reveals any later change. The label comes from EU law, and the United States does not use it. Under the federal ESIGN Act, any electronic sound, symbol, or process adopted with intent to sign is a valid electronic signature, and courts weigh the evidence behind it rather than sort it into tiers. The practical result is that “advanced” describes both a legal status in Europe and a level of technical rigor that carries evidentiary weight anywhere.

The Four Article 26 Requirements

Article 26 of the eIDAS Regulation sets the definition. First, the signature is uniquely linked to the signatory, so it cannot plausibly be attributed to anyone else.1Legislation.gov.uk. Regulation (EU) No 910/2014 – Article 26 Second, it is capable of identifying that signatory through technical data embedded in the signing process.

Third, it is created using electronic signature creation data that the signer can use with a high level of confidence under their sole control. This is not a password requirement. It means the cryptographic key that generates the signature stays with the signer, whether on a hardware token they physically hold or in a cloud environment protected by strong authentication.1Legislation.gov.uk. Regulation (EU) No 910/2014 – Article 26

Fourth, the signature is linked to the signed data in such a way that any subsequent change is detectable. If a single character in the document changes after signing, verification fails. That mathematical bond between signature and content is what gives the tier its evidentiary strength: a valid check proves both who signed and that nothing has been altered since.

Where Advanced Sits Between Simple and Qualified

eIDAS defines three levels, and advanced is the middle one. A simple electronic signature is any electronic data attached to other data and used by the signer to sign, such as typing a name in an email or clicking “accept.” It carries the least evidentiary weight but still cannot be denied legal effect solely because it is electronic.

An advanced electronic signature meets the four Article 26 conditions and typically relies on cryptographic technology to satisfy them. Most business-to-business contracts in the EU use this tier.

A qualified electronic signature is an advanced signature created with a qualified signature creation device and backed by a qualified certificate issued by a government-supervised trust service provider. It is the only tier that automatically carries the same legal effect as a handwritten signature across every EU member state. A qualified signature creation device must ensure that the signer’s private key cannot be extracted or copied, that no signature can be produced without the signer’s deliberate action, and that signed data cannot be modified afterward. Providers issuing qualified certificates need national approval, must comply with ETSI standards, and undergo regular security audits.

How the Technology Actually Works

Advanced electronic signatures are built on Public Key Infrastructure, or PKI. The system uses paired cryptographic keys to establish a verifiable link between a person and a document.

When you sign, your software generates a unique mathematical fingerprint, called a hash, of the document’s contents, then encrypts that hash using your private key. The encrypted hash is your digital signature. Your private key never leaves your control. A corresponding public key, which can only decrypt what the private key encrypted, is available to anyone who needs to verify.

A certificate authority ties those keys to your real-world identity. After verifying who you are, it issues an X.509 digital certificate that binds your public key to your name, organization, and other identifying details. Someone receiving a signed document uses your certificate to retrieve the public key, decrypts the signature hash, and compares it against a fresh hash of the document. Matching hashes mean the document is authentic and unaltered. A mismatch means either the file was tampered with or the signature did not come from you.

PKI also handles compromised or expired certificates. Certificate Revocation Lists and the Online Certificate Status Protocol let verifiers check in real time whether a certificate is still trustworthy. Trust at scale does not depend on knowing the signer personally; it depends on trusting the certificate authority that vouched for them.

Getting the Certificate You Need

Before you can create an advanced electronic signature, you need a digital certificate from a trust service provider. Enrollment usually runs through four steps.

You verify your identity by presenting a government-issued document such as a passport or driver’s license. Depending on the provider and the certificate tier, this may be an in-person meeting, a video verification session with a live agent, or an automated check. You then complete registration forms with your full legal name, contact details, and professional affiliations; organizational certificates may also require corporate documentation. Once the provider confirms your paperwork, the certificate is issued and stored on a physical USB token, a smart card, or a secure cloud-based hardware security module. Most providers require you to install specific software, browser extensions, or a mobile app to use the certificate.

Costs vary by tier and provider. Qualified certificates from established providers typically start at several hundred dollars per year, while standard digital certificates at a lower assurance level can be less expensive. Certificates are usually valid for one to three years, and renewal involves re-verifying your identity.

If you want signatures to validate automatically in common PDF readers without any extra step by the recipient, check whether your provider belongs to the Adobe Approved Trust List. Providers on that list meet specific technical and audit standards, and their signatures display a green checkmark in Adobe Acrobat by default.

Signing and Verifying a Document

Once your certificate is active, the flow is predictable. You upload the document to your signing platform, position the signature field, and start signing. The platform prompts you for a second authentication factor: a one-time code sent to your phone, a PIN for your hardware token, or a biometric scan. That step confirms that the person signing is actually the certificate holder rather than someone who happened to reach the software.

After authentication, the software hashes the document, encrypts the hash with your private key, and embeds the resulting signature into the file along with your certificate details. It also generates an audit trail recording the timestamp, the authentication method, and the certificate information. That audit trail becomes critical evidence if the signature is ever challenged.

Verification runs the process in reverse. The recipient’s PDF reader or specialized tool extracts the embedded certificate, checks its validity against the certificate authority’s records, uses the public key to decrypt the signature hash, and compares it against a fresh hash of the document. Everything matching yields a confirmation that the signature is valid and the file is unchanged. Any modification after signing breaks the hash comparison and the signature shows as invalid.

Keeping Signatures Valid Over Time

Digital certificates expire, and certificate authorities occasionally go out of business. Without extra precautions, a document that was perfectly valid on signing day can become unverifiable years later. That is a real problem for multi-year contracts, regulatory filings, and archived records.

Long-Term Validation, or LTV, handles this by embedding everything needed to verify the signature directly into the document at the time of signing. The ETSI PAdES standard defines two relevant levels.2ETSI. Electronic Signatures and Infrastructures (ESI) – PAdES Digital Signatures Part 1

  • B-LT embeds all certificates in the signing chain plus current revocation data from Certificate Revocation Lists or OCSP responses. A verifier does not need to contact the certificate authority to confirm validity.
  • B-LTA adds a document timestamp from a trusted time-stamp authority. Even after the original certificate expires, the timestamp proves the certificate was valid when the signature was created.

For documents that need to hold up for years, insist on B-LTA. The added cost and complexity are small compared with the risk of an unverifiable contract when you actually need to enforce it.

How US Law Treats These Signatures

The United States does not slot signatures into “advanced” or “qualified” tiers. Under the federal ESIGN Act, an electronic signature is “an electronic sound, symbol, or process, attached to or logically associated with a contract or other record and executed or adopted by a person with the intent to sign the record.”3Office of the Law Revision Counsel. 15 USC 7006 – Definitions A checkbox, a typed name, and a cryptographic digital signature all qualify.

ESIGN’s core rule is that a signature or contract cannot be denied legal effect solely because it is in electronic form, and this applies to any transaction affecting interstate or foreign commerce.4Office of the Law Revision Counsel. 15 USC 7001 – General Rule of Validity At the state level, 49 states plus the District of Columbia, Puerto Rico, and the U.S. Virgin Islands have adopted the Uniform Electronic Transactions Act, which mirrors ESIGN. New York is the sole holdout, though ESIGN still governs there as federal law.

The practical difference matters. In the EU, a qualified signature carries the same legal weight as ink automatically. In the US, every electronic signature starts from the same legal baseline, and its weight in court depends on the evidence supporting it. That is where the technical rigor of an advanced signature still pays off in the American system.

Under Federal Rule of Evidence 901, the party offering an electronically signed document must produce evidence sufficient to support a finding that the document is what they claim it is.5Legal Information Institute (LII). Rule 901 – Authenticating or Identifying Evidence Rule 901(b)(9) permits authentication through “evidence describing a process or system and showing that it produces an accurate result,” which is why detailed audit trails carry so much weight. A signing platform that logs the authentication method, timestamp, certificate details, and hash verification can authenticate the signature without in-person testimony from the signer. Rule 901(b)(4) also allows authentication through distinctive characteristics of the document, its internal patterns, and the surrounding circumstances.

In litigation, this is where a click-to-sign and a PKI-backed advanced signature diverge sharply. A click-to-sign produces a log entry showing that someone clicked a button from a given IP address. An advanced electronic signature produces cryptographic proof tying a verified identity to an unaltered document, backed by a certificate authority’s validation and a full audit trail. When a counterparty claims they never signed, the second set of evidence is far harder to dispute.

Documents You Still Can’t Sign This Way

Even the strongest technical safeguards will not save a signature on a document that federal law excludes from electronic execution. ESIGN carves out several categories that must still be signed on paper.6Office of the Law Revision Counsel. 15 USC 7003 – Specific Exceptions

  • Wills, codicils, and testamentary trusts, though some states have begun building their own frameworks for electronic wills.
  • Adoption, divorce, and other family law documents.
  • Most transactions governed by the Uniform Commercial Code, including negotiable instruments such as promissory notes. A narrow exception exists for “transferable records” tied to loans secured by real property, where the issuer expressly agrees the record is a transferable record.7Office of the Law Revision Counsel. 15 USC Chapter 96 – Electronic Records in Global and National Commerce
  • Court orders and official filings, including briefs and pleadings required in connection with court proceedings.
  • Certain consumer protection notices: utility cancellations, housing default and foreclosure notices, health and life insurance cancellations, and product recall notices affecting health or safety.
  • Documents required to accompany the transportation or handling of hazardous materials, pesticides, or other dangerous substances.

Getting this wrong can invalidate an entire transaction. Before relying on an electronic signature, confirm that the specific document type is not on the excluded list.