- Can I install karser/robokassa-bundle in Laravel?
- No, not in the normal Composer sense. karser/robokassa-bundle is a Symfony bundle with a DI extension and KarserRobokassaBundle, so it has no Laravel service provider, publishable config, or facade. Composer will likely also conflict with Laravel 9+ because it depends on Symfony 2.8/3.x-era components and JMSPaymentCoreBundle.
- Does karser/robokassa-bundle support Laravel 11?
- It is very unlikely to work on Laravel 11 without a fork. The bundle’s last release was in 2018 and its constraints are expected to target php ^5.6 or ^7.0 and Symfony ^2.8 or ^3.0. Check composer.json for the exact constraints before spending time on an install attempt.
- Is karser/robokassa-bundle still maintained?
- No. The last release was 2018-04-12, it has a single maintainer, about 16 stars, and no dependents. There is no active community patching protocol changes or security issues.
- How do I integrate Robokassa into Laravel without this bundle?
- Write a native Laravel adapter instead. Robokassa’s core flow is a signed InvoiceURL redirect plus signed ResultURL and SuccessURL/FailURL callbacks, so the implementation is usually a controller, a signature service, and a job. The bundle is useful mainly as a reference for the protocol shape, not as a dependency.
- What does karser/robokassa-bundle actually do for Robokassa payments?
- The bundle generates signed Robokassa payment URLs, validates ResultURL callbacks and signature checksums, and supports receipt data for fiscalization. It wraps those steps in Symfony services and configuration for merchant credentials, currency, and test mode. It does not provide Laravel integration, queued webhook durability, or reconciliation.
- Does karser/robokassa-bundle support Robokassa receipts and 54-FZ fiscalization?
- Do not assume it meets current 54-FZ requirements. A 2018 Symfony bundle likely under-supports or predates the receipt payload details Robokassa now expects, such as line items, VAT rates, payment method, and payment object. Validate against current merchant-cabinet documentation and test receipt payloads before relying on it for Russian tax compliance.
- What Robokassa signature algorithm does karser/robokassa-bundle use?
- The documented Robokassa signature is built over MerchantLogin:OutSum:InvId:Password, and this bundle’s era is most associated with MD5. Robokassa now supports MD5, SHA256, and SHA512, plus newer flows such as SBP and recurrent payments, so verify the bundle’s assumptions before trusting it. Re-audit signature validation for timing-safe comparison and strict type checks.
- Can I use karser/robokassa-bundle in production for payment callbacks?
- Not as-is for a serious payment integration. The bundle has no first-class idempotency, replay protection, retry queue, or reconciliation job, which are exactly the gaps that cause payment incidents. If you adapt any code, add InvId uniqueness enforcement, strict signature checks, and callback logging before production.
- What are alternatives to karser/robokassa-bundle for Laravel?
- Prefer a maintained Robokassa SDK only if it explicitly supports PHP 8.2+ and Laravel 11. Otherwise implement a small native adapter behind a PaymentGateway interface and keep vendor-neutral DTOs for payment intent and callback result. That also lets Robokassa sit alongside YooKassa, Tinkoff, or Stripe adapters.
- Is karser/robokassa-bundle MIT licensed and safe to fork?
- Yes, the license is MIT, so forking, vendoring, and commercial use are permitted. That is its cleanest attribute, but licensing does not remove the maintenance, protocol drift, and fiscalization risks. If you fork, plan to replace the Symfony and JMS layers rather than carry them into Laravel.