- What does the andrey-helldar/cashier-tinkoff-auth package actually do?
- It adds Tinkoff (T-Bank) payment support to Laravel Cashier, giving you a fluent, Eloquent-friendly API for billing customers and managing subscriptions. The package handles Tinkoff authentication, request signing and API communication so you can create payments and react to provider events without boilerplate. It also covers webhook notifications, refunds and payment state synchronization. Configuration is done through Laravel's service container, and the package publishes config and migrations.
- How do I install cashier-tinkoff-auth in a Laravel application?
- Install it with Composer using composer require andrey-helldar/cashier-tinkoff-auth, then publish the package config and migrations if the service provider does not do that automatically. Check the php and illuminate/* constraints in its composer.json against your app before you commit. Run your migrations and clear the config cache afterwards. Because recent release notes only link a commit range, read the diff between the version you pin and the previous one.
- Which Laravel and PHP versions does this Tinkoff Cashier package support?
- The package is built for Laravel applications and follows Cashier provider conventions, but the exact illuminate/* and php constraints live in its composer.json rather than in the overview. Check that file plus the CI matrix to see which Laravel majors are actually tested. A mature 2.x line implies a stable public API, but it does not by itself guarantee support for every Laravel major. Verify before pinning a version.
- How do I configure Tinkoff / T-Bank API credentials?
- Credentials are managed by the package's auth layer and configured through Laravel's service container, typically via a published config file and environment variables. Keep terminal keys, merchant identifiers and signing secrets out of version control and load them from your env file or secret manager. After changing values, run php artisan config:cache so the container resolves the updated configuration. The exact key names are documented in the published config file for your version.
- How do I create a one-off payment with Laravel Cashier and Tinkoff?
- The package exposes a fluent, Cashier-style API for one-off charges, so you build the charge on your billable model and let the package sign and send the request to Tinkoff. Treat the returned payment state as provisional and let webhook notifications drive the final status instead of assuming a synchronous result. Wrap creation in a transaction or queued job when it must be retried safely. Check the source for the exact fluent method names on your pinned version.
- Does cashier-tinkoff-auth support subscriptions and recurring billing?
- Yes, subscription payments are listed among its core features alongside one-off charges, with an Eloquent-friendly API for managing them on your billable models. Recurring state is synchronized from Tinkoff events, so your webhook endpoint must be reliable and idempotent. Exercise the full lifecycle in a sandbox tenant before relying on it in production. Method names and model traits depend on the version you pin.
- How does this package handle Tinkoff webhooks and payment notifications?
- It includes webhook and notification handling for payment status, so Tinkoff events can update your local payment records and subscription state. Expose an endpoint, exclude it from CSRF protection, and verify the incoming notification before acting on it. Process events idempotently, since providers commonly retry deliveries. Confirm the exact route and verification behaviour against the source for your pinned version.
- How do refunds work with this Tinkoff Cashier integration?
- Refunds are part of the package scope alongside payment state synchronization, and are issued through the same authenticated API layer used for charges. Because refunds are asynchronous on the provider side, treat the local state change as provisional until a notification confirms it. Log both the request and the provider response so finance can reconcile them. Check the source for the exact refund entry point in your version.
- Can I test Tinkoff payments without touching production?
- Integrate against a sandbox T-Bank tenant so no real money moves and credentials stay isolated from live keys. Point your config at the sandbox credentials in a non-production environment and drive status transitions through the package's event handling. Placing the package behind your own auth or payment interface keeps it replaceable and easier to fake in tests. Never auto-merge patch bumps of an auth package; surface them for manual triage instead.
- Is cashier-tinkoff-auth production ready, maintained, and what are the alternatives?
- It is a single-vendor package with a mature 2.x line, which suggests a stabilised API and an existing consumer base, but you should verify maintainer count and release cadence on the repository. Recent releases shipped with only a commit-range link, so you cannot classify whether a patch contains a security fix without reading the diff. Pin an exact version in your lockfile and review upstream releases manually. If you do not specifically need T-Bank, first-party Laravel Cashier with Stripe or Paddle is the lower-risk alternative; otherwise wrap this package behind your own payment interface so it can be swapped.