Salesforce
Run KYC and KYB verification without leaving Salesforce.
Salesforce is a cloud-based CRM platform that helps organizations manage relationships and interactions with customers, prospects, and business processes in one place.
The Salesforce Verification Plugin runs Sumsub Identity (KYC) and Business (KYB) verification natively inside Salesforce. Your team launches checks, sends verification links, and tracks results from the records they already work in — Accounts, Contacts, and Opportunities — while applicant status and verified data stay in sync automatically. No separate tools, no manual data entry, no swivel-chair between systems.
The integration can be used in the following cases:
- You already use Salesforce and want to trigger KYC or KYB verifications from this system.
- You already use our platform and want to move existing verification flows into Salesforce.
Use cases
The Salesforce integration supports the following common use cases:
- User Verification (KYC) — initiate and manage individual verification workflows directly from Salesforce.
- Business Verification (KYB) — verify companies and access verified business information, such as company name, registration details, addresses, and incorporation data.
- In-deal verification — initiate verification during the sales process and incorporate verification statuses into your Salesforce workflows.
- Complex business structures — verify companies with multiple related parties, such as beneficial owners, directors, and shareholders, as part of your business verification process.
- Re-verification and level changes — move applicants between verification levels or initiate additional verification steps directly from Salesforce.
- Compliance operations — access applicant statuses and verification results within Salesforce to support compliance and operational processes.
Solution benefits
Key benefits of Sumsub’s Salesforce integration include the following:
-
CRM-Embedded Verification Workflows — initiate, manage, and track customer verifications directly within Salesforce, without moving between separate systems.
-
Centralized Verification Data — access applicant statuses, verification results, and verified customer data directly from the relevant Salesforce records.
-
Shared Cross-Team Visibility — give sales, compliance, and operations teams a consistent view of verification progress and outcomes within the CRM.
-
Reduced Manual Operations — keep customer and verification data connected in one system, minimizing duplicate data entry, manual updates, and context switching.
-
Flexible Salesforce Implementation — adapt the integration to your Salesforce record structure, internal workflows, and specific verification requirements.
How Sumsub’s Salesforce integration works
Sumsub’s Salesforce integration is provided as a plugin that is installed in your Salesforce environment. The plugin connects Salesforce with Sumsub and enables teams to work with verification data directly within this CRM. Verification statuses and results are returned to Salesforce and can be viewed alongside customer records.
Verification flow
- You initiate a KYC or KYB verification workflow from Salesforce.
- Sumsub generates a verification link for the selected verification level.
- You share the link with the applicant through your preferred communication channel, such as email or a messaging app.
- The applicant completes the verification process using Sumsub.
- Sumsub processes the verification and returns verification statuses, results, and verified data to Salesforce.
- You can access verification information directly in Salesforce, helping you track verification progress and review results alongside your customer data.
Supported verification actions
You can perform the following verification-related actions directly from Salesforce:
| Action | Result |
|---|---|
| Generate WebSDK link | Create a new verification link for an applicant. |
| Get applicant data | Retrieve the latest applicant data and verification status from Sumsub. |
| Change applicant level | Move an applicant to a different verification level for step-up verification or re-verification. |
| Request applicant check | Request a new verification review for an applicant. |
Verification levels are synchronized with your Sumsub account configuration, so available actions always reflect the levels configured in your Sumsub dashboard.
Technical implementation
The integration exchanges data directly between Salesforce and Sumsub using secure API requests and webhooks.
- Salesforce → Sumsub: API requests for verification-related actions, such as generating links, retrieving applicant data, requesting checks, and changing verification levels.
- Sumsub → Salesforce: webhook notifications used to update applicant statuses, results, and verification data. For more information about webhooks, refer to this article.
Data captured in Salesforce
The integration stores verification data in dedicated Salesforce records created by the package:
- Sumsub Applicant — stores applicant information, verification statuses, results, and related verification data.
- Sumsub Webhook Message — stores verification events and status updates received from Sumsub and provides an audit trail for each applicant.
The following information is available in the Sumsub Applicant record:
|
Group |
Fields |
|---|---|
|
Identification |
|
|
Result & status |
|
|
Company (KYB) |
|
|
Integration health |
|
The following information is available in the Sumsub Webhook Message record:
|
Group |
Fields |
|---|---|
|
Event |
|
|
Result & status |
|
|
Identifiers |
|
|
Payload & link |
|
Security and data protection
The integration includes the following security measures:
- Signed outbound requests — requests sent to Sumsub are authenticated using API credentials and request signatures.
- Verified inbound webhooks — incoming webhook notifications are validated before processing using the HMAC (Hash-based Message Authentication Code) algorithm. Payloads that fail validation are rejected and do not update your data.
- Credentials stay in your org — API token, secret key, and webhook secret are stored in your Salesforce configuration, scoped by permission set.
Supported configuration
Sumsub’s Salesforce integration supports the following configuration options:
- Verification types — run KYC (individual) and KYB (company) verification workflows.
- Salesforce records — launch verification workflows from supported Salesforce records.
- Environments — use separate sandbox and production connections.
- Multiple connections — configure multiple Sumsub connections within the same Salesforce environment.
- Link delivery — send verification links through any communication channel.
Setup requirements
Before implementing the integration, make sure you have:
- Salesforce edition — Enterprise, Unlimited, or Developer.
- Salesforce experience — Lightning Experience (Salesforce Classic is not supported).
- API access — API access and Apex callouts enabled.
- Salesforce Sites — a Salesforce Guest Site enabled to receive verification webhooks.
- Connectivity — outbound access to https://api.sumsub.com.
- Sumsub account — an active account with API credentials (app token and secret key), a webhook secret, and at least one configured verification level.
Standard implementation
The standard implementation includes:
- Installation of the Salesforce integration package.
- Initial integration configuration.
- Webhook endpoint setup.
- Standard applicant and verification data model.
- Mapping of up to 20 fields from the Sumsub verification response.
- Configuration of automated email notifications
- Additional customizations or client-specific requirements are assessed separately and may be provided as an additional service, depending on the scope and complexity of the request.
NoteFeatures included in the standard implementation can typically be enabled or disabled through configuration.
Customization
The standard implementation is designed to support common verification use cases. Additional requirements that go beyond the standard implementation scope may require custom development and are assessed separately.
Examples include:
- Additional field mappings — mapping more than the 20 fields included in the standard implementation.
- Custom data model extensions — adding new fields or objects beyond the standard Salesforce data model provided by the integration.
- Additional Sumsub data sources — retrieving data that requires separate Sumsub API methods.
- Advanced data transformations — moving or transforming data outside of the standard verification workflow.
- Client-specific business logic — implementing custom processing rules, workflows, or data formats.
- Other custom development beyond the standard connector functionality.
ImportantMinor configuration adjustments are typically handled as part of the standard implementation. Larger customizations are scoped, quoted, and agreed upon separately before implementation begins. If you are unsure whether a requirement is covered by the standard implementation, contact your Sumsub Customer Success Manager.
Enable Sumsub’s Salesforce integration
To get started with Sumsub’s Salesforce integration, contact your Sumsub Customer Success Manager or account manager. They will help assess your requirements, review the implementation scope, determine the necessary Salesforce configuration, and guide you through the setup process.
NoteSumsub’s Salesforce integration is provided as a Salesforce plugin and is implemented, configured, and supported in collaboration with T1A, a certified Salesforce partner. For additional information about the integration offering and available services, see the T1A partner page.
After the implementation scope is agreed upon, the integration can be installed and configured either by you or by T1A. Installation guidance and setup documentation are provided as part of the onboarding process.
The setup process typically includes the following steps:
- Install the package in your Salesforce environment.
- Create a connection to your Sumsub account using your API credentials and verification configuration.
- Configure webhook communication between Salesforce and Sumsub.
- Assign permission sets to Salesforce users who will manage or perform verification workflows.
- Add verification actions to the relevant Salesforce page layouts.
Setup fee
Sumsub’s Salesforce integration is provided as a paid service and includes a one-time setup fee. Contact your Customer Success Manager or account manager to discuss pricing and implementation details.
Sumsub's Salesforce integration FAQ
Find the most frequently asked questions about Sumsub's Salesforce integration.
What is the plugin?
A native Salesforce app that runs Sumsub KYC and KYB verification inside Salesforce, keeping applicant status and verified data in sync between the two systems.
Which Salesforce editions are supported?
Enterprise, Unlimited, and Developer, on Lightning Experience.
Where can a verification be started?
From an Account, Contact, or an Opportunity, via Start Verification (KYC) or (KYB). Person Accounts supported.
Does it support both individuals and companies?
Yes — KYC (individual) and KYB (company), enabled per connection.
How is the verification link delivered?
The generated verification link is available in Salesforce and can be shared with the applicant by email, messenger, or any other communication channel.
What data appears in Salesforce?
Applicant statuses, verification results (GREEN/RED), reject reasons, and — for KYB — verified company data are stored in the Sumsub Applicant record. Verification events and status updates are stored in Sumsub Webhook Message records.
How many fields can be mapped?
The standard data model plus up to 20 fields. Mapping more than 20 fields that need a separate API call is custom development.
Can we install and configure it ourselves?
Yes. The integration can be installed and configured by your team using the setup guide provided by T1A. If preferred, T1A can also assist with or perform the implementation.
How is the integration secured?
Outbound calls are cryptographically signed; inbound webhooks are verified against a stored webhook secret before any data is updated. Credentials stay in your org, scoped by permission set.
How are updates handled?
It is an unlocked package — updates apply on your schedule and never change your org automatically.
Can the plugin be customized?
Yes. The standard implementation includes the configuration options described above. Requirements beyond the standard implementation scope can be addressed through custom development and are assessed separately.
How is it priced?
Offered as a standard package; custom development is scoped and quoted separately. Contact your Customer Success Manager for current pricing.
How do we get support?
By email to [email protected]. Response times range from 4 hours (critical) to 48 hours (low priority), during business hours (10:00–17:00 CET).