PayU CEE GECAD

Logo

Info

Integration of the PayU CEE GECAD platform is ideal for facilitating e-commerce in fast-growing eastern European countries, and covers the most popular payment methods now available in countries such as Hungary, Romania, Russia or Turkey. With an average internet usage rate of 60%, citizens of these countries provide an attractive market for expansion of international business.

Type

Mixed payment methods

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)

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

MerchantID

ans..30

M

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

TransID

ans..64

M

TransactionID provided by you which should be unique for each payment

refnr

ans..30

O

Merchant’s unique reference number

Amount

n..10

M

Amount in the smallest currency unit (e.g. EUR Cent). Please contact the Computop Helpdesk, if you want to capture amounts <100 (smallest currency unit).

Currency

a3

M

Currency, three digits DIN / ISO 4217, e.g. EUR. Presently only TRY, RON, EUR and USD permitted. Please find an overview here: A1 Currency table

MAC

an64

M

Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here:

• HMAC Authentication (Request)

• HMAC Authentication (Notify)

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.

Common notes:

• We recommend to use parameter "response=encrypt" to get an encrypted response by Paygate

• However, fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess/URLNotify. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.

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.

Common notes:

• We recommend to use parameter "response=encrypt" to get an encrypted response by Paygate

• However, fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess/URLNotify. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.

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 UserDataparameter instead.

Common notes:

• Before follow-up actions (capture / credit / reversal) are carried out on an existing transaction, the first Notify must have been answered by the shop.

• Fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess/URLNotify. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.

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 or actions (e.g. by ETM), enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction or action is submitted again with the same ReqID, Computop Paygate will not carry out the payment or new action, but will just return the status of the original transaction or action.

Please note that the Computop Paygate must have a finalized transaction status for the first initial action (authentication/authorisation). This does not apply to 3-D Secure authentications that are terminated by a timeout. The 3-D Secure Timeout status does not count as a completed status in which the ReqID functionality on Paygate does not take effect. Submissions with identical ReqID for an open status will be processed regularly.

Notice: Please note that a ReqID is only valid for 12 month, then it gets deleted at the Paygate.

Capture

an..6

OM

Determines the type and time of capture.

OrderDesc

ans..768

M

Description of purchased goods, unit prices etc.

ArticleList(n)

ans..2048

M

Customer’s article list in the form:

Articlelist(n)= ArticleName,ArticleCode,UnitPrice,Quantity,VAT-rate,Type+ArticleName,ArticleCode,UnitPrice,Quantity,VAT-rate,Type+…

Articlelist1 to max. Articlelist10 permissible

The ArticleCode hast to be one-to-one because otherwise identical article numbers will be overwritten by PayU and not added. Thereby the total amount of trasaction could be changed by mistake.

Example:

Articlelist1=article1,123456,100,1,16,GROSS+article2,321654,200,2,16,NET

Articlelist2=article3,987654,100,2,16,GROSS+article4,654231,150,1,16,NET

The amount must be equal to the sum of the amounts in ArticleList, i.e. in the sample above: Amount=850 (1 x 100 + 2 x 200 + 2 x 100 + 1 x 150)

Discount

n..10

O

Discount in the smallest currency unit

ChargeAmount

n..10

O

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

AutoStart

bool

O

If you transfer the value 1 here you bypass the first page in the PayU-process. Important: This is possible only, if all necessary parameters are transferred.

Language

a2

O

Language:

RO – Romanian

EN – English

HU – Hungarian

DE – German

FR – French

IT – Italian

ES – Spanish

BG – Bulgarian

PL – Polish

RU – Russian

PayType

ans..25

M

Name of payment method to be executed

Possible values for Romania:

<Card> – VISA/MasterCard

Installment payments:

<BRDF> – BRDFinance Installment

<STAR_BT> – Banca Transilvania’s StarBT

<CARD_AVANTAJ> – Credit Europe’s CardAvantaj

<ALPHABANK> – Alpha Bank

Online bank transfers:

<TRANSFER_ING> – Internet banking with ING Home Bank

<ITRANSFER_BCR> – Internet banking with Click24 Banking BCR

<ITRANSFER_BT> – Internet banking with BT24

Other:

<ZEBRA> – cash deposit with ZebraPay Self Service

<PAYPAL> – PayPal payments

<WIRE> – Bank Wire

Possible values for Turkey:

<Card> – VISA/MasterCard

Other:

<WEBMONEY>

<QIWI>

<MAILRU>

<YANDEX> (not valid for new customers)

<EUROSET_SVYAZNOI>

<ALFACLICK>

<BKM>

Value for merchants which have activated this method:

<MASTERPASS>

Note: If PayType is used, then parameter bdCountryCode becomes mandatory.

InstallmentData

ans..24

OC

Only for Channel=RO: Preconfiguration of possible number of rates

Default value is the configuration from the PayU system

„2,3,4,5,6,7,8,9,10,11,12“ –

All are displayed for choosing

„2,3,7,10,12“ – 2,3,7,10,12 are displayed for choosing

„2“– only 2 is displayed as an option

„1„ – no installments possible

InstallmentNumber

n..2

OC

Only for Channel=TR: Number of months of the payment by instalments (1-12)

Timeout

n..3

O

Validity of transaction in seconds

Channel

a2

O

Channel (country) of payment (the default channel will be configured by Computop Helpdesk):

RO = Romania

TR = Turkey

RU = Russian Federation

HU = Hungary

UA = Ukraine

Plain

ans..50

O

A single value to be set by the merchant to return some information unencrypted in response/notify, e.g. the MID.

"Plain"-parameter is part of encrypted "Data" in Computop Paygate and therefore protected against manipulation.

Custom

ans..1024

O

"Custom"-parameter is added to the request data before encryption and is part of encrypted "Data" in Computop Paygate request. By this they are protected against manipulation by a consumer.

The Custom-value is added to the Computop Paygate response in plain text and the "|" is replaced by a "&". By this you can put a single value into Custom-parameter and get multiple key-value-pairs back in response for your own purpose.

Please find a sample here: Custom

Billing address (PayU)

bdFirstName

ans..128

M

First name of the customer

bdLastName

ans..128

M

Last name of the customer

bdStreet

ans..46

O

Street name in the invoicing address

bdAddressAddition

ans..60

O

Address addition in the billing address

bdCity

ans..40

O

Name of town/city in the billing address

bdZip

ans..8

O

Postcode in the invoicing address

bdState

ans..50

O

Federal state in the invoicing address

bdCountryCode

a2

OC

Country code in the invoicing address according to ISO 3166. Mandatory if PayType is submitted.

bdFax

ans..20

O

Customer’s fax number

bdeMail

ans..128

M

Email address of the customer

bdPhone

ans..40

O

Customer’s phone number

IdCardSeries

ans..3

O

Series of ID card

IdCardNumber

ans..20

O

Serial number of ID card

IdCardIssuer

ans..128

O

Issuer of ID card

NatIdentNr

ans..20

O

CNP of the customer

CompanyName

ans..200

O

Name of company

TaxNumber

ans..20

O

VAT Reg. No.

RegisterNumber

ans..20

O

Register of Companies number/commercial register

AccBank

ans..20

O

Bank name of the company

AccNr

ans..20

O

Account number of the company

Delivery address

sdFirstName

ans..128

O

First name in the delivery address

sdLastName

ans..128

O

Surname in the delivery address

sdStreet

ans..46

O

Street name in the delivery address

sdAddressAddition

ans..60

O

Address addition in the delivery address

sdCity

ans..40

O

Town/city in the delivery address

sdZip

ans..8

O

Postcode in the delivery address

sdState

ans..50

O

Federal state of the delivery address

sdCountryCode

a2

O

Country code in the delivery address according to ISO 3166

sdeMail

ans..128

O

Email address in the delivery address

sdPhone

ans..40

O

Phone number in the delivery address

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 as well as for capture or credit request.

XID

an32

M

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

TransID

ans..64

M

TransactionID provided by you which should be unique for each payment

refnr

ans..30

O

Merchant’s unique reference number

Status

a..30

M

OK, FAILED or AUTHORIZE_REQUEST.

If 25 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

an8

M

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

MAC

an64

M

Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here:

• HMAC Authentication (Request)

• HMAC Authentication (Notify)

CodeExt

n..10

O

Error code from PayU, if agreed with Computop Helpdesk

ErrorText

ans..256

O

Error text from PayU, if agreed with Computop Helpdesk

UserData

ans..1024

O

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

Plain

ans..50

O

A single value to be set by the merchant to return some information unencrypted in response/notify, e.g. the MID.

"Plain"-parameter is part of encrypted "Data" in Computop Paygate and therefore protected against manipulation.

Custom

ans..1024

O

"Custom"-parameter is added to the request data before encryption and is part of encrypted "Data" in Computop Paygate request. By this they are protected against manipulation by a consumer.

The Custom-value is added to the Computop Paygate response in plain text and the "|" is replaced by a "&". By this you can put a single value into Custom-parameter and get multiple key-value-pairs back in response for your own purpose.

Please find a sample here: Custom

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 as well as for capture or credit request.

XID

an32

M

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

TransID

ans..64

M

TransactionID provided by you which should be unique for each payment

refnr

ans..30

O

Merchant’s unique reference number

Status

a..50

M

OK (URLSuccess) or FAILED (URLFailure)

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

an8

M

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

MAC

an64

M

Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here:

• HMAC Authentication (Request)

• HMAC Authentication (Notify)

CodeExt

n..10

O

Error code from PayU, if agreed with Computop Helpdesk

ErrorText

ans..256

O

Error text from PayU, if agreed with Computop Helpdesk

UserData

ans..1024

O

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

Plain

ans..50

O

A single value to be set by the merchant to return some information unencrypted in response/notify, e.g. the MID.

"Plain"-parameter is part of encrypted "Data" in Computop Paygate and therefore protected against manipulation.

Custom

ans..1024

O

"Custom"-parameter is added to the request data before encryption and is part of encrypted "Data" in Computop Paygate request. By this they are protected against manipulation by a consumer.

The Custom-value is added to the Computop Paygate response in plain text and the "|" is replaced by a "&". By this you can put a single value into Custom-parameter and get multiple key-value-pairs back in response for your own purpose.

Please find a sample here: Custom

AmountAuth

n..10

M

Actually authorized amount in the smallest currency unit

Currency

a3

M

Currency, three digits DIN / ISO 4217

TransactionID

ans..25

O

RefNr from PayU system

PayType

ans..25

M

Name of used payment method (see above for possible values)

bdFirstName

ans..128

O

First name of the customer

bdLastName

ans..128

O

Last name of the customer

bdStreet

ans..46

O

Street name in the invoicing address

bdAddressAddition

ans..60

O

Address addition in the billing address

bdCity

ans..40

O

Name of town/city in the billing address

bdZip

ans..8

O

Postcode in the invoicing address

bdState

ans..50

O

Federal state in the invoicing address

bdCountryCode

a2

OC

Country code in the invoicing address according to ISO 3166. Mandatory if PayType is submitted.

bdFax

ans..20

O

Customer’s fax number

bdeMail

ans..128

M

Email address of the customer

bdPhone

ans..40

O

Customer’s phone number

IdCardSeries

ans..3

O

Series of ID card

IdCardNumber

ans..20

O

Serial number of ID card

IdCardIssuer

ans..128

O

Issuer of ID card

NatIdentNr

ans..20

O

CNP of the customer

CompanyName

ans..200

O

Name of company

TaxNumber

ans..20

O

VAT Reg. No.

RegisterNumber

ans..20

O

Register of Companies number/commercial register

AccBank

ans..20

O

Bank name of the company

AccNr

ans..20

O

Account number of the company

sdFirstName

ans..128

O

First name in the delivery address

sdLastName

ans..128

O

Surname in the delivery address

sdStreet

ans..46

O

Street name in the delivery address

sdAddressAddition

ans..60

O

Address addition in the delivery address

sdCity

ans..40

O

Town/city in the delivery address

sdZip

ans..8

O

Postcode in the delivery address

sdState

ans..50

O

Federal state of the delivery address

sdCountryCode

a2

O

Country code in the delivery address according to ISO 3166

sdeMail

ans..128

O

Email address in the delivery address

sdPhone

ans..40

O

Phone number in the delivery address

CustomParameter

ans..

O

If additional parameters are configured in the PayU backend these are returned with the prefix “custom_”; e.g. PayU Parameter = age = custom_age

InstallmentNumber

n..2

O

Number of months of the payment by instalments (1-12), default=1

CardProgram

ans..25

O

Name of the card programme which allows the instalment payment (see table of card programmes)

Card programme

Issuer

Advantage

T. İŞ BANKASI A.Ş.

AsyaCard

ASYA KATILIM BANKASI A.Ş.

Axess

AKBANK T.A.Ş.

CITIBANK A.Ş.

ODEA BANK A.Ş.

Bonus

TÜRK EKONOMİ BANKASI A.Ş.

ŞEKERBANK T.A.Ş.

T.GARANTİ BANKASI A.Ş.

ING BANK A.Ş.

DENİZBANK A.Ş.

TÜRKİYE FİNANS

Cardfinans

FİNANS BANK A.Ş.

Maximum

T.C.ZİRAAT BANKASI A.Ş.

T. İŞ BANKASI A.Ş.

Paraf

T.HALK BANKASI A.Ş.

World

T.VAKIFLAR BANKASI T.A.O.

YAPI VE KREDİ BANKASI A.Ş.

ANADOLUBANK A.Ş.

ALBARAKA TÜRK

MerchantID

ans..30

M

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

TransID

ans..64

M

TransactionID provided by you which should be unique for each payment

RefNr

ans..30

M

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. EUR Cent). Please contact the Computop Helpdesk, if you want to capture amounts <100 (smallest currency unit).

Currency

a3

M

Currency, three digits DIN / ISO 4217, e.g. EUR. Presently only TRY, RON, EUR and USD permitted. Please find an overview here: A1 Currency table

MAC

an64

M

Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here:

• HMAC Authentication (Request)

• HMAC Authentication (Notify)

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.

Common notes:

• We recommend to use parameter "response=encrypt" to get an encrypted response by Paygate

• However, fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess/URLNotify. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.

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.

Common notes:

• We recommend to use parameter "response=encrypt" to get an encrypted response by Paygate

• However, fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess/URLNotify. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.

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 UserDataparameter instead.

Common notes:

• Before follow-up actions (capture / credit / reversal) are carried out on an existing transaction, the first Notify must have been answered by the shop.

• Fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess/URLNotify. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.

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 or actions (e.g. by ETM), enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction or action is submitted again with the same ReqID, Computop Paygate will not carry out the payment or new action, but will just return the status of the original transaction or action.

Please note that the Computop Paygate must have a finalized transaction status for the first initial action (authentication/authorisation). This does not apply to 3-D Secure authentications that are terminated by a timeout. The 3-D Secure Timeout status does not count as a completed status in which the ReqID functionality on Paygate does not take effect. Submissions with identical ReqID for an open status will be processed regularly.

Notice: Please note that a ReqID is only valid for 12 month, then it gets deleted at the Paygate.

Capture

an..6

OM

Determines the type and time of capture.

OrderDesc

ans..768

M

Description of purchased goods, unit prices etc.

ArticleList(n)

ans..2048

M

Customer’s article list in the form:

Articlelist(n)= ArticleName,ArticleCode,UnitPrice,Quantity,VAT-rate,Type+ArticleName,ArticleCode,UnitPrice,Quantity,VAT-rate,Type+…

Articlelist1 to max. Articlelist10 permissible

The ArticleCode hast to be one-to-one because otherwise identical article numbers will be overwritten by PayU and not added. Thereby the total amount of trasaction could be changed by mistake.

Example:

Articlelist1=article1,123456,100,1,16,GROSS+article2,321654,200,2,16,NET

Articlelist2=article3,987654,100,2,16,GROSS+article4,654231,150,1,16,NET

The amount must be equal to the sum of the amounts in ArticleList, i.e. in the sample above: Amount=850 (1 x 100 + 2 x 200 + 2 x 100 + 1 x 150)

ChargeAmount

n..10

O

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

Channel

a2

O

Channel (country) of payment (the default channel will be configured by Computop Helpdesk):

RO = Romania

TR = Turkey

RU = Russian Federation

HU = Hungary

UA = Ukraine

Plain

ans..50

O

A single value to be set by the merchant to return some information unencrypted in response/notify, e.g. the MID.

"Plain"-parameter is part of encrypted "Data" in Computop Paygate and therefore protected against manipulation.

Custom

ans..1024

O

"Custom"-parameter is added to the request data before encryption and is part of encrypted "Data" in Computop Paygate request. By this they are protected against manipulation by a consumer.

The Custom-value is added to the Computop Paygate response in plain text and the "|" is replaced by a "&". By this you can put a single value into Custom-parameter and get multiple key-value-pairs back in response for your own purpose.

Please find a sample here: Custom

Installments (PayU)

InstallmentNumber

n..2

O

Number of months of the payment by instalments (1-12), default=1

CardProgram

ans..25

O

Name of the card programme which allows the instalment payment (see table of card programmes)

Campaign

a5

O

Defines the campaign to be used for the instalments.

Extra=EXTRA_INSTALLMENTS

Delay=DELAY_INSTALLMENTS

Loyalty points (PayU)

PointAmount

n..10

O

Amount of the Loyalty points to be used in the smallest currency unit

Billing address (PayU)

bdFirstName

ans..128

M

First name of the customer

bdLastName

ans..128

M

Last name of the customer

bdStreet

ans..46

O

Street name in the invoicing address

bdAddressAddition

ans..60

O

Address addition in the billing address

bdCity

ans..40

O

Name of town/city in the billing address

bdZip

ans..8

O

Postcode in the invoicing address

bdState

ans..50

O

Federal state in the invoicing address

bdCountryCode

a2

M

Country code in the invoicing address according to ISO 3166

bdFax

ans..20

O

Customer’s fax number

bdeMail

ans..128

M

Email address of the customer

bdPhone

ans..40

O

Customer’s phone number

Delivery address

sdFirstName

ans..128

O

First name in the delivery address

sdLastName

ans..128

O

Surname in the delivery address

sdStreet

ans..46

O

Street name in the delivery address

sdAddressAddition

ans..60

O

Address addition in the delivery address

sdCity

ans..40

O

Town/city in the delivery address

sdZip

ans..8

O

Postcode in the delivery address

sdState

ans..50

O

Federal state of the delivery address

sdCountryCode

a2

O

Country code in the delivery address according to ISO 3166

sdeMail

ans..128

O

Email address in the delivery address

sdPhone

ans..40

O

Phone number in the delivery address

Template

ans..20

O

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

O

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

O

Form background colour:

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

- HTML-colour name

BGImage

ans..256

O

Form background image:

URL for a background image

Please note that this value supersedes “BGColor”.

FColor

ans..7

O

Text colour:

- HTML-colour value as HEX value or

- HTML-colour name

FFace

a..10

O

HTML-name for the font

FSize

n2

O

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, <sp> Spanish, <se> Swedish, <sk> Slovakian, <sl> Slovenian, <tr> Turkey, <zh> Simplified Chinese.

No details means the language is German.

CCSelect

a..10

M

Determines preselected card type in the form: VISA, MasterCard

URLBack

ans..256

O

Complete URL which Paygate calls in case that Cancel is clicked by the customer.

The parameter "URLBack" can be sent

• either as plain parameter (unencrypted) (compatibility mode)

• or be part of encrypted payment request parameters (preferred mode)

In order to exchange values between Paygate and shop you may use something like this:

URLBack=https://your.shop.com/back.php?param1%3Dvalue1%26param2%3Dvalue3%26status%3Dcancelled

When user cancels payment this URL is called exactly like this and you may use URL Decode to extract parameter and values.

Center

n1

O

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

tWidth

ans..4

O

Width of table for input in the form as percent- (50%) or pixel values (320).

tHeight

ans..4

O

Height of table for input of the payment data in the form as percent- (70%) or pixel values (480).

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 as well as for capture or credit request.

XID

an32

M

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

TransID

ans..64

M

TransactionID provided by you which should be unique for each payment

refnr

ans..30

O

Merchant’s unique reference number

Status

a..30

M

OK, FAILED or AUTHORIZE_REQUEST.

If 25 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

an8

M

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

MAC

an64

M

Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here:

• HMAC Authentication (Request)

• HMAC Authentication (Notify)

CodeExt

n..10

O

Error code from PayU, if agreed with Computop Helpdesk

ErrorText

ans..256

O

Error text from PayU, if agreed with Computop Helpdesk

UserData

ans..1024

O

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

PCNr

n16

O

Pseudo Card Number: Random number generated by Computop 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. The PCN can be used like a genuine card number for authorisation, capture and credits.

PCNr is a response value from Computop Paygate and is sent as CCNr in Request or part of card-JSON

CCBrand

a..22

O

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

CCExpiry

n6

O

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

AmountAuth

n..10

MC

Only to URLNotify: Actually authorized amount in the smallest currency unit. For installment payments the charges are added automatically to the initial amount.

Currency

a3

MC

Only to URLNotify: Currency, three digits DIN / ISO 4217

InstallmentNumber

n..2

OC

Only to URLNotify: Number of months of the payment by instalments (1-12), default=1

CardProgram

ans..25

OC

Only to URLNotify: Name of the card programme which allows the instalment payment (see table of card programmes)

PayType

ans..25

MC

Only to URLNotify: Name of used payment method (see above for possible values)

Plain

ans..50

O

A single value to be set by the merchant to return some information unencrypted in response/notify, e.g. the MID.

"Plain"-parameter is part of encrypted "Data" in Computop Paygate and therefore protected against manipulation.

Custom

ans..1024

O

"Custom"-parameter is added to the request data before encryption and is part of encrypted "Data" in Computop Paygate request. By this they are protected against manipulation by a consumer.

The Custom-value is added to the Computop Paygate response in plain text and the "|" is replaced by a "&". By this you can put a single value into Custom-parameter and get multiple key-value-pairs back in response for your own purpose.

Please find a sample here: Custom

MerchantID

ans..30

M

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

TransID

ans..64

M

TransactionID provided by you which should be unique for each payment

refnr

ans..30

O

Merchant’s unique reference number

Amount

n..10

M

Amount in the smallest currency unit (e.g. EUR Cent). Please contact the Computop Helpdesk, if you want to capture amounts <100 (smallest currency unit).

Currency

a3

M

Currency, three digits DIN / ISO 4217, e.g. EUR. Presently only TRY, RON, EUR and USD permitted. Please find an overview here: A1 Currency table

MAC

an64

M

Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here:

• HMAC Authentication (Request)

• HMAC Authentication (Notify)

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 or actions (e.g. by ETM), enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction or action is submitted again with the same ReqID, Computop Paygate will not carry out the payment or new action, but will just return the status of the original transaction or action.

Please note that the Computop Paygate must have a finalized transaction status for the first initial action (authentication/authorisation). This does not apply to 3-D Secure authentications that are terminated by a timeout. The 3-D Secure Timeout status does not count as a completed status in which the ReqID functionality on Paygate does not take effect. Submissions with identical ReqID for an open status will be processed regularly.

Notice: Please note that a ReqID is only valid for 12 month, then it gets deleted at the Paygate.

Capture

an..6

OM

Determines the type and time of capture.

CCNr

n..19

M

Credit card number at least 12-digit, numerical without spaces. You can optionally transmit also a pseudo card number (PCN)

CCCVC

n..4

O

Card verification number: The last 3 digits on the signature strip of the credit card. 4 characters in the case of AMEX.

CCExpiry

n6

M

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

CCBrand

a..22

M

Card type: VISA, MasterCard.

Please note the spelling!

CreditCardHolder

ans..60

O

Name of the card holder

OrderDesc

ans..768

M

Description of purchased goods, unit prices etc.

ArticleList(n)

ans..2048

M

Customer’s article list in the form:

Articlelist(n)= ArticleName,ArticleCode,UnitPrice,Quantity,VAT-rate,Type+ArticleName,ArticleCode,UnitPrice,Quantity,VAT-rate,Type+…

Articlelist1 to max. Articlelist10 permissible

The ArticleCode hast to be one-to-one because otherwise identical article numbers will be overwritten by PayU and not added. Thereby the total amount of trasaction could be changed by mistake.

Example:

Articlelist1=article1,123456,100,1,16,GROSS+article2,321654,200,2,16,NET

Articlelist2=article3,987654,100,2,16,GROSS+article4,654231,150,1,16,NET

The amount must be equal to the sum of the amounts in ArticleList, i.e. in the sample above: Amount=850 (1 x 100 + 2 x 200 + 2 x 100 + 1 x 150)

ChargeAmount

n..10

M

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

Channel

a2

O

Channel (country) of payment (the default channel will be configured by Computop Helpdesk):

RO = Romania

TR = Turkey

RU = Russian Federation

HU = Hungary

UA = Ukraine

Installments (PayU)

InstallmentNumber

n..2

O

Number of months of the payment by instalments (1-12), default=1

CardProgram

ans..25

OC

Only to URLNotify: Name of the card programme which allows the instalment payment (see table of card programmes)

PayType

ans..25

MC

Only to URLNotify: Name of used payment method (see above for possible values)

Loyalty points (PayU)

PointAmount

n..10

O

Amount of the Loyalty points to be used in the smallest currency unit

Billing address (PayU)

bdFirstName

ans..128

M

First name of the customer

bdLastName

ans..128

M

Last name of the customer

bdStreet

ans..46

O

Street name in the invoicing address

bdAddressAddition

ans..60

O

Address addition in the billing address

bdCity

ans..40

O

Name of town/city in the billing address

bdZip

ans..8

O

Postcode in the invoicing address

bdState

ans..50

O

Federal state in the invoicing address

bdCountryCode

a2

M

Country code in the invoicing address according to ISO 3166

bdFax

ans..20

O

Customer’s fax number

bdeMail

ans..128

M

Email address of the customer

bdPhone

ans..40

O

Customer’s phone number

Delivery address

sdFirstName

ans..128

O

First name in the delivery address

sdLastName

ans..128

O

Surname in the delivery address

sdStreet

ans..46

O

Street name in the delivery address

sdAddressAddition

ans..60

O

Address addition in the delivery address

sdCity

ans..40

O

Town/city in the delivery address

sdZip

ans..8

O

Postcode in the delivery address

sdState

ans..50

O

Federal state of the delivery address

sdCountryCode

a2

O

Country code in the delivery address according to ISO 3166

sdeMail

ans..128

O

Email address in the delivery address

sdPhone

ans..40

O

Phone number in the delivery address

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 as well as for capture or credit request.

XID

an32

M

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

TransID

ans..64

M

TransactionID provided by you which should be unique for each payment

refnr

ans..30

O

Merchant’s unique reference number

Status

a..50

M

OK (URLSuccess) or FAILED (URLFailure)

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

an8

M

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

CodeExt

n..10

O

Error code from PayU, if agreed with Computop Helpdesk

ErrorText

ans..256

O

Error text from PayU, if agreed with Computop Helpdesk

UserData

ans..1024

O

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

PCNr

n16

O

Pseudo Card Number: Random number generated by Computop 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. The PCN can be used like a genuine card number for authorisation, capture and credits.

PCNr is a response value from Computop Paygate and is sent as CCNr in Request or part of card-JSON

CCBrand

a..22

O

In combination with PCNr: Description of the credit card brand including VISA, MasterCard, AMEX, DINERS, Elo, Aura or Hipercard

CCExpiry

n6

O

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

InstallmentNumber

n..2

O

Number of months of the payment by instalments (1-12), default=1

CardProgram

ans..25

O

Name of the card programme which allows the instalment payment (see table of card programmes)

PayType

ans..25

M

Name of used payment method (see above for possible values)

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

TransactionID provided by you which should be unique for each payment

Amount

n..10

M

Amount in the smallest currency unit (e.g. EUR Cent). Please contact the Computop Helpdesk, if you want to capture amounts <100 (smallest currency unit).

Currency

a3

M

Currency, three digits DIN / ISO 4217, e.g. EUR, USD, GBP. Please find an overview here: A1 Currency table

RefNr

ans..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!

MAC

an64

M

Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here:

• HMAC Authentication (Request)

• HMAC Authentication (Notify)

ReqId

ans..32

O

To avoid double payments or actions (e.g. by ETM), enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction or action is submitted again with the same ReqID, Computop Paygate will not carry out the payment or new action, but will just return the status of the original transaction or action.

Please note that the Computop Paygate must have a finalized transaction status for the first initial action (authentication/authorisation). This does not apply to 3-D Secure authentications that are terminated by a timeout. The 3-D Secure Timeout status does not count as a completed status in which the ReqID functionality on Paygate does not take effect. Submissions with identical ReqID for an open status will be processed regularly.

Notice: Please note that a ReqID is only valid for 12 month, then it gets deleted at the Paygate.

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 as well as for capture or credit request.

XID

an32

M

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

TransID

ans..64

M

TransactionID provided by you which should be unique for each payment

Status

a..50

M

OK (URLSuccess) or FAILED (URLFailure)

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

an8

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 Helpdesk

ErrorText

ans..256

O

Error text from PayU, if agreed with Computop Helpdesk

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

TransactionID provided by you which should be unique for each payment

Amount

n..10

M

Amount in the smallest currency unit (e.g. EUR Cent). Please contact the Computop Helpdesk, if you want to capture amounts <100 (smallest currency unit).

Currency

a3

M

Currency, three digits DIN / ISO 4217, e.g. EUR, USD, GBP. Please find an overview here: A1 Currency table

MAC

an64

M

Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here:

• HMAC Authentication (Request)

• HMAC Authentication (Notify)

ReqId

ans..32

O

To avoid double payments or actions (e.g. by ETM), enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction or action is submitted again with the same ReqID, Computop Paygate will not carry out the payment or new action, but will just return the status of the original transaction or action.

Please note that the Computop Paygate must have a finalized transaction status for the first initial action (authentication/authorisation). This does not apply to 3-D Secure authentications that are terminated by a timeout. The 3-D Secure Timeout status does not count as a completed status in which the ReqID functionality on Paygate does not take effect. Submissions with identical ReqID for an open status will be processed regularly.

Notice: Please note that a ReqID is only valid for 12 month, then it gets deleted at the Paygate.

OrderDesc

ans..768

O

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

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 as well as for capture or credit request.

XID

an32

M

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

TransID

ans..64

M

TransactionID provided by you which should be unique for each payment

Status

a..50

M

OK (URLSuccess) or FAILED (URLFailure)

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

an8

M

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

CodeExt

n..10

O

Error code from PayU, if agreed with Computop Helpdesk

ErrorText

ans..256

O

Error text from PayU, if agreed with Computop Helpdesk

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 / 2.x

with RefNr (valid for all versions other than 1.0)

Type

a..11

M

HEAD for Header, FOOT for Footer, CC for credit card

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 Computop Helpdesk, if you want to capture amounts <100 (smallest currency unit).

Currency

a3

M

Currency, three digits DIN / ISO 4217, e.g. EUR, USD, GBP. Please find an overview here: A1 Currency table

TransID

ans..64

M

TransactionID provided by you which should be unique for each payment

refnr

ans..30

O

Merchant’s unique reference number

PayID

an32

M

ID assigned by Paygate for this transaction

Action

a..20

M

The parameter Action defines the type of transaction:

Capture

Credit

PayID

an32

M

ID assigned by Paygate for this transaction

Status

a..50

M

OK (URLSuccess) or FAILED (URLFailure)

Code

an8

M

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