rodrigo.carmona | Posts: 13

Transaction Creation

0 votes

HI!

I would like to ask if exists a way to sent an SMS with the transaction created instead of redirect from the current site.

Currently, the flow is: create transaction > redirect > client get OTP SMS > OTP validation > Second SMS with the IDV transaction flow > next steps.

So, in case we cant redirect, it's needed to send the link to the OTP validation step.

 

Thanks in advance!


Duo_Liang | Posts: 3776

Reply to: Transaction Creation

0 votes

Hi Rodrigo,

 

When we talked about "create a transaction and redirect", is this a OneSpan Sign transaction or IDV transaction? Are you trying on one of the demo sites, or you already implemented the integrations?

If we are talking about OneSpan Sign Signing Ceremony, you can definitely generate a signing link and distribute the link in a way you preferred.

 

Duo

 

 

 


rodrigo.carmona | Posts: 13

Reply to: Transaction Creation

0 votes

Hi Duo! Thanks for your answer.

I'm talking about IDV. I've already worked on the integration of both products (IDV/OSS), but this question it's just for IDV.

I know that I can generate the link and distribute it to the user, but as IDV sends SMS, My question is that, if exists a way to deliver the IDV transaction via SMS built-in on IDV.

I have access to UAT environments of IDV if it's needed to do some tests.


Duo_Liang | Posts: 3776

Reply to: Transaction Creation

0 votes

Hi Rodrigo,

 

Thanks to the support team, they've showcased me a tenant which has a similar setup to your account and now I have a better idea of your workflow. Just wondering if there's a specific reason why you assumed the redirection failed? Because from what I saw, every subsequent steps - to initiate the SMS auth, to resend the OTP, to insert the OTP, and to proceed to the IDV flow - all of these have to be controlled by the UI, and the UI by its nature has provided a build-in way to deliver the IDV transaction via SMS (versus your application builds the link and contributes by your own SMS provider).

 

Duo


rodrigo.carmona | Posts: 13

Reply to: Transaction Creation

0 votes

Hi Duo.

I'm not saying the redirection it's failing, that's not the issue we are facing.

We want to create an IDV transaction and send the link to the client. 
So, the current flow implies that the customer starts the transaction > get redirected to OTP auth > get top SMS > authenticate > goes to the transaction.
The thing that I'm looking for is to send the first SMS for a client that, let's say, a backoffice process, creates a transaction and we need to deliver that URL.

It's a step before the same flow that you list in your answer.

And, when I say "create a transaction" (backoffice or customer-facing) I mean the API call to create the transaction ({{base_url}}/api/transaction).

Hope that clarify my question.

Thanks in advance.


rodrigo.carmona | Posts: 13

Reply to: Transaction Creation

0 votes

To clarify more my question:

Instead of getting the accessToken+transactionId from the response for the createTrasaction API call, deliver that URL vía SMS direct to the customer.

Is that possible or if we want to build something like that do we need to get and create the transactionUrl and deliver it to the customer by ourselves?

Again, thanks in advance.


will.lasala@on… | Posts: 16

Reply to: Transaction Creation

0 votes

Hi Rodrigo,

In the Rapid POC environment and the demo environment it is currently not possible to start the transaction with an SMS notification without sending the accessToken+transactionId to the user to start the transaction first.  In production there are a few methods you can use, and we do provide a URL shortener service that can be leveraged to make the accessToken+transactionId able to be sent directly via SMS.  You can work with your professional services team on your production environment to implement a solution that works for your integration.

In the next release of the Rapid POC environment, we will have services setup that allow for multi-device handoff. In this process the user starts on the web browser, and once the user arrives at the document and face capture, the user is redirected to a mobile device to handle those components.  This process is done by sending an SMS to the user once the user has arrived at the start of the capture process, and once the capture process is completed, the web page is notified and allowed for the transaction to continue.  It is not the same flow you have asked for above, but it is another way to handle multiple devices and notifying the user via SMS.

-Will


rodrigo.carmona | Posts: 13

Reply to: Transaction Creation

0 votes

Hi Will!

Thanks for your answer.
I Will talk with PS then to ask this.

Many thanks to you and Duo!.

Rodrigo Carmona.


will.lasala@on… | Posts: 16

Reply to: Transaction Creation

0 votes

Hi Rodrigo,

I heard through the professional services and engineering group that they were unable to recommend a OneSpan pre-built solution for providing the transaction start url via SMS with the built in shortener.  They are currently looking at it for a potential feature enhancement request.  Sorry if I have caused you any confusion.


rodrigo.carmona | Posts: 13

Reply to: Transaction Creation

0 votes

No worries Sal. I've a meet with some PS team and get to a good approach too.

Many thanks for your time and effort.


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off