---
agentTools:
  projectIndex: https://docs.sumsub.com/llms.txt
---

# August 2025

In August, we aimed to make our products and their settings smarter and more accessible. The Sumsub SDKs are now easier to adjust and use. Travel Rule and Crypto Monitoring have expanded their integrations and improved the accuracy of monitoring capabilities, and the Dashboard can now flex with the enhanced UI, easier management, and richer detail.

More is coming soon!

[block:html]
{
  "html": "<div class=\"details-list\">\n    <details open>\n        <summary>August 4 -> August 8</summary>\n\n        <h2>SDK</h2>\n        <p><b>MobileSDK version update</b></p>\n        <p>Version 1.37 of the MobileSDK has been released. This update introduces support for the enhanced NFC reader and the Non-Doc Verification setting in the <b>Identity document</b> step.</p>\n        <p>Changelog:</p>\n        <ul>\n            <li><a href=\"/docs/changelog-ios\">iOS</a></li>\n            <li><a href=\"/docs/changelog-android\">Android</a></li>\n        </ul>\n\n        <p><b>New MobileSDK plugins</b></p>\n        <p>The MobileSDK plugins 1.36.1 have been delivered.</p>\n        <p>Changelog:</p>\n        <ul>\n            <li><a href=\"/docs/cordova-plugin-changelog\">Cordova</a></li>\n            <li><a href=\"/docs/flutter-plugin-changelog\">Flutter</a></li>\n        </ul>\n        <a href=\"/docs/about-mobile-sdk\">Integrate with MobileSDK -></a><br><br>\n        \n        <p><b>Custom instructions for PoA step in WebSDK 2.0</b></p>\n        <p>A new setting has been delivered for adding custom instructional text in a PoA step. The text appears at the bottom of the page and supports Markdown formatting.</p>\n        <p>Translation keys:</p>\n        <ul>\n            <li><code>steps.POA.docTypes.customCopyTips.allowed</code></li>\n            <li><code>steps.POA.docTypes.customCopyTips.notAllowed</code></li>\n        </ul>\n\n        <p><b>PoA hints for applicants in SDK</b></p>\n        <p>From now on, if the uploaded proof of address document does not show all the required information, we will ask applicants to upload the other side as well.</p>\n        <p>Important notes:</p>\n        <ul>\n            <li>This feature only applies to Proof of Address verification.</li>\n            <li>When enabled, it overrides the <b>Accept proof of address documents with multiple pages</b> setting in the PoA presets.</li>\n            <li>Currently, it is only supported in the WebSDK.</li>\n            <li>No extra configuration is needed.</li>\n        </ul>\n\n        <p><b>Redirect URL settings</b></p>\n        <p>We have split the external WebSDK links setting into two separate options to simplify the configuration:</p>\n        <ul>\n            <li><b>Post-verification redirect URL</b> field—A custom URL to which applicants are redirected after successful verification.</li>\n            <li>\n                <b>Use redirect URL for SDK link generation</b> checkbox—A setting that allows to replace the default domain in SDK links with the custom redirect URL. This applies to:\n                <ul>\n                    <li>SDK links sent via email.</li>\n                    <li>Links shared between KYC and KYB applicants.</li>\n                    <li>Links used to continue verification on mobile devices.</li>\n                </ul>\n            </li>\n        </ul>\n        <a href=\"/docs/websdk-settings\">Configure WebSDK -></a>\n\n        <h2>Travel Rule</h2>\n        <p><b>VASP attribution backup</b></p>\n        <p>We have added an ability to specify a VASP in a Travel Rule transaction after its creation.</p>\n        <p>If the transaction cannot be attributed to the VASP, your applicants can still specify whether it belongs to a specific VASP or unhosted wallet, via the new Travel Rule SDK flow.</p>\n        <p>Getting started:</p>\n        <ol>\n            <li>In the Dashboard, go to <b>Transactions and travel rule</b> and navigate to <b>Settings</b>.</li>\n            <li>Go to the <a href=\"https://cockpit.sumsub.com/checkus/kyt/settings/travelRule\">Travel Rule</a> page and select the <b>Activate TR SDK on transaction</b> checkbox.</li>\n        </ol>\n        <p>This enables the new Travel Rule flow, improving the accuracy of VASP attribution.</p>\n        <a href=\"/docs/travel-rule-quickstart-guide\">Get started with the Sumsub Travel Rule -></a>\n\n        <h2>User Verification</h2>\n        <p><b>Field for indefinite documents</b></p>\n        <p>\n            A new <code>termless</code> field has been added to the <code>idDocs</code> object. Now when you fetch a document via the <a href=\"/reference/get-applicant-data\">Get applicant data</a> method, the <code>termless</code> field\n            will be present and set to true, if the document is considered indefinite.\n        </p>\n        <p>The <code>validUntil: 2099-01-01</code> value may still be present as well, but it will be removed for indefinite documents in a few months.</p>\n\n        <h2>Dashboard</h2>\n        <p><b>Effortless level management</b></p>\n        <p>The <b>Change Level</b> button has been renamed to <b>Manage Level</b> and enhanced with new features.</p>\n        <p>What’s new:</p>\n        <ul>\n            <li>You can change the applicant level.</li>\n            <li>You can reset specific steps — even within the current level.</li>\n        </ul>\n        <p>These updates give you full control over what applicants need to submit or re-submit, without triggering a full reset or making unnecessary changes.</p>\n\n        <p><b>Plan details page for enterprise clients</b></p>\n        <p>A new page in the <b>Billing</b> section that provides detailed insights into a current subscription has been added.</p>\n        <p>Data available on the page:</p>\n        <ul>\n            <li>Remaining deposit amount.</li>\n            <li>List of services in the current subscription.</li>\n            <li>Indication of whether each service is charged from the deposit.</li>\n            <li>Price of each service.</li>\n            <li>A separate tab for group and individual commitments, showing the commitment name, amount, and included services.</li>\n        </ul>\n\n        <p><b>Smarter collapsible blocks on Applicant page</b></p>\n        <p>We have improved the behavior of collapsible blocks on the Applicant page to get rid of endless scrolling and resetting.</p>\n        <p>What’s changed:</p>\n        <p>Every module now follows one of two behaviors.</p>\n        <ul>\n            <li><b>Remembered</b> — your open/closed preference is saved.</li>\n            <li>\n                <b>Always open</b> — blocks shown by default:\n                <ul>\n                    <li>Add Documents</li>\n                    <li>Applicant Notes</li>\n                    <li>Attachment images</li>\n                    <li>Identity documents</li>\n                    <li>Videoldent</li>\n                </ul>\n            </li>\n        </ul>\n        <a href=\"/docs/manage-profiles#review-and-verify-applicant-profiles\">Review applicants in the Dashboards -></a>\n\n        <h2>Transaction Monitoring</h2>\n        <p><b>Rule change event log</b></p>\n        <p>You can now view a complete history of rule changes, including who made each change, what was changed, and when it happened. This update makes debugging and client support significantly easier.</p>\n\n        <p><b>Variables support in scoring threshold for rules</b></p>\n        <p>Three rules in the Scoring Threshold bundle now support custom variables.</p>\n\n        <p><b>AML Checks generation improvement</b></p>\n        <p>AML check generation has been updated to prevent duplicate names across institutions, eliminating overlaps and confusion. Each entry is now unique, resulting in cleaner AML audit trails.</p>\n\n        <p><b>AML Screening table updates</b></p>\n        <p>Review time is now displayed as a separate column, consistent with other tables such as Applicants. Event logs for AML Screenings will be moved into this section in an upcoming update.</p>\n\n        <p><b>Expanded AML Screening check details</b></p>\n        <p>The individual AML check pages for counterparties, institutions, and payment details now display additional information:</p>\n        <ul>\n            <li>Fuzziness</li>\n            <li>Search Reference</li>\n            <li>Case ID, etc.</li>\n        </ul>\n\n        <a href=\"/docs/transaction-monitoring\">Learn more about Transaction Monitoring -></a>\n\n        <h2>Crypto Monitoring</h2>\n        <p><b>Elliptic transaction screening</b></p>\n        <p>We have now expanded the Elliptic integration to include transaction screening, enhancing overall monitoring capabilities.</p>\n        <p>Transaction screening analyzes blockchain transactions that have already occurred and have a blockchain hash. The wallet/address and transaction screenings are complementary, allowing VASPs to use either or both.</p>\n        <p>New rules based on this feature have been added to Crypto Monitoring: Elliptic Bundle.</p>\n\n        <p><b>Blockchain screening results in Transaction Reports</b></p>\n        <p>We’ve added the ability to view crypto monitoring screening results in exported Transaction reports.</p>\n        <p>This applies to all our crypto monitoring providers: Chainalysis, Elliptic, Crystal, and TRM Labs.</p>\n        <a href=\"/docs/crypto-monitoring#enable-crypto-monitoring\">Enable Crypto Monitoring -></a>\n    </details>\n</div>"
}
[/block]

***

[block:html]
{
  "html": "  <div class=\"details-list\">\n    <details>\n        <summary>August 11 -> August 15</summary>\n\n        <h2>User Verification</h2>\n        <p><b>Networks page updates</b></p>\n        <p>From now on, self-serve clients can see <b>Networks</b> page in the <b>Applicants</b> section in the Dashboard. To access this page, they will need to sign an <b>Enterprise</b> contract.</p>\n        <p>The <b>Networks</b> page has also been redesigned.</p>\n\n        <p><b>New API methods for applicant notes</b></p>\n        <p>We have released several new methods for managing applicant notes via API:</p>\n        <ul>\n            <li><a href=\"/reference/get-applicant-notes\">Get applicants notes</a></li>\n            <li><a href=\"/reference/add-applicant-note\">Add applicant note</a></li>\n            <li><a href=\"/reference/edit-applicant-note\">Edit applicant note</a></li>\n            <li><a href=\"/reference/remove-applicant-note\">Remove applicant note</a></li>\n            <li><a href=\"/reference/add-attachment-to-applicant-note\">Add attachment to applicant note</a></li>\n            <li><a href=\"/reference/download-note-attachment\">Download note attachment</a></li>\n            <li><a href=\"/reference/remove-note-attachment\">Remove note attachment</a></li>\n        </ul>\n        \n        <h2>Reusable Identity</h2>\n        <p><b>Reusable KYC updates</b></p>\n        <p>We have a new approach to Reusable KYC. From now on, we offer two distinct services:</p>\n        <ul>\n            <li><a href=\"/docs/reusable-kyc\">Reusable KYC</a> – For when the recipient wants a compliant KYC and a radically improved KYC process. <b>Rechecks</b> are always done to make sure all recipient level requirements are met. <b>API</b> and <b>SDK</b> integrations are available.</li>\n            <li><a href=\"/docs/copy-applicant\">Copy Applicant</a> – For when clients want to duplicate applicants across multiple client keys. It does not count as a KYC for the recipient. No rechecks are done, the applicant is simply copied. Only <b>API</b> integration is available.</li>\n        </ul>\n        <p>For both services, you just need to agree to use the respective service one time, and can then set up sharing with any other client.</p>\n        <p>Additionally, in the Dashboard, we now have a new <b>Reusable Identity</b> section that includes a <b>Reusable KYC</b> page and a <b>Partners</b> page.</p>\n        <ul>\n            <li>The <b>Reusable KYC</b> page has an empty state for clients not yet using the service. For those who already agreed to use Reusable KYC, they will see statistics on their usage of Reusable KYC.</li>\n            <li>The <b>Partners</b> page allows customers to add and remove donors and recipients themselves, without our involvement. Partners are shared by Reusable KYC and Copy Applicant services. Read more on how this works <a href=\"/docs/manage-sharing-partners\">here</a>.</li>\n        </ul>\n\n        <h2>SDK</h2>\n        <p><b>Design improvements</b></p>\n        <p>The design of Sumsub SDK has been updated with the following changes:</p>\n        <ul>\n            <li>The step list has been removed.</li>\n            <li><b>Animations</b> have been added to keep applicants engaged during document verification.</li>\n            <li>Due to the new display logic, we are now showing <b>the first step in the queue that is currently being verified</b>. If a step has already been verified by the time the <b>Pending</b> screen opens, it is skipped in the animation. If verification takes more than 1.5 minutes, the message changes to <b>Still verifying, almost done</b>. Once a step is finished, the system checks for any remaining unverified steps and runs the animation for them using the same rules.</li>\n      </ul>\n      \n        <h2>Business Verification</h2>\n        <p><b>Change of the AutoKYB documents approval logic</b></p>\n        <p>If you want to use <b>internal compliance teams</b> in our platform, we have adjusted the <b>Company Documents</b> automatic review and approval logic.</p>\n        <p>Now, the documents provided in the AutoKYB mode will not be marked as <b>Approved</b> until they are manually approved. They will be kept in <b>Pending</b> status and ignored in case of approval.</p>\n        <a href=\"/docs/business-verification\">Verify businesses with Sumsub -></a>"
}
[/block]

***

[block:html]
{
  "html": "<div class=\"details-list\">\n    <details>\n        <summary>August 18 -> August 22</summary>\n\n        <h2>Dashboard</h2>\n        <p><b>Changes to document extension settings</b></p>\n        <p>As part of improving the user experience, we have redesigned the document extension settings interface. These changes aim to make the settings easier to understand and to unify the terminology.</p>\n        <p>Key changes:</p>\n        <ul>\n            <li><b>Unified naming</b>. Global Settings and Supported ID Documents (+levels) now use the same wording, allowing users to navigate settings more easily:</li>\n            <ul>\n                <li>Respect the actual validity period (Global Settings) / Strict (Supported ID Documents (+levels)) → <b>Accept only valid documents</b></li>\n                <li>Accept expired documents extended by the government (Global Settings) / Generally Accepted Regulations (Supported ID Documents (+levels)) → <b>Accept valid and officially extended documents</b></li>\n                <li>Accept expired documents permissible by local regulations (Global Settings) / Local Regulations (Supported ID Documents (+levels)) → <b>Accept documents with no valid expiry date</b></li>\n                <li>Allow expired (Supported ID Documents (+levels)) → <b>Accept valid and expired documents</b></li>\n            </ul>\n            <li><b>Local extensions</b>. It is now possible to additionally enable local extensions via the checkbox: Accept valid and officially extended documents → <b>Accept documents with no valid expiry date</b>.</li>\n            <li><b>View document rules button</b>. The display window now visually separates government and local extensions for better clarity.</li>\n            <li><b>Extension availability tooltip</b>. An informative tooltip has been added to the relevant field in Supported ID Documents (+levels).</li>\n        </ul>\n\n        <p>Important notes:</p>\n        <ul>\n            <li>The functionality of the settings will remain unchanged.</li>\n            <li>All previously selected client preferences will continue to operate as before, without requiring any additional actions.</li>\n            <li>The <b>Accept valid and expired documents</b> setting will remain only in the <b>Supported ID Documents</b> (+levels) tab and will not be shown in <b>Global Settings</b> due to its high-risk nature.</li>\n        </ul>\n\n        <p><b>POI module updates</b></p>\n        <p>We've strengthened backend logic and document handling, making the process much more robust across scenarios.</p>\n        <p>New UI tools & logic enhancements:</p>\n        <ul>\n            <li><b>Set as active</b> button for images (in the All photos drawer)—you can now mark any image as active directly from the drawer.</li>\n            <li><b>Switch sides</b> button—if a document has two images, you can now swap front/back with a single click.</li>\n        </ul>\n        \n        <p><b>Image preview update</b></p>\n        <p>You can now scroll through large PDFs and adjust the preview image width.</p>\n\n        <p><b>Business Verification request page</b></p>\n        <p>We’ve added a request access page for Business Verification.</p>\n        <p>What’s new:</p>\n        <ul>\n            <li>Redesigned layout</li>\n            <li>Page is now available in <b>Applicants</b>, <b>Verification Levels</b>, and <b>Global Settings</b>.</li>\n            <li>Currently, it is only supported in the WebSDK.</li>\n        </ul>\n\n        <p><b>New placement for Custom Fields</b></p>\n        <p>Custom metadata fields — whether passed via API or collected via SDK (applicant data step) — have been relocated.</p>\n        <p>Here’s what’s new:</p>\n        <ul>\n            <li>They’ve moved from<b>Profile data</b> to <b>Provided Personal Data</b></li>\n            <li>Fields are now easier to read — showing the field name, display name, and whether they’re mandatory in the applicant step</li>\n        </ul>\n\n        <p><b>Profile Data improvements</b></p>\n        <p>Profile information now only includes editable fields: Email, Phone, Language, and Source key.</p>\n        <p>Other details are still available in the Overview/header:</p>\n        <ul>\n            <li><b>Created on</b> </li>\n            <li><b>Created by</b> (email of the applicant creator)</li>\n            <li><b>Last Screened</b> </li>\n            <li><b>Entity type</b> (only for Business Verification)</li>\n            <li><b>Applicant ID / External ID</b> </li>\n        </ul>\n\n        <p><b>Filter update: Linked to Company</b></p>\n        <p>We’ve added a new Linked to company filter in the KYC and KYB applicant lists to quickly find profiles connected to company applicants.</p>\n\n        <h2>Transaction Monitoring</h2>\n        <p><b>Transaction Monitoring rules scoring update</b></p>\n        <p>You’ll now see an icon in the Matched Rule block on the Transaction Page if a rule was updated after the transaction was scored.</p>\n        <ul>\n            <li>During scoring, only the rule version active at that time is applied</li>\n            <li>The icon appears only if the rule has been modified since scoring</li>\n            <li>Clicking the rule opens the exact version used during scoring, so you can see precisely what was applied.</li>\n        </ul>\n        <a href=\"/docs/transaction-monitoring\">Learn more about Transaction Monitoring -></a>\n\n        <h2>Business Verification</h2>\n        <p><b>Split of Requires action status into Awaiting service and Awaiting user</b></p>\n        <p>We’re introducing two new statuses to better distinguish cases where verification is waiting on a third party, rather than on the client. This helps improve case filtering and review.</p>\n        <ul>\n            <li><b>Awaiting service</b> (<code>awaitingService</code>) — verification is paused due to a long-running external process (e.g., asynchronous database reply or service process completion).</li>\n            <li><b>Awaiting user</b> (<code>awaitingUser</code>) — verification requires user action other than document submission, such as completion of associated parties’ verification.</li>\n        </ul>\n\n        <a href=\"/docs/applicant-statuses\">Explore verification statuses -></a>\n\n    </details>\n</div>"
}
[/block]

***

[block:html]
{
  "html": "  <div class=\"details-list\">\n    <details>\n        <summary>August 25 -> August 29</summary>\n\n        <h2>User Verification</h2>\n        <p><b>Greek ID card extensions</b></p>\n        <p>All current extensions for old Greek ID cards (without MRZ) will be removed. From now on, all Greek ID cards of such type <b>cannot be valid after 2027-09-25</b>.</p>\n        <a href=\"/docs/identity-verification\">Learn more about ID document verification -></a>\n\n        <h2>Business Verification</h2>\n        <p><b>Filter for company-related applicants</b></p>\n        <p>We have introduced the ability to distinguish applicants that are created as standalone, or as a part of a company-verification. For that, use the <b>Linked to company</b> filter.</p>\n        <p>Note that both <b>Individuals</b> and <b>Companies</b> may be linked to other companies' structure.</p>\n\n        <p><b>Enhanced company status synchronization</b></p>\n        <p>Companies now get the <b>Required actions</b> status when the linked company, beneficiaries, or representatives get <b>Resubmission requested</b> or <b>Required actions</b>. Once all the associated parties get <b>Approved</b> or any of them get the <b>Rejected</b> status, the company is transited to <b>Approved</b>/<b>Rejected</b> automatically.</p>\n        <p>For more information, see <a href=\"/docs/how-business-verification-works#companies-and-associated-individuals-status-synchronization\">this article</a>.</p>\n\n        <p><b>Document editor software auto-check</b></p>\n        <p>Forged company documents are assigned <b>Usage of graphic editor</b> risk label if identified (via metadata). For AutoKYB it triggers <b>Resubmission requests</b> automatically.</p>\n        <p>See the full list of company risk labels <a href=\"/docs/applicant-risk-labels#company-risk-labels\">here</a>.</p>\n\n        <a href=\"/docs/business-verification\">Verify businesses with Sumsub -></a>\n         \n        <h2>SDK</h2>\n        <p><b>MobileSDK update</b></p>\n        <p>New MobileSDK plugin versions have been released – 1.37.1. Changelog:</p>\n        <ul>\n            <li><a href=\"/docs/cordova-plugin-changelog\">Cordova</a></li>\n          <li><a href=\"/docs/react-native-module-changelog\">React Native</a></li>\n        </ul>\n\n        <h2>Dashboard</h2>\n        <p><b>Level interface redesign</b></p>\n        <p>We have updated the Level creation/editing page to make it more streamlined:</p>\n        <ul>\n            <li><b>SDK translations</b> have been moved under the Customization section.</li>\n            <li>You can now collapse the <b>Customization</b> section.</li>\n            <li>The full list of settings in the <b>Video Ident</b> section is hidden until it is turned on on this page.</li>\n        </ul>"
}
[/block]