roneddy's account

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!

This is excellent, thank you! I think I was mistaken, it appears these are our own models which we then convert into calls into OneSpan (I can't say if we use the SDK or REST at the moment, but it looks to me that this answer is applicable to both.

We will look into making sure we are integrating how you show here.  However, we are definitely going to need to know a bit more about this:
If s2 doesn't have any signature, he/she will become a reviewer. We can add an additional step to remove all recipients who doesn't have signatures after the creation

Could you provide a little guidance on this part?

Thanks,

Ron

Was going to create a post for this but then found this request and thought I would add on here. 

I would like to 'upvote' this as well, though maybe in a slightly different way.  We would love to see the API add the ability for us to provide a flag at the point of transaction send which instructs OneSpan not to automatically send any emails for that particular transaction.  Currently this is an account level setting I believe, but dropping this down to a transaction level would greatly increase the flexibility of how we can integrate internally, especially around more interesting use cases involving in person signers who would normally sign with an employee guiding them but would grant that employee the flexibility to trigger a send of the invite email if for some reason the person can't be there in person.  This flag could be on the transaction level or on a per signer level, in line with the original request here, either way would work for our needs.

Thanks!

Ron

Indeed, and we use that feature for our use cases. We request that the inperson emails be disabled and then rely on API calls to trigger the send at the point the signer is interacting with their banker and the banker needs to send the invite. However, this requires us to setup (2) separate accounts in OneSpan to be able to handle this as well as use cases where the business wants invites going out immediately upon sending. By allowing control at the transaction level as to whether OneSpan will send emails it means less admin and account work and coordination (for example, ensuring all customizations remain the same in both accounts). Just throwing out a touch more context. Thanks for the vote!