- Which Laravel versions does maksa988/laravel-freekassa support?
- Version 4.0.0 of the package was released to add Laravel 8 support, so that is the framework version to target. If your application is still on Laravel 7 you would need to pin the ^3.0 line, which forfeits any future fixes landing in the v4 branch. The package does not appear to support Laravel 9 or newer, so on modern applications plan to implement the FreeKassa payload and signature logic directly.
- How do I install and configure laravel-freekassa?
- Install it with Composer using composer require maksa988/laravel-freekassa, then publish the package configuration file with the vendor:publish command. Supply your FreeKassa merchant ID and secret in that config, ideally sourced from environment variables rather than committed files. Finally register a route pointing at your callback handler so FreeKassa can deliver payment notifications.
- Does laravel-freekassa verify the FreeKassa webhook signature?
- The package handles notification processing, but you should not assume it performs full validation on your behalf. Signature verification, source IP allow-listing, and reconciliation against your own order state are responsibilities the assessment explicitly assigns to the host application. Read the callback handler in the source before going live and add any missing checks in your own controller.
- Are FreeKassa notifications handled idempotently by this package?
- FreeKassa, like most aggregators, can resend a notification until it receives a success response, so duplicate callbacks are expected in normal operation. The package does not document built-in deduplication, which means you should store processed merchant order IDs and short-circuit repeats yourself. Do that inside a transaction or behind a unique constraint so concurrent retries cannot double-credit an order.
- Which FreeKassa integration modes does this package cover?
- It is built around the classic redirect flow: assembling a signed form or redirect payload and parsing the notification that comes back. The non-redirect API modes are not clearly documented in the release notes, so verify coverage before relying on them. If you need a mode the wrapper does not cover, a small application-owned client written against the provider spec is the safer route.
- Is the MD5 signature used by laravel-freekassa secure?
- FreeKassa mandates an MD5-based signing scheme, so the package cannot strengthen it; the weakness belongs to the provider, not the wrapper. What you can control is keeping the secret env-sourced and never logged, and comparing signatures in constant time. Treat that secret as a production credential and rotate it if it ever appears in logs or error output.
- Should I use laravel-freekassa on Laravel 9 or 10?
- No, the v4.0.0 release only declares Laravel 8 support, so adopting it on Laravel 9 or later means constraining the framework or maintaining a fork. The substantive logic is small: assembling a signed payload and verifying a callback, on the order of tens of lines. Implementing that directly against the FreeKassa spec is usually faster than stabilising a fork.
- Is maksa988/laravel-freekassa actively maintained?
- It is a single-maintainer community package, and the release history shows framework support being added reactively rather than ahead of time. Before adopting it in a payment path, check commit activity over the last twelve months, whether issues get answered, and whether a fork or succession plan exists. Bus factor matters more than usual when the code handles money.
- How do I test FreeKassa payments in a Laravel application?
- There is no evidence in the release notes of a test suite or CI pipeline in the package itself, so budget for your own coverage. Use Laravel's HTTP fakes and a fake notification payload to exercise your callback controller, including invalid signatures and duplicate deliveries. Assert that your order state transitions only once per successful payment and that rejected callbacks leave it untouched.
- What compliance issues come with integrating FreeKassa into a Laravel app?
- FreeKassa is a Russian payment aggregator, which means RUB settlement, potential sanctions exposure, and data-residency and AML obligations that vary by operating entity. That is a legal and finance review gate rather than an engineering decision, and it can rule out the integration regardless of code quality. Get written sign-off from Legal and Finance before you write the adapter.