rajiv.nagpur's account

Screen shots attached for your reference.

Thank you very much for your prompt response, Duo! Likewise, it's so nice to reconnect with you, Duo, hope all is going well at your end!

Can you please elaborate a bit more on how we can get the information before starting the signing session? You mentioned that it is possible to retrieve information about a customer's location within an application before starting the signing session, I understand the signer authentication token theory of 30 minutes, but can you share more info on how to use field injection or label field to present the GIS during the signing? Can you please provide an example?  

Hi Duo - Hope you are doing well! I am just following up with you in reference to my previous post, can you please advise on that? 

Also, I wanted to check with you on the following:

1. Do you know if OneSpan currently has a geolocationization setting/feature or any similar setting/feature in JSON in Back-Office to track where the signer was when they registered a transaction? In other words, it would be great if we could have a new column added in 
the audit trail(evidence summary) for signer location. To a certain degree, the evidence summary does provide details such as the IP address, but does not include co-ordinates/geolocation/country/city or any such information of a signer in OSS.

2. If not, then do you know if this is on the roadmap in the near future? If this is in OSS's pipeline, then is there any time frame about when it could become available? 

3. If not, then can it be submitted as an enhancement request? 

Please share your inputs.

Regards,
Rajiv Nagpur

Hi Duo - Can you also please share your insights or provide us with some context on how we can go about using Geolocation API in eSign through the SDK?

Thank you Duo for your prompt response! Using the session field, can you please tell me how I can go about getting the location/position of a signer?

 {
     "packageId": "package ID",
     "sessionFields": {
         "Transaction ID": "1234567890",
         "Login Token": "8888888888888"
     },
     "signerId": "signer1"
 }