Trashing Transactions - Reasons and Notifications
Wednesday, August 16, 2023 at 07:30amHey!
I have a couple of general queries regarding the movement of a transaction into "Trash" that I have been unable to find answers on.
1. Are we able to add a user-defined reason for why something was trashed? We have a "void" functionality within our front-end which trashes transactions through the API integration, and we were wondering if we'd be able to add and capture the reasons for a user "voiding" here?
2. Is there an email template that can be used when a transaction is moved to "Trash" which goes out to recipients to inform them that transaction is no longer valid?
Thanks,
Tom.
Reply to: Trashing Transactions - Reasons and Notifications
Monday, August 21, 2023 at 12:05pmHi Tom,
Thanks for your post! Unfortunately I don't think there's an email template to notify signers when a transaction get trashed with reasons. Something came on top of my mind is to use the email.notify template, you can invoke the signer notify API (the message will override the $PACKAGE_MESSAGE; variable) to trigger this email template before you trashed the transaction.
POST /api/packages/{packageId}/notifications
Example Payload:
{ "email": "[email protected]", "message": "Some trash reason here." }
If you are not using the email.notify in your current workflow, you can customize the email subject and the wordings. Otherwise you can make the subject and body general and rely on the passed in message.
Duo
Duo Liang OneSpan Evangelism and Partner Integrations Developer