Download the PHP package openpayu/openpayu_php_sdk without Composer

Official OpenPayU PHP Library

The OpenPayU PHP library provides integration access to the REST API 2.1

Dependencies

PHP >= 5.3 with extensions cURL and hash

Documentation

Full implementation guide: English, Polish.

To process operations such as:

• order status update
• order retrieve
• order cancel

You will need to provide a parameter called orderId. The value of orderId is your order identifier that is set by PayU Payment system, and it's used to invoke remote methods.

There are two ways to get orderId:

1. It is present inside the received notification message from PayU Payment System as a result of payment.
2. In the response from method OpenPayU_Order::create.

In both cases you will find orderId using this statement: $response->getResponse()->orderId.

Installation

Composer

To install with Composer, simply add the requirement to your composer.json file:

Then install by running

Manual installation

Obtain the latest version of openpayu_php SDK with:

Getting started

If you are using Composer use autoload functionality:

Or simply add this lines anywhere in your application:

Configure

Important: SDK works only with 'REST API' (Checkout) points of sales (POS). If you do not already have PayU merchant account, please register in Production or please register in Sandbox

Example "Configuration keys" from Merchant Panel

To configure OpenPayU environment you must provide a set of mandatory data in config.php file.

For production environment:

For sandbox environment:

If you want to use sandbox environment, register at this link https://secure.snd.payu.com/cp/register?lang=en

OAuth configuration

SDK supports two PayU OAuth grant types: client_credentials and trusted_merchant. Default is client_credentials.

If you want to change grant type use:

grant_type can be one of the following OauthGrantType::CLIENT_CREDENTIAL or OauthGrantType::TRUSTED_MERCHANT

Parameters needed for client_credentials

Parameters needed for trusted_merchant

Connection over Proxy

Cache

OpenPayU library automatically stores OAuth authentication data in the Cache.

OpenPayU library has two classes implemented to manage the Cache:

• OauthCacheFile - data is stored in the file system. This is a default and automatic Cache method which stores the data in lib/Cache folder. ATTENTION: for security reasons it is recommended to change the Cache folder, so it would not be accessible from the web browser.

  Configuration:

  $directory - absolute path to the data folder; if the parameter is missing, the folder is lib/Cache

• OauthCacheMemcached - data is stored in Memcached This method requires Memcached (https://memcached.org/) to be installed on the server along with Memcached PHP module (http://php.net/manual/en/book.memcached.php)

  Configuration:

  $host - Memcached server address - localhost by default $port - Memcached server port - 11211 by default $weight - Memcached server priority - 0 by default

It is possible to implement another method to manage cache. In such a case it needs to implement OauthCacheInterface

Usage

Remember: All keys in "order array" must be in lowercase.

Creating order using REST API

File with working example: examples/v2/order/OrderCreate.php

To create an order using REST API in back-end you must provide an Array with order data:

in your controller

Retrieving order from OpenPayU

File with working example: examples/v2/order/OrderRetrieve.php

You can retrieve order by its PayU order_id

Retrieving transactions for order from OpenPayU

File with working example: examples/v2/order/OrderTransactionRetrieve.php

You can retrieve transactions for order by its PayU order_id

Cancelling order

File with working example: examples/v2/order/OrderCancel.php

You can cancel order by its PayU order_id

Updating order status

File with working example: examples/v2/order/OrderStatusUpdate.php

You can update order status to accept order.

Handling notifications from PayU

File with working example: examples/v2/order/OrderNotify.php

PayU sends requests to your application when order status changes

Refund money

File with working example: examples/v2/refund/RefundCreate.php

You can create refund to refund money on buyer account

Retrieving pay methods from POS

File with working example: examples/v2/retrieve/RetrievePaymethods.php

You can retrieve pay methods from POS

You can add optional parameter lang to payMethods()

Delete card token

File with working example: examples/v2/token/TokenDelete.php

You can delete user's card token.

Token deletion is possible only for trusted_merchant grant type.

Get Shop

File with working example: examples/v2/shops/Get.php

You can retrieve shop data.

Contributing

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request