Weave Code
Monnify Laravel Laravel Package
monnify/monnify-laravel
A Laravel wrapper for the Monnify payment gateway, making it easy to accept collections, initiate single and bulk transfers, verify transactions, and handle webhooks. Includes configurable credentials, a fluent API, and support for sandbox and live environments.
Laravel Wrapper for Monnify Payment Gateway
Frequently asked questions about Monnify Laravel
- How do I install monnify/monnify-laravel in a Laravel application?
- Install it with Composer using composer require monnify/monnify-laravel, then publish the package config file so you can manage credentials per environment. Add the three required environment variables (API key, secret key, and contract code) and switch the package between sandbox and live mode. After that you can initiate a sandbox charge and verify the callback, which is the fastest way to confirm the wiring is correct.
- Which Laravel and PHP versions does monnify-laravel support?
- The documentation does not publish an explicit Laravel or PHP version matrix, so check the constraints in the package's composer.json before you set a platform baseline. PHP 8.1 compatibility is asserted through PHPStan at level 6 targeting the PHP 8.1 API rather than by running tests on an actual 8.1 runtime in CI. That is a reasonable proxy but not a hard guarantee, and the Composer lock platform constraint was adjusted for PHP 8.2 and above.
- How do I verify Monnify webhook signatures in Laravel?
- The package includes signature verification plus a complete webhook controller example covering the twelve supported event types. Register the webhook route and make sure it is excluded from CSRF protection, either in the VerifyCsrfToken middleware exceptions or the equivalent bootstrap configuration, or Monnify's POST requests will be rejected. Verifying the signature before you act on the payload is the documented best practice and prevents spoofed payment notifications.
- How do I accept card payments with Monnify in Laravel?
- Use the fluent API to initialize a transaction, then redirect the customer to the returned checkout URL to complete the charge. When Monnify redirects back, verify the transaction reference server-side before you mark an order as paid. The package deliberately does not persist transactions or model payments as domain entities, so storing the order state and reference is your application's job.
- Does monnify-laravel support single and bulk transfers?
- Yes. Version 1.1.0 covers disbursements with single and bulk transfer endpoints in addition to collections, refunds, and transaction verification. Note that destination account name is now an optional field, so payloads that previously failed client-side validation may now reach the API. Audit any logic that reads the beneficiary name for reconciliation or fraud screening before you upgrade.
- Can I test Monnify integration in Laravel without real money?
- Yes, the package supports a sandbox environment that you enable through configuration. The documentation includes a sandbox test card table covering no-OTP, OTP, 3DS, and failure scenarios, which lets QA write deterministic test cases instead of guessing at magic card numbers. Run your full checkout, refund, and webhook paths against sandbox before switching credentials to live mode.
- Does the package provide idempotency keys, retries, or transaction storage?
- No. monnify-laravel is a transport adapter around Monnify's REST API, not a payments subsystem, so it does not store transactions, run reconciliation, or manage ledgers. It also does not appear to expose idempotency keys or a reference generator, which means your application should mint and persist unique references for transfers and bill vends. Retry policy and deduplication for irreversible operations are likewise your responsibility.
- How do I implement Monnify bill payments and vend flows in Laravel?
- The package exposes each step: biller categories, billers, products, customer validation, vend, and requery. Because vend moves money irreversibly against third-party billers with their own downtime profiles, the multi-step browse, validate, vend, requery sequence needs orchestration and a state machine in your application. The package will not resume a half-finished flow for you, so budget explicitly for that work and harden it in sandbox first.
- Is monnify-laravel production ready and well maintained?
- The test posture is strong for a Laravel payment wrapper: roughly 235 tests at about 99.87 percent line and 99.38 percent method coverage, plus PHPStan at level 6, which lowers the risk of silent auth or response-parsing regressions. There were no breaking changes in 1.1.0, but the newly added bills payment surface area is first-release code and deserves a sandbox hardening period. Single-maintainer risk cannot be assessed from the documentation alone, so review the repository activity before committing.
- How are API credentials configured and auth tokens cached in monnify-laravel?
- Credentials are environment-driven and configured through the publishable config file, which keeps sandbox and live keys out of source control. Monnify's API requires a bearer token obtained from your API key and secret, and the package handles that authentication flow so you do not hand-roll an HTTP client. The documentation does not state whether tokens are cached per request, per process, or through the Laravel cache, so confirm the refresh strategy in the source before high-volume production use.
Weaver
How can I help you explore Laravel packages today?