Verifying Your Identity
Before you can sign a contract, E-SignSeal verifies that you are the intended signer using a one-time passcode (OTP). The OTP step runs just-in-time when you select Sign in your signing session — it provides cryptographic proof that you had access to your Jira-registered email at the moment of signing.

OTP verification screen showing 6-digit code input field
How OTP verification works
You open your signing session and review the contract document.
You select Sign this document to proceed.
E-SignSeal sends a 6-digit OTP to the email address associated with your Jira account.
The OTP input screen appears. Check your email and enter the code.
On success, the signing session advances to the Consent stage.
The code arrives within a few seconds in most cases. Check your spam folder if you do not see it after 30 seconds.
OTP specifications
Property | Value |
|---|
Code length | 6 digits |
Algorithm | HMAC-SHA256 |
Validity window | 5 minutes from the time it was sent |
Maximum attempts | 3 per signing session |
Delivery channel | Email to your Jira-registered address |
What if the code expires?
OTP codes are valid for 5 minutes. If 5 minutes pass before you enter the code, the code is no longer accepted. To get a new code:
Select Resend code on the OTP input screen.
A new 6-digit code is sent to your email. The previous code is immediately invalidated.
There is no limit on how many times you can request a new code, as long as the contract has not expired.
What if you enter the wrong code?
You have 3 attempts per signing session. After each incorrect entry, the screen shows how many attempts remain.
If you exhaust all 3 attempts, your signing session is locked for that session. You will need to:
Close the signing session.
Return to your invitation (the Jira notification or email link) to start a new session.
Request a new OTP code in the fresh session.
The failed OTP attempts are recorded in the contract's audit trail.
Why OTP and not just my Jira login?
Being logged into Jira confirms your identity within the Jira session. OTP adds a second factor: it confirms you also have access to the email inbox associated with your Jira account at the precise moment you sign. This two-layer approach provides stronger non-repudiation evidence for the signing event — evidence that the correct person signed, not just that someone with the account password signed.
Your email address
The OTP is sent to the primary email address on your Jira account. To see which email address Jira has on file, check your Atlassian account profile at id.atlassian.com. If you need to update your email, do so there before your next signing session.
Next steps