Weave Code
Omnipay Bridge Laravel Package
payum/omnipay-bridge
Bridge for Payum that lets you use any Omnipay payment gateway through Payum's unified API. Wrap Omnipay gateways as Payum payment services to handle purchases, authorizations, captures, refunds and notifications via one consistent interface.
Payum Omnipay Bridge integrates Omnipay gateways into Payum, letting you reuse Omnipay’s broad gateway ecosystem behind Payum’s unified payment API. It adapts Payum requests to Omnipay operations and maps results back, so existing Payum workflows can use Omnipay providers without custom glue code.
- Wrap supported Omnipay gateways as Payum gateways
- Reuse Payum’s actions, storage, and status handling
- Bridge purchase, authorize, capture, refund, and void operations
- Configure credentials through Payum gateway config
- Keep gateway-specific logic behind a consistent interface
Frequently asked questions about Omnipay Bridge
- What is payum/omnipay-bridge used for?
- It is an adapter that lets you use Omnipay payment gateways inside Payum's payment workflow abstraction, so your app keeps Payum tokens, payment state, and actions while reaching Omnipay drivers. It is useful only when Payum is already your payment abstraction and you need a gateway that has an Omnipay driver but no native Payum driver.
- Is payum/omnipay-bridge a Laravel package?
- No. It is a plain PHP library with no Laravel service provider, config file, facades, or published assets. In Laravel you can compose it manually through a small service provider or container binding, but it does not install as a Laravel module.
- How do I install payum/omnipay-bridge in a Laravel app?
- Install it with Composer alongside Payum and the Omnipay gateway driver you need, then register the bridge's gateway factory with Payum. In a Laravel app you will usually add a small service provider or container binding yourself and configure each Omnipay gateway per Payum gateway. Expect dependency resolution, not wiring, to be the main effort because the package is old.
- How do I configure an Omnipay gateway with Payum using this bridge?
- Instantiate the Omnipay gateway with its credentials, wrap it through the bridge, and register it with Payum's gateway registry so Payum actions can create, capture, and inspect payments. Configuration is per gateway, and you must verify that Payum capture and status handling map correctly to the Omnipay driver's purchase, authorize, capture, refund, and void semantics.
- Does payum/omnipay-bridge support Laravel 10 or 11 and PHP 8?
- It has no Laravel-specific code, so Laravel support depends on its PHP, Payum, Omnipay, and Symfony constraints. The last release was in 2017 and predates PHP 8 and current Symfony majors, so it is unlikely to install cleanly on Laravel 10 or 11 without a fork with widened constraints.
- Is payum/omnipay-bridge maintained and safe for production payments?
- No, it should be treated as unmaintained. The last release was 2017, it has very low usage, and it is likely pinned to Omnipay 2.x and an old Payum version, so upstream security fixes will not flow to it. Because it handles money movement, adopting it in production requires a fork you own, security review, and an explicit sunset plan.
- Can I use payum/omnipay-bridge without already using Payum?
- You can technically install it, but it adds no value if Payum is not your payment abstraction. The bridge exists to keep Payum's token, persistence, and workflow model in front of Omnipay gateways; if you are talking to Omnipay directly, use Omnipay or the PSP SDK directly instead.
- What are alternatives to payum/omnipay-bridge?
- Use native Payum drivers where they exist, or call Omnipay 3 or the payment provider's official SDK directly for gateways that lack a Payum driver. A third option is to fork the bridge as a short-lived tactical unblock for one or two gateways, with modern constraints and a sunset date. Avoid making the unmaintained bridge a permanent foundation.
- How should I test a Payum Omnipay Bridge integration?
- Test the bridge at the workflow level: create Payum payments, run capture and status actions, and assert the correct Omnipay requests and payment state. Use Omnipay mock or test gateways and cover edge cases such as authorize-only, partial capture, refund, void, and failed payments. You can also try running the package's own PHPUnit suite, but its old dependencies may not resolve on a modern stack.
- What compatibility issues should I check before adopting payum/omnipay-bridge?
- Check the package's PHP constraint against your runtime, the Omnipay major it requires, the Payum major, and transitive Symfony event-dispatcher and options-resolver versions. Also check the PHPUnit version if you intend to run its tests. The realistic outcome is a fork with widened constraints, so budget time for dependency reconciliation and payment-flow verification.
Weaver
How can I help you explore Laravel packages today?