omnipay / eway
eWay driver for the Omnipay payment processing library
Installs: 881 492
Dependents: 5
Suggesters: 0
Security: 0
Stars: 13
Watchers: 7
Forks: 17
Open Issues: 7
Requires
- omnipay/common: ^3
Requires (Dev)
- omnipay/tests: ^3
- phpro/grumphp: ^0.14.0
- squizlabs/php_codesniffer: ^3
README
eWAY driver for the Omnipay PHP payment processing library
Omnipay is a framework agnostic, multi-gateway payment processing library for PHP 5.3+. This package implements eWAY support for Omnipay.
eWay was launched in Australia in 1998 and now operates payment gateways in 8 countries.
Installation
Omnipay is installed via Composer. To install, simply require league/omnipay
and omnipay/eway
with Composer:
composer require league/omnipay omnipay/eway
Basic Usage
The following gateways are provided by this package:
- Eway_Direct -- This gateway is deprecated. If you have existing code that uses it you can continue to do so but you should consider migrating to Eway_RapidDirect
- Eway_RapidDirect -- This is the primary gateway used for direct card processing, i.e. where you collect the card details from the customer and pass them to eWay yourself via the API.
- Eway_Rapid -- This is used for eWAY Rapid Transparent Redirect requests. The gateway is just called Eway_Rapid as it was the first implemented. Like other redirect gateways the purchase() call will return a redirect response and then requires you to redirect the customer to the eWay site for the actual purchase.
- Eway_RapidShared -- This provides a hosted form for entering payment information, other than that it is similar to the Eway_Rapid gateway in functionality.
See the docblocks within the gateway classes for further information and links to the eWay gateway on line.
For general usage instructions, please see the main Omnipay repository.
Support
If you are having general issues with Omnipay, we suggest posting on Stack Overflow. Be sure to add the omnipay tag so it can be easily found.
If you want to keep up to date with release announcements, discuss ideas for the project, or ask more detailed questions, there is also a mailing list which you can subscribe to.
If you believe you have found a bug, please report it using the GitHub issue tracker, or better yet, fork the library and submit a pull request.