Custom field in callback notifications
Wednesday, March 8, 2023 at 03:51amHello,
We started integration with oneSpan and our applications and we are now facing issue with callback notification service.
We have 2 applications which can initate signing process in oneSpan (sales app and hr app). Both has different client apps key configured.
We created endpoint for receiving callbacks from oneSpan, but received message has only information about packageId, signerId and documentId.
Is there any possibility to add custom field to notification payload (for example to pass information about source app)
best regards
Tomasz
Reply to: Custom field in callback notifications
Wednesday, March 8, 2023 at 09:03amHi Tomasz,
Thanks for your post! To distinguish different source applications, you can use different URL paths or set different parameters for the callback URLs, e.g.:
https://example.com/callback?app=application1
https://example.com/callback?app=application2
Duo
Reply to: Custom field in callback notifications
Wednesday, March 8, 2023 at 09:09amHi,
Thank you for quick reply.
I don't see possibility to insert 2 differrent addresses in Event notfifications -> callback url field.
I have one account, but need to connect more than one client app.
Tomasz
Reply to: Custom field in callback notifications
Wednesday, March 8, 2023 at 09:40amHi Tomasz,
Thanks for the elaboration, I understand your use case now. Above suggestion is for scenarios when multiple accounts pointing to the same callback listener. If both of your client apps are registered under one account, during the transaction creation, you can specify additional custom transaction data to indicate which line of business this transaction is for. You can use either of the client app to receive the package JSON, or you can register a third client app particularly for processing callback notifications.
Duo