Weave Code
Mollie Laravel Package
omnipay/mollie
Omnipay Mollie is a Mollie gateway driver for the Omnipay PHP payment library. It lets Laravel and PHP apps create payments, handle redirects and webhooks, and process refunds through a consistent API, simplifying Mollie integration into existing Omnipay checkout flows.
Mollie driver for the Omnipay payment processing library
Frequently asked questions about Mollie
- How do I install omnipay/mollie in a Laravel application?
- Install it with Composer using composer require omnipay/mollie. It is not a native Laravel package, so you must bind the Omnipay gateway in a service provider or container binding and load Mollie credentials from your Laravel configuration. Keep the gateway behind your own payment interface so controllers do not depend directly on Omnipay classes.
- Does omnipay/mollie support Laravel 10 or Laravel 11?
- The package is framework-agnostic and does not declare Laravel version support in the same way a Laravel-specific package would. You need to verify compatibility through Composer constraints for PHP, omnipay/common, and omnipay/mollie, then test against your Laravel version in staging. Pin versions and check release history before upgrading Laravel.
- How do I configure Mollie API keys with Omnipay in Laravel?
- Create the Omnipay Mollie gateway with your Mollie API key, typically from config/services.php and environment variables. Configure return and webhook URLs in your Laravel routes and Mollie dashboard, and ensure HTTPS is used. Keep separate keys per environment and never commit live credentials.
- Can omnipay/mollie handle refunds and transaction lookups?
- The driver supports purchase, complete purchase, refunds, and transaction lookups according to the package overview. Validate the exact operations you need against the installed driver version and your Mollie account configuration, especially for recurring payments, chargebacks, and method-specific flows. Do not assume full parity with Mollie’s official SDK without testing.
- How do I handle Mollie webhooks and return URLs with omnipay/mollie?
- The driver helps create hosted checkout payments and handle returned payment results, but your Laravel application owns the webhook route, CSRF exemption, verification, idempotency, and status reconciliation. Expose a return URL for the customer redirect and a separate webhook endpoint for Mollie notifications where supported. Store payment records and log transitions so duplicate webhooks do not corrupt state.
- Is omnipay/mollie suitable for production, or should I use Mollie's official PHP SDK?
- Use it in production only after a staging spike and a clear feature matrix. It fits applications already standardized on Omnipay or needing a multi-gateway abstraction. If Mollie is your only gateway, Mollie’s official PHP SDK is often a better architectural fit and exposes more Mollie-specific capability; the Omnipay driver has a small community footprint and uncertain maintainer responsiveness.
- How do I test omnipay/mollie payments without live Mollie credentials?
- Use Mollie test API keys and a staging environment to exercise create-payment, redirect, return, and webhook flows. The package does not provide Laravel testing helpers, so wrap the gateway behind an internal interface and fake that interface in unit tests. Keep a small number of integration tests against Mollie’s test mode for status and refund behavior.
- Can omnipay/mollie be used alongside other Omnipay gateways for multi-gateway support?
- Yes, that is a primary reason to use Omnipay: you can configure Mollie alongside other Omnipay gateways behind a consistent API. Keep each gateway binding in Laravel configuration and avoid leaking Omnipay request or response objects into domain models. Confirm that the operations you need are supported by every gateway you expose.
- What are the risks of using omnipay/mollie with an unknown maintainer or small community?
- The main risks are compatibility drift with Omnipay and Mollie API versions, incomplete Laravel guidance, webhook and security gaps, and coupling domain models to Omnipay objects. The package has a small community footprint and unknown repository/maintainer, so release durability and responsiveness are uncertain. MIT licensing reduces legal risk, but your team must monitor releases and own fallback planning.
- How do I handle idempotency and reconciliation with omnipay/mollie in Laravel?
- Implement idempotency in your Laravel application by recording payment and event identifiers, rejecting duplicate webhook processing, and reconciling Mollie status through lookups. Use queues for webhook and reconciliation jobs, and keep Omnipay calls behind an internal PaymentGateway interface. Define failure paths and a runbook for credential, webhook, refund, and reconciliation issues.
Weaver
How can I help you explore Laravel packages today?