- How do I install aceraven777/laravel-paymaya in a Laravel application?
- Install the package with Composer using composer require aceraven777/laravel-paymaya. Then check the package README for any service provider registration or configuration publishing steps required by your Laravel version. Because the provided context does not include installation details, confirm the exact commands and setup instructions in the repository before adopting it.
- Which Laravel and PHP versions are supported by this PayMaya package?
- The provided assessment does not include a documented compatibility matrix, so supported Laravel and PHP versions are not confirmed. You should inspect the package composer.json constraints and test it in a disposable Laravel sandbox matching your production runtime. TPM guidance specifically recommends requiring a documented compatibility matrix before adoption.
- How do I configure PayMaya API credentials in Laravel with this package?
- The package is described as offering configuration and API helpers for PayMaya integration, but the provided context does not document specific environment variable names or config keys. Look for a publishable config file or README section covering public and secret keys, sandbox versus production endpoints, and callback URLs. Validate credential loading in a non-production environment before handling real payments.
- Does aceraven777/laravel-paymaya support creating PayMaya checkout payments?
- The package blurb states that it provides configuration and API helpers to create payment requests and manage checkout flows. The exact methods and payload structure are not included in the provided context, so review the package source or README for checkout creation examples. Confirm that the supported PayMaya API operations match your required payment flow.
- How do I handle PayMaya webhooks or callbacks with this Laravel package?
- Webhook handling is not documented in the provided context, so you should not assume the package includes route registration, signature verification, or event dispatching. Check the repository for webhook support and verify how PayMaya callback payloads are validated. If webhooks are not provided, plan to implement secure callback handling in your Laravel application.
- Is this package suitable for production PayMaya payments?
- The TPM assessment confidence is low because it is based only on a v1.1.2 release note and lacks source, test evidence, and a compatibility matrix. Treat it as a candidate for sandbox evaluation rather than a proven production drop-in until you validate payment authorization, failure paths, webhooks, and dependency resolution. Payment and PCI compliance implications should also be reviewed with your security team.
- What is the difference between using this package and the PayMaya SDK directly?
- Version 1.1.2 reportedly imports the base PayMaya SDK as a Composer dependency, suggesting the package wraps or supplements the SDK for Laravel projects. The key question is whether it adds Laravel-specific value such as configuration publishing, facades, webhook helpers, queues, or test utilities beyond a thin SDK wrapper. Review the source to decide whether the abstraction justifies the extra dependency.
- How can I test PayMaya integration in sandbox mode with Laravel?
- The provided context does not include sandbox testing instructions, so check the package README and PayMaya developer documentation for test credentials and endpoints. TPM guidance recommends installing in a disposable Laravel sandbox and running authorization, capture, refund, webhook, and failure-path tests. Pin both the Laravel package and PayMaya SDK versions during validation.
- What should I check before upgrading to aceraven777/laravel-paymaya v1.1.2?
- The v1.1.2 release note says it imports the base PayMaya SDK as a Composer dependency, which may change dependency provenance even if runtime behavior is similar. Review Composer resolution against your existing Guzzle, PSR, and Laravel constraints, and confirm whether the release changes behavior or only packaging. Run regression tests in staging before promoting the upgrade.
- Who maintains this Laravel PayMaya package and is it actively supported?
- The Composer name indicates the maintainer is aceraven777, but the provided context does not document support ownership, release cadence, or escalation paths. Because the package depends on the PayMaya SDK, you should track both the Laravel wrapper and upstream SDK releases for security and breaking changes. Before adopting it, review the repository activity, license, and known limitations.