📌 Enhancements

1. OCR Labs Data Connect Serpro offers 2 API solutions “Consulta CPF” and “Datavalid” to check for Brazilian DL and Passport documents.
   1. The system identifies Brazilian CPF number from Brazilian DL dynamically and triggers Serpro data checks.
   2. If the customer scans a non-Brazilian ID, the Serpro data check will not be invoked.
   3. The "Document Only" flow, i.e., the Normal V2 flow for which the Liveness Check is turned off, will only invoke the Serpro Consulta CPF API and not the Serpro Datavalid API.
   4. If the Consulta CPF call returns an invalid CPF, the Datavalid API check is not invoked.
   5. Refer Serpro portal documentation here
   6. Refer Serpro API documentation here

📌 Enhancements

1. Resend SMS and Emails via API
   1. Clients can resend a verification link for an ID check in either "Initiated" or "In Progress" status via API. These links will be resent using the same delivery method that was originally used. For instance, if the initial delivery method was via SMS, the verification link will be resent via SMS, and the same applies for Email.
   2. See API documentation here.
   3. See how you resend SMS and Email via IDKit portal here.
2. Minor improvements and bug fixes.

📌 Enhancements

1. Minor improvements and bug fixes.

📌 Enhancements

1. OCR Labs PEP and Sanctions will now be powered by Acuris/ION. The DataZoo service will be deactivated soon.
   1. Users will experience minor changes while activating this service through the portal.
   2. There are no changes to the API response; it remains consistent with the previous version.
   3. Refer to the updated IDKit portal and API changes.
2. Other minor improvements and bug fixes.

📌 Enhancements

1. Email notification for completed transactions
   1. This enhancement ensures that select IDKit users are prompted about the status of completed transactions.
   2. As a client admin, you can enable or disable the setting to receive email notifications by navigating to Settings → Configurations. You can add multiple comma-separated email addresses that will receive notifications each time a transaction moves to the completed state.
   3. The notification email will include essential details such as the transaction ID, reference, verification status, and a transaction link with deep linking.
2. Configuration to increase the number of ID recaptures
   1. This aims to provide a smoother process for capturing ID images, reducing inconveniences during the verification process.
   2. Previously, if ID images had insufficient quality or cut-off edges, users were prompted to recapture once. Now, the system allows explicit configuration for multiple recapture attempts up to 5.
   3. As a client admin, if you wish to adjust the number of recapture attempts, please contact your IDKit representative or customer support.
3. Send transaction via Email, including QR code
   1. An IDKit user, in addition to SMS, can opt for email as a delivery method to send a transaction link both through the IDKit Portal and API service.
   2. Both 'Send Verification via portal' and 'API' will be toggled off and will require to be toggled on. To enable the email delivery method, head over to Settings → Configuration and enable the setting.
   3. The branded email will include a transaction link and a QR code. The QR code facilitates quick access for users accessing the link from a desktop or laptop.
   4. For limited customization of the email subject and language, please contact IDKit customer support.
4. Individual Sender IDs for Australian clients
   1. We have enabled the use of individual Sender IDs for our Australian clients again. For any queries related to setting up sender IDs, please reach out to IDKit customer support.
5. Removal of Intercom chat from the portal
   1. Intercom chat has been removed from all areas of the portal. For assistance with any blockers or issues, client users are encouraged to utilize the support functionality within the application.

📌 Flow Updates

1. Document Fraud Assessment (DFA) on Secondary Documents

   We have enhanced our VOI V2 flow by introducing the capability to enable Document Fraud Assessment (DFA) on secondary documents. This feature can be activated according to your verification policy's specific requirements. While we offer this option, we recommend careful consideration, as our "single ID verification process" already aligns with ARNECC guidelines. We advise its use only when necessary, as this may result in an increased flag rate.

2. Simple VOI
   1. To meet ARNECC compliance standards while providing a user-friendly experience, we offer the "Simple VOI" configuration. This configuration simplifies the verification process when turned on within the VOI V2 flow while adhering to ARNECC guidelines. Key details of this configuration include:
      1. Users only need to provide two ID documents, reducing user effort.
      2. Accepted Primary IDs: Passport, Driver's License, or ImmiCard.
      3. Accepted Secondary IDs: Any other Primary ID, Medicare card, Birth certificate, or Citizenship certificate. The Simple VOI configuration strikes a balance between regulatory compliance and a user-centric approach, ensuring a smooth and efficient verification journey.
   2. The Simple VOI flow balances regulatory adherence with a user-centric approach, ensuring a smooth and efficient verification journey.

💡 General Updates

1. Customisable Transaction Expiry Time for Resellers

   Resellers now have the ability to customize the transaction expiry time through the reseller configuration. This feature empowers resellers to tailor the verification process to their specific needs and requirements, offering flexibility and control.

📌 Flow Updates

1. Updated Re-capture ID Logic for Cut-off Documents
   1. Our OCR engine now intelligently evaluates whether a re-capture of the ID is needed if certain document parts are inadvertently cropped or cut off during the capture process. This enhancement will improve the accuracy of processing captured IDs.
2. Normal Flow - “Doc Only” Configuration
   1. We are introducing a new configuration option, available for IDKit Resellers and Super Admins, allowing clients to exclude Facematch and Liveness checks from the single ID verification flow Normal V2. This is particularly useful in cases where biometric comparison and Liveness aren’t required by the client, such as alcohol delivery.
   2. By default, this configuration is disabled and needs to be activated by a Reseller or IDKit Admin.

📌 VOI Updates

1. Configuration Option: Multi-Document Validation
   1. When enabled, if the 2nd, 3rd, or 4th documents can't be validated via OCR, the transaction will be flagged for review.
   2. As a client admin, you can enable this within Flow Settings to ensure the correctness of the secondary documents.
   3. This toggle is off by default, meaning transactions won't fail even if subsequent documents can't be validated.
2. Document Name Matching Enhancement
   1. When verifying multiple documents, the system will validate whether the names match all documents.
   2. If names differ, users will be prompted to provide additional documentation such as a name or marriage certificate change.
   3. Users can skip this step if it's not applicable or the name is different or unknown, and transactions will proceed accordingly.
   4. Exceptions include situations where documents can't be read (e.g., descent certificates), where the previous "Is your name the same across documents" screen will be displayed with an updated header copy.
3. Document Upload and Check Logic Improvement
   1. In the VOI V2 flow, customers verifying their IDs will receive clear feedback after uploading each document.
   2. The upload success status will be shown before progressing to the next document.
   3. If a document can't be recognized or requires additional information (e.g., back of card), users will be informed after uploading the document before proceeding to the next steps.

📊 New Graph

We added a new graph showing monthly transactions on client and partner accounts. Please refer to the Report Management page.