[email protected]

Rapid Proof Of Concept - Supported Workflow ID's and descriptions

1 votes

When working with the Rapid Proof of Concept environment only specific Workflow ID's are currently supported.  These may change from time to time, but will be backwards compatible through out the Rapid Proof of Concept phase of any project.

Here are the currently supported workflow IDs:

  • "00000000-0000-0000-0000-300000000007", - Full SAA Workflow with development friendly rules
  • "00000000-0000-0000-0000-310000000007", - Identity Verification only Workflow with development friendly rules
  • "00000000-0000-0000-0000-400000000007", - Full SAA Workflow with UAT testing rules
  • "00000000-0000-0000-0000-410000000007", - Identity Verification only Workflow with UAT testing rules
  • "00000000-0000-0000-0000-200000000007", - Full SAA Workflow with development friendly rules (North American (US/CA) Drivers License Support)

If you need more information about any of these workflows, please feel free to ask us.

Will LaSala

Sr. Director of Global Solutions, Security Evangelist

M: +1 978 666 4495 
O: +1 508 281 6670 x. 6326

[email protected]

OneSpan, Inc.

www.onespan.com


Reply to: Rapid Proof Of Concept - Supported Workflow ID's and descriptions

0 votes

Dear Will,

Could we have a customized workflow based on our business requirement ? like for example a customized workflow in which we will apply the Document OCR Parsing where we will take only an image capture of the national id document and benefits from the OCR data/fields automatically extracted from the doc (attached onespan_document_captue.jpg) in addition to the checking on the validity of the scanned doc. And to have another customized workflow for the liveness detection where the user will take a selfie capture with smile and then we can benefits from the liveness detection service separately ? (attached onespan_face_capture_and_smile.jpg)

This way, and in case feasible, we can benefits from the Document Verification and OCR Parsing from our backend services without the need of the customer intervention to take a live selfie, so we can validate a set of documents uploaded by the customer in backend without the customer intervention, by calling OneSpan IDV REST API in which we can provide the byte arrays (or base 64) representation of the Document Capture and receive in response the OCR fields and Document Scoring results.

Plus could we have please some details on the above workflows, for example what is the difference between "00000000-0000-0000-0000-300000000007" and "00000000-0000-0000-0000-310000000007" ? because we have tried to create transactions with each one of them and we found that both of them are asking for Document Capture and for Face and Smile Capture, (step  onespan_document_captue.jpg then step of onespan_face_capture_and_smile.jpg ), what's the difference between them ?

Thank you,

Nabil,

 

 

 


Reply to: Rapid Proof Of Concept - Supported Workflow ID's and descriptions

0 votes

Hi Nabil,

In the next update for the demo workflows, we will be implementing a Document Only workflow.  This workflow could be used to capture the document only details for you.  Validating the face separately could be an issue however.  We currently do not have the ability to take an image of the face and only do that component of the workflow, as you would need to capture a document first and then capture the face to do the validation.

When you signup with OneSpan, our professional services group can help you further to create custom integrations like this.  In our demo and poc environments we are a bit more limited to what we can do there.

Hope this helps.

Will

OneSpan


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