- How do I install the shureban/laravel-sumsub-sdk package?
- Run composer require shureban/laravel-sumsub-sdk, then add Shureban\LaravelSumsubSdk\SumsubServiceProvider::class to the providers array in config/app.php. After that, publish the config files with the artisan vendor:publish commands from the README so you can bind your own implementations. The package is installed via Composer and has no manual file copying step beyond publishing config.
- Which Laravel versions are supported by laravel-sumsub-sdk?
- The v2.3.1 release adds Laravel 13 support to the package's compatibility range. The assessment indicates Laravel 8 through 13 may be supported, but you must confirm the exact matrix in composer.json because a framework-support bump can either widen or replace older constraints. If you are on Laravel 10, 11, or 12, v2.3.1 should be a drop-in Composer update.
- How do I register the SumsubServiceProvider in Laravel?
- Add Shureban\LaravelSumsubSdk\SumsubServiceProvider::class to the providers array in config/app.php as shown in the README. If your Laravel version uses package discovery, check whether the provider is auto-registered, but the documented path is manual registration. Then publish config and verify the container bindings resolve correctly.
- How do I publish and customize the Sumsub SDK config?
- Publish the SDK config with php artisan vendor:publish --provider=Shureban\LaravelSumsubSdk\SumsubServiceProvider --force, and also publish the object mapper config for LaravelObjectMapper. The published config lets you swap interfaces for specific classes, so you can customize HTTP clients, response mapping, or other implementations. Commit the published config and review it per environment.
- Does this package handle Sumsub webhooks for KYC events?
- Yes, the package includes event-driven webhook handling for Sumsub KYC and identity verification events. You should still verify the exact event payloads and routing in your application, because the SDK is a thin integration layer. Test webhook delivery in staging before relying on it in production.
- Is the SHAREHOLDER_REGISTRY document type supported by this SDK?
- The SHAREHOLDER_REGISTRY document subtype was introduced in the v2.2.6 line and remains unchanged in v2.3.1. If your KYC workflow depends on that subtype, v2.3.1 does not alter document types or API contracts. Confirm your business logic still handles it as expected.
- What PHP version do I need for laravel-sumsub-sdk?
- The SDK's minimum PHP version is not stated in the README; check the php constraint in composer.json for the exact floor. Be aware that Laravel 13 raises the PHP requirement, so verify the SDK against your CI, staging, production, and legacy queue-worker images. Do not assume the framework-support bump leaves the PHP constraint unchanged.
- What changed in laravel-sumsub-sdk v2.3.0 and v2.3.1?
- v2.3.1 is a framework-compatibility release that adds Laravel 13 support, with no advertised breaking changes, deprecations, or API surface changes. The v2.3.0 contents are currently unverified in the assessment and should be read from the changelog or compare diff before scheduling work. The last functional change to the integration surface was the SHAREHOLDER_REGISTRY subtype in v2.2.6.
- Should I pin the laravel-sumsub-sdk version in composer.json?
- Pin the package to ^2.3 only after confirming the supported Laravel and PHP matrix, rather than floating on ^2.x. Run composer update --dry-run in CI to catch dependency-resolution conflicts early, especially around illuminate/support, nesbot/carbon, and symfony packages. Re-run your existing test suite and validate webhook automation in staging.
- Is laravel-sumsub-sdk actively maintained and what are the alternatives?
- The package is at v2.3.1 and has added Laravel 13 support, which indicates active maintenance, but release notes are only available for the latest version. Alternatives include calling the Sumsub REST API directly or using another SDK; this package's value is its Laravel service provider, config publishing, and webhook handling. Check the GitHub repository for recent commits, issues, and release cadence before adopting it.