- What is cashier-provider/sber-auth used for?
- cashier-provider/sber-auth is a Laravel package that adds Sberbank authentication to the Cashier payment ecosystem. It handles the provider-side credential and token flow so your app can call Sber APIs without writing custom auth logic. It is intended for Laravel applications that accept Sber payments through Cashier.
- How do I install cashier-provider/sber-auth?
- Install the package with Composer using composer require cashier-provider/sber-auth. Laravel package auto-discovery should register the service provider automatically. After installation, publish the package configuration so you can add your Sber credentials and environment settings.
- Do I need to publish the configuration file?
- Yes, you should publish the package config to set your Sberbank credentials and environment-specific options. The package provides publishable configuration for credentials and environment settings. Keep the published config values driven by environment variables rather than committing secrets.
- Which Laravel versions does cashier-provider/sber-auth support?
- The package is built for Laravel applications and follows standard Laravel service-provider and configuration conventions. The exact Laravel and PHP version constraints are declared in the package composer.json and repository documentation. Check those constraints before installing to confirm compatibility with your application.
- How does cashier-provider/sber-auth integrate with Laravel Cashier?
- It plugs Sberbank authentication into the Cashier provider ecosystem so your billing code stays consistent with other Cashier providers. The package handles the Sber credential and token flow needed to talk to Sber APIs. This lets you use Sber credentials within Cashier-based billing and checkout flows.
- Where should I store Sberbank credentials for this package?
- Store Sberbank credentials in your environment file or a secrets manager, and reference them from the package configuration. The package provides publishable config for credentials and environment settings. Avoid hard-coding credentials in source control or committing them to the repository.
- Can I use cashier-provider/sber-auth in production?
- You can use it in production when your credentials, environment settings, and Cashier integration are configured correctly. Test the full authentication and payment flow in a non-production environment before going live. Keep Sber credentials secure and review the package repository for the latest release notes and compatibility details.
- How do I test Sber authentication without hitting the real API?
- Use Sber sandbox credentials if available, and mock or fake outbound HTTP calls in your Laravel tests. Avoid using production credentials in CI or local test suites. Confirm the package's token flow with integration tests that cover successful and failed authentication responses.
- Does cashier-provider/sber-auth support different Sber environments?
- The package includes publishable configuration for credentials and environment settings, which lets you separate values per environment. Use environment variables to switch between sandbox and production settings without changing code. Always verify the correct endpoints and credentials for each environment before deployment.
- What are alternatives to cashier-provider/sber-auth?
- Alternatives include implementing the Sberbank credential and token flow yourself or using another Cashier-compatible provider package if one fits your billing setup. This package is focused on plugging Sber authentication into the Cashier ecosystem with Laravel service-provider and config wiring. Evaluate maintenance activity, Laravel version support, and fit with your existing Cashier integration before choosing.