E-sign consent and disclosure: what you must tell customers
Short answer: When a law requires you to give a consumer a written disclosure, a loan term, a cancellation policy, certain notices, the US ESIGN Act requires specific steps before you can deliver that disclosure electronically instead of on paper: the consumer has to affirmatively consent, you have to clearly explain their right to a paper copy instead and how to withdraw consent, and you have to confirm they can actually access the electronic format you're using. This applies specifically to legally required consumer disclosures, not to every electronic signature generally. This article covers what the consent language should include and gives a plain-language example to adapt, but it's not a substitute for having a lawyer review your specific disclosure.
You're sending a consumer a document that requires a written disclosure by law, and want to know exactly what you need to tell them before doing it electronically.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
This specific requirement, consent before electronic disclosure, gets confused with general e-signature consent constantly, and they're not quite the same thing. General e-signature validity doesn't require much of a formal consent process for most business contracts. This specific rule is narrower and stricter: it applies when some other law already requires you to give a consumer a written disclosure, and you want to deliver that particular disclosure electronically instead of on paper. For the wider law behind it, read ESIGN Act and UETA explained.
Required consent elements for consumers
Under the ESIGN Act, before delivering a legally required written disclosure electronically to a consumer, you generally need to cover:
- Affirmative consent. The consumer has to actively agree to receive this disclosure electronically, not just passively not object.
- The right to a paper copy. Clear notice that they can request a paper copy instead, and whether there's a fee for it.
- The right to withdraw consent. How they can withdraw consent to electronic delivery later, and any consequences of doing so (for example, needing to then receive future disclosures on paper).
- What hardware and software they need. A statement of what's required to access, print, and retain the electronic disclosure, a specific file format, a particular type of device or software.
- Confirmation of ability to access. Some way of confirming the consumer can actually open and retain the format you're sending, before you rely on their consent going forward.
- What happens if your system changes. If a later change to your system would affect their ability to access records in the format they consented to, you generally need to notify them and get fresh consent.
This specific requirement is about disclosures that some other law already requires in writing, not a general requirement for every electronic signature. Plenty of ordinary contracts don't trigger it at all. It becomes relevant for things like certain lending disclosures, insurance documents, subscription or membership cancellation terms, and other consumer-protection notices where a separate law mandates the written disclosure in the first place. Electronic versus wet signatures covers the cases where paper still matters.
A sample disclosure, in plain language
Here's an illustration of what this might look like in practice, adapted to your specific situation rather than copied directly, since the exact requirements depend on which underlying disclosure law applies to your document:
Electronic Delivery Consent
Before you continue, please read this notice.
We'd like to send you [name the specific disclosure, e.g., "your service agreement and billing terms"] electronically instead of on paper. By checking the box below, you agree to receive this document electronically.
You have the right to a paper copy instead. If you'd prefer paper, contact us at [contact method] and we'll send one at no charge / for a fee of [amount, if applicable].
You can change your mind later. You can withdraw your consent to electronic delivery at any time by contacting us at [contact method]. If you withdraw consent, [describe what happens next, e.g., "future documents will be sent by mail"].
What you'll need. To view and keep this document, you'll need [software/format requirement, e.g., "a PDF reader and the ability to save or print a PDF file"].
Confirming you can access this. By checking the box below, you confirm you're able to access, view, and retain this document in the format described above.
[ ] I agree to receive this document electronically, and I confirm I can access it in the format described.
Treat this as a starting structure to adapt, not a finished legal document. The underlying disclosure law your specific document falls under, lending, insurance, consumer subscription terms, might have its own additional specific wording requirements on top of this general ESIGN consent framework, which is exactly the kind of detail worth a lawyer's review before you put it into production.
Where to place it
This consent notice should appear before, or as part of, the signing or disclosure delivery flow itself, not buried somewhere the consumer is unlikely to see it, like a general terms-of-service page they never open. In practice, that usually means: as a distinct screen or checkbox the consumer actively interacts with before the disclosure is shown or sent, rather than something pre-checked by default; separate from your general terms of service, since this is a specific, narrower consent about delivery method, not a blanket agreement; and recorded with a timestamp as part of your audit trail, the same way a signature itself would be, so you can show the consent was actually captured if it's ever questioned.
A worked example
Say you run a small financing company offering buy-now-pay-later style installment plans to consumers. Before a customer can see their payment schedule and the specific terms governing late fees, a separate law governing consumer lending disclosures requires you to give them that information in writing. If you simply email them a PDF without ever capturing the specific consent described above, affirmative agreement, the right to paper, the right to withdraw, confirmation they can access the format, you've technically delivered the disclosure, but you haven't satisfied ESIGN's conditions for doing so electronically. If that customer later disputes a late fee and claims they were never properly informed, your position is considerably weaker than it would be if you'd captured this consent properly at the point of signup. The fix isn't complicated, it's a one-time screen before the first disclosure goes out, but it has to actually happen, and it has to be documented.
Common mistakes with this specific requirement
- Burying consent inside a general terms-of-service click-through. A single "I agree to the Terms of Service" checkbox covering dozens of unrelated things doesn't clearly demonstrate the consumer specifically consented to electronic delivery of this particular disclosure.
- Never actually confirming access. Some businesses skip the step of confirming the consumer can open and retain the specific format being used, which is one of ESIGN's explicit requirements, not an optional nicety.
- Forgetting to re-confirm consent after a system change. If you switch document platforms or file formats in a way that could affect access, failing to notify existing customers and get fresh consent is a specific, named gap under ESIGN.
- Treating this as a one-time legal checkbox rather than an ongoing process. New customers need this consent captured too, not just the ones who signed up before you built the process.
When you might not need this at all
It's worth being clear about the flip side: if nothing you're sending a consumer is a legally required written disclosure under some other specific law, a standard service agreement, an invoice, a routine notice, this stricter consent process generally doesn't apply at all. A simple statement that the customer agrees to electronic communication generally is a reasonable, lighter-touch practice for those situations, but it's not the same formal requirement covered above. Knowing which category a given document falls into is the actual judgment call here, more than memorizing the consent language itself. Some documents can never go electronic at all; which documents cannot be e-signed lists them.
How I'd approach this
When a client's business involves sending consumers anything that counts as a legally required written disclosure, lending terms, certain insurance documents, cancellation policies tied to a specific consumer protection law, I treat this consent step as its own small, separate piece of the workflow, not something to fold quietly into a general signup flow. It's a short, one-time interaction for the consumer, and getting it right up front avoids a much bigger headache later if a regulator or a consumer ever challenges whether the disclosure was properly delivered.
Frequently asked questions
Questions people ask
Does every electronic signature require this consent process?
No. This specific requirement applies when some other law already requires you to give a consumer a written disclosure and you want to deliver it electronically. Most ordinary contracts and e-signature flows don't trigger it on their own.
Can I just use one general consent checkbox for everything?
It's cleaner to keep this consent specific to the disclosure it covers, rather than burying it inside a broad terms-of-service agreement, since the point is that the consumer actively agreed to electronic delivery of this particular document.
What happens if a consumer withdraws consent after I've already sent several disclosures electronically?
Generally you'd need to switch future disclosures to paper (or whatever alternative you offered) going forward. Past disclosures already properly delivered under valid consent aren't automatically invalidated.
Is the sample disclosure above ready to use as-is?
No, treat it as a structural starting point. Have a lawyer review the specific wording against whichever underlying disclosure law actually applies to your document before using it in production.
Do B2B contracts need this same consent process?
Generally no, this specific, stricter consent requirement is aimed at consumer protection. My guide on the ESIGN Act and commercial customers covers what's different for B2B.