- What is omalizadeh/laravel-multi-payment used for?
- Laravel Multi Payment is a Laravel package that provides a unified, driver-based API for integrating multiple online payment gateways. It lets you configure providers, initiate payments, verify callbacks, and manage transactions through one consistent interface instead of writing separate gateway-specific integration code. It is useful when an application needs to support more than one payment provider.
- How do I install laravel-multi-payment in a Laravel application?
- Install the package with Composer using composer require omalizadeh/laravel-multi-payment. Then follow the package documentation to publish any configuration files and set credentials for the gateways you plan to use. Before upgrading, confirm that the package version supports your Laravel and PHP versions.
- Does laravel-multi-payment support multiple payment gateways?
- Yes. Multi-gateway support is the package's core purpose: it abstracts payment providers behind a common driver-based integration layer. You configure providers and use one consistent API for payment initiation, callback verification, and transaction handling. The v3.1.0 release adds Paystar as another gateway option.
- What changed in laravel-multi-payment v3.1.0?
- v3.1.0 is an additive feature release that introduces a Paystar payment gateway via PR #18. The release information does not indicate breaking API changes, removed gateways, or deprecations. Existing users who do not enable Paystar should generally expect a minor-version update, but should still run dependency and regression checks.
- Which Laravel and PHP versions does laravel-multi-payment v3.1.0 support?
- The provided release information does not state the exact Laravel and PHP version constraints for v3.1.0. Check the package composer.json on the repository and Packagist before upgrading. Validate the update in a non-production branch, especially if your application is on an older Laravel version.
- Does the Paystar driver support refunds and callback verification?
- The v3.1.0 release note only confirms that Paystar was added; it does not document supported Paystar operations, callback and verification behavior, refunds, or error handling. Review how the Paystar driver implements the package's gateway contract and test those flows in sandbox before relying on it in production. Treat refund and callback support as items to validate rather than assume.
- Is laravel-multi-payment v3.1.0 a breaking change from v3.0.0?
- The release appears additive, with no indicated breaking API changes, removed gateways, or deprecations. Teams already on v3.0.0 can generally plan a standard Composer minor-version update to ^3.1 followed by regression testing. Teams on older major versions should first assess the v3.0.0 upgrade requirements.
- How should I test the Paystar integration before production?
- Configure Paystar in sandbox and run your existing payment gateway regression tests against the shared package interface. Validate payment initiation, callback handling, verification, failure paths, retries, misconfigured credentials, currency or amount mismatches, and duplicate payment attempts. Then roll out behind a feature flag or limited merchant scope before broader production use.
- What are the production risks of using Paystar with laravel-multi-payment?
- Paystar-specific risk is moderate until the gateway is validated against real payment flows, sandbox behavior, and error cases. Areas to check include Paystar API outages, callback verification failures, credential misconfiguration, amount or currency mismatches, duplicate attempts, and inconsistent error responses compared with other gateways. The thin release notes and limited documented test coverage also mean teams should confirm maintainer support before relying on Paystar for critical payment volume.
- What maintenance concerns should I consider before adopting laravel-multi-payment?
- For existing users not enabling Paystar, v3.1.0 is likely a low-risk routine update, but it still warrants dependency and regression checks. Paystar-specific maintenance will depend on the payment provider's API stability and the package maintainers' responsiveness to issues. Before critical use, confirm documentation, issue triage, and test coverage, and evaluate whether the package's driver abstraction fits your required payment flows.