EviSign is the Namirial Notify service for sending documents for remote electronic signature. You create a signature request specifying the document, the signer or signers, and the signing method. Namirial Notify delivers the request, tracks each signer's actions, and records evidence for the configured workflow stages.
EviSign requests are created in the Namirial Notify platform. This page focuses on workflow behaviour, signer experience, and callback semantics. For issuer step-by-step instructions, see How to create a new EviSign.
For API-based integrations, see the EviSign API reference, including submission, tracking, evidence retrieval and temporary signing links.
For shared concepts and terminology used across services, see States and outcomes and Evidence and affidavits.
EviSign has entered Long-Term Support (LTS). It will continue to receive security patches and critical bug fixes, but no new features will be developed.
Pick EviSign when you need to obtain a remote electronic signature on one or more documents and record evidence for the signature workflow. Pick a different service when:
- You need to deliver a certified message to a recipient's inbox without a signing step. Use EviMail.
- You need recipients to access hosted content and record on-platform interactions. Use EviNotice.
- You need to deliver a certified message via SMS or RCS. Use EviSMS.
- You need certified physical mail. Use EviPost.
A side-by-side comparison is on the Services page.
EviSign involves a small set of related concepts. Keep these distinct as you read the rest of the page.
- EviSign — a single signature request for one document and one or more signers. Identified by a
UniqueIdassigned by the platform. - Signing party — a signer, reviewer, or interested party. Each signer has their own delivery, access, and commitment events tracked separately.
- Event — a recorded fact during the lifecycle, such as
Sent(signature request delivered) orSigned(signer completed the flow). - Evidence item — the recorded data behind an event, including timestamps and signer details.
- Affidavit — a signed PDF that certifies one or more evidence items.
- Callback — an HTTP POST that Namirial Notify sends to a configured endpoint when an event matches the push notification filter you set.
Submitted → Processed — Namirial Notify validates the submission, certifies the document content, and prepares the signature workflow.
Processed → Sent — The evidence state advances when sending is recorded as successful for the signing and review parties. Sequential workflows can remain Processed while later parties await their turn. An individual Sent callback reports a transmission event and can arrive while the workflow is still Processed.
Processed or Sent → Closed — The workflow closes after completing the configured signing flow, recording a rejection, timing out, processing a cancellation, or encountering a terminal failure. The Outcome field records the result. Initial processing failures can also close a Submitted request.
Party status (per signer) — Each signing party has its own status independent of the evidence state: None (awaiting action) → Signed or Rejected.
The signing method configured for each signer controls how they authenticate and complete the signature step.
| Value | Description |
|---|---|
MobilePin | A PIN is sent to the signer's mobile number. The signer enters it to confirm the signature. |
EmailPin | A PIN is sent to the signer's email address. The signer enters it to confirm the signature. |
Challenge | The signer answers a challenge question defined when the request is created. |
Handwriting | The signer draws their signature on a web canvas. |
ExternalHandwriting | Handwriting signature collected via an external service. |
UserCertificate | The signer signs using their own personal digital certificate. |
WebClick | Simple web click to accept. |
The signing methods available depend on the certification level selected and on which methods are enabled for your tenant.
Each signer is defined in SigningParties with both a notification address and the way that address should be interpreted:
| Parameter | Values | Meaning |
|---|---|---|
SigningParties[n].AddressType | Email, PhoneNumber | Whether the signature request is delivered to an email inbox or to a mobile number. |
SigningParties[n].Address | string | The actual email address or international-format phone number. |
When the signer is notified through a mobile number, SignatureRequestPolicy controls the channel used for the signature-request notification:
| Value | Behaviour |
|---|---|
SmsOnly | Send the request by SMS only. |
WhatsAppOnly | Send the request by WhatsApp only. |
SmsThenWhatsApp | Try SMS first, then WhatsApp as fallback. |
WhatsAppThenSms | Try WhatsApp first, then SMS as fallback. |
For MobilePin signing, the PIN delivery itself is configured separately:
WhatsAppPinPolicy:Disabled,Optional,FallbackAllowVoicePinFallback: allows the signer to request the PIN by voice call if PIN delivery is needed
Other delivery-related fields on each signer include RequiresCaptcha, DisableSignRequests, DisableFinalNotification, and DisableStateNotifications. The older top-level Options.RequireCaptcha field is kept only for backward compatibility; use SigningParties[n].RequiresCaptcha instead.
Signature questions (SignatureQuestions) are additional data fields presented to the signer during the signing flow — for example, to capture identity data, consent answers, or other information required by the process.
Each question is an object in the SigningParties[n].SignatureQuestions array with a Key, Label, TypeName, and optional Required, ValidationRegex, DefaultValue, and SelectListItems (for SelectList type only).
| TypeName | What the signer provides | Validation |
|---|---|---|
Text | Free text (single line) | None |
MultiLineText | Free text (multiple lines) | None |
Number | Integer number | Must be a valid integer |
Decimal | Decimal number | Must be a valid decimal |
Date | Date | Must be in dd-MM-yyyy format |
CheckBox | Checkbox (true / false) | None |
SelectList | One option from a provided list | Must match a value in SelectListItems |
Password | Text (input is masked) | None |
EmailAddress | Email address | Must be a valid email format |
PhoneNumber | Phone number | Must be in international format (e.g. +34914237080) |
BankAccount | Bank account number | No format validation |
BankAccountES | Spanish bank account (20 digits, no spaces) | Must be a valid Spanish account with check digit |
BankAccountIBAN | IBAN account (ISO 13616) | Must be a valid IBAN |
BankAccountIBANES | Spanish IBAN (24 digits, no spaces) | Must be a valid Spanish IBAN with check digits |
SwiftCode | SWIFT / BIC code | None |
DocumentId | Identity document or passport number | None |
SpanishDocumentId | Spanish NIF or NIE (including check digit) | Must be a valid Spanish NIF/NIE format |
IntlVatId | International VAT ID | No check-digit validation |
SpanishVatId | Spanish tax ID (NIF, CIF, or VIES VAT number with country prefix) | Must be a valid Spanish fiscal identifier |
Image | Image file upload (JPEG or PNG) | Must be a JPEG or PNG |
File | Any file upload | None |
DynamicSignature | Biometric handwritten signature with metadata | Requires a mobile device and the Namirial signing app |
None | No input — displayed as informational text only | None |
DynamicSignature requires a supported mobile device and the Namirial mobile signing app. It is not available in standard browser-based flows.
SignStep controls at what point in the signing flow the identity or authentication step happens relative to document review. It is set per signing party as SigningParties[n].SignStep (nullable — when omitted the platform uses AfterDoc).
| Value | When authentication happens | Lite Flow | Typical use |
|---|---|---|---|
Begin | Before everything — authentication is the first action the signer takes, before any document or attachment is shown. | ✅ Compatible | When the issuer wants to confirm signer identity before exposing any content. |
BeforeDoc | After any pre-document attachments, before the main document — signer authenticates, then reads the document. | ❌ Incompatible | When the issuer wants identity confirmed before the document is opened, but after optional prior information is reviewed. |
AfterDoc | During or immediately after viewing the main document — the signer reads the document, then completes the authentication/signature step. This is the default when SignStep is not set. | ✅ Compatible | Standard signature flows where the signer reads the document and then signs. |
End | After all documents and attachments — the signer reviews everything first, then authenticates and commits at the very end. | ❌ Incompatible | When the issuer wants the signer to see the complete package before any commitment. |
SignStep is independent per signer — different parties in the same submission can use different values.
The older SignDelivery boolean is an earlier equivalent of SignStep: setting SignDelivery: true is the same as SignStep: Begin. To avoid ambiguity, set SignStep on its own rather than combining the two.
GSD produces an additional PDF after the signing process completes. The output document contains the original content with each signatory's electronic signature graphically embedded at the configured position. It is independent of the affidavits generated during the process.
GSD is controlled by two parameters in the top-level Options object:
| Parameter | Type | Description |
|---|---|---|
Options.GenerateSignedDocument | bool | Set to true to enable GSD for this submission. |
Options.GenerateSignedDocumentOptions.CertificationCertificate | string | Identifier of the site or user certificate to use when certifying the generated document. Omit to use the default configured certificate. |
Each object in SigningParties accepts a SignatureAppearances parameter that defines where the signer's signature is placed in the generated PDF.
SignatureAppearances: '[{"PageNumber":1,"Left":100,"Bottom":100,"Right":300,"Top":150}]'The value is a JSON array serialized as a string. Each element defines one appearance on one page:
| Field | Type | Description |
|---|---|---|
PageNumber | int | 1-indexed page number where the signature box is placed. |
Left | number | X coordinate of the left edge of the signature box, in PDF points from the left of the page. |
Bottom | number | Y coordinate of the bottom edge of the signature box, in PDF points from the bottom of the page. |
Right | number | X coordinate of the right edge of the signature box, in PDF points from the left of the page. |
Top | number | Y coordinate of the top edge of the signature box, in PDF points from the bottom of the page. |
The PDF coordinate system has its origin (0, 0) at the bottom-left of the page. X increases to the right; Y increases upward. One point equals 1/72 of an inch.
If SignatureAppearances is omitted for a signer, GSD still runs but that signer's signature is embedded without a visual representation at a specific location.
SignatureAppearances requires Handwriting signing method and is not compatible with Lite Flow.
Lite Flow is a simplified signing interface that reduces the number of steps a signer sees, for a faster signing experience.
LiteFlow is set per signing party in SigningParties:
| Parameter | Type | Default | Description |
|---|---|---|---|
SigningParties[n].LiteFlow | bool? | false | Set to true to activate Lite Flow for this signer. Can be mixed — some signers can use Lite Flow while others use the standard flow in the same submission. |
Not all EviSign features are supported when LiteFlow is true for a signer.
| Feature | Supported |
|---|---|
Challenge signing method | No |
Handwriting signing method | No |
SignatureAppearances | No |
SignedRedirectUrl | No — always redirects to the finish page |
BeforeDoc sign step | No |
End sign step | No |
| Geolocation | No |
LandingPageInfoText | No — accepted but not shown |
MobilePin signing method | Yes |
EmailPin / WebClick signing method | Yes |
| Voice PIN fallback | Yes |
| WhatsApp (Disabled, Optional, Fallback) | Yes |
| Iframe delivery | Yes — requires simple delivery |
| Signature questions | Yes |
Begin sign step | Yes |
AfterDoc sign step | Yes |
| Attachments (with or without required signature) | Yes |
| Additional commitments | Yes |
| Commitment options | Yes |
| Accept / reject reasons | Yes |
| Generated Signed Document (GSD) | Yes |
| Reviewer role | Yes |
| Signing order | Yes |
| Role | Description |
|---|---|
Signer | Must complete the signing step. Their action is tracked and drives the party status. |
Reviewer | Reviews the document before the signing step. Depending on configuration, a reviewer may need to accept or reject before signers can act. |
Interested | Receives notifications at configured stages but does not sign. |
The certification level determines the legal strength of the signature and which signing methods are supported.
| Value | Description |
|---|---|
None | No legal certification. Evidence is recorded but no certified affidavit is generated. |
Standard:EU | Standard electronic signature under EU eIDAS. |
Standard:CO, Standard:CR, Standard:EC, Standard:MX, Standard:PE | Standard signature for the respective country. |
Advanced:EU | Advanced electronic signature under EU eIDAS. Requires a stronger signing method. |
Advanced:CO, Advanced:CR, Advanced:EC, Advanced:MX, Advanced:PE | Advanced signature for the respective country. |
Do not submit Standard or Advanced without a country suffix. For regions not covered, the EU value is usually used, as European regulations are widely accepted.
EvidenceAccessControlMethod controls who can open the evidence record after the process closes. It is set in Options alongside optional challenge fields.
| Value | Behaviour |
|---|---|
Default | Uses the access control method configured for the site or reseller. |
Public | No access restriction — anyone with the evidence URL can view it. |
Session | Deprecated. Throws an error for all new integrations. Use Challenge or AutoChallenge instead. |
Challenge | The viewer must correctly answer a custom question defined by the issuer at submission time. |
AutoChallenge | The viewer must answer a system-generated question based on known transaction data (for example, the issuer's email address or the destination address used in the submission). |
When Challenge is selected, set the question and expected answer in the same Options object:
| Parameter | Type | Description |
|---|---|---|
Options.EvidenceAccessControlMethod | AccessControlMethod? | The access control method to apply. |
Options.EvidenceAccessControlChallenge | string | The challenge question shown to the viewer. Required when method is Challenge. |
Options.EvidenceAccessControlChallengeResponse | string | The correct answer. Required when method is Challenge. Comparison is case-insensitive. |
For how recipients experience the access challenge when following an evidence link, see Accessing archived evidence as a recipient.
The signer receives the signature request through the channel configured for their party — email for Email parties, or SMS/WhatsApp delivery for PhoneNumber parties. They follow a secure link into the Namirial Notify signing flow, complete any required authentication step (challenge, PIN, etc.), review the document, and accept or reject.
For the full recipient experience, see How a recipient receives an EviSign.
Use SignLink to obtain a temporary signing URL for an existing EviSign. Use the returned URL exactly as supplied and follow the compatibility rules for single- and multiple-document flows.
EviSign supports loading the signing flow directly inside your application via an iframe or a native WebView. This allows you to embed the signing experience without redirecting the user away from your product.
The following parameters in each SigningParties object control how the signing URL is delivered and loaded:
| Parameter | Type | Description |
|---|---|---|
DeliveryWebView | string | Identifier of the WebView channel registered for your site. When set, the signing URL is scoped to that WebView context. |
DeliverySubDomain | string | Custom subdomain under which the delivery area is loaded. Used when the signing flow should be served from a branded domain. |
DeliveryCustomUrl | string | Custom redirect URL used when DeliverySubDomain is set. |
DeliveryProfile | string | ID of the delivery profile that selects which delivery portal the signer should sign on. |
The signing flow emits browser events at selected steps, including start, completion, rejection and user input errors. The event payload uses the fields below. The event status describes the step and can differ from the HTTP response status when the flow redirects.
For WebView channels, the response that emits an event can carry this header:
X-Herma-Problem-Details: <JSON>For iframe channels, the signing page relays browser event data to the top-level window via postMessage. Handle the message event and check its origin against the signing host you expect.
| Field | Type | Description |
|---|---|---|
Type | string | Event name, such as EviSignProcessStarted or EviSignSignatureCompleted. |
Status | int | Status code assigned to the event. |
Title | string | Short human-readable description of the event. |
Detail | string | Detailed description of the event. |
Instance | string | Request path for the event. |
Data | object | Additional event-specific data. Common keys include PartyId (present when the event is associated with a specific signer) and error detail entries when a problem occurred. |
{
"Type": "EviSignSignatureCompleted",
"Status": 200,
"Title": "Document signed",
"Detail": "Operation successfully completed.",
"Instance": "/delivery/evisign/commitment",
"Data": {}
}For integrators receiving callbacks. These notifications are sent to your application, whether configured through the API or the platform UI. Users who only need to track requests can use EviSign transaction search.
When an event matches the push notification filter, Namirial Notify sends a JSON POST to the configured endpoint. Callbacks are per-EviSign and opt-in. They are configured at creation time either in the platform UI or through Options.PushNotificationUrl and Options.PushNotificationFilter in API-based submissions.
| Event | When it fires |
|---|---|
Processed | The document was certified and the workflow was prepared |
Sent | A party’s signature or review request was attempted, sent or abandoned. |
Delivered | Delivery of a party’s signature or review request was reported. |
Signed | One signer completed the signing step |
Rejected | One signer rejected the document |
FullySent | The workflow reached the aggregate sending milestone for the signing and review parties. |
FullyDelivered | The workflow reached the aggregate delivery milestone. |
FullySigned | All signing and review parties completed their approval or signing step. |
Closed | The workflow reached its final state |
AffidavitPublished | An affidavit was generated and is ready for download |
A party can have multiple Sent events. Read AdditionalData.TransmissionSuccess and AdditionalData.EventDescription to interpret the transmission result. Use Delivered events for per-party delivery confirmation. FullySent, FullyDelivered and FullySigned describe workflow milestones. A callback retry can repeat the same Identifier.
Every callback shares the same envelope:
{
"Identifier": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"Kind": "Signed",
"Date": "2026-03-10T09:22:14.0000000+01:00",
"EvidenceId": "9f3e1a02-b74c-4d8e-91c5-f00012345678",
"EvidenceType": "eviSign",
"EvidenceState": "Sent",
"Owner": "John Doe",
"OwnerEmail": "sender@example.com",
"Site": "my-site",
"AdditionalData": { }
}Deduplicate using EvidenceType, EvidenceId, Kind and Identifier. A party event and an aggregate event can share the same Identifier. For retry behavior and general callback guidance, see Callbacks and webhooks.
Party events can include role and notification details in AdditionalData. The sender includes SignerName, SignerNotificationAddres, and transmission descriptions only for HTTPS callback URLs. Retry can appear on Sent transmission events when the event supplies a notification attempt number.
The field names SignerNotificationAddres and SignerNotificationAddresType (both missing the final s) and OutCome (capital C) reflect the actual payload produced by the platform. Use these exact strings when reading from AdditionalData.
Sent — successful signature request transmission example
{
"Kind": "Sent",
"AdditionalData": {
"SignerName": "Alice Martin",
"SignerNotificationAddres": "alice@example.com",
"SignerNotificationAddresType": "Email",
"SignerRole": "Signer",
"TransmissionSuccess": true,
"TransmissionDescription": "The system successfully sent the signature/review request to Alice Martin (alice@example.com)",
"EventDescription": "Request sent"
}
}Delivered — signature request confirmed delivered to one signer
{
"Kind": "Delivered",
"AdditionalData": {
"SignerName": "Alice Martin",
"SignerNotificationAddres": "alice@example.com",
"SignerNotificationAddresType": "Email",
"SignerRole": "Signer",
"TransmissionSuccess": true,
"TransmissionDescription": "The system confirmed delivery to Alice Martin at alice@example.com of the signature/review request with the access link, but the content has not yet been opened/read",
"EventDescription": "Request delivered"
}
}Signed — one signer completed the signing step
{
"Kind": "Signed",
"AdditionalData": {
"SignerName": "Alice Martin",
"SignerNotificationAddres": "alice@example.com",
"SignerNotificationAddresType": "Email",
"SignerRole": "Signer"
}
}Rejected — one signer rejected the document
{
"Kind": "Rejected",
"AdditionalData": {
"SignerName": "Alice Martin",
"SignerNotificationAddres": "alice@example.com",
"SignerNotificationAddresType": "Email",
"SignerRole": "Signer"
}
}FullySent, FullyDelivered, FullySigned, Processed — AdditionalData can contain the configured ExtraData. These events add no event-specific fields.
Closed — workflow reached its final state
{
"Kind": "Closed",
"AdditionalData": {
"OutCome": "Signed"
}
}When the outcome is Cancelled, CancelComments is also included if a reason was provided:
{
"Kind": "Closed",
"AdditionalData": {
"OutCome": "Cancelled",
"CancelComments": "Request withdrawn by issuer"
}
}AffidavitPublished — an affidavit is ready
{
"Kind": "AffidavitPublished",
"AdditionalData": {
"AffidavitId": "b7f1e3c0-1234-5678-abcd-ef0987654321",
"AffidavitKind": "PartyCommitted",
"AffidavitName": "Party commitment affidavit"
}
}RequestId is included only for on-demand affidavits. Regenerated: true is included only when the affidavit was regenerated by a platform command.
Kind | What happened | Typical action |
|---|---|---|
Processed | Document certified, workflow ready | Log and wait for Sent |
Sent | Transmission event for a party | Record the attempt and inspect TransmissionSuccess and EventDescription |
Delivered | Delivery of one party’s request was reported | Update that party’s delivery status |
Signed | One signer completed signing | Track per-signer progress |
Rejected | One signer rejected the document | Notify your process owner |
FullySent | Aggregate sending milestone | Record sending progress separately from delivery |
FullyDelivered | Aggregate delivery milestone | Record delivery progress |
FullySigned | All signing and review parties completed their actions | Track signing completion and use Closed for the final outcome |
Closed | Workflow complete | Check OutCome and update your records |
AffidavitPublished | Affidavit ready | Download and store using AffidavitId |
For your receiving application, follow Handling callbacks reliably. It covers deduplication, acknowledgement after safely storing each callback, and correlation using AdditionalData.ExtraData.
For integrators receiving callbacks.
Namirial Notify sends callbacks as plain HTTP POST requests with no authentication header. Use HTTPS and validate EvidenceType and EvidenceId on every incoming request. Treat source IP only as an operational signal unless Namirial explicitly provides official egress ranges for your environment. See Security and authentication for the supported callback model and compensating controls.
| State | Description | Terminal? |
|---|---|---|
Draft | The EviSign has been staged but not yet submitted | No |
Submitted | The submission was accepted and is being processed | No |
Processed | The document was certified and the workflow was prepared | No |
Sent | Sending was recorded as successful across the signing and review parties | No |
Closed | The workflow reached its terminal state. Later evidence publication can still be reported. | Yes |
Forwarded and Received are also defined states. Query accepts both and returns the stored state. The normal workflow shown above has no transition into either state.
The Outcome is None until closure. During ordinary finalization, the workflow evaluates cancellation, rejection, full signing and expiry in that order. Terminal failures can close the workflow with Failed.
| Outcome | When it is set |
|---|---|
None | Workflow is still active |
Signed | All signing and review parties completed their approval or signing step and the workflow closed |
Rejected | A signing or review party rejected the document and the workflow closed with that result |
Expired | The workflow reached its deadline without a higher-priority closure result |
Cancelled | Cancellation was processed. Query returns the Closed state with this outcome. |
Failed | A processing error prevented the workflow from completing normally |
| Affidavit kind | Stage | What it certifies |
|---|---|---|
Submitted | Processing | Document content and submission metadata at the moment of submission |
SubmittedAdvanced | Processing | Extended submission certification |
SignatureRequestDispatched | Per signer — Sent | That the signature request was sent to a specific signer |
SignatureRequestResult | Per signer — transmission result | The result of sending the signature request |
PartyCommitted | Per signer — commitment | The signer's explicit commitment action with timestamp and identity details |
FinalNotificationDispatched | Closure | That the final notification was sent after the workflow closed |
FinalNotificationResult | Final-notification transmission result | The result of sending the final notification |
Main | Eligible signed or rejected closure | Main evidence document when this affidavit kind is enabled |
Summary | Normal finalization | Workflow summary when enabled. Direct cancellation and failure use a separate closure path. |
Attachment | Eligible signed or rejected closure | Each attachment that requires a separate commitment, when this affidavit kind is enabled |
AttachmentMasked | Eligible signed or rejected closure | Masked affidavit for a commitment-required attachment when both attachment affidavits and masking are enabled. |
OnDemand | While open | Additional affidavit generated after an eligible request. |
Event | Per tracked event | Per-event evidence record |
Failed | On failure | Failure details and state at failure time |
If the first rejection is by a reviewer, the workflow skips Main, Attachment and AttachmentMasked.
If subscribed, AffidavitPublished reports the published affidavit ID. Retrieve the file through Bundle or the shared affidavit download API.
Use this as a reference when integrating callbacks or downstream processes with an EviSign workflow.
Workflow configuration
- Callback endpoint URL is HTTPS in production
- Push notification filter includes at minimum
FullySigned,Closed,AffidavitPublished - Affidavit kinds are selected to match your compliance requirements
- Certification level matches the legal requirements for your use case
Callback handling
- Your endpoint responds
2xxbefore doing any heavy processing - Your endpoint is idempotent — the same callback may arrive more than once
- You validate
EvidenceType == "eviSign"on every incoming callback - You use
Identifierto deduplicate retried callbacks
State handling
- You do not treat
FullySignedas final — wait forClosedbefore updating your records - You handle all terminal outcomes:
Signed,Rejected,Expired,Cancelled,Failed
Affidavits
- You download and store affidavits when the
AffidavitPublishedcallback fires
Possible cause: The notification address is incorrect, or the notification was filtered as spam.
What to check:
- Ask the signer to check their spam or junk folder.
- Verify the email address or phone number configured for the signer.
- Check the party’s
Sentcallbacks and inspectTransmissionSuccessandEventDescription. Check the transaction history if you need more delivery detail. - In sequential workflows, the evidence can remain
Processedwhile later parties await their turn. Use per-party delivery events or the transaction history to check a particular request.
Possible cause: A signing or review party is still waiting to act. FullySigned follows completion by all signing and review parties.
What to check:
- Review the signing and review parties for any pending approvals or signatures.
- Check
SentwithTransmissionSuccessfor per-party transmission progress, and useDeliveredfor reported delivery. - If the workflow uses a sequential signing order, check whose turn it is.
Possible cause: A signing or review party rejected the document.
What to check:
- Identify the party in the
Rejectedcallback or the transaction history. - Decide whether to create a new EviSign with corrected content or contact the signer directly.
Possible cause: AffidavitPublished is not in the push notification filter, or no affidavit kinds were selected at creation time.
What to check:
- Confirm
AffidavitPublishedis included in the configured event filter. - Confirm at least one affidavit kind was selected when the EviSign was created.
Possible cause: The EviSign has already closed (signed, rejected, expired, or cancelled), or the signing link has reached its configured time limit.
What to check:
- Check the current state of the EviSign.
- If the EviSign is still open and the party’s details show Resend, use it to send another request.
- If the EviSign is already
Closed, it cannot be reopened — create a new one.