Community and customer portal
  • OneSpan.com
  • Documentation portal
  • TrustCenter
  • Customer support
Community and customer portal
Toggle navigation
  • Get started
  • Code shares
  • Interactive APIs
  • Developer sandbox
  • Developer sandbox
  • Forums
  • Demos

User account menu

  • Sign up
  • Login
  1. Home
  2. Search

Search

237 results matched your search criteria
Bad Request 400 eslClient.CreatePackage() after upgrade from 10.3 to 10.13
Forum topic
OneSpan Sign
Hello, I recently updated the api version for Silanis.ESL.dll from 10.3 to 10.13, after doing so the code that I'm using to dynamically build the packages for getting signed no longer works.
Mouse capture error
Forum topic
OneSpan Sign
Hello, would help me understand what I'm doing wrong ? The method is called in package creation process. In the following are the values for Mobile signature method compare with Mouse capture. I don't see any problem for Mobile signature. // Mobile signature - Error response String response = clie
Multiple signers and Multiple documents - com.silanis.esl.sdk.internal.EslServerException: Could not create a new package
Forum topic
OneSpan Sign
Exception in thread "main" com.silanis.esl.sdk.internal.EslServerException: Could not create a new package in one-step Exception: HTTP POST on URI https://sandbox.esignlive.com/api/packages resulted in response with status code: [400, Bad Request].
documentExtractError
Forum topic
OneSpan Sign
Hello, I get documentExtractError when create and send package with pdf document in REST API. It started when I added "extractAnchor".  
Verify transaction on Mobile Device - Page Cannot be Found
Forum topic
OneSpan Identity Verification
Hi,
Can you mix-and-match remote authenticated signing with in-person signing within a single signature package?
Forum topic
OneSpan Sign
Hello, we currently are using e-signature packages (created using the RESTful API) where all signers are fully remote e-signers.
Specifying Sender of Package
Forum topic
OneSpan Sign
Hi there. What I'm trying to do is specify the sender of a package to be [email protected].  Our main account owner is [email protected]. No matter how I update my JSON, the package sender is still [email protected].  Here is my pertinent JSON package
  • Home
  • Products
  • Documentación
  • Forums
  • Demos
OneSpan

Footer menu

  • Products
  • Forum
  • Demos
  • Contact Support
  • Documentation Portal
  • Trust Center

Follow us on:

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

Copyright 2025 OneSpan. All Rights Reserved.