Documentation

Automatic Live Update (deprecated; use Authorize API V4)

ALU, short for Automatic Live Update, is intended for merchants who want to place transactions directly in the PayU system. The main advantage that ALU presents is that it allows the Merchant to also send the Shopper card data.

• Go to Automatic Live Update V1 Documentation
• Go to Automatic Live Update V2 Documentation
• Go to Automatic Live Update V3 Documentation

Card Info API (deprecated; use CardInfo API V4)

Card Info API represents the automated way of retrieving informations abount a given BIN.

• Go to Card Info V2 API Documentation

Instant Payment Notification (deprecated; use Notification API V4)

For an authorized and authenticated order, the PayU server will send to a predefined URL an HTTP POST which encapsulates a data structure with all data referencing that order. That information will be assigned a signature for authentication. The signature is realized using an HMAC_MD5 signature and a common secret key established between PayU and the seller. The HMAC algorithm is applied to all data set.

• Go to Instant Payment Notification Documentation

Instant Delivery Notification (deprecated; use Capture API V4)

The Instant Delivery Notification facilitates automatic delivery confirmations from your system directly to the PayU system which automatically registers these confirmations on the PayU servers. As soon as your orders made to the PayU system are confirmed, a POST must be sent through your administration system to a URL provided by PayU, containing the identification data for transaction about to be confirmed.

• Go to Instant Delivery Notification Documentation

Instant Refund/Reverse Notification (deprecated; use Refund API V4)

Instant Refund/Reverse Notification (IRN) makes it possible for you to automate the sending of reverse/refund requests for orders paid through PayU, directly from the order management application/platform.

The process requires the sending of the order information through HTTP POST, validated with a HMAC_MD5, to the following URL: https://secure.payu.ro/order/irn.php

This process has to be executed for each order where an order reversal, partial refund or total refund of the paid amount is required.

• Go to Instant Reverse/Refund Notification Documentation

Instant Order Status (deprecated; use Status API V4)

Instant Order Status (IOS) makes it possible to query the PayU platform for the status of an order.

IOS can be triggered through HTTP POST or HTTP GET by accessing: https://secure.payu.ro/order/ios.php.

The query of the PayU database will be made individually, for one order at a time.

• Go to Instant Order Status Documentation

Live Update

For each customer that clicks the "Checkout" button in the merchant's website (or mobile application), an HTTP POST must be initiated to https://secure.payu.ro/order/lu.php using the LiveUpdate (LU) API, in order for the order to get started. The customer is then redirected to the PayU payment pages, where he has to enter the data required to authorize the transaction.

• Go to Live Update Documentation

Payment page

The customer enters his card data (card number, expiration date, security code, card holder's name) and installment options, if available. After the payment is processed, the customer will be redirected back to the Merchant using the HTTP POST request method, among a set of return parameters.

• Go to Payment page Documentation

Reports API

The reports API provides methods for accessing merchant reports such as order reports, products reports or operator reports.
All API requests are made using the HTTPs GET protocol.
All API responses are in JSON format, except the operator report download method that returns the specified operator report in PDF format.

• Go to Reports API Documentation

Token Payments (deprecated; use Token API V4)

Token payments are an alternate way of doing online transactions. Assigning a token to a new transaction will enable future automatic processing for the same client.

An initial transaction can be used to create a token, offering a way to remember the customer and handle future automatic payments. Using this unique identifier, merchants will be able to handle future transactions for the same client/credit card, regardless of the transaction amount.

• Go to Token Payments V1 Documentation
• Go to Token Payments V2 Documentation

Merchant Transfers API

The Transfers API offers the functionality of retrieving information about merchant transfers.

• Go to Merchant Transfers API Documentation

FX API

The FX feature allows for completing payments by using different currencies than the order's currency. This can help your international buyers to understand the total price that they are going to pay, but converted to their own card's currency.

• Go to FX API Documentation

API limits

PayU API methods might have specific limits for each type of request.

• Go to API limits Documentation

Sandbox Integration

• Go to Sandbox Integration Documentation

API V4

This collection of APIs is used to interact with PayU for processing payments.

• Go to API V4 Documentation