The attachment ID that I define in the payload is overwritten
Thursday, November 23, 2023 at 02:55pmHi,
I'm having a problem. When I define the payload to create the transaction, OneSpan overrides the attachment ID.
For example, the user is required to attach 2 documents.
In the first document I want it to have the "Id" 00012345 and in the second, the "Id" should be 00012346.
However, once the transaction is created, when querying the transaction information, the originally defined attachment IDs, OneSpan overrides it
How can I prevent OneSpan from overwriting attachment IDs?
I need to have the original IDs so that I can download the documents individually.
Request Payload Example:
"attachmentRequirements":[
{
"description":"Please upload a scanned copy of your ID",
"required":true,
"id":"00012345",
"data":null,
"status":"INCOMPLETE",
"comment":"",
"name":"Photo ID"
},
{
"description":"Please upload a scanned copy of your license",
"required":true,
"id":"00012346",
"data":null,
"status":"INCOMPLETE",
"comment":"",
"name":"License"
}
]
Reply to: The attachment ID that I define in the payload is overwritten
Thursday, November 23, 2023 at 03:37pmHi Leandro,
Thanks for your post! It's a known limitation that you won't be able to set the signer attachment ID and OneSpan Sign system will generate a random ID for you. Therefore, you'd have to invoke an additional get package API (GET /api/package/{packageId}) and loop through the "roles" > "attachmentRequirements" to retrieve the generated attachment ID.
Duo