- What is cashier-provider/tinkoff-auth used for?
- cashier-provider/tinkoff-auth is a Laravel package that adds Tinkoff authentication support to Cashier-style payment integrations. It helps manage merchant credentials and secure API access for Tinkoff acquiring flows. It is a subtree split of the Cashbox component from cashbox/foundation, so treat it as a provider and authentication layer rather than a complete payment application.
- How do I install cashier-provider/tinkoff-auth in a Laravel app?
- Install it with Composer using composer require cashier-provider/tinkoff-auth, then confirm service provider auto-discovery and publish any package configuration with vendor:publish. Configure merchant credentials through environment variables as documented in the README. Run a sandbox transaction before using production credentials.
- Which Laravel and PHP versions does cashier-provider/tinkoff-auth support?
- The provided release information does not publish a verified Laravel and PHP support matrix for v2.6.1. Check the package composer.json require constraints and the README before adopting it. Match those constraints against your platform baseline and test on your target Laravel version.
- Does this package replace Laravel Cashier or provide full payment processing?
- No, it is described as adding Tinkoff authentication support to Cashier-style integrations, not as a complete replacement for Laravel Cashier. It sits behind a provider-style contract and handles merchant credentials and API access concerns. You still need to own checkout flow, order state, reconciliation, and payment business logic in your application.
- How do I configure Tinkoff merchant credentials and API access?
- The expected Laravel pattern is to publish the package config and supply merchant credentials through environment variables rather than hard-coding them. Keep secrets out of source control and separate sandbox credentials from production credentials. Verify the exact config keys and required Tinkoff merchant or terminal values in the package README.
- Can I test cashier-provider/tinkoff-auth against the Tinkoff sandbox?
- A sandbox-credential smoke test is the expected integration path, and the assessment treats it as a short spike rather than a large project. Use Tinkoff sandbox credentials and run a representative authentication or acquiring call before production rollout. Confirm the supported sandbox endpoints and test data in the vendor documentation.
- Does the package handle Tinkoff webhooks and signature verification idempotently?
- The overview focuses on authentication and secure API access, while the assessment flags webhook signature verification and idempotency as shared concerns at the authentication boundary. Do not assume idempotent webhook handling or a signature-verification helper is included without checking the source and README. If you rely on webhooks for payment state, implement or verify idempotency and reconciliation in your application.
- What changed in cashier-provider/tinkoff-auth v2.6.1?
- The v2.6.1 release body has no changelog beyond a compare link, so the change is not documented in the release notes. Semver suggests a patch-level change with no intended breaking changes, but that is an assumption. Review the v2.6.0...v2.6.1 diff before upgrading.
- Is cashier-provider/tinkoff-auth actively maintained and safe for production?
- The package is a community or vendor integration, and the assessment warns to assess release cadence, maintainer count, issue responsiveness, and security policy before making it load-bearing. The empty v2.6.1 changelog is low-signal, so inspect commits and tags. For production, pin a version, monitor upstream Tinkoff API changes, and keep financial correctness checks in your own code.
- What are alternatives to cashier-provider/tinkoff-auth for Laravel Tinkoff payments?
- Alternatives include integrating Tinkoff's API directly behind your own PaymentGateway port, using a broader Cashbox or foundation package, or choosing another maintained Laravel payment provider that supports Tinkoff. Because this package is a subtree split, the upstream Cashbox component may be the better place to evaluate scope. Compare support matrices, webhook handling, and maintenance activity before switching.