Sagepay Laravel Package

Product Decisions This Supports

• Feature: Add Sage Pay/Opayo card payments to a Laravel/PHP checkout without building raw gateway protocol handling. The driver can support common flows such as purchase, authorize, capture, refund, and void where implemented; validate exact methods, 3DS/SCA behavior, and hosted/redirect support before committing.
• Roadmap: Prioritize UK/Ireland payment coverage or retain existing Sage Pay/Opayo customers. If the product already uses Omnipay, this is a low-incremental-cost adapter. If greenfield, compare against Opayo/Elavon native SDKs or hosted checkout before choosing this path.
• Build vs buy: Buy the gateway protocol layer via this MIT package; build the Laravel integration layer yourself: config, routes, webhook handling, idempotency, reconciliation, logging, and operational runbooks. It is not a turnkey Laravel payment module.
• Use cases: One-time card checkout, admin capture/refund workflows, hosted or server-to-server payment flows, and migrations from legacy Sage Pay forms. Treat tokenization, subscriptions, and advanced fraud tooling as separate validation items.
• Risk: Low community footprint and a non-Laravel-native design mean the team owns integration quality and maintenance. Payment compliance, PCI scope, and gateway account obligations remain product responsibilities.

When to Consider This Package

Consider it when:

• The target gateway is confirmed as Sage Pay/Opayo/Elavon and the merchant account supports the required payment methods.
• The application is PHP/Laravel and can adopt the Omnipay abstraction with a small application-level wrapper.
• The team values an MIT-licensed adapter, forkability, and avoiding a custom gateway protocol build.
• Basic card flows are sufficient, or required capabilities such as 3DS/SCA, refunds, and webhooks are verified in the driver version.
• Hosted/redirect payment pages are acceptable and can help reduce PCI scope.

Look elsewhere when:

• You need a vendor-supported SLA, a modern native SDK, or a Laravel-native package with service providers, admin UI, and migrations.
• You need advanced capabilities not proven in the driver: tokenization, recurring billing, partial refunds, multi-currency complexity, marketplace splits, or sophisticated payment orchestration.
• The gateway roadmap is uncertain, the account is migrating to another Elavon/Opayo API, or the product needs global payment methods.
• The team cannot own payment security, idempotency, webhook verification, reconciliation, and ongoing dependency maintenance.

How to Pitch It (Stakeholders)

Executives: This is a small, MIT-licensed adapter that can add Sage Pay/Opayo card payments for UK/Ireland customers faster and cheaper than a custom gateway build, with exit options through Omnipay and the ability to fork. It is not a managed payment service: we still own compliance, reconciliation, and maintenance. Approve a short spike to validate account compatibility, 3DS/SCA, refunds, and webhook flows before committing it to the roadmap.

Engineering: Install via Composer, pin the version, wrap it in an application payment service, keep credentials server-side, prefer hosted/server integration to limit PCI scope, implement idempotency and webhook verification, add sandbox integration tests, and monitor upstream releases. Treat the package as protocol code; own the Laravel glue and operational runbooks.