For the PayU Connection there are two different variants of the interface depending on the countries as well as two manuals. This connection PayU CEE Single is valid only for Poland, Czech and Slovakia. For Hungary, Romania, Russia and Turkey the connection PayU CEE GECAD has to be used. For that a separate manual exist: PayU CEE GECAD.
|
|
PayU CEE Single process flow
In order to process a payment with PayU CEE Single via a form, please use the following URL:
payu.aspx |
There are 3 possible scenarios to process a payment using BLIK OneClik.
This scenario is possible for all merchants.
To use this option, parameter PayType has to be set to "blik" and parameter AuthCode contains valid authorization code. Please note, regards this functionality the customer/client/browser will not be forwarded to the and your shop system will receive only the status by URLNotify response.
This scenario is possible only for merchants, registered as "trusted merchants" on PayU side.
To use this option, parameter PayType has to be set to "blik" and parameter AuthCode has to contain a valid authorization code.
As the merchant is registered as "trusted merchants" on PayU side, after successfull payment a token will be created and registered on PayU side. Registered token is sent in response in scope of JSON object AllowedPayMethods (field "value" contains the token, for details refer to description of JSON object AllowedPayMethods below). Additionally the token can be received by call PayUPayMethods.aspx.
This scenario is possible only for merchants, registered as "trusted merchants" on PayU side.
A token, created using Scenario 2, can be used for further payments.
In this scenario payment request should be sent with parameter PayType equals to "blik", parameter TokenExt and parameter AppKey with values returned in parameter AllowedPayMethods. AllowedPayMethods contains token in field "value" and key is returned in field "key".
|
Parameters for payments with PayU CEE Single
|
Return parameters for URLSuccess, URLFailure and URLNotify with PayU CEE Single
The request returns Blik token associated with the customer in this specific merchant/web shop.
The request can be used to retrieve the token before using it for Blik payment with token (Scenario 3).
PayUPayMethods.aspx |
|
Parameters for Allowed Payment Methods request.
|
Parameters for Allowed Payment Methods response.
In order to process a credit card payment with PayU CEE Single via a form, please use the following URL:
payssl.aspx |
|
Parameters for credit card payments with PayU CEE Single
|
Layout parameters for forms for credit card payments with PayU CEE Single
|
Return parameters for URLSuccess, URLFailure and URLNotify with PayU CEE Single
In order to process a recurring credit card payment with PayU CEE Single via a Server-to-Server connection, please use the following URL:
direct.aspx |
|
Parameters for credit card payments with PayU CEE Single via socket connection
|
Result parameters for socket connection for PayU CEE Single
Captures are possible via a Server-to-Server connection. To carry out a Capture for a credit card payment with PayU CEE Single via a Server-to-Server connection please use the following URL:
capture.aspx |
Parameters for captures of PayU CEE Single via socket connections
|
Response parameters for captures of PayU CEE Single via socket connections
credit.aspx |
|
Parameters for credit payments with PayU CEE Single via socket connection
|
Response parameters for credit payments with PayU CEE Single via socket connection
Reversals are possible via a Server-to-Server connection. To carry out a reversal, please use the following URL:
reverse.aspx |
Notice: Reverse.aspx does not only reverse authorisations, but any LAST TRANSACTION STAGE!! If the last transaction was a capture, Reverse.aspx initiates the reverse, e.g. a credit. Therefore, the utmost caution is urged. Use is at your own risk. We recommend checking the transaction status with Inquire.aspx before using Reverse.aspx.
Parameters for reversals of payments with PayU CEE Single
Response parameters for reversals of payments with PayU CEE Single
This section describes the parameters which must be transferred within the data set (Record) for executing payments / credits with PayU CEE Single and which information can be found within the response file about the payment status.
Following table gives an overview of all batch versions that are possible for a specific action and their specialities:
|
Description of the possible batch versions
The structure for a PayU payment within a Batch file to be submitted is the following:
|
Example for Master MID function:
|
|
Description of fields within the record for Batch files
The record area within the response file for Batch transactions looks as follows:
|
|
Description of result parameters within the record for Batch files