To verify your documents, identity and gain verification experience from BASIS ID, use the widget below. The results are displayed in our CRM dashboard, we will get in touch with you.

Integration Guidance

1. Widget Integration

BASIS ID provides a configurable web-and-mobile friendly widget to embed onto your platform with only 3 simple html-code blocks.

Embed the BASIS ID widget at the desired stage of your customer journey.

Insert widget code in <head> … </head> section of the page:


<script type="text/javascript" src="https://api.basisid.com/assets/js/widget.multi.js"></script>

Add widget location on your website after <body> tag:


<div id="bas-widget-container" style="min-height: 350px;"> BASIS ID loading...</div> 

Add widget code on the bottom of your page before </body> tag:


  <script type="text/javascript"> 
  window.BAS.AS.initFrame({
  key: "BASISID_API_KEY",
  bas_gw: "https://api.basisid.com/",
  container_id: "bas-widget-container",
  ui: {
      width: "100%",
      height: "705px",
      style: "",
      mobile_height: “auto”
  },
  options: {
  },
  events:{
      onLoad: function(){
          console.log("BAS AS loaded");
      },
      onManualCheck: function(result) {
          if (result.status === "ok"){
            // User data sending success
            // ... Add Your code here ...
          }
      },
  }
});
         

2. Widget Options

BASIS ID widget is configurable:

Apart from the general flow of verification, which you shall discuss with your account manager, there are other options available.

The options field of the widget can also include the following lines:

},
  options: {
          "api_form_token": "insert form token",
          "language": "en"
  },

API form token is a parameter, that we can enable to make widget only work with it inserted into the code of the widget. API form token is issued separately from the widget, with a simple API call.

Language is a parameter that allows to pre-define the language of the widget and skip this step from the standard flow.

The parameter is inserted in ISO code of the country.
The following languages are currently available: en/ru/vn/es/cn/pl/jp/kr

Also, you may find the background color configurator in the CRM.

BASIS ID is also able to set up a Widget origin URL, that makes widget open up only from specific URLs for further security.

3. Callback

Important

BASIS ID is using the callback method to transfer the statuses of the verification to the client’s platform.

There are various types of callbacks BASIS ID is able to send, each designed for a specific stage of the verification process. A client has to set up a callback URL from where their system will collect the statuses of the verification process.

An example of such a callback:

{
"user_id":20272,
"user_hash":"27c5728a-7130-408d-b0a1-d55ed8ae7b2f",
"status":11,
"signature":"7ca05937a0e5c42147be2aa23ffad87e80bd866e1ff7950ec6841d4d87d844fe",
"autocheck_bad_reasons":""
}

In response to a callback, you have to send back the status “200 OK” with any text, for example, “OK”.

If a response has not been received or it did not contain “200OK”, the system stops sending requests for 3 minutes. After 3 attempts the system will delay the next attempt by an hour.

The list of available callbacks and their respective callbacks are at the bottom of this page.

4. Callback settings

The callback can be sent at various points of the verification process. Client selects which callbacks would they like to receive.

At what stage(s) the callback may to be sent:

Callback type Status values
A When a new user is registered in the system 2
B When the AML/Sanction screening is completed 10 or 11
C When the full verification is completed 10 or 11
D When a user is requested to provide additional data 3

Callback Examples


{
"user_id":1337,
"user_hash":"27c5728a-7130-408d-b0a1-d55ed8ae7b2f",
"status": 2,
"signature":"7ca05937a0e5c42147be2aa23ffad87e80bd866e1ff7950ec6841d4d87d844fe",
“autocheck_bad_reasons”:
“email“: “johndoe@mail.com“
}


{
"user_id":1337,
"user_hash":"27c5728a-7130-408d-b0a1-d55ed8ae7b2f",
"status":10,
"signature":"7ca05937a0e5c42147be2aa23ffad87e80bd866e1ff7950ec6841d4d87d844fe",
“autocheck_bad_reasons”:
}

reasons in "autocheck_bad_reasons" field:

pep - politically exposed person
law enforcement
regulatory enforcement
other bodies
sanctions - governmental and other sanctions
black_list - A person with the same name is mentioned in blacklist.
video - No match in facial recognition or failed liveness check.
mrz - customer data does not match with ID's machine readable zone (MRZ)
or the document is not valid.


{
"user_id":1337,
"user_hash":"27c5728a-7130-408d-b0a1-d55ed8ae7b2f",
"status":11,
"signature":"7ca05937a0e5c42147be2aa23ffad87e80bd866e1ff7950ec6841d4d87d844fe",
“autocheck_bad_reasons”:
}

reasons in "autocheck_bad_reasons" field:

pep - politically exposed person
law enforcement
regulatory enforcement
other bodies
sanctions - governmental and other sanctions
black_list - A person with the same name is mentioned in blacklist.
video - No match in facial recognition or failed liveness check.
mrz - customer data does not match with ID's machine readable zone (MRZ)
or the document is not valid.


{
"user_id": 1337,
"user_hash":"27c5728a-7130-408d-b0a1-d55ed8ae7b2f",
"status":10,
"signature":"7ca05937a0e5c42147be2aa23ffad87e80bd866e1ff7950ec6841d4d87d844fe",
"autocheck_bad_reasons":
}

reasons in "autocheck_bad_reasons" field:

pep - politically exposed person
law enforcement
regulatory enforcement
other bodies
sanctions - governmental and other sanctions
black_list - A person with the same name is mentioned in blacklist.
video - No match in facial recognition or failed liveness check.
mrz - customer data does not match with ID's machine readable zone (MRZ)
or the document is not valid.


{
"user_id": 1337,
"user_hash":"27c5728a-7130-408d-b0a1-d55ed8ae7b2f",
"status":11,
"signature":"7ca05937a0e5c42147be2aa23ffad87e80bd866e1ff7950ec6841d4d87d844fe",
"autocheck_bad_reasons":"mrz"
}

alternative:

{
"user_id":2027,
"user_hash":"27c5728a-7130-408d-b0a1-d55ed8ae7b2f",
"status":11,
"signature":"7ca05937a0e5c42147be2aa23ffad87e80bd866e1ff7950ec6841d4d87d844fe",
"autocheck_bad_reasons":"",
"reason": 0,
"message": "",
}

reasons in "autocheck_bad_reasons" field:

pep - politically exposed person
law enforcement
regulatory enforcement
other bodies
sanctions - governmental and other sanctions
black_list - A person with the same name is mentioned in blacklist.
video - No match in facial recognition or failed liveness check.
mrz - customer data does not match with ID's machine readable zone (MRZ)
or the document is not valid.

Final reason in "reason" field:
0 - Wrong data
1 - Wrong photos
2 - Fake documents
3 - Other

"Message" - a message with the reason for declining this customer


{
"callback_type": "request",
"user_id":2027,
"user_hash":"27c5728a-7130-408d-b0a1-d55ed8ae7b2f",
"status":3,
"signature":"7ca05937a0e5c42147be2aa23ffad87e80bd866e1ff7950ec6841d4d87d844fe",
"reason": "0,5",
"request": "1,2",
"message": "Request message",
}

"reasons" - list of reasons for requesting data, separated with ','
0 - No required data 1 - Data has mistakes 2 - Email not confirmed
3 - Bad photo quality 4 - No required photos 5 - No MRZ zone on document photos
6 - Bad video quality 7 - Bad utility bill photo
8 - Utility bill is old 9 - Social accounts are not relevant
10 - Bad quality of latest pay slip photo
11 - Pay slip is old 12 - Bad quality of proof of income photo 13 - Proof of income is old

"request" - list of requested data, separated with ','.
0 - Name 1 - Gender 2 - Birthday
3 - Country of Nationality 4 - Full Address 5 - Phone
6 - E-mail 7 - Passport/ID card photo 8 - Client photo
9 - Video 10 - Bank statement 11 - Social networks accounts
12 - Utility bill 13 - Proof of income

Сookies!
This site uses cookies to provide the best online experience. By using this site, you agree that we may store and access cookies on your device.
Close