PayU CEE Single

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.

Type

Mixed payment methods

Card Scheme

VISA

MasterCard

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, USD, GBP. Only EUR, PLN and CZK permissible. 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..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 from ArticleList and ShippingData must be equal to the parameter Amount. If you need to disable this check (e.g. for processing of gift cards) please contact the Computop Helpdesk and also PayU support.

PayType

ans..4

O

Payment method to be used. Possible values can be found in the list https://developers.payu.com/en/overview.html#paymethods at Value. E.g., "dpcz" for Twisto CZK.

AuthCode

n6

O

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

Please note that the additional BLIK-OneClick variant is also active on the PayU account (POS ID).

TokenExt

ans..64

O

For payment method BLIK parameter TokenExt can be transmitted.

AppKey

ans..32

O

For payment method BLIK parameter Appkey can be transmitted together with parameter TokenExt.

In case a customer has accounts in several banks and uses BLIK in each of the banks, parameter AppKeycontains application key for which the TokenExt has to be used.

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

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

CustomerID

ans..64

C

Mandatory in case of Blik Scenario 2 (Payment using AuthCode with token registration).

Phone

ans..100

O

Customer’s phone number

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.

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

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

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

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

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.

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

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)

AllowedPayMethods

ans..1024

C

Base64-encoded JSON object.

The object contains "blickToken" in the same format, as it was returned by PayU.

Example of the object:

1
[
2
  {
3
    value: 'TOKB_EaVSDM7dXXN1qXXExDdakvfviizKnIys',
4
    type: 'UID',
5
    brandImageUrl: 'https://static.payu.com/images/mobile/logos/pbl_blik.png',
6
    bankApplicationReferences: [
7
      {
8
        key: '18422',
9
        label: 'ma...tt@co...om',
10
      },
11
      {
12
        key: '18407',
13
        label: 'ma...tt@co...om',
14
      },
15
    ],
16
  },
17
];

MerchantID

ans..30

M

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

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

CustomerID

ans..64

M

Identifier of the customer in merchant's system/web shop.

Must be the same as in token registration request (Blik Scenario 2).

Email

ans..100

M

Email address of the customer

Must be the same as in token registration request (Blik Scenario 2).

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

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)

AllowedPayMethods

ans..1024

C

Base64-encoded JSON object.

The object contains "blickToken" in the same format, as it was returned by PayU.

Example of the object:

1
[
2
  {
3
    value: 'TOKB_EaVSDM7dXXN1qXXExDdakvfviizKnIys',
4
    type: 'UID',
5
    brandImageUrl: 'https://static.payu.com/images/mobile/logos/pbl_blik.png',
6
    bankApplicationReferences: [
7
      {
8
        key: '18422',
9
        label: 'ma...tt@co...om',
10
      },
11
      {
12
        key: '18407',
13
        label: 'ma...tt@co...om',
14
      },
15
    ],
16
  },
17
];

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

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. 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)

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.

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

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)

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

O

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

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

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

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.

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 etc.

CCExpiry

n6

O

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

MaskedCCNr

an..19

OC

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

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)

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, 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)

Capture

an..6

OM

Determines the type and time of capture.

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.

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.

CCNr

n..19

M

Credit card number

CCExpiry

n6

M

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

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)

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 or AUTHORIZED (URLSuccess) as well as 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.

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)

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

Merchant’s unique reference number

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

refnr

ans..30

O

Merchant’s unique reference number

OrderDesc

ans..768

O

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

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)

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 reversed

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.

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)

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, 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 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)