roneddy's account

Hi Duo,

Thanks for your reply that helps answer our question.  But it does lead me to an alternate question.  If we have had a single account in operation for a couple of years, and to that account we have added hundreds of senders, is it possible to remove those senders from that account?  Or will it prevent us from doing so if they have transactions associated with them?

The reason I am asking this is our business line has contemplated a workaround where we assign a fixed email address as the default sender on all transactions going forward on that old account and then on our new account we take advantage of being able to specify the sender, where that capability is needed more.  But in order for this to work we have to either delete all senders from the older account or somehow transfer the senders from the old account to the new account.

In case you are curious why we need separate accounts it is because each has its own branding requirements, email requirements, etc, and it is just better for us that these two use cases maintain separate accounts - if we can find a way past this sender constraint.

Thoughts? Thanks!  

Ron

Hello again,

We have recently made a change of direction for new internal clients where we will be using OneSpan SaaS instead of our own OneSpan On-Premise instance.  So I am wondering, how would the sender concept work with SaaS?  I am assuming we would not be able to set a sender to an email address of our own domain since the emails will be coming from your own server, is that correct? Or does SaaS handle senders differently as it pertains to the FROM email address of the invitation email coming from you?  In our on-prem environment we were able to have the sender email be the from email but that might be because we have our own email server here.  Just curious what the SaaS behavior is.

Thanks!

Thanks Duo for the information on this.  It appears the zip you attached was empty (22 bytes in size), but I think I get the idea here. For some reason though when I read about text tags I misunderstood, so I just want to confirm I understood you correctly now.  This is using text on the document and not pdf fields for its location, is that right? I am 99% sure that is what you are saying, but since I can't try it out myself at this second and it is important for this use case that it locates based on content on the PDF I just want to make sure.

So if I have a PDF template with a signature block, it sounds like if we were to render a string on top of it (or on top of multiple signature fields for that matter) with white text as follows:

{{esl:Signer1:signature:size(200,40)}}

Then OneSpan will place a signature field in each location provided we sent a signer with role of 'Signer1' in our API call. 

Is that correct?

Thanks Duo,

One last question for you.  Let's say we already have a process which uses anchor text values.  And lets say there are LOTS of signatures across LOTS of documents and that we have ensured all the anchor texts are unique and everything is working fine, functionally speaking.  If we were to convert this to the text tag solution, certainly our call into your API would be greatly simplified, but do you know if it would have any performance ramifications, good or bad?  We have found with other signing processes implemented at the bank using different technology stacks that certain types of positioning are (much) faster or (much) slower than others.  Can you comment on the differences pertaining to anchor vs text here?

Thanks again!

Hello,

Thanks for the answer on this.  Quick follow-up related to this...  Assume that we have an account setup which has emails configured to send for invite, reminder, etc.  Is it possible via the REST API to create a transaction with this account in a way that causes those emails to be suppressed for that transaction only?  A flag of some sort that would instruct your system not to send them?

Thanks!