- How do I install barryvdh/laravel-omnipay in a Laravel app?
- Install it with Composer using composer require barryvdh/laravel-omnipay, then publish the package configuration so config/omnipay.php is available. Laravel 5+ uses service provider and facade auto-discovery, so no manual registration is normally needed. Pin the package version you validate and confirm the exact publish command or provider name from the package README for your Laravel version.
- Which Laravel versions does barryvdh/laravel-omnipay support?
- The package is documented as supporting Laravel 5+ through its service provider and facade integration. The v0.2.5 release is a compatibility-only update for Laravel 10, 11, and 12 with no API changes or deprecations. Wrapper compatibility does not guarantee that every Omnipay gateway driver supports the same PHP and Laravel matrix, so verify drivers individually.
- How do I configure multiple payment gateways in config/omnipay.php?
- Define a default gateway and add each provider under the gateways array in config/omnipay.php, including its Omnipay driver name plus credentials and settings. You can then resolve a named gateway through the Omnipay facade or container instead of constructing gateway classes manually. Keep credentials in environment variables where possible and preserve the existing config shape during upgrades to minimize production risk.
- How do I resolve a gateway using the Omnipay facade or dependency injection?
- The package binds Omnipay into Laravel's service container and exposes an Omnipay facade for resolving configured gateways. You can request the default gateway or select a named gateway before calling Omnipay operations such as purchase, refund, or callback handling. For testability, inject the manager or configured gateway where your application design supports it rather than calling the facade directly in domain code.
- Can barryvdh/laravel-omnipay handle purchases, refunds, voids, and callbacks?
- It provides access to Omnipay's unified API, so purchases, refunds, voids, and callback handling are possible when the underlying gateway driver supports those operations. The wrapper itself does not add payment-domain features such as idempotency, reconciliation, webhook verification, or failure-path UX. Test each required operation against the specific gateway sandbox before relying on it in production.
- Is barryvdh/laravel-omnipay safe to use for production payments?
- Treat it as a convenience layer over Omnipay, not as strategic billing infrastructure. It is pre-1.0, effectively single-maintainer, community-supported, and has no SLA, LTS commitment, or documented security-disclosure process. Your team still owns merchant onboarding, credential management, webhook verification, refund and void flows, reconciliation, observability, and PCI scope decisions. Pin the version, name an internal owner, and define a fallback plan before putting it in the payment path.
- How do I test Omnipay payment flows with sandbox gateways?
- Configure sandbox credentials for one gateway in config/omnipay.php and verify that the driver supports test mode if you need it. Exercise each flow you plan to ship, including authorize, capture, refund, void, and callback or webhook handling, against the gateway sandbox. In automated tests, mock or fake the gateway boundary so unit tests do not depend on external payment APIs.
- Does barryvdh/laravel-omnipay work with PayPal, Stripe, and Authorize.Net?
- It can work with those providers through their respective Omnipay gateway drivers, which must be installed and configured separately. The package's value is swapping providers behind a consistent Laravel configuration and facade with minimal application code changes. Check driver-by-driver maintenance and PHP/Laravel compatibility rather than assuming wrapper health implies driver health.
- Should I use laravel-omnipay or Laravel Cashier for subscriptions?
- Choose Laravel Cashier when you need first-party Stripe or Paddle subscription billing, metered billing, or a billing portal. barryvdh/laravel-omnipay is a better fit when a genuine multi-gateway abstraction or an Omnipay-only driver is required and you are prepared to own the surrounding billing logic. It does not provide subscriptions, checkout UX, or reconciliation by itself.
- How maintained is barryvdh/laravel-omnipay and what are the risks?
- It is a pre-1.0, community-supported package with an effectively single-maintainer profile and no vendor SLA. The v0.2.5 release shows compatibility maintenance for Laravel 10 through 12, but it is not evidence of broader project maturity. Low star count and no listed dependents mean you should not treat it as battle-tested infrastructure. Pin the version, verify each gateway driver, assign an internal owner, and plan an exit path if maintenance stalls.