Lorem ipsum dolor, sit amet consectetur adipisicing elit. Neque, accusamus dolor optio eaque
exercitationem
error possimus molestias! Natus, eius est eveniet cum adipisci laboriosam, voluptatum, minima laudantium
inventore repellendus similique!
window.BAS.AS.initFrame({
key: "BASISID_API_KEY",
bas_gw: "https://api.basisid.com/",
container_id: "bas-widget-container",
ui: {
width: "100%",
height: "108px",
style: "",
},
options: {
},
events:{
onLoad: function(){
console.log("BAS AS loaded");
},
onManualCheck: function(result) {
if (result.status === "ok"){
// User data sending success
// ... Add Your code here ...
}
},
}
});
Upon successful/unsuccessful end of the user registration via Widget, you will receive an
object called
“result”.
Possible values of the “result” object:
• status – request status;
• user_hash – unique string user ID;
If a user has successfully registered, result looks like:
{
status: 'ok',
user_hash: '27c5728a-7130-408d-b0a1-d55ed8ae7b2f'
}
In case if registration has been cancelled:
{status: 'canceled'}
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 “200OK” 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.
Every callback contains a signature that allows verifying that the callback is genuine and comes from the
BASIS ID.
The signature is a sha256 concatenation of the values/text in all the fields
of a callback and API Secret
Key 2, available in the Widget Designer:
sha256(BASIS_API_SECRET2+user_id+user_hash+status+autocheck_bad_reasons)=signature
Java signature example:
String sign256hex =
org.apache.commons.codec.digest.DigestUtils.sha256Hex(BASIS_API_SECRET2 + user_id + user_hash + status + autocheck_bad_reasons);
if (sign256hex.equals(signature)) {
// Signed ...
}
PHP signature example:
$signature = hash('sha256', BASIS_API_SECRET2 . $inp['user_id'] . $inp['user_hash'] . $inp['status'] . $inp['autocheck_bad_reasons']);
if ($signature == $inp['signature']) {
}
The reasons for the profile to be automatically declined. You can have one reason or many comma separated
reasons in “autocheck_bad_reasons” field:
The callback can be sent at various points of the verification process. Please select when would you like
to receive callbacks to your URL.
At what stage/s the callback needs 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/11 |
C | When the full verification is completed | 10/11 |
D | When a user is requested to provide additional data | 3 |
{
"user_id":1337,
"user_hash":"27c5728a-7130-408d-b0a1-d55ed8ae7b2f",
"Status": 2,
"Signature":"7ca05937a0e5c42147be2aa23ffad87e80bd866e1ff7950ec6841d4d87d844fe",
“Autocheck_bad_reasons”:
“Email”: johndoe@mail.com
“autocheck_bad_reasons”:
}
{
"user_id":1337,
"user_hash":"27c5728a-7130-408d-b0a1-d55ed8ae7b2f",
"Status": 2,
"Signature":"7ca05937a0e5c42147be2aa23ffad87e80bd866e1ff7950ec6841d4d87d844fe",
“Autocheck_bad_reasons”:
“Email”: johndoe@mail.com
“autocheck_bad_reasons”:
}
{
"user_id":1337,
"user_hash":"27c5728a-7130-408d-b0a1-d55ed8ae7b2f",
"Status": 2,
"Signature":"7ca05937a0e5c42147be2aa23ffad87e80bd866e1ff7950ec6841d4d87d844fe",
“Autocheck_bad_reasons”:
“Email”: johndoe@mail.com
“autocheck_bad_reasons”:
}