Access clear and detailed documentation to integrate our APIs effortlessly. Everything you need to get started
is at your fingertips.
Please enter the api-token field in the input above to do API testing in the page, fill in the {token} for
production or fill in the {token_sandbox} to try the API in sandbox mode
Below is the result classification for Location Verification result
INDOSAT OOREDOO HUTCHISON
Score
Description
1
Less than 0.5 km
2
0.5 - 1 km
3
1 - 2 km
4
2 - 5 km
5
5 - 10 km
6
10 - 50 km
7
More than 50 km
TELKOMSEL and XLAXIATA
Score
Description
1
0 - 250 meter
2
251 - 500 meter
3
501 - 750 meter
4
751 meter - 1 km
5
1,001 meter - 2 km
6
2,001 meter - 4 km
7
>4 km
Below is the result classification for NIK Matching Verification result
Match and Mismatch Cases
Case
Description
1
Match, NIK only registered to 1 MSISDN
2
Match, NIK registered to more than 1 MSISDN
3:01
Not Match, NIK Exist in db, MSISDN Exist in DB
3:02
Not Match, NIK Exist in db, MSISDN not Exist in DB
3:03
Not Match, NIK not Exist in db, MSISDN Exist in DB
4
Not Match, Both MSISDN and NIK not exist/active
0
Not Match, information is kept confidential by the provider
Below is the result classification for NPWP Score result
Tax Percentages
Score
Percentage
Taxable Income Range
E
5%
Untuk penghasilan kena pajak hingga Rp60.000.000 per tahun
D
15%
Untuk penghasilan kena pajak Rp60.000.000 sampai dengan Rp250.000.000 per tahun
C
25%
Untuk penghasilan kena pajak Rp250.000.000 sampai dengan Rp500.000.000 per tahun
B
30%
Untuk penghasilan kena pajak di atas Rp500.000.000 sampai dengan Rp5.000.000.000 per tahun
A
35%
Untuk penghasilan kena pajak di atas Rp5.000.000.000
Below is the result of Tenure Score
Indosat Tenure Calssification
Score
Description
1
Age ≤ 30d
2
30d < Age ≤ 90d
3
90d < Age ≤ 180d
4
180d < Age ≤ 365d
5
Age > 365d
XlAxiata Tenure Calssification
Score
Description
1
Less than 3 Month (<= 89 days)
2
3 - 6 Months (90 days < D <=179 days)
3
6 - 12 Months (180 days < D <=364 days)
4
1 - 2 Year (180 days < D <=729 days)
5
2 - 3 Year (730 days < D <=1079 days)
6
3 - 5 Year (1080 days < D <=1800 days)
7
> 5 Year (> 1800 days)
Below is the result of SES Score
Below is description of screening result
PEP : Politically Exposed Person (apakah pernah mengikuti
kampanye, pernah menjabat di pemerintahan)
RCA : Relative & close associates (memberi tau berapa banyak
anggota keluarga yang di temukan)
SIP : Special Interest Person (memberi informasi apakah nama
tersebut pernah terkait dengan tindak pidana pencucian uang)
Crime : Memberi info apakah ada berita yang pernah
menginformasikan bahwa nama tersebut pernah melakukan kejahatan
Sanctions : Memberikan informasi jika nama tersebut telah menerima
sanksi dari badan internasional seperti interpol, atau dari
pemerintahan setempat. Contoh : Red Notice dari Interpol
Watchlist : Daftar individu, kelompok, atau hal-hal yang
memerlukan pengawasan ketat, biasanya karena alasan hukum atau
politik.
Below is the result classification for Sim Swap result This API will detect the last time SIM CARD last changed IMEI, which indicates the SIM has changed slots
TELKOMSEL
Score
Description
1
Before 24hours
2
24hours - 48hours
3
48hours - 72hours
4
More than 72hours
To protect your data, we use a strong encryption method called AES-256-CBC. Here's a step-by-step explanationthat's easy to understand:
Encryption method used: AES-256 in CBC Mode with PKCS7 Padding.
Secure Key from a Strong Passphrase We start with a secret key. This key should be securely stored on your side, you need this to encrypt and decrypt the content. You can re-generate the key if needed, but remember to keep it safe.
Random Code for Extra Security (IV) Every time data is encrypted, we generate a new random 16-byte Initialization Vector (IV). This ensures
that even if the same data is encrypted multiple times, the result will always be different.
Encrypting the Data We encrypt the data using AES-256 in CBC (Cipher Block Chaining) mode — a trusted and secure encryption method. We also apply PKCS7 Padding to make sure the data fits properly into encryption blocks.
Combining IV and Encrypted Data Before storing or sending the encrypted data, we prepend the IV to the encrypted message. This makes it possible to correctly decrypt the data later.
Safe to Store or Send (Base64 Encoding) Next, the combined IV and encrypted data is encoded into a Base64 string. This makes it safe and easy to store or transmit over the internet.
Logging Transaction Finally, all request and response data is logged in the database as encrypted content. This allows us to keep track of transactions securely. If the log is ever leaked and someone tries to access the data without the correct key, they will only see a jumble of meaningless characters.
