Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.
RSS feed

Changelog

New updates and improvements

API v2 Update — Share Verified KYC/KYB Data

New: Share Verified KYC/KYB Data

A new method is now available in the Compliance endpoint — Share Verified KYC/KYB Data — POST /v2/compliance/{customerId}/share.

This method applies a SumSub share token to an existing customer, transferring already-verified KYC/KYB data instead of requiring the customer to go through verification again. One token covers the whole share:

  • For an INDIVIDUAL — the customer's own verified profile.

  • For a CORPORATE — the company profile, copied together with its verified beneficiaries/UBOs.

The token is validated before it is consumed. If the token is rejected, the response returns applied: false with the reason in message, and nothing is applied — the request can be retried with a corrected token. Once a token has been successfully applied (applied: true), the customer can no longer be shared again and subsequent calls will return 409.

Tokens are short-lived (~20 minutes) and single-use.

Required next steps after a successful share

  • Call PATCH /v2/customer/{customerId}/application to finalize the customer's application status.

  • If the response includes items in outstanding, the shared data did not fully cover the required verification level. Use GET /v2/compliance/{customerId}/web_sdk_link to generate a link for the customer to upload the remaining document sets (e.g. PROOF_OF_RESIDENCE).

Please note: this method is not available for partners on the BaaS verification program (403).

API v2 Update — Compliance & Document Types

New: Compliance

A new Compliance endpoint is now available. It includes a new method Get Compliance Link — GET/v2/compliance/{customerId}/web_sdk_link — which generates a short-lived URL for the customer's KYC/KYB verification flow. When opened, the URL launches a modal window with the required verification fields for the customer to complete.

Heads up: Set Customer Application is being deprecated

The Set Customer Application method in the Application endpoint will be deprecated soon. Going forward, the new application flow should be handled through the Get Compliance Link method.

Please note: Get Compliance Link does not affect the current functionality of Set Customer Application. Both methods remain active and can be used simultaneously.

New: Additional document types

In the Get Customer Application endpoint, the following new document types have been added:

SOURCE_OF_FUNDS, TYPE_VISA, IDENTIFY_BIOMETRICS, INCUMBENCY_CERT, PHOTO, COMPLIANCE_OFFICER_RESUME, REGULATORY_LICENSE, SANCTIONS_AUDIT, SANCTIONS_POLICY, TRADE_LICENSE, COMMERCIAL_LICENSE, WOLFSBERG_GCBDDQ, SOURCE_OF_WEALTH_COMPANY, SOURCE_OF_WEALTH_SHAREHOLDER, ORG_CHART, AML_KYC_POLICY, OWNERSHIP_STRUCTURE, UBO_POA, DIRECTOR_POA, UBO_LIVENESS, DIRECTOR_LIVENESS, CONTRACT, INVOICE, TERM_SHEET, BILL_OF_LADING.

KYC/KYB Requirements article updated

Please note that the sample documents templates have been updated, make sure use the new versions for your clients' onboarding.

Last updated