- How do I install nexa-merchant/apis in Laravel?
- Install it with Composer using composer require nexa-merchant/apis, then register or discover the service provider according to your Laravel version. The package is distributed as a standard Composer package under the MIT license. Because third-party adoption is very low, verify the install in a clean Laravel app before adding it to an existing project.
- Which Laravel versions are supported by nexa-merchant/apis?
- The available context does not publish an explicit Laravel version support matrix, so you must inspect the package composer.json constraints before upgrading. It is described as Laravel-ready and PSR-compatible, but that is not the same as validated support for every Laravel major. Test against your exact Laravel and PHP versions, especially if you rely on route, middleware, or auth guard behavior.
- How do I configure Nexa Merchant API credentials in Laravel?
- The package provides Laravel-ready merchant configuration, so credentials are expected to be set through Laravel configuration rather than hard-coded in requests. Keep secrets in environment variables and avoid committing them. Confirm the exact config keys and guard setup in the source, since the public documentation is thin.
- Does nexa-merchant/apis support merchant payments and authentication?
- The package is positioned as an integration layer for Nexa Merchant APIs, including merchant payment endpoints and authentication. It also ships controllers, resources, middleware, and an auth guard for the NexaMerchant platform surface. That means it is more than a thin HTTP client, so review how its auth and payment flows bind to your models.
- Is nexa-merchant/apis production-ready?
- Treat it as a single-vendor, low-adoption package rather than a proven production dependency. It has an MIT license and active tagging, but only about 3 GitHub stars, 0 dependents, and no published support or security commitments. Production use should follow source review, integration tests, and a plan to own or fork the code if needed.
- Does nexa-merchant/apis include caching?
- Yes, the technical assessment confirms the package contains CMS functionality and a cache layer, despite earlier assumptions that it had no built-in caching. Release V1.3.8 includes a changelog entry for fixing CMS cache behavior. Cache correctness and cache-key scoping should be reviewed before use, particularly in multi-tenant or multi-store deployments.
- Can I use nexa-merchant/apis without Laravel?
- The package is described as Laravel/PHP and lightweight PSR-compatible PHP usage is listed, so some parts may be usable outside Laravel. However, its architecture includes Laravel service providers, routes, controllers, middleware, and an auth guard, so full functionality is Laravel-oriented. Non-Laravel use would require isolating the PSR-compatible pieces and avoiding the framework-bound layers.
- How do I test Nexa Merchant API calls in Laravel?
- There is no published test evidence or formal API contract for this package, so consumer tests must be built around your own integration boundaries. Mock HTTP responses or wrap the package behind your own service interface so upgrades do not break tests unpredictably. Also add tests for cache invalidation behavior if you enable its CMS features.
- Is nexa-merchant/apis actively maintained?
- It is actively tagging releases, including V1.3.8 with a CMS cache fix, so the repository is writable and not archived. The changelog jumps from V1.3.6 to V1.3.8, skipping V1.3.7, which suggests either a withdrawn release or irregular tagging. Active tags are a positive signal but not proof of security handling or long-term support.
- What are alternatives to nexa-merchant/apis?
- There is no widely adopted ecosystem around this package, so direct alternatives are not evident from the provided context. You can build a small in-house client against the Nexa Merchant API if you only need payment endpoints and authentication. If you need CMS and cache behavior, compare adopting NexaMerchant platform components against owning that logic yourself.