- How do I install siganushka/wxpay-api in a Laravel app?
- Install it with Composer by running composer require siganushka/wxpay-api. Then follow the package README for any service provider registration, configuration publishing, and credential setup. Because the package is a PHP client, the exact Laravel wiring depends on the version and documentation you are using.
- What WeChat Pay operations does siganushka/wxpay-api support?
- The package is described as a simple client for common WeChat Pay workflows: orders, refunds, and notifications. That makes it a fit for typical payment flows such as creating a payment order, requesting a refund, and receiving WeChat Pay callbacks. Check the README for the specific endpoints and methods exposed by your version.
- Does siganushka/wxpay-api require Laravel, or can I use it in plain PHP?
- It is a PHP package, so it can be used in plain PHP projects as well as Laravel applications. In Laravel you would typically resolve the client through the container and keep credentials in configuration or environment variables. There is no indication in the provided context that Laravel is strictly required.
- How do I configure WeChat Pay credentials with siganushka/wxpay-api?
- You configure the client with your WeChat Pay merchant and API credentials as documented by the package. Keep those values out of source control by using environment variables and Laravel configuration caching where appropriate. The provided overview does not list exact config keys, so confirm names and required certificates in the README.
- How do I create a WeChat Pay order using this package?
- Use the package's order client to build and send a WeChat Pay order request, passing the amount, description, and identifiers required by WeChat Pay. The package is intended to reduce boilerplate around these API calls, but you still need valid merchant credentials and a correctly configured client. Refer to the README for the exact method signatures.
- How do I issue a refund with siganushka/wxpay-api?
- Refunds are one of the supported workflows, so you can call the package's refund API with the original transaction and refund details. Make sure your refund logic is idempotent and records the refund result for reconciliation. The package documentation should be checked for required parameters and response handling.
- How should I handle WeChat Pay payment notifications in Laravel?
- WeChat Pay sends asynchronous notifications that your application must receive, validate, and acknowledge correctly. Use the package's notification support to process the callback payload, then verify signatures and handle duplicate deliveries idempotently. Always return the response format WeChat Pay expects so it does not keep retrying.
- Is siganushka/wxpay-api safe to use in production?
- It can be used in production if you follow normal payment integration practices: protect credentials and certificates, enforce HTTPS, validate notifications, log requests safely, and make order and refund handling idempotent. The package is a client wrapper, so production reliability also depends on your application's error handling and reconciliation. Pin a known version and monitor for updates.
- How can I test a WeChat Pay integration without making real payments?
- The provided context does not document a dedicated fake or sandbox mode for this package. In Laravel tests you can isolate the client behind an interface or wrapper and mock it so your application code is tested without calling WeChat Pay. For end-to-end checks, use any WeChat Pay sandbox or test merchant facilities available to you and keep them separate from production credentials.
- Which Laravel versions does siganushka/wxpay-api support, and how is it maintained?
- The provided overview does not state Laravel version constraints, so check the package's composer.json and release history before adopting it. If the constraints do not cover your Laravel version, evaluate the official WeChat Pay SDK or other maintained PHP packages. Pin the version you test and review changelogs for compatibility updates.