Securepay Laravel Package

Product Decisions This Supports

• Market expansion into Australia/NZ: SecurePay is an established Australian gateway (Australia Post-owned). If the roadmap includes accepting AUD or serving Australian customers, this driver is a low-cost path to validating demand before funding a bespoke integration.
• Build vs. buy for payments: Omnipay provides a gateway-agnostic interface (purchase, authorize, capture, refund, void). Adopting this driver means buying the protocol glue instead of building SecurePay's request/signing/response handling in-house — days of integration work rather than weeks.
• Multi-gateway and regional routing strategy: Because Omnipay normalizes gateway APIs, product can support SecurePay alongside a primary processor — as a regional option, a fallback, or a lever in rate negotiations — without rewriting checkout per gateway.
• Checkout feature scoping: The driver covers standard card transaction flows, which is enough to prioritize "accept payments" for an MVP. It does not abstract subscriptions, card vaulting, dunning, or rich webhook tooling — so it directly informs decisions about what must be built around it (billing engine, stored-card handling, reconciliation jobs).
• Laravel roadmap fit: Laravel Cashier has no first-class SecurePay support, so this package (via a thin Laravel/Omnipay bridge) is the shortest path to SecurePay inside a Laravel app — a small, reversible buy decision rather than a platform commitment.
• Concrete use cases: one-off purchases, direct-API or hosted card payments, authorize/capture flows for e-commerce, refund handling in back-office tooling, and regional pilot launches.
• The real decision: with 13 stars and a last release in 2018, the product question isn't "should we use this?" but "do we adopt it as an owned/forked dependency, or budget for a direct integration?" That framing belongs in the roadmap review.

When to Consider This Package

Adopt when:

• You already hold (or are contractually required to use) a SecurePay merchant account, or SecurePay is the commercially preferred processor for Australian customers.
• Your stack is PHP — ideally Laravel — and you're comfortable adding a Composer dependency behind your own service abstraction.
• You need standard card transactions (purchase, authorize/capture, refund, void) and can build subscription or vaulting logic yourself, or do without it.
• Speed to market matters more than long-term maintenance elegance — a pilot or market-validation launch where time-to-learn beats time-to-polish.
• You're willing to pin the version, wrap it in an internal PaymentGateway contract, and treat the driver as replaceable.

Look elsewhere when:

• You need active maintenance, security-patch SLAs, or vendor support. The package is effectively unmaintained since 2018 with a negligible community; compliance-sensitive contexts (PCI DSS, SOC 2) should fork and own it, or integrate SecurePay's official API directly.
• You need subscriptions, tokenization/vaulting, partial refunds at scale, or rich webhook handling — model those around Omnipay itself or choose a modern provider SDK.
• Your stack isn't PHP, or you need managed checkout surfaces (hosted fields, Apple Pay/Google Pay) the driver doesn't abstract.
• Your PHP or Laravel versions are recent — a stale driver can silently become an upgrade tax; verify the compatibility matrix before committing.
• SecurePay isn't a specific requirement: for Stripe, Adyen, or Braintree, use their maintained SDKs instead.

How to Pitch It (Stakeholders)

For executives: This is a small, MIT-licensed adapter that lets our Laravel application accept payments through SecurePay, an established Australian gateway. It is a low-cost way to test the Australian market or satisfy an existing SecurePay commercial relationship without building a payment integration from scratch. The trade-off is that it's a low-profile, unmaintained open-source component (last release 2018, 13 stars), so we should treat it as a tactical accelerator rather than a strategic platform. Recommendation: adopt behind an internal payment abstraction, pin the version, and budget a small amount of engineering ownership — or a fork — to cover security patches and API drift.

For engineering: Omnipay gives us a uniform gateway API; this driver implements SecurePay's protocol on top of it. We'll isolate it behind our own PaymentGateway contract so we can swap to SecurePay's direct API or another Omnipay driver without touching checkout code. Expect to verify PHP/Laravel compatibility, add tests around the transaction flows we rely on, and own patching. Integration cost is days, not weeks — the ongoing maintenance is the real line item.