--- title: "Deferred event signature validation" slug: "oas-fullsdk-pg-deferred-event-signature-validation-3-29" updated: 2026-04-15T13:41:46Z published: 2026-04-15T14:13:22Z canonical: "docs.onespan.com/oas-fullsdk-pg-deferred-event-signature-validation-3-29" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # Deferred event signature validation This operation performs an event-based signature validation on a signature. Signature validation is performed within the event window of the specified deferred event count. For this operation to succeed, the following administrative tasks should be performed in OneSpan Authentication Server: 1. Register the client application. 2. Define/assign a current event signature validation policy. 3. Define users and assign authenticators supporting event-based transaction authentication. At a minimum, the `authSignature` command requires the following set of signature field attributes in order to perform signature validation: - `SIGNFLD_COMPONENT_TYPE` - `SIGNFLD_USERID` - `SIGNFLD_SIGNATURE` - `SIGNFLD_DEFERRED_EVENT_COUNT`. The event count used to generate the deferred event signature. For more information about required and optional signature validation attributes for `authSignature`, see [SOAP signature validation](/sec/docs/oas-fullsdk-soapref-soap-signature-validation-3-29). If the transaction authentication is successful, OneSpan Authentication Server will return the verified event counter in the SOAP response. This information will be specified as signature attribute `SIGNFLD_VERIFIED_EVENT_VALUE` in the `resultattribute` element.