Doc Less Sync

Product guide

This section provides documentation for the Doc Less service.

Doc Less is a solution designed to optimize the user onboarding process by reusing documents already stored in our database.

By doing so, it eliminates the need to request the same documents again, making the onboarding process faster, more efficient, and increasing conversion rates.

Benefits

  • Higher conversion rates: Speeds up onboarding by reusing existing documents.

  • Improved operational efficiency: Eliminates repetitive steps and reduces user effort.

  • Client flexibility: Allows clients to define the level of document validation based on their risk appetite.

How it works

Doc Less queries a centralized database of previously stored documents.

During the onboarding process, the service checks whether the user's documents already exist in the database, avoiding the need for new document capture.

Usage options

Doc Less is available in two modes:

  • Web onboarding: Integrated into Caf's standard onboarding flow.

  • API flow: Ideal for clients using direct integration through Caf’s Document Capture SDK.

Activation process

  1. Contract validation: Make sure your contract includes permission to use Doc Less.

  2. Activation by Caf: Our technical team will enable the functionality for your account.

Requirements

  • For the API flow, it is mandatory to provide the user's CPF (Brazilian ID number) along with confirmation of acceptance of the terms of use and privacy policy in order to retrieve the document reference.

Document reference

The document reference is an encrypted hash that serves as a unique identifier for locating the corresponding document in the database.

The document will only be made available after a valid transaction is created in Caf’s system. These mechanisms ensure both efficient data reuse and compliance with current privacy regulations.

API flow guide

This guide outlines the three main steps to integrate the Doc Less service via API.

1. Inserting Caf’s Terms of Use and Privacy Policy

To use Caf’s Doc Less product, it is mandatory to include Caf’s Terms of Use and Privacy Policy in the user's onboarding flow.

The user's acceptance of Caf’s Terms and Privacy Policy must be properly recorded, including logs such as IP address, date, time, and the URLs of the documents accepted. These records and evidences must be shared with Caf. This measure ensures legal compliance and regulatory security in the use of the service.

Recommended example

"By continuing, you acknowledge and agree that your personal data will be processed by Caf in accordance with the Terms of Use and the Privacy Policy."

2. Getting the document reference

Once you have your access token, you can request a document reference for reuse.

We provide a service that checks whether the user's documents already exist in our centralized database. If a match is found, the response will include the documentRef — a hash string that references the stored document.

Doc Less command

post

This endpoint allows clients to obtain the document reference. The request has a timeout of 5 seconds.

Authorizations
Body
personIdstringRequired

Unique identifier of the user to be consulted.

Responses
200
Success
application/json
post
POST /v1/doc-less/ HTTP/1.1
Host: api.combateafraude.com
Authorization: Bearer JWT
Content-Type: application/json
Accept: */*
Content-Length: 101

{
  "personId": "text",
  "acceptedTerms": {
    "userIp": "text",
    "datetime": "text",
    "acceptedTermsLinks": [
      "text"
    ]
  }
}
{
  "requestId": "text",
  "status": "FOUND",
  "documentType": "IDENTITY_CARD",
  "documentRef": "text"
}

3. Reusing the document reference

If the response from the previous step is successful and the status is "FOUND", the documentRef property will be returned.

With this reference in hand, you can proceed to create a transaction in Caf’s processing flow.

To reuse the document, pass the documentRef in the files array when creating a transaction with the type set to "DOCUMENT_REF":

{
    ...
    "files": [
      "data": "<documentRef value>",
      "type": "DOCUMENT_REF"
    ]
}

You can find the full documentation on how to create a transaction by clicking here.

Last updated