User account menu

  • OneSpan.com
  • Trust Center
  • Sign up
  • Login
Toggle navigation
  • Products
    • Intelligent Adaptive Authentication
      • Getting Started
      • Documentation
      • Code Share
      • Forums
    • Mobile Security Suite
      • Getting Started
      • Documentation
      • Code Share
      • Forums
    • OneSpan Cloud Authentication
      • Getting Started
      • Documentation
      • Code Share
      • Forums
    • OneSpan Identity Verification
      • Getting Started
      • Documentation
      • Code Share
      • Forums
    • OneSpan Sign
      • Getting Started
      • Documentation
      • Code Share
      • Forums
    • Risk Analytics
      • Getting Started
      • Documentation
      • Code Share
      • Forums
  • Documentation Portal
    • Intelligent Adaptive Authentication
      • Guides
      • Interactive API Reference
      • Release Notes
      • Free Developer Sandbox
    • Mobile Security Suite
      • Guides
      • Release Notes
      • Free Developer Sandbox
    • OneSpan Cloud Authentication
      • Guides
      • Interactive API Reference
      • Release Notes
      • Free Developer Sandbox
    • OneSpan Identity Verification
      • Guides
      • Release Notes
    • OneSpan Sign
      • Guides
      • Interactive API Reference
      • Release Notes
      • Free Developer Sandbox
    • Risk Analytics
      • Guides
      • Interactive API Reference
      • Release Notes
      • Free Developer Sandbox
  • Forums
    • Intelligent Adaptive Authentication
    • Mobile Security Suite
    • OneSpan Cloud Authentication
    • OneSpan Identity Verification
    • OneSpan Sign
    • Risk Analytics
  • Demos
Search
  1. Home
  2. Search

Search

159 results matched your search criteria
In the approval when using text anchoring, is the "page": attribute optional?
Forum topic
OneSpan Sign
Hi Haris, I would like to quickly clarify on the below approval format where I noticed that even if the page detail is not provided it works fine to realize the exact text to place the textfield using text anchor. “approvals”: [ { “role”: “signer1”, “fields”: [ { “subtype”: â€
Missing Signature.signed property
Forum topic
OneSpan Sign
We can verify when a signer signed all the documents as follow:
List of Error codes, Error Messages, Error Name
Forum topic
OneSpan Sign
Hi, I have noticed that there are a bunch of different error messages under the EslServerException. Where can I find a list of all these error messages with their corresponding error codes and error names. Example: com.silanis.esl.sdk.internal.EslServerException: Could not create a new package Exce
Document signed Event notification message
Forum topic
OneSpan Sign
When a Document is signed for a given Signer, in the call back notification, I see following information "name":"DOCUMENT_SIGNED","sessionUser":"SignerID2","packageId":"XXXXXXXXXXXXXXXXXXXXXXXXX","message":null,"documentId":"Document_ID" if we see, message is coming as null. Is it possible to get
DatePicker "SigningDate" fails on selecting date
Forum topic
OneSpan Sign
  Hi friends,
Combining Approvals for same signer
Forum topic
OneSpan Sign
Guys - I have a document with 4 signature fields. When I tried to combine the fields for the one signer, it didn't work. Do we have to create a new approval for each new field that we are trying to sign? If not, can I get a JSON Package example of how to do it since mine isn't working.
"message": "Invalid position. Object placed outside of document page boundary."
Forum topic
OneSpan Sign
Hi Team, I am using REST API. While creating packages I received following exception. { "messageKey": "error.validation.invalidPageLocation", "message": "Invalid position.
Failed to communicate with the callback server.
Forum topic
OneSpan Sign
Running some test on QA now we are running on this issue. Can you share a light of what this could be?
Changing package status
Forum topic
OneSpan Sign
When I do PUT request to /api/packages/{package_id} with request payload as { "status": "DRAFT" } I get error response as { "code": 415, "entity": null, "message": "Unsupported Media Type", "messageKey": "http.status.415", "name": "Unsupported Media Type", "technical":
Signing status "Completed" instead of "Signing Complete"
Forum topic
OneSpan Sign
Hi There, I am using the example provided on this page : https://developer.esignlive.com/guides/quick-start/check-package-status-and-download-documents-java/ In this example, there's a line to check the Signing Status: SigningStatus sentSigningStatus = eslClient.getSigningStatus( packageId, nul
  • Load More
  • Home
  • Products
  • Documentación
  • Forums
  • Demos
OneSpan

Footer menu

  • Getting Started
  • Products
  • Documentation Portal
  • Forum
  • Contact Support
  • Partner Portal
  • Trust Center

Follow us on:

  • Privacy Center
  • Cookie Policy
  • Terms of Use
  • Legal Notice
  • Preference Center

Copyright 2024 OneSpan. All Rights Reserved.

X
  • Create new account
  • Request new password