SMS Code Sent to Wrong Recipient For Downloading Completed DocumentsWednesday, March 18, 2020 at 12:38pm
We are using the Java REST API to create and send the transactions. We would like our customer recipients to use SMS authentication for the signing ceremony, but our back office/branch senders will not be using SMS. Our transactions are sent via the API are created successfully, and both the customer recipients and senders are able to complete the signing ceremony. However, when the back office/branch senders receive the "documents for the *** are available to download" email and click on the link to access the completed documents, SMS codes are sent to the customer recipient instead.
I have attached the JSON payload we used for creating the transaction as well as the evidence summary for one of our transactions. We have an open case #: CS0022888 for this issue. Jaclyn Schipper is our client representative.
Can you let us know if we are creating the transactions correctly? How can we stop the SMS codes sent to the senders? Thanks!