v2.0.0

Package Separation

As of 2.0, Omnipay has been split into separate packages. Core functionality is contained within the omnipay/common repository, and all gateways have their own repositories. This means that if your project only requires on a single gateway, you can load it without installing all of the other gateways. All officially supported gateways can be found under the Omnipay GitHub organization.

If you want to install all gateways, you can still use the omnipay/omnipay metapackage in composer.json:

{
    "require": {
        "omnipay/omnipay": "~2.0"
    }
}

Alternatively, if you want to migrate to an individual gateway, simply change your composer.json file to reference the specific gateway (omnipay/common will be included for you automatically):

{
    "require": {
        "omnipay/paypal": "~2.0"
    }
}

Breaking Changes

The GatewayFactory class can now longer be called in a static fashion. To help those who want to use dependency injection, you can now create an instance of GatewayFactory:

$factory = new GatewayFactory();
$gateway = $factory->create('PayPal_Express');

The following code is invalid and will no longer work:

$gateway = GatewayFactory::create('PayPal_Express'); // will cause PHP error!

If you want to continue to use static methods for simplicity, you can use the new Omnipay class:

// at the top of your PHP file
use Omnipay\Omnipay;

// further down when you need to create the gateway
$gateway = Omnipay::create('PayPal_Express');

Behind the scenes, this will create a GatewayFactory instance for you and call the appropriate method on it.

Additions

Omnipay now supports sending line-item data to gateways. Currently this is only supported by the PayPal gateway. Line item details can be added to a request like so:

$request->setItems(array(
    array('name' => 'Food', 'quantity' => 1, 'price' => '40.00'),
    array('name' => 'Drinks', 'quantity' => 2, 'price' => '6.00'),
));

For more details, see the pull request.

Omnipay now also supports modifying request data before it is sent to the gateway.. This allows you to send arbitrary custom data with a request, even if Omnipay doesn't support a parameter directly. To modify the request data, instead of calling send() directly on the request, you may use the new sendData() method:

// standard method - send default data
$response = $request->send();

// new method - get and send custom data
$data = $request->getData();
$data['customParameter'] = true;

$response = $request->sendData($data);

For more details, see the pull request.

v1.1.0

• Paypal [BC BREAK]: Removed default values for noShipping and allowNote Express Checkout options. To retain previous behavior, pass 'noShipping' => 1 and 'allowNote' => 0 when creating the request. (@aderuwe)
• Add TargetPay gateway (@aderuwe)
• MultiSafepay: Add purchase parameter (@aderuwe)
• MultiSafepay: Add support for directtransaction (@ruudk)
• Authorize.Net SIM: Add support for hash secret (@amsross)
• Authorize.Net AIM: Add extra response getters
• Sage Pay Direct: Don't pass state unless country is US

v1.0.4

• Update Pin gateway to support using JS tokens (@nagash)
• More tests (@johnkary)

v1.0.3

• Stripe: Added fetchTransaction method (@cfreear)
• MultiSafepay: Assorted bug fixes (@aderuwe)
• Sage Pay: Fixed not sending correct card brand for MasterCard and Diners Club (@steveneaston)
• Sage Pay: Fixed RefundRequest not sending correct transaction type

v1.0.2

• Added MultiSafepay gateway
• Added PayPal Subject parameter
• PHPDoc fixes

v1.0.1

• Added Buckaroo gateway
• Added eWAY Rapid 3.0 gateway
• Added getRedirectResponse() method to AbstractResponse
• A few minor bug fixes & typos

v1.0.0

amount is now specified as a decimal (i.e. '10.00' instead of 1000
to represent $10.00. Passing integers will throw an exception, reminding you
to update your application code. To be clear, that means instead of this:

$gateway->purchase(array('amount' => 1000, 'currency' => 'USD'));

You must now create the request like so:

$gateway->purchase(array('amount' => '10.00', 'currency' => 'USD'));

This should avoid any further confusion over how to specify the amount.

• Added Mollie payment gateway
• Added notifyUrl and issuer fields to example app