state_esra_consent_required

Last updated Jun 14, 2026

Cause

Matter records explicit ESRA-style consent before any natural person can sign a document electronically inside the platform. The consent captures the signer's affirmative agreement to transact electronically, the technologies they consent to, and the means by which they can withdraw consent. state_esra_consent_required fires when a signing operation targets a natural person who has no current ESRA consent on file.

The consent is per signer, not per document. Once recorded with the current language version, it covers subsequent signings until withdrawn or until Matter publishes a new version that supersedes the prior one. The check fires the first time a signer attempts a signature, after an ESRA version bump, or after the signer has explicitly withdrawn consent.

Fix

1. Surface the canonical ESRA disclosure text to the signer. Fetch the current text via /api-reference/acknowledgements with the esra_consent slug.
2. Capture the signer's affirmative click together with accepted_at, IP, and user-agent.
3. Record the consent via the documented acknowledgement-record endpoint, attaching it to the signer's stk_* Stakeholder id.
4. Retry the signing operation. The pre-flight check now passes.

Related codes

• state_authorisation_required — a governance Resolution is missing.
• state_transition_invalid — the document is in a state that cannot be signed yet.

API reference

• Signing — /api-reference/signing
• Acknowledgements — /api-reference/acknowledgements
• Legal basis — /api/auth/legal-basis