# Shufti for Developers

> REST API documentation for Shufti identity, business, and transaction verification services.

## API Essentials

- **Base URL:** `https://api.shuftipro.com/` — a single endpoint serves every service; you select services as objects in the JSON request body.
- **Authentication:** HTTP Basic Auth (Client ID = username, Secret Key = password). Access Token authentication is also supported. Every request must be authorized.
- **Responses:** Each request yields two JSON responses — a synchronous HTTP response and an asynchronous callback to your `callback_url`. Both carry a `Signature` header you must validate to confirm the source.
- **Integration modes:** Onsite (Shufti-hosted iFrame/Verify component) or Offsite (you collect proofs and call the API directly).
- **Testing:** Use Test IDs and a trial account to validate integration before going live.

## Overview & Reference
- [Get Started](https://developers.shuftipro.com/docs/get_started.md): Shufti's REST API offers a developer-friendly solution for seamlessly integrating Identity, Business, and Transaction Verification/Monitoring services into web or mobile applications.
- [General Parameters](https://developers.shuftipro.com/docs/general_parameters.md): This section outlines the universal parameters that are integral to every verification request processed by Shufti.
- [Multi Service Integration](https://developers.shuftipro.com/docs/multi_service_integration.md): Shufti allows clients to use multiple services at once through one API request.
- [Test ID Samples](https://developers.shuftipro.com/docs/test_ids.md): The below-provided Test ID Samples for different services can be used either during the testing or the integration process.
- [Glossary](https://developers.shuftipro.com/docs/glossary.md): Reference table of Term, Definition.
- [Revision History](https://developers.shuftipro.com/docs/revision_history.md): Reference table of Date, Description.

## Verification Modes
- [Onsite Verification Mode](https://developers.shuftipro.com/docs/verification_methods/onsite.md): The Onsite verification process by Shufti offers an intuitive and direct interaction for end users through the sophisticated iFrame/Verify component.
- [Offsite Verification Mode](https://developers.shuftipro.com/docs/verification_methods/offsite.md): The Offsite verification process by Shufti is characterized by its efficient and straightforward approach.

## User Identification & Authentication
- [Fast ID](https://developers.shuftipro.com/docs/user_identification_authentication/fast_id.md): Shufti Fast ID is a revolutionary service that transforms customer onboarding by enabling instant identity verification with just a facial scan.
- [Fraud Hub](https://developers.shuftipro.com/docs/user_identification_authentication/fraud_hub.md): Fraud Hub is an advanced risk intelligence module designed to provide comprehensive fraud detection and risk assessment for identity verification workflows.
- [How It Works?](https://developers.shuftipro.com/docs/user_identification_authentication/eidv_pro/how_it_works.md): eIDV(Electronic Identity Verification) a digital identity verification solution designed to authenticate and confirm the identities of individuals online.
- [Onsite Integration](https://developers.shuftipro.com/docs/user_identification_authentication/eidv_pro/onsite.md): With On-site verification, Shufti directly interacts with the end-user, managing data collection to facilitate identity verification.
- [Offsite Integration](https://developers.shuftipro.com/docs/user_identification_authentication/eidv_pro/offsite.md): Offsite Verification means Shufti doesn't interact directly with the end-user.
- [Responses](https://developers.shuftipro.com/docs/user_identification_authentication/eidv_pro/responses.md): Here is an extensive breakdown of responses tailored for a variety of Electronic Identity Verification (eIDV Pro) services available in supported countries.
- [Declined Reasons](https://developers.shuftipro.com/docs/user_identification_authentication/eidv_pro/declined_reasons.md): When a verification request involving eIDV Pro service is declined, the following reasons are presented to the end user or client.
- [How It Works?](https://developers.shuftipro.com/docs/user_identification_authentication/facial_biometrics/how_it_works.md): AI-powered biometric technology that identifies individuals by comparing and analyzing end user facial features.
- [Onsite Integration](https://developers.shuftipro.com/docs/user_identification_authentication/facial_biometrics/onsite.md): In onsite verification, Shufti will directly interact with the end user to collect the required proofs for verification.
- [Offsite Integration](https://developers.shuftipro.com/docs/user_identification_authentication/facial_biometrics/offsite.md): In the offsite verification process, Shufti's clients are solely responsible for gathering all necessary proof from the end user and then submitting it to Shufti for verification.
- [Declined Reasons](https://developers.shuftipro.com/docs/user_identification_authentication/facial_biometrics/declined_reasons.md): When a verification request involving Facial Biometrics service is declined, the following reasons are presented to the end user or client.
- [Sample Face Documents](https://developers.shuftipro.com/docs/user_identification_authentication/facial_biometrics/sample_face_documents.md): The below-provided sample face images for the Face biometric service can be used either during the testing or the integration process.
- [How it works](https://developers.shuftipro.com/docs/user_identification_authentication/age_verification/how_it_works.md): Verify end users' age to comply with regulatory requirements and protect minors from age-restricted content, products, or services.
- [Onsite Integration](https://developers.shuftipro.com/docs/user_identification_authentication/age_verification/onsite.md): With Onsite verification, Shufti will directly interact with the end user, managing data collection to facilitate age verification.
- [Offsite Integration](https://developers.shuftipro.com/docs/user_identification_authentication/age_verification/offsite.md): In Offsite verification, the client is responsible for collecting the required proofs and information from the end user and submitting it to Shufti for verification.
- [How it works](https://developers.shuftipro.com/docs/user_identification_authentication/one_to_one_authentication/how_it_works.md): 1:1 authentication is a biometric identity verification process in which a person’s face is compared against a single, pre-enrolled reference record associated with a unique identifier.
- [Onsite Integration](https://developers.shuftipro.com/docs/user_identification_authentication/one_to_one_authentication/onsite.md): With Onsite verification, Shufti will directly interact with the end user, managing data collection to facilitate 1:1 authentication.
- [Offsite Integration](https://developers.shuftipro.com/docs/user_identification_authentication/one_to_one_authentication/offsite.md): In Offsite verification, the client is responsible for collecting the required proofs and information from the end user and submitting it to Shufti for verification.
- [Declined Reasons](https://developers.shuftipro.com/docs/user_identification_authentication/one_to_one_authentication/declined_reasons.md): When a verification request involving 1:1 Authentication is declined, the following reasons are presented to the end user or client.
- [How it works?](https://developers.shuftipro.com/docs/user_identification_authentication/document_verification/how_it_works.md): Verify the authenticity of end user’s ID documents to prevent fraud.
- [Onsite Integration](https://developers.shuftipro.com/docs/user_identification_authentication/document_verification/onsite.md): In onsite verification, Shufti will directly interact with the end user to collect the required proofs for verification purposes.
- [Offsite Integration](https://developers.shuftipro.com/docs/user_identification_authentication/document_verification/offsite.md): In the offsite verification process, Shufti's clients are solely responsible for gathering all necessary proof from the end user and then submitting it to Shufti for verification.
- [Custom Add-Ons](https://developers.shuftipro.com/docs/user_identification_authentication/document_verification/custom_addons.md): Shufti provides its customers with the facility of extracting enhanced data features using OCR technology.
- [Name Matching Preferences](https://developers.shuftipro.com/docs/user_identification_authentication/document_verification/name_matching_preferences.md): Shufti allows two types of name matches in document service according to your business requirements.
- [Declined Reasons](https://developers.shuftipro.com/docs/user_identification_authentication/document_verification/declined_reasons.md): When a verification request involving Document Verification is declined, the following reasons are presented to the end user or client.
- [Sample ID Documents](https://developers.shuftipro.com/docs/user_identification_authentication/document_verification/sample_id_documents.md): The below-provided Test ID Samples for document services can be used either during the testing or the integration process.
- [How It Works?](https://developers.shuftipro.com/docs/user_identification_authentication/address_verification_and_validation/standard_address_verification/how_it_works.md): In standard address verification, the end user's provided address is confirmed by obtaining a valid address document.
- [Verification Parameters](https://developers.shuftipro.com/docs/user_identification_authentication/address_verification_and_validation/standard_address_verification/verification_parameters.md): To ensure successful verification in standard address verification, it is crucial for the client to provide complete and accurate address information in the fulladdress field of…
- [Onsite Integration](https://developers.shuftipro.com/docs/user_identification_authentication/address_verification_and_validation/standard_address_verification/onsite.md): In onsite verification, Shufti will directly interact with the end user to collect the required proofs for verification purposes.
- [Offsite Integration](https://developers.shuftipro.com/docs/user_identification_authentication/address_verification_and_validation/standard_address_verification/offsite.md): In the offsite verification process, Shufti's clients are solely responsible for gathering all necessary proof from the end user and then submitting it to Shufti for verification.
- [How It Works?](https://developers.shuftipro.com/docs/user_identification_authentication/address_verification_and_validation/enhanced_address_verification/how_it_works.md): In enhanced address verification the end user is only required to upload a valid address document and all the essential information from the document is extracted and verified against official global address databases.
- [Verification Parameters](https://developers.shuftipro.com/docs/user_identification_authentication/address_verification_and_validation/enhanced_address_verification/verification_parameters.md): The enhanced address verification feature in Shufti includes a new key named enhancedaddressverification that is passed in the address service.
- [Onsite Integration](https://developers.shuftipro.com/docs/user_identification_authentication/address_verification_and_validation/enhanced_address_verification/onsite.md): In onsite verification, Shufti will directly interact with the end user to collect the required proofs for verification purposes.
- [Offsite Integration](https://developers.shuftipro.com/docs/user_identification_authentication/address_verification_and_validation/enhanced_address_verification/offsite.md): In the offsite verification process, Shufti's clients are solely responsible for gathering all necessary proof from the end user and then submitting it to Shufti for verification.
- [Sample Address Documents](https://developers.shuftipro.com/docs/user_identification_authentication/address_verification_and_validation/sample_address_documents.md): The below-provided test address samples for address services can be used either during the testing or the integration process.
- [Declined Reasons](https://developers.shuftipro.com/docs/user_identification_authentication/address_verification_and_validation/declined_reasons.md): When a verification request involving Address Verification & Validation is declined, the following reasons are presented to the end user or client.
- [Overview](https://developers.shuftipro.com/docs/user_identification_authentication/user_aml_screening/overview.md): Shufti's Individual AML Screening checks a person against 4,000+ global watchlists spanning 240+ countries and territories, covering sanctions, Politically Exposed Persons (PEPs),…
- [How It Works?](https://developers.shuftipro.com/docs/user_identification_authentication/user_aml_screening/how_it_works.md): Individual AML Screening evaluates a person against Shufti's connected watchlists and returns every record that resembles them, each with a match score you can act on.
- [Onsite Integration](https://developers.shuftipro.com/docs/user_identification_authentication/user_aml_screening/onsite.md): This verification process mandates that the end user provide their full name and date of birth.
- [Offsite Integration](https://developers.shuftipro.com/docs/user_identification_authentication/user_aml_screening/offsite.md): In this verification procedure, the client is required to provide Shufti with the end user's full name and date of birth.
- [Match Results](https://developers.shuftipro.com/docs/user_identification_authentication/user_aml_screening/match_results.md): For every record returned, Shufti reports the degree of correlation between the screened individual's details and the watchlist entry, so you can see exactly why a record was surfaced.
- [Responses](https://developers.shuftipro.com/docs/user_identification_authentication/user_aml_screening/responses.md): "reference": "",
- [Declined Reasons](https://developers.shuftipro.com/docs/user_identification_authentication/user_aml_screening/declined_reasons.md): When a verification request involving User AML Screening is declined, the following reasons are presented to the end user or client.
- [How It Works](https://developers.shuftipro.com/docs/user_identification_authentication/crypto_wallet_screening/how_it_works.md): Crypto Wallet Screening allows merchants to screen a wallet address or an entity name against selected databases and watchlists.
- [Offsite Integration](https://developers.shuftipro.com/docs/user_identification_authentication/crypto_wallet_screening/offsite.md): In offsite integration, the merchant collects input through their own interface and sends the screening request to Shufti via the API or backoffice.
- [Responses](https://developers.shuftipro.com/docs/user_identification_authentication/crypto_wallet_screening/responses.md): The following is a sample response for a Crypto Wallet Screening request.
- [Declined Reasons](https://developers.shuftipro.com/docs/user_identification_authentication/crypto_wallet_screening/declined_reasons.md): When a verification request involving Crypto Wallet Screening is declined, the following reasons are presented to the end user or client.
- [How It Works?](https://developers.shuftipro.com/docs/user_identification_authentication/due_diligence_form/how_it_works.md): Shufti assists clients in gathering crucial user information necessary for onboarding and enhanced due diligence verification.
- [Onsite Integration](https://developers.shuftipro.com/docs/user_identification_authentication/due_diligence_form/onsite.md): In onsite verification, Shufti will directly interact with the end user to collect the required proofs for verification purposes.
- [Declined Reasons](https://developers.shuftipro.com/docs/user_identification_authentication/due_diligence_form/declined_reasons.md): When a verification request involving Due Diligence Form is declined, the following reasons are presented to the end user or client.
- [How It Works?](https://developers.shuftipro.com/docs/user_identification_authentication/consent_verification/how_it_works.md): Shufti enables organizations to gather live image consent from users, confirming their real presence and safeguarding against bot activity.This service can authenticate a variety…
- [Onsite Integration](https://developers.shuftipro.com/docs/user_identification_authentication/consent_verification/onsite.md): In onsite verification, Shufti will directly interact with the end user to collect the required proofs for verification purposes.
- [Offsite Integration](https://developers.shuftipro.com/docs/user_identification_authentication/consent_verification/offsite.md): In offsite verification process, Shufti's clients are solely responsible for gathering all necessary proof from the end user and then submitting it to Shufti for verification.
- [Declined Reasons](https://developers.shuftipro.com/docs/user_identification_authentication/consent_verification/declined_reasons.md): When a verification request involving Consent Verification is declined, the following reasons are presented to the end user or client.
- [Sample Consent Documents](https://developers.shuftipro.com/docs/user_identification_authentication/consent_verification/sample_consent_documents.md): The below-provided test consent Samples for consent service can be used either during the testing or the integration process.
- [How It Works?](https://developers.shuftipro.com/docs/user_identification_authentication/phone_verification_and_validation/how_it_works.md): Verify the legitimacy of the end user's phone number by employing a OTP (One-Time Password) verification process combined with rigorous fraud detection checks for validation to…
- [Onsite Integration](https://developers.shuftipro.com/docs/user_identification_authentication/phone_verification_and_validation/onsite.md): In onsite verification, Shufti will directly interact with the end user to collect the required proofs for verification purposes.
- [Declined Reasons](https://developers.shuftipro.com/docs/user_identification_authentication/phone_verification_and_validation/declined_reasons.md): When a verification request involving Phone Verification & Validation is declined, the following reasons are presented to the end user or client.
- [How It Works?](https://developers.shuftipro.com/docs/user_identification_authentication/email_verification_and_validation/how_it_works.md): Confirm the authenticity of the end user email address.
- [Onsite Integration](https://developers.shuftipro.com/docs/user_identification_authentication/email_verification_and_validation/onsite.md): In onsite verification, Shufti will directly interact with the end user to collect the required proofs for verification purposes.
- [Declined Reasons](https://developers.shuftipro.com/docs/user_identification_authentication/email_verification_and_validation/declined_reasons.md): When a verification request involving Email Verification & Validation is declined, the following reasons are presented to the end user or client.
- [How It Works?](https://developers.shuftipro.com/docs/user_identification_authentication/user_risk_assessment/how_it_works.md): Our risk assessment process commences with extensive data collection, succeeded by meticulous analysis employing advanced fraud prevention rules to assign a risk score.
- [Onsite Integration](https://developers.shuftipro.com/docs/user_identification_authentication/user_risk_assessment/onsite.md): In onsite verification, Shufti will directly interact with the end user to collect the required proofs for verification purposes.
- [Fraud Prevention Rules](https://developers.shuftipro.com/docs/user_identification_authentication/user_risk_assessment/fraud_prevention_rules.md): Our fraud prevention rules empower merchants to customise parameters aligned with their risk tolerance levels.
- [Declined Reasons](https://developers.shuftipro.com/docs/user_identification_authentication/user_risk_assessment/declined_reasons.md): The risk assessment service enables clients to categorize KYC services based on risk levels, such as low, medium, and high.
- [How It Works?](https://developers.shuftipro.com/docs/user_identification_authentication/video_kyc/how_it_works.md): The VideoIdent process works in the following way:
- [Request Parameters](https://developers.shuftipro.com/docs/user_identification_authentication/video_kyc/request_parameters.md): Shufti uses the following BASE URL for VideoIdent: https://api.shuftipro.com/service/realtime/verification
- [VideoIdent with OCR](https://developers.shuftipro.com/docs/user_identification_authentication/video_kyc/video_kyc_with_ocr.md): In a verification request with OCR, Shufti's client defines the parameters to be verified.
- [VideoIdent without OCR](https://developers.shuftipro.com/docs/user_identification_authentication/video_kyc/video_kyc_without_ocr.md): In verification requests without OCR, Shufti's clients define the parameters to be verified.
- [Declined Reasons](https://developers.shuftipro.com/docs/user_identification_authentication/video_kyc/declined_reasons.md): When a VideoIdent verification request is declined, the end user or client is informed of the specific reasons for the decline related to the services used during VideoIdent.

## Transaction Trust Monitoring
- [How It Works?](https://developers.shuftipro.com/docs/transaction_trust_screening/how_it_works.md): Shufti's Transaction Trust Monitoring solution is designed to automatically monitor and assess financial transactions for potential risks, including money laundering, fraud, and non-compliance with regulations.
- [Offsite Integration](https://developers.shuftipro.com/docs/transaction_trust_screening/offsite.md): In the offsite transaction monitoring process, Shufti's clients are responsible for collecting all relevant transaction data from the end user and submitting it to Shufti for analysis and verification.
- [Complete List of Datapoints](https://developers.shuftipro.com/docs/transaction_trust_screening/complete_list_of_datapoints.md): .theme-doc-markdown table {
- [Complete List of Attributes](https://developers.shuftipro.com/docs/transaction_trust_screening/complete_list_of_attributes.md): .theme-doc-markdown table {

## Travel Rule
- [Introduction](https://developers.shuftipro.com/docs/travel_rule/introduction.md): The Travel Rule is a regulatory requirement that mandates financial institutions and VASPs to collect, verify, and transmit information about the originator and beneficiary of cryptocurrency transactions above certain thresholds.
- [How It Works?](https://developers.shuftipro.com/docs/travel_rule/how_it_works.md): The Shufti Travel Rule solution follows a straightforward flow to ensure compliance with global regulatory requirements for crypto asset transfers.
- [Transactions](https://developers.shuftipro.com/docs/travel_rule/transactions.md): The Transactions API allows you to create, read, update, and delete Travel Rule transactions for crypto asset transfers.
- [VASP Directory](https://developers.shuftipro.com/docs/travel_rule/vasp_directory.md): The VASP Directory API provides access to an extensive directory of Virtual Asset Service Providers.
- [Wallets](https://developers.shuftipro.com/docs/travel_rule/wallets.md): The Wallets API allows you to manage wallet records within the Travel Rule system.
- [Wallet Verification](https://developers.shuftipro.com/docs/travel_rule/wallet_verification.md): The Wallet Verification API enables you to verify ownership of wallet addresses through multiple verification flows.
- [Reference Data](https://developers.shuftipro.com/docs/travel_rule/reference_data.md): Reference data endpoints return the supported value lists used elsewhere in the Travel Rule API — the blockchain names accepted on wallets/transactions and the country names used for VASP Directory filtering.
- [Responses](https://developers.shuftipro.com/docs/travel_rule/responses.md): All Shufti Travel Rule API responses follow a consistent JSON structure.
- [Declined Reasons](https://developers.shuftipro.com/docs/travel_rule/declined_reasons.md): When a Travel Rule transaction is declined by the receiving VASP, the status is set to DECLINED and a statusreasoning field is populated explaining the reason.
- [Best Practices](https://developers.shuftipro.com/docs/travel_rule/best_practices.md)

## Business Identification & Risk
- [How it Works?](https://developers.shuftipro.com/docs/business_identification_risk/know_your_business/enhanced_kyb/how_it_works.md): Enhanced KYB delivers in-depth business verification by querying official registries, trusted data sources, and proprietary databases in real time.
- [Onsite Integration](https://developers.shuftipro.com/docs/business_identification_risk/know_your_business/enhanced_kyb/onsite.md): In onsite verification, Shufti will directly interact with the end user to collect the required information for verification purposes.
- [Offsite Integration](https://developers.shuftipro.com/docs/business_identification_risk/know_your_business/enhanced_kyb/offsite.md): In the offsite verification process, Shufti's merchants are solely responsible for gathering all necessary information from the end user and then submitting it to Shufti for verification.
- [Response](https://developers.shuftipro.com/docs/business_identification_risk/know_your_business/enhanced_kyb/responses.md): Shufti’s Enhanced KYB API response parameters return company information such as registration details, financial metrics, filings, UBOs, and contacts.
- [Declined Reasons](https://developers.shuftipro.com/docs/business_identification_risk/know_your_business/enhanced_kyb/declined_reasons.md): When a verification request involving Enhanced KYB is declined, the following reasons are presented to the end user or client.
- [How it Works?](https://developers.shuftipro.com/docs/business_identification_risk/know_your_business/standard_kyb/how_it_works.md): This documentation is for the Standard Version, encompassing foundational features.
- [Offsite Integration](https://developers.shuftipro.com/docs/business_identification_risk/know_your_business/standard_kyb/offsite.md): In the offsite verification process, Shufti's clients are solely responsible for gathering all necessary information from the end user and then submitting it to Shufti for verification.
- [Response](https://developers.shuftipro.com/docs/business_identification_risk/know_your_business/standard_kyb/responses.md): Shufti’s Standard KYB API response parameters define the types of data returned, like registration details, financial metrics, filings, and contacts.
- [Overview](https://developers.shuftipro.com/docs/business_identification_risk/business_aml_screening/overview.md): Shufti's Business AML Screening checks a business against global sanctions, warnings and regulatory enforcement lists, fitness and probity, adverse media, special interest entity (SIE), and insolvency records.
- [How It Works?](https://developers.shuftipro.com/docs/business_identification_risk/business_aml_screening/how_it_works.md): Business AML Screening evaluates a business, and related subjects such as vessels and aircraft, against Shufti's connected watchlists and returns every record that resembles them, each with a match score you can act on.
- [Onsite Integration](https://developers.shuftipro.com/docs/business_identification_risk/business_aml_screening/onsite.md): In On-site verification, Shufti directly interacts with the end-user, managing data collection to facilitate AML checks.
- [Offsite Integration](https://developers.shuftipro.com/docs/business_identification_risk/business_aml_screening/offsite.md): In the offsite verification process Shufti’s merchants are solely responsible for managing data collection and providing it to Shufti to facilitate AML checks.
- [Match Results](https://developers.shuftipro.com/docs/business_identification_risk/business_aml_screening/match_results.md): For every record returned, Shufti reports the degree of correlation between the screened business's details and the watchlist entry, so you can see exactly why a record was surfaced.
- [Responses](https://developers.shuftipro.com/docs/business_identification_risk/business_aml_screening/responses.md): "reference": "",
- [Declined Reasons](https://developers.shuftipro.com/docs/business_identification_risk/business_aml_screening/declined_reasons.md): When a verification request involving Business AML Screening is declined, the following reasons are presented to the end user or client.
- [How It Works?](https://developers.shuftipro.com/docs/business_identification_risk/investor_verification/how_it_works.md): Shufti aids clients in collecting vital investor information essential for onboarding and verification providing customised forms tailored to their unique business needs.
- [Onsite Integration](https://developers.shuftipro.com/docs/business_identification_risk/investor_verification/onsite.md): In onsite verification, Shufti will directly interact with the end user to collect the required documents for verification purposes.

## Electronic Signature
- [How It Works?](https://developers.shuftipro.com/docs/electronic_signature/how_it_works.md): The Shufti e-Signature service allows you to instantly send documents to multiple recipients simultaneously, enabling them to sign from anywhere using their devices.
- [Onsite Integration](https://developers.shuftipro.com/docs/electronic_signature/onsite.md): With On-site verification, Shufti directly interacts with the end-user, managing data collection to facilitate document signing.

## Qualified Electronic Signature
- [How It Works?](https://developers.shuftipro.com/docs/business_identification_risk/qualified_electronic_signature/how_it_works.md): Shufti's Qualified Electronic Signature (QES) service enables businesses to collect legally binding electronic signatures from end users in compliance with the eIDAS Regulation (EU) 910/2014.
- [Onsite Integration](https://developers.shuftipro.com/docs/business_identification_risk/qualified_electronic_signature/onsite.md): The Onsite integration mode is the primary integration path for QES.

## Verification Endpoints
- [Requests](https://developers.shuftipro.com/docs/verification_endpoints/requests.md): To initiate a verification request, you must access the base URL https://api.shuftipro.com/ endpoint and provide the desired services within the verification request object.
- [Callback Logs](https://developers.shuftipro.com/docs/verification_endpoints/callback_logs.md): Shufti's Callback Logs feature provides Merchants with a complete delivery history of every callback sent from Shufti to their configured callback URL.
- [Responses](https://developers.shuftipro.com/docs/verification_endpoints/responses.md): The Shufti Verification API will send you two types of responses if a request for verification is made.

## Coverage
- [Countries](https://developers.shuftipro.com/docs/coverage/countries.md): Shufti provides global identity verification with a vast presence in 240+ countries.
- [Documents](https://developers.shuftipro.com/docs/coverage/documents.md): Shufti's KYC services offer extensive global coverage, accommodating a wide range of major documents for user verification.
- [Supported Languages](https://developers.shuftipro.com/docs/coverage/languages.md): Shufti offers multilingual support across various features to enhance user experience and ensure accurate verification processes.

## System Insights & Request Limits
- [User Agent & Geolocation](https://developers.shuftipro.com/docs/kyc/system_insights_and_request_limits/user_agent_and_geolocation.md): Upon the acceptance or decline of a verification request, the system returns an info object containing two additional sub-objects: Agent and Geolocation which provides essential details about user's device and geolocation.
- [Supported Browsers and Devices](https://developers.shuftipro.com/docs/kyc/system_insights_and_request_limits/supported_browsers_and_devices.md): For seamless verification experiences, our verification iframe is designed to be compatible with a range of modern web browsers.
- [Rate Limiting & Webhook IPs](https://developers.shuftipro.com/docs/kyc/system_insights_and_request_limits/rate_limiting_and_webhook_ips.md): Shufti imposes request limits for both Production and Trial accounts to ensure smooth operation and fair usage of the service.

## Backoffice
- [Account Settings](https://developers.shuftipro.com/docs/backoffice/account_settings.md): In the Account Settings section, Shufti offers a comprehensive suite of features to fortify your experience.
- [Role-Based Access Control (RBAC)](https://developers.shuftipro.com/docs/backoffice/features/rbac.md): The Role-Based Access Control (RBAC) feature allows administrators to manage user roles and permissions effectively within the back office.
- [Customer ID](https://developers.shuftipro.com/docs/backoffice/features/customer_id.md): The Customer ID feature enables merchants to maintain a consistent reference for individual end users across multiple verification requests.
- [Callback Logs](https://developers.shuftipro.com/docs/backoffice/features/callback_logs.md): Shufti's Callback Logs feature provides Merchants with a complete delivery history of every callback sent from Shufti to their configured callback URL.
- [Business Keys](https://developers.shuftipro.com/docs/backoffice/features/business_keys.md): Business Keys allow Merchants to group customers and verifications by their source, brand, business line, or any other dimension that matters to operations.
- [Blocklist Customer](https://developers.shuftipro.com/docs/backoffice/features/blacklist_customer.md): Introducing our latest enhancement in fraud prevention, the new Blocklisting feature empowers merchants to proactively safeguard their operations.
- [Risk Assessment](https://developers.shuftipro.com/docs/backoffice/features/default_risk_assessment.md): In the verification industry, most providers offer a simple accept or decline decision without delving into the underlying risk factors.
- [Document Type & Country Settings](https://developers.shuftipro.com/docs/backoffice/features/document_type_and_country_settings.md): Introducing the Document Type and Country Settings feature, empowering merchants to customize country and document coverage to align with their specific business needs directly from the BackOffice.
- [Multi-Tenancy](https://developers.shuftipro.com/docs/backoffice/features/multi_tenancy.md): Multi-Tenancy feature is designed to enhance flexibility and efficiency, allowing merchants to manage multiple brands as child accounts with admin or read-only access from a single master account.
- [Vendor Comparison](https://developers.shuftipro.com/docs/backoffice/features/vendor_comparison.md): The Vendors Comparison feature empowers merchants to thoroughly assess and compare the performance of different verification providers with Shufti.
- [Document Verification Settings](https://developers.shuftipro.com/docs/backoffice/features/document_verification_settings.md): Shufti allows their clients to customise which document to accept or decline based on their business requirements directly from back office.
- [Verification Report Warnings](https://developers.shuftipro.com/docs/backoffice/features/allow_warnings.md): Shufti uses advanced image analysis techniques to detect inconsistencies, tampering, and suspicious activities during the verification process.
- [Device Risk Signals](https://developers.shuftipro.com/docs/backoffice/features/device_risk_signals.md): Shufti leverages advanced analysis to detect suspicious device and network behaviors, anomalies, and potential fraud during the verification process.
- [IDV Modes](https://developers.shuftipro.com/docs/backoffice/features/idv_modes.md): IDV modes are designed to provide merchants with flexibility in choosing the most suitable verification approach based on their specific needs.
- [Shufti AI](https://developers.shuftipro.com/docs/backoffice/features/shufti_ai.md): Shufti AI is an AI-powered assistant built into the Shufti Backoffice that gives clients a single, conversational way to reach both their own verification data and the full depth of Shufti's product and compliance knowledge.
- [Journey Builder](https://developers.shuftipro.com/docs/backoffice/plug_and_play_integration/journey_builder.md): Shufti provides a user-friendly, no-code solution for creating custom verification journeys for clients.
- [iFrame Design](https://developers.shuftipro.com/docs/backoffice/plug_and_play_integration/iframe_branding.md): Customise the verification user interface to align with your organisation's branding guidelines.

## MCP Server
- [What Is Shufti MCP?](https://developers.shuftipro.com/docs/mcp/intro.md): Shufti MCP is a Model Context Protocol server that connects the AI agents your team already uses, such as Claude and ChatGPT, directly to your Shufti account.
- [Connect Your Agent](https://developers.shuftipro.com/docs/mcp/connecting.md): Pick your client below and follow its steps to connect.
- [Available Tools](https://developers.shuftipro.com/docs/mcp/tools.md): All 26 tools below are available as soon as you connect with your Shufti Client ID and Secret Key.
- [Troubleshooting & Fixes](https://developers.shuftipro.com/docs/mcp/troubleshooting.md): Most connection issues come down to one thing: reconnect the connector and re-enter your Client ID and Secret Key.

## Mobile SDK
- [Introduction](https://developers.shuftipro.com/docs/mobile/intro.md): Benefits of using Shufti mobile SDK:
- [Android SDK](https://developers.shuftipro.com/docs/mobile/platforms/android-sdk.md): AndroidX Support
- [iOS SDK](https://developers.shuftipro.com/docs/mobile/platforms/ios-sdk.md): It’s always recommended to use the updated version and run on physical device to get real results.
- [Flutter Plugin](https://developers.shuftipro.com/docs/mobile/platforms/flutter-sdk.md): It’s always recommended to use the updated version
- [React Package](https://developers.shuftipro.com/docs/mobile/platforms/react-sdk.md): It’s always recommended to use the updated version
- [Cordova](https://developers.shuftipro.com/docs/mobile/platforms/cordova-sdk.md): It’s always recommended to use the updated version
- [Auth Object Parameters](https://developers.shuftipro.com/docs/mobile/parameters/auth-parameters.md): In this object, we add authorization key in verification request.
- [Config Object Parameters](https://developers.shuftipro.com/docs/mobile/parameters/config-parameters.md): In this object, we add an extra configuration of verification that the user wants.
- [Common Parameters ](https://developers.shuftipro.com/docs/mobile/parameters/requestObject/common-parameters.md): The parameters mentioned below are applicable for both onsite and offsite verifications in KYC service.
- [Face Service ](https://developers.shuftipro.com/docs/mobile/parameters/requestObject/face-object-parameters.md): "proof" : "",
- [Document and Document Two Service ](https://developers.shuftipro.com/docs/mobile/parameters/requestObject/doc-object-parameters.md): Shufti provides document verification through various types of documents.
- [Address Service ](https://developers.shuftipro.com/docs/mobile/parameters/requestObject/address-object-parameters.md): For address verification, a valid identity document is required with the same address printed on it as the one claimed by the end-user.
- [Consent Service ](https://developers.shuftipro.com/docs/mobile/parameters/requestObject/consnet-object-parameters.md): Customised documents/notes can also be verified by Shufti.
- [Phone Service ](https://developers.shuftipro.com/docs/mobile/parameters/requestObject/phone-service-parameters.md): Verify the phone number of end-users by sending a random code to their number from Shufti.
- [Background Check ](https://developers.shuftipro.com/docs/mobile/parameters/requestObject/background_service-object-parameters.md): It is a verification process that will require you to send us the full Name of end-user in addition to date of birth.
- [Responses](https://developers.shuftipro.com/docs/mobile/parameters/responses.md): The Shufti SDK will send a callback response to your application when the user completes the verification process and the control shifts to your user application.
- [NFC Supported Countries](https://developers.shuftipro.com/docs/mobile/parameters/nfc-supported-countries.md): Experience seamless identity verification with Shufti NFC, a cutting-edge solution designed to enhance security and user experience.
- [Android SDK Changelog](https://developers.shuftipro.com/docs/mobile/changelog/android-changelog.md): Released on Jun 2, 2026
- [iOS SDK Changelog](https://developers.shuftipro.com/docs/mobile/changelog/ios-changelog.md): Released on May 26, 2026
- [Flutter SDK Changelog](https://developers.shuftipro.com/docs/mobile/changelog/flutter-changelog.md): Released on May 25, 2026
- [React SDK Changelog ](https://developers.shuftipro.com/docs/mobile/changelog/react-changelog.md): Released on June 02, 2026

## Marketplaces
- [Introduction](https://developers.shuftipro.com/docs/marketplaces/intro.md): Deploy Shufti directly from your cloud marketplace for seamless on-premises integration.
- [AWS Marketplace Integration](https://developers.shuftipro.com/docs/marketplaces/aws/introduction.md): Integrates Shufti's services through AWS to deliver fast, secure, and easily accessible cloud-based identity verification.
- [User Guide](https://developers.shuftipro.com/docs/marketplaces/aws/user-guide.md): Deployment & Usage Guide
- [API Documentation](https://developers.shuftipro.com/docs/marketplaces/aws/endpoints.md): /api/verification-request

## Optional
- [Full documentation (single file)](https://developers.shuftipro.com/llms-full.txt): Every indexed page's clean Markdown concatenated into one file for bulk ingestion.