Force Notary to have to accept the default consent
Thursday, June 6, 2019 at 04:46amGuys,
Is there a way to force our Notary accounts to have to accept the default consent?
OneSpan Introduces DigipassONE, Bringing a Unified Platform Approach to Authentication Modernization
A new authentication platform helps financial institutions support diverse customer authentication preferences while modernizing at their own pace Learn More
Reply to: Force Notary to have to accept the default consent
Thursday, June 6, 2019 at 10:57am{ "status": "", "description": "Must be accepted and agreed to before starting the signing process.", "id": "default-consent", "data": { "ese_document_texttag_extract_needed": "false" }, "external": null, "approvals": [], ... }notary signing:{ "status": "", "description": "Must be accepted and agreed to before starting the signing process.", "id": "default-consent", "external": null, "signedHash": null, "approvals": [ //only signer was added, not notary { "role": "956cfd92-d31c-44cb-8d90-1b57db85c153", "id": "6f4dd1c1-6c13-42c1-b604-9edb196ebaba", "optional": false, "accepted": "2019-06-06T18:54:47Z", "enforceCaptureSignature": false, "signed": "2019-06-06T18:54:47Z", "data": null, "fields": [], "name": "" } ], ...... }To work it around, if you added an accept approval for notary by REST in separate call after notary role id was chosen but before the package was finally sent:HTTP Request POST /api/packages/{packageId}/documents/{documentId}/approvals HTTP Headers Accept: application/json Content-Type: application/json Authorization: Basic api_key Request Payload { "role": "notary_role_id", "id": "approval_id", "name": "approval_name" }Notary will be forced to accept the default consent. Hope this could help! Duo