OneSpan

At Onboarding Accounts we have an issue with customer signed documents including Customer Agreement, Statement of Income, Customer Consent which in some cases OneSpan does not return to PEGA or there are delays in response. which causes the Unique Client File to be incomplete.

If possible we need to hold a call with a technician to solve this incident in production.

If you need some examples of client IDs for which we did not receive the documents, please let us know.

Greetings,

I use the event notifier with a Iframe (https://community.onespan.com/documentation/onespan-sign/codeshare/esignlive-event-notifier) for couple years in my projet and when I have configure it initially the event to check for completion was ESL:MESSAGE:SUCCESS:SIGNER_COMPLETE.

I don't know if there has been a change in the event because i'm not receving ESL:MESSAGE:SUCCESS:SIGNER_COMPLETE anymore and I receive ESL:MESSAGE:SUCCESS:SIGNER_COMPLETE_REVIEWED for the last message after signature.

What is the difference and impact?

 Hello,

I'm a front dev from a company that wishes to integrate your ESign product in our android/Ios apps.
I wanted to try out the Android solution and test the integration with the sandbox but I encountered some problems during the android integration process.

I followed the link :
https://community.onespan.com/documentation/onespan-sign/guides/feature-guides/developer/introducing-our-android-sdk