Eway Laravel Package

Product Decisions This Supports

• Payment provider support for Australia/NZ: Enables eWay as a checkout option where customer demand or local market requirements justify it, especially for existing Omnipay-based systems.
• Build vs. buy for payment integrations: Informs whether to adopt a community Omnipay driver versus building against eWay’s official SDK/API or selecting a more actively maintained gateway package.
• Legacy roadmap and technical debt: Supports decisions about maintaining, isolating, replacing, or retiring an existing eWay integration in a Laravel/PHP application.
• Migration planning: Helps assess the cost of moving from Omnipay/eWay to a modern provider SDK, hosted checkout, or payment orchestration layer.
• Risk review for PCI/payment flows: Flags maintenance, security, and compliance concerns before committing roadmap capacity to a low-adoption, stale driver.

When to Consider This Package

• You already use Omnipay in a Laravel/PHP application and need an eWay driver with minimal integration churn.
• You have an existing eWay merchant account and a legacy integration that must keep working while a replacement is planned.
• Transaction volume and exposure are limited, and the integration can be isolated behind an internal payment abstraction.
• You can perform due diligence on eWay API compatibility, supported payment methods, 3-D Secure/SCA requirements, refunds, and webhook behavior.
• You are prepared to fork, patch, or wrap the package because the last release was in 2019 and community adoption is low.

Look elsewhere if:

• You are building a new payment integration and can use eWay’s official SDK/API or a modern Laravel payment package.
• You need active maintenance, security patching, modern PHP/Laravel support, or clear vendor backing.
• You require hosted checkout, tokenization, subscriptions, complex fraud controls, or multi-gateway routing.
• You are not already standardized on Omnipay and would be adding it solely for this driver.
• Compliance or procurement requires a supported, actively maintained payment dependency.

How to Pitch It (Stakeholders)

Executive summary: omnipay/eway is a small MIT-licensed driver that lets an Omnipay-based PHP application connect to eWay. It may be useful for maintaining an existing eWay integration or supporting an Australia/NZ payment option with minimal code changes. However, it is not a strategic new-build choice: it has very low adoption, no recent releases since 2019, and no obvious active maintenance signal. For new work, engineering should evaluate eWay’s official SDK/API or a maintained Laravel payment package. If we proceed, treat it as a contained legacy dependency with an owner, compatibility tests, and a replacement plan.

For engineering: Use it only behind a payment abstraction, pin the dependency, add integration tests for authorize/capture/refund/webhook flows, verify supported eWay API versions and PHP/Laravel compatibility, and document a fork/patch path. Avoid spreading Omnipay/eWay calls throughout the codebase.

For product/roadmap: This package does not unlock new product capabilities by itself; it supports an eWay payment option or legacy continuity. Prioritize it only if eWay is required for market coverage or existing merchant commitments. Otherwise, spend roadmap capacity on a better-supported provider integration.