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 GECAD is valid for Hungary, Romania, Russia and Turkey. For Poland, Czech and Slovakia the connection PayU CEE Single has to be used. For that a separate manual exist: PayU CEE Single.
|
PayU CEE GECAD process flow
Process flow PayU CEE GECAD via form interface payssl.aspx
Process flow PayU CEE GECAD via server-to-server interface direct.aspx
For configuring PayU CEE GECAD some settings are necessary in the PayU back end. Calling the back end is carried out by calling the respective URL for each country:
Romania: https://secure.payu.ro/cpanel/
Russian Federation: https://secure.payu.ru/cpanel/
Hungary: https://secure.payu.hu/cpanel/
Turkey: https://secure.payu.com.tr/cpanel/
Activate the tab Account settings at System settings. In the section of notifications IPN or Email Text & IPN must be selected. Additionally the options Canceled and returned orders and Complete orders must be activated.
Now go to the tab IPN settings. Within the URL field enter the modified link in that form payuceecomplete.aspx?merchantid=MID, but you must insert your own MID.
Furthermore the parameters REFNO, REFNOEXT, ORDERSTATUS, IPN_TOTALGENERAL and CURRENCY must be activated.
In the back end of PayU CEE GECAD additional parameters can be created. They will be displayed on the payment page and can/must be filled in by the customer.
If Customfields is selected within IPN Settings, will forward these parameters to the merchant.
To make a payment with PayU CEE GECAD, please use the following URL:
payucee.aspx |
|
Parameters for payments with PayU CEE GECAD
|
Response parameters for URLSuccess and URLFailure with PayU CEE GECAD
The following table gives the results parameters which the transfers to URLNotify:
|
Return parameters for URLNotify with PayU CEE GECAD
Following table gives an overview of supported card programmes for instalment payments. Please note that new programmes can be added and the participating banks can be changed.
Card programme | Issuer |
---|---|
Advantage | T. İŞ BANKASI A.Ş. |
AsyaCard | ASYA KATILIM BANKASI A.Ş. |
Axess | AKBANK T.A.Ş. |
Bonus | TÜRK EKONOMİ BANKASI A.Ş. |
Cardfinans | FİNANS BANK A.Ş. |
Maximum | T.C.ZİRAAT BANKASI A.Ş. |
Paraf | T.HALK BANKASI A.Ş. |
World | T.VAKIFLAR BANKASI T.A.O. |
Supported card programmes for instalment payments
In order to process a SSL credit card payment with PayU CEE GECAD via a form, please use the following URL:
payssl.aspx |
|
Parameters for credit card payments with PayU CEE GECAD
|
Layout parameters for forms for credit card payments with PayU CEE GECAD
|
Return parameters for URLSuccess, URLFailure and URLNotify with PayU CEE GECAD
In order to execute an SSL credit card payment with PayU CEE GECAD via a server-to-server connection, please use the following URL:
direct.aspx |
|
Parameters for credit card payments with PayU CEE GECAD via socket connection
|
Result parameters for socket connection with PayU CEE GECAD
Captures are possible via a Server-to-Server connection. To carry out a Capture for a credit card payment with PayU CEE GECAD via a Server-to-Server connection, please use the following URL:
capture.aspx |
|
Parameters for captures of PayU CEE GECAD via socket connections
|
Response parameters for captures of PayU CEE GECAD via socket connections
credit.aspx |
|
Parameters for credit payments with PayU CEE GECAD via socket connection
|
Response parameters for credit payments with PayU CEE GECAD via socket connection
This section describes the parameters which must be transferred within the data set (Record) for executing payments / credits with PayU CEEE GECAD 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 CEE 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