# Revision History

| Date         | Description                                                                                                                                                                                                                                                                                                                                                                                                           |
|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 06 Oct 2026  | **Standard KYB has been deprecated.** Going forward, [Enhanced KYB](/docs/business_identification_risk/know_your_business/enhanced_kyb/how_it_works) is the default KYB service and should be used for all business verification requests. Send `kyb.advanced_search` as `1` with `country_names` and either `company_name` or `company_registration_number`, as shown on the [Offsite](/docs/business_identification_risk/know_your_business/enhanced_kyb/offsite) page. The Standard KYB pages and its jurisdiction-code list on [supported countries](/docs/coverage/countries?service=kyb#kyb) have been removed. |
| 17 Sep 2026  | Expanded the **Indonesia** vehicle registration provider to thirteen provinces on [e-IDV Pro](/docs/user_identification_authentication/eidv_pro/how_it_works), adding **Kalimantan Timur**, **Kalimantan Selatan**, **Sumatera Selatan**, **DKI Jakarta** and **Riau**. Name the province with `type` (`ID-KALTIM-SAMSAT`, `ID-KALSEL-SAMSAT`, `ID-SUMSEL-SAMSAT`, `ID-JAKARTA-SAMSAT`, `ID-RIAU-SAMSAT`). Kalimantan Selatan, Sumatera Selatan and Riau also require `chassis_number`, and echo only its last five digits back as `chassis_last_five`. What each registry returns continues to vary: Kalimantan Timur reports an online payment code, Kalimantan Selatan omits any total payable, Sumatera Selatan reports no tax due date, DKI Jakarta returns a body type and registration status but no plate suffix, and Riau nests a full `previous_assessment` breakdown alongside the current one. Sample payloads for every province are on the [Offsite](/docs/user_identification_authentication/eidv_pro/offsite#request-payloads-for-offsite-verifications) and [Responses](/docs/user_identification_authentication/eidv_pro/responses) pages, and the sources are listed under [supported countries](/docs/coverage/countries?service=eidv-pro). |
| 15 Sep 2026  | Added new **passive** sources for the **Philippines** and **Mexico** on [e-IDV Pro](/docs/user_identification_authentication/eidv_pro/how_it_works). The Philippines gains a residential lookup, which takes the holder's name and date of birth — with the address fields optional and returned as a match — and a vehicle registration lookup against the LTO plate release tracker, keyed on the number plate alone and returning an `lto_nru_office`, the dealer it was released to and the release date in a `vehicle_details` section. Mexico gains two: a CURP lookup, which identifies the holder from the CURP alone with no name or date of birth required, and a national ID lookup keyed on the CURP alongside the name and date of birth, with `middle_name` and `gender` optional. Name the source with `data_source` (`philippines-residential`, `phvi`, `mexico-national-id`); the existing lookups are `phid` and `mxid`. Sample payloads for each are on the [Offsite](/docs/user_identification_authentication/eidv_pro/offsite#request-payloads-for-offsite-verifications) and [Responses](/docs/user_identification_authentication/eidv_pro/responses) pages via the provider selector, and the sources are listed under [supported countries](/docs/coverage/countries?service=eidv-pro). |
| 14 Sep 2026  | The United States driving licence **not found** decline now returns **SPDR370** instead of SPDR398. SPDR370 is the shared driving-licence reason already returned by the UAE and Bangladesh licence lookups, so one code now carries one message across every driving-licence source. **SPDR398 is no longer sent for driving licences** - merchants matching on it for a licence must match on SPDR370 instead. SPDR398 itself remains in use for vehicle-registration expiry. The reason text changes with the code: SPDR370 reads *"Driving License is not found in the database."* The expiry decline returns **SPDR370** as well: one reason per driving-licence role, matching the UAE and Bangladesh lookups. An expired licence is still distinguishable from a missing one, because it returns its `license_details` while a missing one returns none. **SPDR397 and SPDR399 are not sent by any source** and must not be matched on. See the [reason codes](/docs/user_identification_authentication/eidv_pro/declined_reasons). |
| 14 Sep 2026  | Expanded the **Indonesia** vehicle registration provider with five further provincial sources on [e-IDV Pro](/docs/user_identification_authentication/eidv_pro/how_it_works) — **Bali**, **Sulawesi Tengah**, **Jawa Timur**, **Bengkulu** and **Jambi** — bringing it to eight. Name the province with `type` (`ID-BALI-SAMSAT`, `ID-SULTENG-SAMSAT`, `ID-JATIM-SAMSAT`, `ID-BENGKULU-SAMSAT`, `ID-JAMBI-SAMSAT`). Each registry is queried differently: Bali requires `chassis_number` and `plate_colour`, Sulawesi Tengah and Jawa Timur also require `chassis_number`, while Bengkulu and Jambi take the plate alone. The fields returned vary by province — Jambi reports registration and status without any tax amounts, Bengkulu adds a tax cycle and a total excluding renewal fees, and Jawa Timur reports a progressive vehicle tax. Sample payloads for every province are on the [Offsite](/docs/user_identification_authentication/eidv_pro/offsite#request-payloads-for-offsite-verifications) and [Responses](/docs/user_identification_authentication/eidv_pro/responses) pages, and the sources are listed under [supported countries](/docs/coverage/countries?service=eidv-pro). |
| 14 Sep 2026  | Added a **Ghana** proof of address source to [e-IDV Pro](/docs/user_identification_authentication/eidv_pro/how_it_works). The new **passive** source resolves a GhanaPost GPS digital address and returns the registered address in an `address_details` section; no identity fields are required. Name it with `data_source` (`epoa_gh_cr_p`) — it sits alongside the existing Ghana identity lookups, which continue to be selected with `type` (`GH-SSNIT-VERIFICATION`, `GH-DRIVER-LICENSE-VERIFICATION`, `GH-OLD-VOTER-ID`, `GH-NEW-VOTER-ID`). Sample payloads are on the [Offsite](/docs/user_identification_authentication/eidv_pro/offsite#request-payloads-for-offsite-verifications) and [Responses](/docs/user_identification_authentication/eidv_pro/responses) pages via the provider selector, and the source is listed under [supported countries](/docs/coverage/countries?service=eidv-pro). |
| 11 Sep 2026  | Added a **Hong Kong** vehicle registration source to [e-IDV Pro](/docs/user_identification_authentication/eidv_pro/how_it_works). The new **passive** source checks a number plate against the GovHK Vehicle Licence enquiry platform and reports whether the registration is valid, returning a `vehicle_details` section in place of personal details. Name it with `data_source` (`hkvi`); the existing Hong Kong name-and-address lookup is `hkid`, and `data_source` may be omitted when only one source is enabled on the account. Sample payloads for both are on the [Offsite](/docs/user_identification_authentication/eidv_pro/offsite#request-payloads-for-offsite-verifications) and [Responses](/docs/user_identification_authentication/eidv_pro/responses) pages via the provider selector, and the source is listed under [supported countries](/docs/coverage/countries?service=eidv-pro). |
| 11 Sep 2026  | Expanded [e-IDV Pro](/docs/user_identification_authentication/eidv_pro/how_it_works) coverage for the **United Arab Emirates** and **Bangladesh** with two newly integrated **passive** driving licence sources. The UAE adds a Roads & Transport Authority (RTA) lookup — keyed on the licence number and its issue date, returning nationality alongside the permitted vehicle class, licence status and expiry in a `driving_license_details` section. Bangladesh adds a BRTA lookup keyed on the licence number and issue date, returning the holder's name with licence type, vehicle class, validity window and issuing authority. Name the source with `data_source` (`aeid_rta` / `bdid_dl`), and for the UAE name the certificate with `type` (`RTA-DL`). The UAE identity lookup response was also corrected to document the full `personal_details` payload it returns. An expired licence declines with the new **SPDR397** [reason code](/docs/user_identification_authentication/eidv_pro/declined_reasons). See the updated [request payloads](/docs/user_identification_authentication/eidv_pro/offsite#request-payloads-for-offsite-verifications), [responses](/docs/user_identification_authentication/eidv_pro/responses) and [supported countries](/docs/coverage/countries?service=eidv-pro). |
| 04 Sep 2026  | Added a third **passive** driving licence registry for the United States: **Louisiana** (`US-LA-OMV`), keyed on the nine-digit driver license number plus the **last 4 digits of the holder's Social Security Number**. Unlike the Washington and Florida sources, Louisiana therefore requires an input that appears on no document, so it must be supplied in the request and cannot be resolved from a document's OCR — it is unavailable to the `use_ocr_data` and `verify_driving_license` flows. Send it as `ekyc.ssn_last4` (exactly 4 digits; a full SSN is rejected rather than truncated). Responses use the same `license_details` section as the other two states, and declines use the existing **SPDR370** [reason code](/docs/user_identification_authentication/eidv_pro/declined_reasons). See the updated [request payloads](/docs/user_identification_authentication/eidv_pro/offsite#request-payloads-for-offsite-verifications), [responses](/docs/user_identification_authentication/eidv_pro/responses) and [supported countries](/docs/coverage/countries?service=eidv-pro). |
| 01 Sep 2026  | Expanded [e-IDV Pro](/docs/user_identification_authentication/eidv_pro/how_it_works) coverage for Pakistan with two newly integrated **passive** sources. **CNIC Lookup** takes the CNIC and date of birth and returns the holder's identity together with their driving licence card — licence number, type, allowed vehicles, issue date, validity window, status and issuing district. **ePOA** additionally takes the driving licence number and returns the holder's identity with their registered address. Name the source with `type` (`PK-CNIC-LOOKUP` / `PK-EPOA`) when both are enabled on the account; with only one enabled it is optional. The CNIC is accepted bare or dashed. See the updated [request payloads](/docs/user_identification_authentication/eidv_pro/offsite#request-payloads-for-offsite-verifications), [responses](/docs/user_identification_authentication/eidv_pro/responses) and [supported countries](/docs/coverage/countries?service=eidv-pro). |
| 01 Sep 2026  | Expanded [e-IDV Pro](/docs/user_identification_authentication/eidv_pro/how_it_works) coverage for the United States with a **passive** driving licence lookup over two state licensing registries — Washington, keyed on the driver license number plus the holder's date of birth, and Florida, keyed on the driver license number alone. The merchant names the state per request via `type` (`US-WA-DOL` / `US-FL-DHSMV`); there is no default, because the two states run independent registries. The licence sources return a `license_details` section in place of personal details, and decline with the **SPDR370** [reason code](/docs/user_identification_authentication/eidv_pro/declined_reasons) when the licence is not found or is not a valid driving credential. Note that these sources verify a **credential**, not a person: neither registry returns a name, an address or a date of birth. See the updated [request payloads](/docs/user_identification_authentication/eidv_pro/offsite#request-payloads-for-offsite-verifications), [responses](/docs/user_identification_authentication/eidv_pro/responses) and [supported countries](/docs/coverage/countries?service=eidv-pro). |
| 31 Aug 2026  | Expanded [e-IDV Pro](/docs/user_identification_authentication/eidv_pro/how_it_works) coverage for Indonesia and Vietnam with four newly integrated **passive** data sources. Indonesia adds a resident identity card lookup (full name, date of birth, 16-digit resident ID number and gender, with the registered address returned where available) and a vehicle registration lookup covering three provinces — DI Yogyakarta, Banten and Sulawesi Utara — keyed on the number plate. Vietnam adds a vehicle inspection certificate lookup over two sources: one keyed on the plate plus the chassis (VIN) number, the other on the plate plus the inspection stamp / certificate number. The vehicle sources return a `vehicle_details` section in place of personal details, and decline with the new **SPDR396** [reason code](/docs/user_identification_authentication/eidv_pro/declined_reasons) when the registration is not found. See the updated [request payloads](/docs/user_identification_authentication/eidv_pro/offsite#request-payloads-for-offsite-verifications), [responses](/docs/user_identification_authentication/eidv_pro/responses) and [supported countries](/docs/coverage/countries?service=eidv-pro). |
| 19 Aug 2026  | Introduced the `pdf_mode` parameter for the Hash Submission approach of [Qualified Electronic Signature (QES)](/docs/business_identification_risk/qualified_electronic_signature/onsite), which declares that each digest submitted in `qes.hashes` is the ByteRange digest of a PDF. The CMS signature is then built to the PAdES profile — the signed attributes are exactly `content-type`, `message-digest` and `signing-certificate-v2`, with `signing-time` excluded, because a PDF already records the signing time natively in the signature dictionary's `/M` entry and a duplicate inside the CMS causes strict validators to report the signature as the older PAdES-BES rather than a PAdES-BASELINE profile. Sent with `qes.proofs` (Document Upload) the parameter is ignored, and omitting it retains `signing-time` exactly as before for CAdES signatures over non-PDF content. |
| 10 Aug 2026  | Documented the `validate_document` parameter for Document Based [Enhanced KYB](/docs/business_identification_risk/know_your_business/enhanced_kyb/how_it_works), which uses the data extracted from the submitted business document to look up and validate the business against official registry data, reporting the outcome as part of the KYB result. Document validation currently resolves one document per request, so exactly one label must be provided — `additional_proof_labels` for [Onsite](/docs/business_identification_risk/know_your_business/enhanced_kyb/onsite) and `proofs` for [Offsite](/docs/business_identification_risk/know_your_business/enhanced_kyb/offsite). Sending more than one is rejected with a validation error. |
| 03 Aug 2026  | Expanded [e-IDV Pro](/docs/user_identification_authentication/eidv_pro/how_it_works) coverage with 41 newly integrated services — 22 **active** eIDs and 19 **passive** data-source lookups — across 29 countries, with Bolivia, Côte d'Ivoire, South Korea, Latvia, and Serbia joining the [supported countries](/docs/coverage/countries?service=eidv-pro) for the first time. Sample request payloads and responses for every new service are available on the [Offsite](/docs/user_identification_authentication/eidv_pro/offsite) and [Responses](/docs/user_identification_authentication/eidv_pro/responses) pages via the new provider selector. |
| 30 Jul 2026  | Introduced the `id_number` and `proof_number` parameters in [e-IDV Pro Offsite](/docs/user_identification_authentication/eidv_pro/offsite) to support Saudi Arabia's National Address Verification Service (Saudi Post). Both are 10-digit numeric values submitted together to verify and retrieve the applicant's registered address on file. Saudi Arabia (SA) is now listed under [Passive e-IDV supported countries](/docs/coverage/countries?service=eidv-pro). |
| 27 Jul 2026  | Introduced the `ocr_autofill` parameter in [e-IDV Pro Onsite](/docs/user_identification_authentication/eidv_pro/onsite), which pre-fills the eIDV form with the data extracted from the document submitted in [Document Verification](/docs/user_identification_authentication/document_verification/onsite). The pre-filled values stay editable so the end user can review and correct them before submitting. The parameter applies to onsite passive eIDV requests that also include the Document Verification service, and enabling it enforces `show_ocr_form` as **1** and `allow_fallback` as **0**. |
| 24 Jul 2026  | Removed several non-business-related documents from [Document Based KYB](/docs/coverage/documents#document-based-kyb) coverage. The following are no longer supported: Official Identification (Mexico), Apostille Authentication Number (Montana, United States), Company Verification (Pakistan), Verify Identity (Philippines), and Certificate of Public Liability Insurance (United Kingdom). Guatemala is no longer supported for Document Based KYB. |
| 03 Jul 2026  | The KYB service now supports 45 additional [countries](/docs/coverage/countries?service=kyb#kyb) for business verification. This expands global reach for company registration and jurisdiction checks. |
| 30 Jun 2026  | Introduced `enable_choice_document_eidv` and `signal_for_choice` parameters in [e-IDV Pro Onsite](/docs/user_identification_authentication/eidv_pro/onsite) and [Document Verification Onsite](/docs/user_identification_authentication/document_verification/onsite), allowing the end user to choose between Document Verification and eIDV service when both services are selected. |
| 24 June 2026 | Added [Travel Rule](/docs/travel_rule/introduction) documentation in the developer guide, covering the FATF Travel Rule compliance flow for VASP-to-VASP crypto transfers, including wallet verification, VASP directory, transactions, responses, and declined reasons. |
| 24 June 2026 | Added [Business Keys](/docs/backoffice/features/business_keys) feature documentation in the back office, explaining how to group customers and verifications by source, brand, or business line, with per-key configuration and duplicate account detection. |
| 02 June 2026 | Added [Qualified Electronic Signature (QES)](/docs/business_identification_risk/qualified_electronic_signature/how_it_works) documentation in the developer guide, explaining how Shufti orchestrates eIDAS-compliant qualified electronic signatures, including identity proofing, qualified certificate issuance, and signature collection. |
| 12 May 2026  | Added [Fraud Hub solution](/docs/user_identification_authentication/fraud_hub) in the Backoffice, an advanced risk intelligence module for fraud detection. It analyzes device behavior, network activity, and document integrity to generate real-time risk scores, helping merchants assess user risk and adjust onboarding strategies. |
| 12 May 2026  | Enhanced [Individual AML Screening](/docs/user_identification_authentication/user_aml_screening/how_it_works) and [Business AML Screening](/docs/business_identification_risk/business_aml_screening/how_it_works) documentation with new sections covering Search by Profile, AML Match Score engine, Context Parameter, Face Match, Custom Risk Scoring Engine, AI Compliance Agent, and Case Management. Introduced two new parameters — `unique_id` and `context` — for Individual AML [Onsite](/docs/user_identification_authentication/user_aml_screening/onsite) and [Offsite](/docs/user_identification_authentication/user_aml_screening/offsite) integrations, and `unique_id` and `context` for Business AML [Onsite](/docs/business_identification_risk/business_aml_screening/onsite) and [Offsite](/docs/business_identification_risk/business_aml_screening/offsite) integrations. Added [AML Supported Languages](/docs/coverage/languages#aml-supported-languages) page listing all 80 supported languages. |
| 23 Apr 2026 | Added Crypto Wallet Screening documentation, covering the end-to-end screening flow against Sanctions, Warnings, and Adverse Media databases. Includes Offsite integration, Declined Reasons, and Responses. For more details, refer to [Crypto Wallet Screening](/docs/user_identification_authentication/crypto_wallet_screening/how_it_works.md). |
| 20 Apr 2026  | Added [Transaction Trust Monitoring](/docs/transaction_trust_screening/how_it_works) (Know Your Transaction) documentation in the developer guide, covering real-time transaction risk screening with Offsite integration and the complete list of datapoints and attributes. |
| 14 Apr 2026  | The eIDV onsite and offsite configurations have been updated across **active**, **passive**, and **biometric** enriched eIDs. Additionally, the [eIDV country coverage](https://developers.shuftipro.com/docs/coverage/countries?service=eidv-pro#e-idv-pro) has been expanded to include a wider range of supported eIDs. |
| 09 Apr 2026  | Introduced `ai_business_insights` parameter in [Enhanced KYB](../docs/business_identification_risk/know_your_business/enhanced_kyb/how_it_works.md), leveraging AI to extract business information. |
| 03 Apr 2026  | Introduced `skip_document_type_and_country_selection` parameter in [Document](../docs/user_identification_authentication/document_verification/onsite) and [Address](../docs/user_identification_authentication/address_verification_and_validation/standard_address_verification/verification_parameters) verification, enabling the KYC flow to bypass the country and document type selection screen for a more streamlined user experience. |
| 01 Mar 2026  | Introduced the `enhanced_address_extraction` parameter within [Enhanced Address Verification](../docs/user_identification_authentication/address_verification_and_validation/enhanced_address_verification/verification_parameters), leveraging AI to automatically extract and validate additional information. |
| 29 Jan 2026  | Added detail documentation for [1:1 Facial Authentication](/docs/user_identification_authentication/one_to_one_authentication/how_it_works.md) in the back office, enabling users to securely enroll and authenticate using facial biometrics for improved security. |
| 29 Jan 2026  | Introduced `customer_unique_id` parameter in [General Parameters](/docs/general_parameters.md) and added detailed [Customer ID feature documentation](/docs/backoffice/features/customer_id.md), including the new `/customer/details` endpoint for managing customer identifiers and linking verifications to consistent customer profiles. |
| 02 Jan 2026  | Detailed documentation has been added for the [Age Verification feature](/docs/user_identification_authentication/age_verification/how_it_works.md) in the back office, enabling the verification of a user's age through various services, including facial biometrics, document verification, and eIDV.  |
| 02 Jan 2026  | Added NFC-enabled countries to Shufti’s overall verification coverage  |
| 25 Dec 2025  | Introduced [Fast ID Verification](/docs/user_identification_authentication/fast_id.md), a streamlined identity verification process that allows users to verify their identity quickly and securely using advanced facial recognition and document scanning technologies. |
| 25 Dec 2025  | Added [Plug & Play Integration Section](/docs/backoffice/plug_and_play_integration/journey_builder.md) in the back office, providing users with easy-to-use tools and guides for integrating identity verification services into their applications without extensive coding. |
| 04 Dec 2025  | Documentation for [Enhanced KYB](/docs/business_identification_risk/know_your_business/enhanced_kyb/how_it_works.md) has been added to the developer guide, offering detailed information on how to perform thorough business background checks and verify corporate entities. |
| 04 Dec 2025  | Added [Business AML Screening Documentation](/docs/business_identification_risk/business_aml_screening/how_it_works.md) in the developer guide, providing guidance on how to conduct Anti-Money Laundering (AML) checks on businesses to ensure compliance with regulatory requirements. |
| 24 Oct 2025  | Detailed documentation for [Enhanced Address Verification](/docs/user_identification_authentication/address_verification_and_validation/enhanced_address_verification/how_it_works.md) is now available in the developer guide, providing comprehensive information on advanced address verification methods. |
| 13 Oct 2025  | [Consent Verification Documentation](/docs/user_identification_authentication/consent_verification/how_it_works.md) has been added to the developer guide, explaining how to verify user consent for data processing and other activities. |
| 13 Oct 2025  | Added [e-IDV Pro Documentation](/docs/user_identification_authentication/eidv_pro/how_it_works.md) in the developer guide, providing instructions on how to use electronic identity verification services for professional and high-security applications. |
| 03 Oct 2025  | Detailed documentation for **Standard KYB** is now available in the developer guide, offering basic information on business identification and risk assessment. |
| 18 Sept 2025 | Added [Investor Verification Documentation](/docs/business_identification_risk/investor_verification/how_it_works.md) in the developer guide, providing guidance on how to verify the identity and status of investors for financial and regulatory compliance. |
| 09 Sept 2025 | Added [Electronic Signature Documentation](/docs/electronic_signature/how_it_works.md) in the developer guide, explaining how to integrate electronic signature services for secure and legally binding document signing. |
| 22 Aug 2025  | Detailed documentation for [VideoIdent](/docs/user_identification_authentication/video_kyc/how_it_works.md) has been added to the developer guide, offering information on video-based identity verification methods. |
| 22 Aug 2025  | Added [Phone MFA Documentation](/docs/user_identification_authentication/phone_verification_and_validation/how_it_works.md) in the developer guide, providing instructions on how to implement multi-factor authentication using phone-based verification. |
| 22 Aug 2025  | Added [Email MFA Documentation](/docs/user_identification_authentication/email_verification_and_validation/how_it_works.md) in the developer guide, explaining how to implement multi-factor authentication using email-based verification. |
| 22 Aug 2025  | Detailed documentation for [User Risk Assessment](/docs/user_identification_authentication/user_risk_assessment/how_it_works.md) has been added to the developer guide, providing information on assessing and managing user risk. |
| 07 Aug 2025  | [Due Diligence Form Documentation](/docs/user_identification_authentication/due_diligence_form/how_it_works.md) is now available in the developer guide, explaining how to use due diligence forms for user information collection and verification. |
| 04 July 2025 | Documentation for [Standard Address Verification](/docs/user_identification_authentication/address_verification_and_validation/standard_address_verification/how_it_works.md) has been added to the developer guide, offering basic information on address verification methods. |
| 19 June 2025 | Added [User AML Screening Documentation](/docs/user_identification_authentication/user_aml_screening/how_it_works.md) in the developer guide, providing guidance on conducting Anti-Money Laundering (AML) checks on individual users. |
| 22 May 2025  | Detailed documentation for [Document Verification](/docs/user_identification_authentication/document_verification/how_it_works.md) is now available in the developer guide, offering information on verifying various types of identification documents. |
| 21 Apr 2025  | Added [Facial Biometrics Documentation](/docs/user_identification_authentication/facial_biometrics/how_it_works.md) in the developer guide, providing instructions on using facial recognition technology for identity verification. |
| 14 Mar 2025  | [General Parameters Documentation](/docs/general_parameters.md) has been added to the developer guide, explaining the common parameters used across Shufti identity verification services. |
| 14 Mar 2025  | Added [Verification Endpoints Documentation](/docs/verification_endpoints/requests.md) in the developer guide, providing information on the API endpoints used for identity verification requests and responses. |
| 03 Feb 2025  | [Getting Started Guide](/docs/get_started.md) is now available in the developer guide, offering an overview and initial steps for integrating Shufti identity verification services. |
| 03 Feb 2025  | Added [Verification Modes Documentation](/docs/verification_methods/onsite.md) in the developer guide, explaining the different modes available for identity verification, such as onsite and offsite. |
| 15 Jan 2025  | [Glossary of Terms](/docs/glossary.md) has been added to the developer guide, providing definitions for common terms used in identity verification and regulatory compliance. |
| 15 Jan 2025  | Added [Revision History Documentation](/docs/revision_history.md) in the developer guide, providing a record of changes and updates to the documentation over time. |