digitickets/omnipay-verifone-web-service

Verifone (Ocius) Web Service driver for the Omnipay payment processing library

v1.0.5 2017-11-30 06:17 UTC

README

Verifone Web Service driver for the Omnipay PHP payment processing library

Omnipay implementation of the Verifone (Commidea) Web Service payment gateway.

Build Status Latest Stable Version Total Downloads

This driver supports the remote Verifone Payment Gateway (Web Service). Payment information is sent and received via XML messages.

Installation

Important: Driver requires PHP's Intl extension to be installed.

The Verifone Omnipay driver is installed via Composer. To install, simply add it to your composer.json file:

{
    "require": {
        "digitickets/omnipay-verifone-web-service": "~1.0"
    }
}

And run composer to update your dependencies:

$ curl -s http://getcomposer.org/installer | php
$ php composer.phar update

What's Included

This driver was originally written to support Session-Based transactions (except for refunds, which are non session-based and were implemented). We then realised that Session-based didn't work for us, so Non Session-Based was implemented.

The driver registers a token when any purchase is made. This means repeat payments will be available on any payments, although actually making repeat payments is not yet implemented.

What's Not Included

It does not currently support PAYERAUTH.

The Session-based code wasn't completely finished, although it does work as it is. Ideally the token registration and confirm/reject messages need to be handled inside the purchase/refund request classes.

Basic Usage

This driver supports the following processes to handle transactions and refunds:

Non Session-based

Purchase Request (Transaction Request) -> Purchase Response (plus confirm/reject request)

Refund Request (Transaction Request) -> Refund Response (plus confirm/reject request)

Session-based

Generate Session Request -> Generate Session Response
-> <card form submission to Verifone>
-> Get Card Details Request -> Get Card Details Response
-> Token Registration Request -> Token Registration Response [optional step]
-> Purchase Request -> Purchase Response
Then one of:
-> Confirm Request -> Confirm Response
or
-> Reject Request -> Reject Response

For general Omnipay 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 believe you have found a bug in this driver, please report it using the GitHub issue tracker, or better yet, fork the library and submit a pull request.