omnipay/rabobank

Rabobank Omnikassa driver for the Omnipay payment processing library

v3.0.0-beta1 2018-12-19 13:23 UTC

README

Rabobank OmniKassa driver for the Omnipay PHP payment processing library

Build Status Latest Stable Version Total Downloads

Omnipay is a framework agnostic, multi-gateway payment processing library for PHP 5.6+. This package implements Rabobank OmniKassa V2 support for Omnipay.

Installation

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

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

And run composer to update your dependencies:

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

Basic Usage

The following gateways are provided by this package:

  • Rabobank

For general usage instructions, please see the main Omnipay repository.

Updating to V2

In order to upgrade to Omnikassa V2 you need the following codes:

  • RefreshToken
  • SigningKey

You can look those up in your Omnikassa V2 Dashboard. See the documentation on rabobank.nl.

  1. The Merchant ID and Key Version parameters are not needed anymore. The refresh token is the new merchant identification.
  2. It's not possible anymore to provide more then one Payment Method per purchase by separating them with a comma. (eg. IDEAL,CARDS)
  3. There is no option anymore for providing a notice URL per purchase. The notice URL needs to be configured in the Omnikassa V2 Dashboard.
  4. The notify POST doesn't have any status information about the order anymore. You can fetch information about orders by making a StatusRequest. You'll need the notificationToken that's received in the notification POST.
    Make sure you fetch all open order statuses by checking the moreOrderResultsAvailable parameter in the response. If set to true, make another StatusRequest with the same notificationToken, until moreOrderResultsAvailable is false.

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 anouncements, 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.