- How do I install andrey-helldar/cashier-sber-auth in a Laravel application?
- Install it with Composer using composer require andrey-helldar/cashier-sber-auth. Then publish the package config file so you can supply your Sber client credentials, and wire up the routes or middleware hooks the package exposes for the SberID redirect and callback. The package follows standard Laravel service provider and facade conventions, so auto-discovery should handle registration on supported Laravel versions. Confirm the PHP and Laravel floors in composer.json before installing.
- Which Laravel and PHP versions does cashier-sber-auth support?
- The package is described as compatible with standard Laravel service provider and facade patterns, and Laravel 10/11 with PHP 8.1+ is a reasonable working hypothesis. The authoritative answer is in the package's composer.json require section and any published compatibility matrix. Check that your app's Laravel and Cashier major versions fall inside that range before you build a spike, since a Cashier version outside the supported range is a hard stop that surfaces late and expensively.
- How do I configure Sber client credentials for SberID authentication?
- Credentials are supplied through the published config file rather than hard-coded in your application code. After publishing, set the client ID and secret, plus any redirect URI or scope values from your Sber app registration, using environment variables. Keep these values out of version control and treat them as secrets, since they authorize access to Sber's identity flow on your behalf.
- Does cashier-sber-auth work with Laravel Cashier's existing models and flows?
- The package is positioned as an extension that adds a SberID auth driver to Laravel Cashier, integrating with Cashier's models and flows rather than replacing them. That suggests your existing Cashier setup (billable models, migrations, configuration) stays in place, with Sber layered on as the authorization path. Whether it implements Cashier's provider contract cleanly or touches Cashier internals is worth verifying in the source, because forking internals makes future Cashier upgrades fragile.
- How does the SberID OAuth redirect and callback exchange work in this package?
- A user is redirected to Sber's OAuth authorization endpoint, and Sber returns them to your configured callback route with an authorization code. The package handles the code-for-token exchange and resolves the Sber identity so you can match or create a local user. You then persist the link between that Sber account and your application's user record. Your routes and middleware decide which parts of the app require a Sber-linked session.
- Is there a test suite or CI for cashier-sber-auth, and are webhook signatures verified?
- The available release and README material does not document a test suite, CI pipeline, or webhook signature verification, so do not assume them. Inspect the repository's tests directory, CI configuration, and the code path that handles inbound callbacks before putting this in a revenue-critical flow. For an auth or billing adapter, signature verification and duplicate-callback handling should be confirmed in code and, ideally, covered by tests.
- What changed in version 2.6.1 of cashier-sber-auth?
- The v2.6.1 release notes contain no human-readable content beyond an auto-generated changelog link, so the change set is not disclosed in the notes. Review the commit range between v2.6.0 and v2.6.1 to see which files were touched before upgrading. Patch numbering implies no breaking change, but in a provider adapter a vendor-API behavior fix can be operationally breaking while still being semver-compliant.
- Do I need a Sber merchant or business account to use this package?
- In practice, yes: you need Sber-side credentials from an app or merchant registration before the OAuth flow can work, and the package only handles the Laravel side of the exchange. Sber onboarding, contracting, and any data-residency or compliance obligations are commercial and legal dependencies with lead times measured in weeks. Plan for that gate separately from the engineering work.
- What are the alternatives to cashier-sber-auth for Sberbank login in Laravel?
- You can implement the SberID OAuth flow directly with Laravel Socialite or a small custom OAuth client, which avoids depending on a single-maintainer adapter but means writing and maintaining the callback exchange yourself. If you do not actually need Cashier integration, a plain OAuth package is often the better fit. Keeping the Sber integration behind an interface your application owns makes swapping implementations later much cheaper.
- Is cashier-sber-auth production-ready and how actively is it maintained?
- It is a single-vendor, likely single-maintainer package, so bus-factor risk and documentation depth deserve scrutiny before you commit a revenue-critical path to it. Check the open-issue backlog, release cadence, whether releases are tagged and signed with provenance, and whether a SECURITY.md or disclosure channel exists. The empty v2.6.1 notes are a weak but real signal about documentation investment, and they do not tell you whether the release is safe to adopt.