- How do I install lokielse/omnipay-unionpay in a Laravel application?
- Install it with Composer using the package name lokielse/omnipay-unionpay. Because it is an Omnipay gateway driver rather than a Laravel-native package, you then create the UnionPay gateway through Omnipay and wrap it in your own Laravel service. Bind that service in the container and keep Omnipay objects out of controllers.
- Is lokielse/omnipay-unionpay a Laravel package or an Omnipay driver?
- It is an Omnipay gateway driver for China UnionPay, not a Laravel-native package. It can be used in Laravel because Laravel is a PHP application, but the integration pattern should be an application-owned adapter around the Omnipay driver. Treat it as a protocol adapter rather than a full payment orchestration layer.
- Which Laravel and PHP versions are supported by lokielse/omnipay-unionpay?
- The package does not present itself as a Laravel-versioned package, so compatibility depends on your PHP version, Laravel version, Omnipay major version, Guzzle/PSR dependencies, and required extensions such as OpenSSL. Check the Composer constraints and test dependency resolution before adopting it. The safest approach is to gate it behind an adapter and verify it in your exact application stack.
- What UnionPay merchant credentials and certificates are needed for this package?
- You need a UnionPay merchant account, the correct UnionPay product or API variant, test credentials, and the certificate or key material required by that product. You should also clarify whether you are processing domestic China payments or cross-border payments, because the requirements can differ. Store merchant IDs, keys, and certificates in Laravel configuration or a secrets store rather than in code.
- Does lokielse/omnipay-unionpay support authorize, capture, refund, void, query, and callback verification?
- The package is a focused UnionPay driver, but the overview does not guarantee coverage of every transaction type you may need. Before committing, verify in the package source and current UnionPay documentation whether authorize, capture, refund, void, query, and callback verification are supported for your product. Your application should still own callback authenticity checks, idempotency, and reconciliation.
- How should I store UnionPay credentials securely in Laravel?
- Keep UnionPay merchant credentials and certificate material in Laravel configuration backed by environment secrets or a dedicated secrets manager. Do not commit certificates or private keys to the repository. Bind a configured UnionPayGateway service in the container so controllers and jobs never handle raw credentials directly.
- Can lokielse/omnipay-unionpay be used for cross-border UnionPay payments?
- It may be usable if the driver supports the UnionPay product and region you require, but cross-border versus domestic processing must be confirmed against the package and UnionPay specifications. The overview specifically flags region and product variant as key questions. Validate endpoint versions, currency and amount rules, certificate formats, and callback payloads before relying on it for cross-border flows.
- How can I test UnionPay payments without using production credentials?
- You need sandbox or test credentials from UnionPay and clarity on the correct product and API variant. Start with low-value or sandbox transactions and verify callbacks, refunds, and reconciliation before moving to production. Do not assume the package supplies a sandbox environment by itself.
- Is lokielse/omnipay-unionpay safe to use in production?
- It is feasible for production only if your application owns the regulated payment-path concerns: signature validation, certificate rotation, callback authenticity, idempotency, timeout handling, and reconciliation. The driver may lag UnionPay API changes or Omnipay major versions, so pin dependencies and monitor compatibility. Prefer hosted or redirect UnionPay flows where supported to minimize PCI scope.
- What are alternatives to lokielse/omnipay-unionpay for Laravel?
- Alternatives include other Omnipay UnionPay drivers, compatible forks, or a custom UnionPay integration hidden behind your own PaymentGateway contract. If you already have a custom integration, normalize both implementations to the same domain request and response contract before canarying traffic. The package has a favorable MIT license and focused scope, but its moderate adoption means maintenance posture and issue responsiveness should be evaluated.