Maintenance Work Notice!

We will carry out maintenance work on this documentation on Tuesday, 15.06.2021 between 3 pm and 4 pm CEST. Thank you for your understanding.

Page tree

Search

Skip to end of metadata
Go to start of metadata


About PayU CEE Single

General information about payment methods via PayU CEE Single

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 and Czech. For Hungary, Romania, Russia and Turkey the connection PayU CEE GECAD hast to be used. For that a separate manual exist.


Logo

Info

PayU is the leading wallet system in Poland. Merchants can offer the comprehensive payment services via the Paygate in Eastern Europe and further countries as well and thus reach over 500 million potential customers.

TypeMixed payment methods EN

Card Scheme
VISA
MasterCard

Process flow chart

PayU CEE Single process flow


Paygate interface

Definitions

Data formats

Format

Description

a

alphabetical

as

alphabetical with special characters

n

numeric

an

alphanumeric

ans

alphanumeric with special characters

ns

numeric with special characters

bool

boolean expression (true or false)

3

fixed length with 3 digits/characters

..3

variable length with maximum 3 digits/characters

enum

enumeration of allowed values

dttm

ISODateTime (YYYY-MM-DDThh:mm:ss)


Abbreviations

Abbreviation

Description

Comment

CND

condition


M

mandatory

If a parameter is mandatory, then it must be present

O

optional

If a parameter is optional, then it can be present, but it is not required

C

conditional

If a parameter is conditional, then there is a conditional rule which specifies whether it is mandatory or optional


Notice: Please note that the names of parameters can be returned in upper or lower case.


Payment with PayU CEE Single via Paygate form interface

In order to process a payment with PayU CEE Single via a Paygate form, go to the following URL:


Notice: For security reasons, Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter.

The following table describes the encrypted payment request parameters:

Parameter

Format

CND

Description

MerchantID

ans..30

M

MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too.

TransID

ans..64

M

Merchant transaction number, which must be unique

RefNr

ans..30

O

Unique reference number

Amount

n..10

M

Amount in the smallest currency unit (e.g. PLN Grosz)

Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit).

Currency

a3

M

Currency, three digits DIN / ISO 4217. Presently only PLN and CZK allowed.

MAC

an64

M

Hash Message Authentication Code (HMAC) with SHA-256 algorithm

URLSuccess

ans..256

M

Complete URL which calls up Paygate if payment has been successful. The URL may be called up only via port 443 This URL may not contain parameters: In order to exchange values between Paygate and shop, please use the parameter UserData.

URLFailure

ans..256

M

Complete URL which calls up Paygate if payment has been unsuccessful. The URL may be called up only via port 443 This URL may not contain parameters: In order to exchange values between Paygate and shop, please use the parameter UserData.

Response

a7

O

Status response sent by Paygate to URLSuccess and URLFailure, should be encrypted. For this purpose, transmit Response=encrypt parameter.

URLNotify

ans..256

M

Complete URL which Paygate calls up in order to notify the shop about the payment result. The URL may be called up only via port 443 It may not contain parameters: Use the UserData parameter instead.

UserData

ans..1024

O

If specified at request, Paygate forwards the parameter with the payment result to the shop

ReqID

ans..32

O

To avoid double payments, enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction is submitted again with the same ReqID, Paygate will not carry out the payment, but will just return the status of the original transaction. Please note that the Paygate must have a finalized transaction status for the first initial action. Submissions with identical ReqID for an open status will be processed regularly.

Capture

ans..6

O

Determines the type and time of capture. AUTO: capturing immediately after authorisation (default value). MANUAL: capturing made by the merchant. <Number>: Delay in hours until the capture (whole number; 1 to 696).

OrderDesc

ans..35

M

Description of purchased goods, unit prices etc.

The first 27 characters appear on the customer-account statement.

OrderDesc2

ans..384

O

Quantity and description of the goods purchased, unit prices. Comma-delimited list, no special characters permitted.

ArticleList

ans..1024

M

Article list. These parameters must have the following structure:

Product name,unit price,number

Several articles can be separated with a +, e.g.: iPhone,700,1+Samsung Galaxy,700,2

The sum of prices must be equal to the parameter Amount. If you need to disable this check (e.g. for processing of gift cards) please contact the helpdesk and also PayU support.

PayType

ans..4

O

Payment method to be used. Possible values can be found in the list http://developers.payu.com/en/quick_start.html#introduction_paymenttypes at name.

AuthCode

n6

O

For payment method BLIK an AuthCode can be transmitted. If it is not transmitted the customer will be redirected to an appropriate page.

Timeout

n..3

O

Time span in seconds within the payment must be executed

Language

a2

O

ISO code for language; currently only en, pl, cs permitted

Plain

ans..50

O

A value to be set by the merchant to return some information unencrypted, e.g. the MID

Custom

ans..1024

O

The merchant can submit several values separated by | which are returned unencrypted and separated by &.

Custom=session=123|id=456 will change in the answer to Session=123&id=456

Purchaser data

FirstName

ans..100

M

First name of the customer

LastName

ans..100

M

Last name of the customer

Email

ans..100

M

Email address of the customer

Phone

ans..100

C

Customer’s phone number, mandatory in case of payment type TWISTO (PayType=dpcz)

SocialSecurityNumber

ans..100

O

Social security number

Delivery data

sdName

ans..100

C

Name.

In case of payment type TWISTO (PayType=dpcz) PayU recommends the submission, which can have impacts on the Scoring Result.

sdStreet

ans..100

C

Street name and street number

If Name is transmitted this parameter must be transmitted too.

In case of payment type TWISTO (PayType=dpcz) PayU recommends the submission, which can have impacts on the Scoring Result.

sdAddressAddition

ans..100

O

Address c/o

sdZIP

ans..10

C

Postcode

If Name is transmitted this parameter must be transmitted too.

In case of payment type TWISTO (PayType=dpcz) PayU recommends the submission, which can have impacts on the Scoring Result.

sdCity

ans..100

C

Town

If Name is transmitted this parameter must be transmitted too.

In case of payment type TWISTO (PayType=dpcz) PayU recommends the submission, which can have impacts on the Scoring Result.

sdCountryCode

a..3

C

Country code (2 or 3 digits according to ISO 3166-1 alpha-2, alpha-3)

If Name is transmitted this parameter must be transmitted too.

In case of payment type TWISTO (PayType=dpcz) PayU recommends the submission, which can have impacts on the Scoring Result.

sdState

ans..100

O

Federal state

sdEmail

ans..100

O

E-mail address

sdPhone

ans..100

O

Telephone number

sdPOBox

ans..100

O

PO box

ShippingData

ans..256

C

Selection of shipping provider.

This parameter must have the following structure:

Country,Price (in smallest currency unit),Name

Several selection possibilities can be separated with a +.

e.g. PL,700,UPS+PL,600,DHL

In case of payment type TWISTO (PayType=dpcz) PayU recommends the submission, which can have impacts on the Scoring Result.

Invoice data

bdName

ans..100

O

Name

bdStreet

ans..100

C

Street name and street number

If Name is transmitted this parameter must be transmitted too

bdAddressAddition

ans..100

O

Address c/o

bdZIP

ans..10

C

Postcode

If Name is transmitted this parameter must be transmitted too

bdCity

ans..100

C

Town

If Name is transmitted this parameter must be transmitted too

bdCountryCode

a..3

C

Country code (2 or 3 digits according to ISO 3166-1 alpha-2, alpha-3)

If Name is transmitted this parameter must be transmitted too

bdState

ans..100

O

Federal state

bdEmail

ans..100

O

E-mail address

bdPhone

ans..100

O

Telephone number

bdPOBox

ans..100

O

PO box

TaxNumber

n..30

O

National Identification Number (tax number)

InvoiceFlag

n1

O

Defines if tick for invoice dispatch is displayed on the PayU page.

1 = tick is displayed

0 = tick is not displayed

Parameters for payments with PayU CEE Single


The following table describes the result parameters that the Paygate transmits to your URLSuccess, URLFailure or URLNotify. If you have specified the Response=encrypt parameter, the following parameters are forwarded Blowfish encrypted to your system:

Parameter

Format

CND

Description

MID

ans..30

M

MerchantID, assigned by Computop

PayID

an32

M

ID assigned by Paygate for the payment, e.g. for referencing in batch files.

XID

an32

M

ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate

TransID

ans..64

M

Merchant’s transaction number

RefNr

ans..30

O

Merchant’s unique reference number

Status

a..30

M

OK, FAILED or AUTHORIZE_REQUEST.

If 10 seconds after the redirect to CallBack page no notify is received from PayU, the status “AUTHORIZE_REQUEST”, Code “00000000” and Description ”REQUEST” is submitted to the URLSuccess.

Please note, the status “AUTHORIZE_REQUEST” will be sent only to URLSuccess and there is no call of URLNotify.

Should Computop Paygate receive a further final PayU status for this open payment, it will be sent separately via URLNotify. If you don't want to process a separate final status via URLNotify this open payment can be cancelled via calling reverse.aspx and should PayU nevertheless receive a revenue this will automatically be refunded to the customer.

Description

ans..1024

M

Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis!

Code

n8

M

Error code according to Paygate Response Codes (A4 Error codes)

CodeExt

n..10

O

Error code from PayU, if agreed with Computop support

ErrorText

ans..256

O

Error text from PayU, if agreed with Computop support

UserData

ans..1024

O

If specified at request, Paygate forwards the parameter with the payment result to the shop

MAC

an64

M

Hash Message Authentication Code (HMAC) with SHA-256 algorithm

Plain

ans..50

O

A value to be set by the merchant to return some information unencrypted, e.g. the MID

Custom

ans..1024

O

The merchant can submit several values separated by | which are returned unencrypted and separated by &.

Custom=session=123|id=456 will change in the answer to

Session=123&id=456

TransactionID

ans..32

O

ID for identification with PayU

AmountAuth

n..10

M

Authorized amount in the smallest currency unit (e.g. PLN Grosz)

AmountCap

n..10

M

Captured amount in the smallest currency unit (e.g. PLN Grosz)

AmountCred

n..10

M

Credited amount in the smallest currency unit (e.g. PLN Grosz)

Return parameters for URLSuccess, URLFailure and URLNotify with PayU CEE Single



Credit card payment with PayU CEE Single via Paygate form interface

In order to process a credit card payment with PayU CEE Single via a Paygate form, go to the following URL:


Notice: For security reasons, Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter.

The following table describes the encrypted payment request parameters:

Parameter

Format

CND

Description

MerchantID

ans..30

M

MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too.

TransID

ans..64

M

Merchant transaction number, which must be unique

RefNr

ns..30

O

Unique reference number which appears on your printed card account or in the EPA-file (Electronic Payment Advice). Format must be mutually agreed beforehand with Computop!

Amount

n..10

M

Amount in the smallest currency unit (e.g. PLN Grosz)

Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit).

Currency

a3

M

Currency, three digits DIN / ISO 4217

MAC

an64

M

Hash Message Authentication Code (HMAC) with SHA-256 algorithm

URLSuccess

ans..256

M

Complete URL which calls up Paygate if payment has been successful. The URL may be called up only via port 443 This URL may not contain parameters: In order to exchange values between Paygate and shop, please use the parameter UserData.

URLFailure

ans..256

M

Complete URL which calls up Paygate if payment has been unsuccessful. The URL may be called up only via port 443 This URL may not contain parameters: In order to exchange values between Paygate and shop, please use the parameter UserData.

Response

a7

O

Status response sent by Paygate to URLSuccess and URLFailure, should be encrypted. For this purpose, transmit Response=encrypt parameter.

URLNotify

ans..256

M

Complete URL which Paygate calls up in order to notify the shop about the payment result. The URL may be called up only via port 443 It may not contain parameters: Use the UserData parameter instead.

UserData

ans..1024

O

If specified at request, Paygate forwards the parameter with the payment result to the shop

ReqID

ans..32

O

To avoid double payments, enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction is submitted again with the same ReqID, Paygate will not carry out the payment, but will just return the status of the original transaction. Please note that the Paygate must have a finalized transaction status for the first initial action. Submissions with identical ReqID for an open status will be processed regularly.

RTF

a1

O

„I“ for initializing recurrent payments

OrderDesc

ans..35

M

Description of purchased goods, unit prices etc.

The first 27 characters appear on the customer-account statement.

OrderDesc2

ans..384

O

Quantity and description of the goods purchased, unit prices. Comma-delimited list, no special characters permitted.

Plain

ans..50

O

A value to be set by the merchant to return some information unencrypted, e.g. the MID

Custom

ans..1024

O

The merchant can submit several values separated by | which are returned unencrypted and separated by &.

Custom=session=123|id=456 will change in the answer to Session=123&id=456

Purchaser data

FirstName

ans..100

M

First name of the customer

LastName

ans..100

M

Last name of the customer

Email

ans..100

M

Email address of the customer

Phone

ans..100

O

Customer’s phone number

SocialSecurityNumber

ans..100

O

Social security number

Delivery data

sdName

ans..100

O

Name

sdStreet

ans..100

C

Street name and street number

If Name is transmitted this parameter must be transmitted too

sdAddressAddition

ans..100

O

Address c/o

sdZIP

ans..10

C

Postcode

If Name is transmitted this parameter must be transmitted too

sdCity

ans..100

C

Town

If Name is transmitted this parameter must be transmitted too

sdCountryCode

a..3

C

Country code (2 or 3 digits according to ISO 3166-1 alpha-2, alpha-3)

If Name is transmitted this parameter must be transmitted too

sdState

ans..100

O

Federal state

sdEmail

ans..100

O

E-mail address

sdPhone

ans..100

O

Telephone number

sdPOBox

ans..100

O

PO box

Invoice data

bdName

ans..100

O

Name

bdStreet

ans..100

C

Street name and street number

If Name is transmitted this parameter must be transmitted too

bdAddressAddition

ans..100

O

Address c/o

bdZIP

ans..10

C

Postcode

If Name is transmitted this parameter must be transmitted too

bdCity

ans..100

C

Town

If Name is transmitted this parameter must be transmitted too

bdCountryCode

a..3

C

Country code (2 or 3 digits according to ISO 3166-1 alpha-2, alpha-3)

If Name is transmitted this parameter must be transmitted too

bdState

ans..100

O

Federal state

bdEmail

ans..100

O

E-mail address

bdPhone

ans..100

O

Telephone number

bdPOBox

ans..100

O

PO box

TaxNumber

n..30

O

National Identification Number (tax number)

Parameters for credit card payments with PayU CEE Single


To adapt the layout of the SSL-page to your shop you can use the following unencrypted parameters to configure colours, fonts and images.

Parameter

Format

CND

Description

Template

ans..20

M

Name of XSLT-file with your own layout for the pay form. If you want to use the redesigned and downwards compatible Computop template, please transfer the template name “ct_compatible”. If you want to use the responsive Computop template for mobile devices, please transfer the template name “ct_responsive”.

Background

ans..256

M

Background ambiance of form:

URL for a background image

- HTML-colour value for background colour as HEX value or

- HTML-colour name

BGColor

ans..7

M

Form background colour:

- HTML-colour value for background colour as HEX value or

- HTML-colour name

BGImage

ans..256

M

Form background image:

URL for a background image

Please note that this value supersedes “BGColor”.

FColor

ans..6

M

Text colour:

- HTML-colour value as HEX value or

- HTML-colour name

FFace

a..10

M

HTML-name for the font

FSize

n2

M

Number for font size

Language

a2

(enum)

M

Language code: <de> German, <al> Albanian, <at> Austrian, <cz/cs> Czech, <dk> Danish, <en> English, <fi> Finish, <fr> French, <gr> Greek, <hu> Hungarian, <it> Italian, <jp> Japanese,  <nl> Dutch, <no> Norwegian, <pl> Polish, <pt> Portuguese, <ro> Romanian, <ru> Russian, <es> Spanish, <se> Swedish, <sk> Slovakian, <sl> Slovenian, <tr> Turkey, <zh> Simplified Chinese.

No details means the language is German.

CCSelect

a..16

M

Determines preselected card type in the form: VISA, AMEX, JCB, DINERS, MasterCard, Cartes Bancaires, Bancontact, Maestro, Dankort, Hipercard, CBN, Airplus, ComfortCard, Discover, Elo, Auro, CUP

URLBack

ans..256

M

URL for "Cancel" button

Center

n1

M

By default the form is centered vertically and horizontally. The value <1> centres the form at the top.

tWidth

ans..4

M

Width of table for input of the credit card data as percent- (50%) or pixel values (320).

tHeight

ans..4

M

Height of table for input of the credit card data as percent- (70%) or pixel values (480).

Layout parameters for Paygate forms for credit card payments with PayU CEE Single


The following table describes the result parameters that the Paygate transmits to your URLSuccess, URLFailure or URLNotify. If you have specified the Response=encrypt parameter, the following parameters are forwarded Blowfish encrypted to your system:

Parameter

Format

CND

Description

MID

ans..30

M

MerchantID, assigned by Computop

PayID

an32

M

ID assigned by Paygate for the payment, e.g. for referencing in batch files.

XID

an32

M

ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate

TransID

ans..64

M

Merchant’s transaction number

RefNr

ans..30

O

Merchant’s unique reference number

Status

a..30

M

OK, FAILED or AUTHORIZE_REQUEST.

If 10 seconds after the redirect to CallBack page no notify is received from PayU, the status “AUTHORIZE_REQUEST”, Code “00000000” and Description ”REQUEST” is submitted to the URLSuccess.

Please note, the status “AUTHORIZE_REQUEST” will be sent only to URLSuccess and there is no call of URLNotify.

Should Computop Paygate receive a further final PayU status for this open payment, it will be sent separately via URLNotify. If you don't want to process a separate final status via URLNotify this open payment can be cancelled via calling reverse.aspx and should PayU nevertheless receive a revenue this will automatically be refunded to the customer.

Description

ans..1024

M

Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis!

Code

n8

M

Error code according to Paygate Response Codes (A4 Error codes)

CodeExt

n..10

O

Error code from PayU, if agreed with Computop support

ErrorText

ans..256

O

Error text from PayU, if agreed with Computop support

UserData

ans..1024

O

If specified at request, Paygate forwards the parameter with the payment result to the shop

MAC

an64

M

Hash Message Authentication Code (HMAC) with SHA-256 algorithm

PCNr

n..16

O

Pseudo Card Number: Random number generated by Paygate which represents a genuine credit card number. The pseudo card number (PCN) starts with 0 and the last 3 digits correspond to those of the real card number. You can use the PCN like a genuine card number for authorisation, capture and credits.

CCBrand

a..22

O

In combination with PCNr: Name of credit card brand like Visa, MasterCard etc.

CCExpiry

n6

O

In combination with PCNr: Expiry date of the credit card in the format YYYYMM.

MaskedPan

an..19

O

Masked card number 6x4

TokenExt

an..64

C

For recurring payments (RTF=I) the Token is transmitted for referencing the credit card data

Plain

ans..50

O

A value to be set by the merchant to return some information unencrypted, e.g. the MID

Custom

ans..1024

O

The merchant can submit several values separated by | which are returned unencrypted and separated by &.

Custom=session=123|id=456 will change in the answer to

Session=123&id=456

TransactionID

ans..32

O

ID for identification with PayU

AmountAuth

n..10

M

Authorized amount in the smallest currency unit (e.g. PLN Grosz)

AmountCap

n..10

M

Captured amount in the smallest currency unit (e.g. PLN Grosz)

AmountCred

n..10

M

Credited amount in the smallest currency unit (e.g. PLN Grosz)

Return parameters for URLSuccess, URLFailure and URLNotify with PayU CEE Single



Credit card payment with PayU CEE Single via Server-to-Server connection

In order to process a recurring credit card payment with PayU CEE Single via a Paygate form, go to the following URL:


Notice: For security reasons, Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter.

The following table describes the encrypted payment request parameters:

Parameter

Format

CND

Description

MerchantID

ans..30

M

MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too.

TransID

ans..64

M

Merchant transaction number, which must be unique

RefNr

ns..30

O

Unique reference number

Amount

n..10

M

Amount in the smallest currency unit (e.g. PLN Grosz)

Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit).

Currency

a3

M

Currency, three digits DIN / ISO 4217

MAC

an64

M

Hash Message Authentication Code (HMAC) with SHA-256 algorithm

Capture

a..6

O

Determines the type and time of capture. AUTO: capturing immediately after authorisation (default value). MANUAL: capturing made by the merchant. <Number>: Delay in hours until the capture (whole number; 1 to 696).

UserData

ans..1024

O

If specified at request, Paygate forwards the parameter with the payment result to the shop

ReqID

ans..32

O

To avoid double payments, enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction is submitted again with the same ReqID, Paygate will not carry out the payment, but will just return the status of the original transaction. Please note that the Paygate must have a finalized transaction status for the first initial action. Submissions with identical ReqID for an open status will be processed regularly.

OrderDesc

ans..35

M

Description of purchased goods, unit prices etc.

The first 27 characters appear on the customer-account statement.

RTF

a1

O

„R“ for executing recurrent payments

CCNr

n..19

M

Pseudo card number

CCExpiry

n6

M

Credit card expiry date (YYYYMM), e.g. 201807

CCBrand

a..2

M

Card brand: only VISA, MasterCard. Please note the spelling!

TokenExt

an..64

M

Token for referencing the credit card data at PayU

Purchaser data

FirstName

ans..100

M

First name of the customer

LastName

ans..100

M

Last name of the customer

Email

ans..100

M

Email address of the customer

Phone

ans..100

O

Customer’s phone number

SocialSecurityNumber

ans..100

O

Social security number

Delivery data

sdName

ans..100

O

Name

sdStreet

ans..100

C

Street name and street number

If Name is transmitted this parameter must be transmitted too

sdAddressAddition

ans..100

O

Address c/o

sdZIP

ans..10

C

Postcode

If Name is transmitted this parameter must be transmitted too

sdCity

ans..100

C

Town

If Name is transmitted this parameter must be transmitted too

sdCountryCode

a..3

C

Country code (2 or 3 digits according to ISO 3166-1 alpha-2, alpha-3)

If Name is transmitted this parameter must be transmitted too

sdState

ans..100

O

Federal state

sdEmail

ans..100

O

E-mail address

sdPhone

ans..100

O

Telephone number

sdPOBox

ans..100

O

PO box

Invoice data

bdName

ans..100

O

Name

bdStreet

ans..100

C

Street name and street number

If Name is transmitted this parameter must be transmitted too

bdAddressAddition

ans..100

O

Address c/o

bdZIP

ans..10

C

Postcode

If Name is transmitted this parameter must be transmitted too

bdCity

ans..100

C

Town

If Name is transmitted this parameter must be transmitted too

bdCountryCode

a..3

C

Country code (2 or 3 digits according to ISO 3166-1 alpha-2, alpha-3)

If Name is transmitted this parameter must be transmitted too

bdState

ans..100

O

Federal state

bdEmail

ans..100

O

E-mail address

bdPhone

ans..100

O

Telephone number

bdPOBox

ans..100

O

PO box

TaxNumber

n..30

O

National Identification Number (tax number)

Parameters for credit card payments with PayU CEE Single via socket connection


The following table gives the parameters with which Paygate responds:

Parameter

Format

CND

Description

MID

ans..30

M

MerchantID, assigned by Computop

PayID

an32

M

ID assigned by Paygate for the payment, e.g. for referencing in batch files.

XID

an32

M

ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate

TransID

ans..64

M

Merchant’s transaction number

RefNr

ns..30

O

Merchant’s unique reference number

Status

a..30

M

OK, AUTHORIZED or FAILED

Description

ans..1024

M

Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis!

Code

n8

M

Error code according to Paygate Response Codes (A4 Error codes)

CodeExt

n..10

O

Error code from PayU, if agreed with Computop support

ErrorText

ans..256

O

Error text from PayU, if agreed with Computop support

UserData

ans..1024

O

If specified at request, Paygate forwards the parameter with the payment result to the shop

TransactionID

ans..32

O

ID for identification with PayU

AmountAuth

n..10

M

Authorized amount in the smallest currency unit (e.g. PLN Grosz)

AmountCap

n..10

M

Captured amount in the smallest currency unit (e.g. PLN Grosz)

AmountCred

n..10

M

Credited amount in the smallest currency unit (e.g. PLN Grosz)

Result parameters for socket connection for PayU CEE Single



Capture of a payment with 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:


Notice: For security reasons, Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter.

The following table describes the encrypted payment request parameters:

Parameter

Format

CND

Description

MerchantID

ans..30

M

MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too.

PayID

an32

M

ID assigned by Paygate for the payment to be captured

TransID

ans..64

M

ID assigned by Merchant for the payment process to be captured

Amount

n..10

M

Amount in the smallest currency unit (e.g. PLN Grosz)

Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit).

Currency

a..3

M

Currency code, three digits DIN / ISO 4217

RefNr

ans..30

O

Unique reference number

MAC

an64

M

Hash Message Authentication Code (HMAC) with SHA-256 algorithm

ReqIDans..32OTo avoid double payments, enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction is submitted again with the same ReqID, Paygate will not carry out the payment, but will just return the status of the original transaction. Please note that the Paygate must have a finalized transaction status for the first initial action. Submissions with identical ReqID for an open status will be processed regularly.

Parameters for captures of PayU CEE Single via socket connections


The following table describes the Paygate response parameters:

Parameter

Format

CND

Description

MID

ans..30

M

MerchantID, assigned by Computop

PayID

an32

M

ID assigned by Paygate for the payment, e.g. for referencing in batch files

XID

an32

M

ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate

TransID

ans..64

M

Merchant’s transaction number

Status

a..30

M

OK or FAILED

Description

ans..1024

M

Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis!

Code

n8

M

Error code according to Paygate Response Codes (A4 Error codes)

RefNr

ans..30

O

Merchant’s unique reference number

CodeExt

n..10

O

Error code from PayU, if agreed with Computop support

ErrorText

ans..256

O

Error text from PayU, if agreed with Computop support

Response parameters for captures of PayU CEE Single via socket connections



Credit with reference

Credits (refunds) are possible via a Server-to-Server connection. For a Credit with reference to a capture the amount of the Credit is limited to the amount of the previous capture.

To carry out a credit with a reference transaction, please use the following URL:


Notice: For security reasons, Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter.

The following table describes the encrypted payment request parameters:

Parameter

Format

CND

Description

MerchantID

ans..30

M

MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too.

PayID

an32

M

ID assigned by Paygate for the payment to be credited

TransID

ans..64

M

ID assigned by Merchant for the payment process to be credited

Amount

n..10

M

Amount in the smallest currency unit (e.g. EUR Cent)

Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit).

Currency

a..3

M

Currency code, three digits DIN / ISO 4217

RefNr

ans..30

O

Unique reference number

MAC

an64

M

Hash Message Authentication Code (HMAC) with SHA-256 algorithm

OrderDesc

ans..768

O

Description of refunded goods, unit prices, merchant’s comment etc.

ReqIDans..32OTo avoid double payments, enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction is submitted again with the same ReqID, Paygate will not carry out the payment, but will just return the status of the original transaction. Please note that the Paygate must have a finalized transaction status for the first initial action. Submissions with identical ReqID for an open status will be processed regularly.

Parameters for credit payments with PayU CEE Single via socket connection


The following table describes the Paygate response parameters:

Parameter

Format

CND

Description

MID

ans..30

M

MerchantID, assigned by Computop

PayID

an32

M

ID assigned by Paygate for the payment, e.g. for referencing in batch files

XID

an32

M

ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate

TransID

ans..64

M

Merchant’s transaction number

Status

a..30

M

OK or FAILED

Description

ans..1024

M

Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis!

Code

n8

M

Error code according to Paygate Response Codes (A4 Error codes)

CodeExt

n..10

O

Error code from PayU, if agreed with Computop support

ErrorText

ans..256

O

Error text from PayU, if agreed with Computop support

Response parameters for credit payments with PayU CEE Single via socket connection


Reversal

Reversals are possible via a Server-to-Server connection. To carry out a reversal, please use the following URL:


Notice: For security reasons, Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter.

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.

The following table describes the encrypted request parameters:

Parameter

Format

CND

Description

MerchantID

ans..30

M

MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too.

PayID

an32

M

Paygate ID for the identification of a payment

TransID

ans..64

M

Merchant ID for the identification of the payment process to be reversed

Amount

n..10

M

Amount in the smallest currency unit (e.g. EUR Cent)

Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit).

Currency

a3

M

Currency code, three digits DIN / ISO 4217

MAC

an64

M

Hash Message Authentication Code (HMAC) with SHA-256 algorithm

ReqIDans..32OTo avoid double payments, enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction is submitted again with the same ReqID, Paygate will not carry out the payment, but will just return the status of the original transaction. Please note that the Paygate must have a finalized transaction status for the first initial action. Submissions with identical ReqID for an open status will be processed regularly.

Parameters for reversals of payments with PayU CEE Single


The following table describes the Paygate response parameters:

Parameter

Format

CND

Description

MID

ans..30

MC

MerchantID, assigned by Computop

PayID

an32

M

ID assigned by Paygate for the payment, e.g. for referencing in batch files

XID

an32

M

ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate

TransID

ans..64

M

Merchant’s transaction number

Status

a..50

M

OK or FAILED

Description

ans..1024

M

Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis!

Code

n8

M

Error code according to Paygate Response Codes (A4 Error codes)

Response parameters for reversals of payments with PayU CEE Single



Batch processing via the interface

Basic information about using Batch files and about their structure can be found in the Batch Manager manual. Within batch processing not alle functions are available which are usually available for the online interface.

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:

Action

Version

Description

Capture

1.0 / 2.0

Standard version without return of parameter Code

 

1.x / 2.x

with RefNr (valid for all versions other than 1.0)

Credit

1.0 / 2.0

Standard version without return of parameter Code

 

1.x / 2x.

with RefNr (valid for all versions other than 1.0)

Description of the possible batch versions


The structure for a PayU payment within a Batch file to be submitted is the following:

HEAD,<MerchantID>,<Date>,<Version>

PayU,Capture,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>

PayU,Credit,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>

FOOT,<CountRecords>,<SumAmount>


Example for Master MID Funktion:

HEAD,[Master]MerchantID,Date,2.x
Type,Action,[Slave]MID,Amount,Currency,TransID,Data (depends on Action)
FOOT,CountRecords,SumAmount


The following table describes the individual fields and values used within the data set (record) in the batch file:

Parameter

Format

CND

Description

Type

a..11

M

HEAD for Header, FOOT for Footer, PayU for PayU

Action

a..20

M

The parameter Action defines the type of transaction:

Capture

Credit

Amount

n..10

M

Amount in the smallest currency unit (e.g. EUR Cent)

Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit).

Currency

a3

M

Currency code, three digits DIN / ISO 4217

TransID

ans..64

M

TransactionID which should be unique for each payment

RefNr

ns..30

O

Unique reference number

PayID

an32

M

ID for this transaction given by Paygate

Description of fields within the record for Batch files

 

The record area within the response file for Batch transactions looks as follows:

HEAD,<MerchantID>,<Date>,<Version>

PayU,Capture,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>,<Status>,<Code>

PayU,Credit,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>,<Status>,<Code>

FOOT,<CountRecords>,<SumAmount>

 

The following table describes the response parameters which the Batch Manager saves in the Record area for each transaction (standard parameters not explained here, such as <TransID> or <RefNR> and request parameters are returned unchanged and correspond to the call as specified before):

Parameter

Format

CND

Description

Action

a..20

M

The parameter Action defines the type of transaction:

Capture

Credit

PayID

an32

M

ID for this transaction given by Paygate

Status

a..50

M

OK or FAILED

Code

n8

M

Error code according to Paygate Response Codes (A4 Error codes)

Description of result parameters within the record for Batch files