- How do I install kingflamez/laravelrave in a Laravel application?
- Install it with Composer using composer require kingflamez/laravelrave, then confirm your app's PHP and Laravel versions satisfy the package's composer.json constraints. Laravel's package auto-discovery usually registers the service provider, but you should verify a config file can be published if the package ships one. Run composer why kingflamez/laravelrave and composer audit afterwards to confirm dependency resolution is clean. Always test the install on a branch or staging copy before touching production.
- Does kingflamez/laravelrave support Laravel 10?
- Release v4.2.1 is described as adding Laravel 10 support, so it is the version to target for Laravel 10 projects. The release note is sparse, so check the package's composer constraints, changelog, and CI matrix to confirm whether that support is fully tested or best-effort. Also verify which PHP versions are allowed, since framework bumps often come with PHP requirement changes. Do not assume Laravel 11 or 12 compatibility from this release alone.
- How do I configure my Flutterwave API keys with laravelrave?
- The package is designed to be configurable, so you should publish its config file and supply your Flutterwave public and secret keys through environment variables rather than hardcoding them. Keep the keys out of version control and use separate credentials for staging and production. After changing configuration, clear any cached config with php artisan config:clear so the new values are picked up. Confirm the exact environment variable names against the package's published config file.
- How do I initiate a payment with laravelrave in Laravel?
- The package is intended to simplify initiating Rave payments from your Laravel application, typically through a small set of facade or helper calls that build the payment request and return a redirect or payment link. Follow the README's usage example for the correct method names and required fields such as amount, currency, email, and callback URL. Test against Flutterwave's test keys first before switching to live credentials. Because the API surface is not documented in the release notes, read the source or README for the exact signatures in your installed version.
- How do I verify a Flutterwave transaction with laravelrave?
- Transaction verification is one of the package's stated responsibilities, so it should expose a way to confirm a payment by its transaction reference after the customer returns to your callback URL. Always verify server-side before fulfilling an order, and never trust a status passed in the query string alone. Check that the amount and currency returned match what you expected for that order. See the package source for the exact verification method name in your installed version.
- How do I handle Flutterwave webhooks using laravelrave?
- The package covers webhook handling, so you'll typically expose a route that receives Flutterwave's POST payload and pass it to the package's handler. Webhooks should be treated as the source of truth for payment status, with your callback page used only for user experience. Make the endpoint idempotent so repeated deliveries don't double-credit an order. Also confirm any signature or secret-hash verification the package supports, and return a 200 response quickly by queueing slow work.
- Which Laravel and PHP versions does kingflamez/laravelrave support?
- The v4.2.1 release note only mentions Laravel 10 support, so the full supported matrix is not documented in the release itself. Check the composer.json require and require-dev sections plus the CI configuration to see which Laravel and PHP combinations are actually tested. That matters if your estate still runs Laravel 8 or 9, or if a patch may have raised the minimum PHP version. Build a version-by-version compatibility matrix before standardizing on the package across multiple apps.
- Is kingflamez/laravelrave still maintained and safe for production?
- The project is still publishing releases, with v4.2.1 adding Laravel 10 support, which suggests ongoing compatibility maintenance rather than active feature development. Semver suggests a patch release carries low API-break risk, but you should still review the changelog for constraint changes and run your test suite. Treat the maintainer's support policy and security posture as unknown until you verify them directly on the repository. Pin a known-good version and keep a rollback path in your lockfile.
- How do I test laravelrave payments without charging real cards?
- Use Flutterwave's test credentials and test cards in a staging environment, keeping live keys out of local and CI environments entirely. Wrap your payment initiation and verification calls behind a small service class so you can swap in a fake or mock in unit tests instead of hitting the Flutterwave API. For webhooks, post recorded sample payloads to your endpoint in feature tests. Verify that signature checks and amount matching behave correctly for both success and failure cases.
- What should I check before upgrading to laravelrave v4.2.1 in production?
- Pin your current version, branch, update to ^4.2.1, and review the exact composer.lock diff so the change is auditable. Run composer why and composer audit, then execute the full test suite including config publishing, service providers, queue workers, and any scheduled jobs. Confirm there are no public API or behavioral changes and that your PHP version still satisfies the constraints. Pilot in your lowest-risk Laravel 10 application, monitor staging or a canary, then promote, keeping a rollback to the prior version ready.