- How do I install openpesa/laravel-pesa in a Laravel app?
- Install it with Composer as openpesa/laravel-pesa, then review the tagged release documentation for any required service-provider registration or configuration publishing steps. The available evaluation confirms Laravel 9 and PHP 8.1 support, but you should verify exact install commands and package constraints against the version you pin.
- What Laravel and PHP versions does openpesa/laravel-pesa support?
- The available evaluation cites Laravel 9 and PHP 8.1 as the stated support baseline. It does not confirm maintenance for older Laravel or PHP versions, so validate the Composer constraints before adopting it in legacy applications.
- Which Tanzanian mobile money providers and payment flows are supported?
- The package is positioned for Tanzanian mobile money providers and exposes flows for payment requests, transaction status checks, and callback processing through one interface. The available evidence does not list exact providers or API coverage, so confirm the provider matrix in the tagged source and sandbox before committing.
- Does openpesa/laravel-pesa support idempotency, retries, and callback verification?
- The available assessment does not confirm idempotency keys, retry behavior, or callback signature and source verification. Treat these as due-diligence items and plan to implement or wrap them in your own adapter before production.
- Is the removed Artisan command a breaking change in laravel-pesa v1.0.2?
- The release notes mention a command removal, and the evaluation flags it as a possible breaking change for teams that relied on it. Because it was published in the 1.x line, review the changelog and test scripts or scheduled jobs before upgrading.
- Why do the laravel-pesa v1.0.2 release notes and changelog disagree?
- Release metadata is inconsistent: the notes are labeled v1.0.2 while the changelog compares v1.0.0 to v1.0.1. Resolve this with the maintainers and pin a verified tag before relying on version constraints.
- How should I test openpesa/laravel-pesa safely before production?
- Start with a non-production pilot using sandbox credentials and the updated demo examples, pinned to an exact Composer version. Validate the package against your Laravel 9 and PHP 8.1 stack, then add callback verification and reconciliation before any production canary.
- Can I use openpesa/laravel-pesa for production payment processing?
- It can be a fit for Laravel applications that need Pesa-style mobile money calls, but the available evidence is limited to release notes and does not confirm security posture or production readiness. Treat it as an infrastructure adapter behind your own gateway interface, with queued calls, timeouts, retries, callback verification, audit logging, and reconciliation.
- Is openpesa/laravel-pesa actively maintained and what license does it use?
- The available assessment says maintenance likely depends on upstream activity and does not confirm the license, security disclosure process, or support arrangements. Modern CI tooling such as Pest, PHPStan, PHP CS Fixer, and GitHub Actions is positive, but the version and changelog mismatch means you should verify release discipline yourself.
- What are alternatives to openpesa/laravel-pesa for Laravel mobile money payments?
- The available evidence does not benchmark laravel-pesa against other Tanzanian mobile money SDKs or Laravel payment packages. Compare it with direct provider APIs and maintained Composer packages by checking provider coverage, callback security, idempotency, license, release cadence, and sandbox support, and keep it behind an internal gateway interface so you can switch.