Download the PHP package omnipay/rabobank without Composer
On this page you can find all versions of the php package omnipay/rabobank. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Informations about the package rabobank
Omnipay: Rabobank OmniKassa V2
Rabobank OmniKassa driver for the Omnipay PHP payment processing library
Omnipay is a framework agnostic, multi-gateway payment processing library for PHP PHP. This package implements Rabobank OmniKassa V2 support for Omnipay.
Installation
Omnipay is installed via Composer. To install, simply require league/omnipay
and omnipay/rabobank
with Composer:
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.
- The
Merchant ID
andKey Version
parameters are not needed anymore. The refresh token is the new merchant identification. - It's not possible anymore to provide more then one Payment Method per purchase by separating them with a comma. (eg.
IDEAL,CARDS
) - There is no option anymore for providing a notice URL per purchase. The notice URL needs to be configured in the Omnikassa V2 Dashboard.
- The notify
POST
doesn't have any status information about the order anymore. You can fetch information about orders by making aStatusRequest
. You'll need thenotificationToken
that's received in the notificationPOST
.
Make sure you fetch all open order statuses by checking themoreOrderResultsAvailable
parameter in the response. If set to true, make anotherStatusRequest
with the samenotificationToken
, untilmoreOrderResultsAvailable
isfalse
.
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.