Omnipay Unionpay Laravel Package

Product Decisions This Supports

• Payment method expansion / market entry: Decide whether adding UnionPay is worth it for China and cross-border customers by estimating addressable GMV, checkout conversion lift, and support burden.
• Build vs. buy: Use an Omnipay driver instead of a bespoke UnionPay API integration, reducing initial engineering effort while accepting community-maintenance risk.
• Roadmap prioritization: Compare UnionPay against Alipay, WeChat Pay, local acquirers, and international card rails to decide whether it is launch-critical or a fast-follow experiment.
• Checkout architecture: Keep UnionPay behind Omnipay’s gateway abstraction so the Laravel app can route, fail over, or swap providers without rewriting checkout logic.
• Operational readiness: Force explicit decisions on refunds, reconciliation, settlement, webhooks, idempotency, PCI scope, and monitoring before committing to production.
• Commercial validation: Use demand for UnionPay as evidence in acquirer/PSP negotiations and pricing discussions.

When to Consider This Package

• You are on PHP/Laravel, already use or are willing to adopt Omnipay, and need UnionPay as a card/payment option for China or cross-border customers.
• You want a low-cost MIT starting point and can own integration hardening: tests, monitoring, retries, refunds, reconciliation, and security review.
• Your required UnionPay flows match what the driver actually supports. Verify purchase, refund, authorize/capture, 3DS/secure pay, currencies, settlement, and webhook behavior; do not assume coverage for QR, wallet, mini-program, or recurring billing.
• You can tolerate community-package risk: 112 stars, not Laravel-native, no official UnionPay support, and an opportunity score of 3.39 suggesting tactical rather than strategic leverage. Plan for maintenance and exit criteria.
• Look elsewhere if you need a turnkey Laravel payment package, official SDK/support, subscriptions, marketplace payouts, QR/wallet-heavy China payments, multi-acquirer routing, or strong SLAs. Prefer an official UnionPay/acquirer integration, regional PSP/aggregator, or a more actively maintained Omnipay gateway.

How to Pitch It (Stakeholders)

Executives: This is a small MIT-licensed PHP driver that lets us test UnionPay demand without funding a bespoke integration. Treat it as a tactical enabler for China and cross-border checkout, not a strategic platform bet. Engineering: It plugs into Omnipay, so we can wrap it in a Laravel service and keep payment code behind an abstraction. The main risks are maintenance, incomplete UnionPay product coverage, and compliance/ops work around refunds, reconciliation, and security. Recommend a timeboxed spike with verified supported flows and clear go/no-go criteria before production commitment.