Guidance changelog
Guidance releases and notices: dated messages about legal and product changes in the places Esign Comply publishes rule packs for. Open to everyone, with Atom and JSON feeds.
Rules, obligations, recommendations and legal notices are published as data on their own release train, apart from code deployments and from the API contract. Nothing in a guidance release can stop an existing integration from recording. See Guidance and adoption.
Guidance is product information drawn from the sources it cites. It is not legal advice and it is not exhaustive. Publication targets are targets, not warranties. A notice describes a change. It does not say whether your flow is or is not lawful.
Notices
- ntc_2026_0003published · effective 2026-11-20
Germany: consumer credit and the text-form profile
inforecord changelaw effectiveresearch reviewedEUDESince 20 November 2026 general consumer credit in Germany may be concluded in text form. The EU pack's exclusion screen blocks immovable-property credit, stricter-form and unresolved transitional cases, and enables general consumer credit only through an approved text-form profile.
- Esign Comply's record
- Sessions that declare the document category consumer_credit for a signer in Germany are screened: immovable-property credit, stricter-form and unresolved transitional cases are blocked from the generic flow.
- Your obligations
- None stated by this notice. The form requirements of the credit agreement remain yours to meet.
- What Esign Comply recommends
- Esign Comply recommends confirming with counsel which text-form requirements apply to your credit product before enabling the flow: a named durable declaration, no defaults, a clear prior explanation and unequivocal assent for checkboxes.
- Does your code have to change
- No
- ntc_2026_0002published · effective 2026-06-19
EU: online withdrawal function for distance contracts
recommendedobligationlaw effectiveresearch reviewedEUDirective (EU) 2023/2673 amends the Consumer Rights Directive to require an online withdrawal function for distance contracts concluded through an online interface, applicable from 19 June 2026. The EU pack carries this as rule EU-12.
- Esign Comply's record
- The EU pack records a withdrawal.submitted event in a distinct contract-withdrawal workflow when your interface reports one, with dispatch time, name, contract identification and the acknowledgment destination. Delivery you perform yourself is tagged asserted.
- Your obligations
- Trader: disclose withdrawal rights and function placement pre-contract; offer accessible withdrawal throughout the period, collect name, contract and contact details, provide separate submission, and acknowledge content, date and time durably without undue delay (EU-12).
- What Esign Comply recommends
- Esign Comply recommends sending a withdrawal.acknowledged report when your own function acknowledges a withdrawal, so the acknowledgment is on file with an independent receipt time.
- Does your code have to change
- Only to follow the rule
- ntc_2026_0001published · effective 2026-11-21
Rule packs published as research drafts
infoinformationproductresearch reviewedFederalCANYFLTXDEVAMAEUUKCHThe first guidance release publishes eleven rule packs: United States Federal, seven U.S. state packs, the European Union, the United Kingdom and Switzerland. Each pack shows its review state. Until counsel admitted in a jurisdiction has reviewed its pack, the pack is a research draft.
- Esign Comply's record
- Every record lists the packs and rules applied. While a pack is a research draft, its record conditions are evaluated and stored with the record, and they do not refuse a live record. State packs that are research drafts run in test mode only; a live session that would apply one falls back to Federal rules with the warning state_pack_unavailable.
- Your obligations
- None. The obligations each pack lists are shown under Profiles and in your generated prompt. The lists are not exhaustive and are not legal advice.
- What Esign Comply recommends
- Esign Comply recommends building and testing against the packs you expect to need in test mode now, so that adoption is a review and not a rebuild once a pack is counsel-reviewed.
- Does your code have to change
- No
Releases
Each publication is a guidance release with an ID, a content hash and a signature under a content-signing key. Every session and every record carries the release in force.
2026.11.1
published- Items
- 11 added · 0 changed · 0 retired
- Content hash
- sha256:77eba20237f4844b35835f650434578633dad6e528ca11ee0778f084b48ffdc7
- Signed with
- esc-content-2026-11
- Notices
- ntc_2026_0001ntc_2026_0002ntc_2026_0003
Pack Version Change Review state US-FED 2026-11-21 added research reviewed US-CA 2026-11-21 added research reviewed US-NY 2026-11-21 added research reviewed US-FL 2026-11-21 added research reviewed US-TX 2026-11-21 added research reviewed US-DE 2026-11-21 added research reviewed US-VA 2026-11-21 added research reviewed US-MA 2026-11-21 added research reviewed EU 2026-11-21 added research reviewed UK 2026-11-21 added research reviewed CH 2026-11-21 added research reviewed
Feeds and API
The public feed is open to everyone and needs no key. Add a jurisdiction to filter it, for example ?jurisdiction=US-NY.
- Atom feed /docs/guidance/feed.atom
- JSON Feed /docs/guidance/feed.json
- Guidance API GET /v1/guidance/notices · GET /v1/guidance/releases
Each notice also has a Markdown copy for AI coding tools, linked from its page.