CFWeb Process

In this scenario, the Merchant is the requestor and the Customer is the person submitting the document and selfie upon request.

Merchant Sends a Request

A Customer walks into a Merchant store and would like to purchase an item, (this could be a bank, a mobile phone company, etc.). The Merchant would like to verify the Customer’s identity. The Customer agrees to the request and submits a document for verification.

There are three options to initiate a request (SMS, Email, and URL). Once the request is sent, the Customer opens the link and begins submitting their documents and selfies.

Note: Our CFWeb application can only work on a mobile device because the CFWeb App uses a mobile device camera.

  • Send request via SMS

    • The Merchant or HID will send an SMS link to the CFWeb Application.

  • Send request via Email

    • The Merchant or HID will send an email link to the CFWeb Application.

  • Send request via URL

    • The Merchant or HID will send a URL link to the CFWeb Application.

Merchant specifies the fields they want to be returned in the response using the channelResponse parameter in api/verify. The Merchant sends the request, the api/verify checks for required information. Listed below is an example of this process:

  1. How do you want to send the request to the Customer (via email or SMS)?

  2. Does this need a customized look and feel to capture the document?

  3. After the Customer submits the document, what information does the Merchant want back?

    1. Does the Merchant want a selfie retrieved back? (This is optional and can be set in verify request).

    2. How does the Merchant wish to retrieve the data back?

      1. PostbackURL or

      2. redirectURL

Customer Submits Verify Request

There are three main parameters sent in with Verify Request. Verify Request API then goes to the CFWeb server, looks at the submitted documents, and validates that the content is good.

CFWeb Server then sends a link for the CFWeb Client to the Customer. The Customer starts taking pictures and submits each document to CFWeb Server for validation. The Customer keeps submitting each document as he captures it to the CFWeb Server.

The Request is Verified

When the customer has submitted all of the documents and verified everything, CFWeb server forwards the submitted request to CFAir for validation and fraud protection (Authenticate Document); this contains the front and back captures of the document. Once all the documents are sent out and CFAir processes everything, the response comes back to the CFWeb Server and sends the results to the Customers mobile phone.

Note: Near and Far Selfies can be disabled within Verify Request. This is a configurable parameter located in channelConfiguration. The customer can send a Near Selfie and Far Selfie, it then sends this out to CFWeb Server, which also forwards the information to CFAir for validation and fraud protection.

Merchant Retrieves Data from the System

CFWeb server offers three methods to retrieve data from the system. The data is returned using one of the two postback mechanisms. We will call the Merchant and the customer configures the Postback. CFWeb will call this URL using the POST method. 

API & Postback Type Method
api/status Response Returned GET Postback for request
/api/status/uid Response Returned GET Postback for transaction

Postback to url

(Provided by enterprise customer)

 Response Sent to Postback URL POST Postback for transaction and request

PostbackURL: If  Verify Request says, “send information back” using PostbackURL then the Merchant gets notified that the Customer has completed the transaction and it was a good document. The Merchant integrates the request to send back information using PostbackURL.

Polling: If the Merchant wants the data, the Merchant calls CFWeb to retrieve the data back.

To view more details about how PostbackURL works, refer to CFWeb Verify Request API.