About PayU India

General information about payment methods via PayU India

Logo
Info	With the integration of PayU biz India merchants open the door to a rapidly growing e-commerce market. Only 30% of online customers in India have access to internationally accepted payment methods. With the integration of PayU biz via Computop Paygate merchants can offer 76 local payment methods to serve the majority of customers. This comprises of online transfers, credit and debit cards, eWallets and cash-in payments.
Type	Mixed payment methods

Card Scheme
MasterCard
VISA
AMEX
Diners
RuPay

Process flow charts

eyJleHRTcnZJbnRlZ1R5cGUiOiIiLCJnQ2xpZW50SWQiOiIiLCJjcmVhdG9yTmFtZSI6IkFkbWluIiwib3V0cHV0VHlwZSI6ImJsb2NrIiwibGFzdE1vZGlmaWVyTmFtZSI6IkFkbWluIiwibGFuZ3VhZ2UiOiJlbiIsInVpQ29uZmlnIjoie1wiY3VzdG9tUHJlc2V0Q29sb3JzXCI6W1wiMTQxOTMyXCIsXCIwMDVhOTZcIixcIjAwOWVmZlwiLFwiZTQwMDAwXCIsXCJhNWY3MjlcIixcImZmYjcwMFwiXSxcImRlZmF1bHRDdXN0b21MaWJyYXJpZXNcIjpbXCJBMVwiXSxcInZlcnNpb25cIjpcIjEuMFwifSIsImRpYWdyYW1EaXNwbGF5TmFtZSI6IiIsInNGaWxlSWQiOiIiLCJhdHRJZCI6IjcxMjA1MDc3IiwiZGlhZ3JhbU5hbWUiOiJQYXlVSW5kaWFfQ1QiLCJhc3BlY3QiOiIiLCJsaW5rcyI6ImF1dG8iLCJjZW9OYW1lIjoiUGF5VSBJbmRpYSIsInRic3R5bGUiOiJ0b3AiLCJjYW5Db21tZW50IjpmYWxzZSwiZGlhZ3JhbVVybCI6IiIsImNzdkZpbGVVcmwiOiIiLCJib3JkZXIiOnRydWUsIm1heFNjYWxlIjoiMSIsIm93bmluZ1BhZ2VJZCI6MjYyNDc2MTgsImVkaXRhYmxlIjpmYWxzZSwiY2VvSWQiOjI2MjQ3NjE4LCJwYWdlSWQiOiIiLCJsYm94Ijp0cnVlLCJzZXJ2ZXJDb25maWciOnsiZW1haWxwcmV2aWV3IjoiMSJ9LCJvZHJpdmVJZCI6IiIsInJldmlzaW9uIjowLCJtYWNyb0lkIjoiZDMwYzZkNGQtOTliNy00MWVmLWFmNDAtYjMxYTljMDU4MWQ1IiwicHJldmlld05hbWUiOiJQYXlVSW5kaWFfQ1QucG5nIiwibGljZW5zZVN0YXR1cyI6Ik9LIiwic2VydmljZSI6IiIsImlzVGVtcGxhdGUiOiIiLCJ3aWR0aCI6IjExMDkiLCJzaW1wbGVWaWV3ZXIiOmZhbHNlLCJsYXN0TW9kaWZpZWQiOiJPY3QgMTgsIDIwMjIsIDc6NDk6MDkgQU0iLCJleGNlZWRQYWdlV2lkdGgiOmZhbHNlLCJvQ2xpZW50SWQiOiIifQ==

Process flow for PayU India WebCheckout

eyJleHRTcnZJbnRlZ1R5cGUiOiIiLCJnQ2xpZW50SWQiOiIiLCJjcmVhdG9yTmFtZSI6IkFkbWluIiwib3V0cHV0VHlwZSI6ImJsb2NrIiwibGFzdE1vZGlmaWVyTmFtZSI6IkFkbWluIiwibGFuZ3VhZ2UiOiJlbiIsInVpQ29uZmlnIjoie1wiY3VzdG9tUHJlc2V0Q29sb3JzXCI6W1wiMTQxOTMyXCIsXCIwMDVhOTZcIixcIjAwOWVmZlwiLFwiZTQwMDAwXCIsXCJhNWY3MjlcIixcImZmYjcwMFwiXSxcImRlZmF1bHRDdXN0b21MaWJyYXJpZXNcIjpbXCJBMVwiXSxcInZlcnNpb25cIjpcIjEuMFwifSIsImRpYWdyYW1EaXNwbGF5TmFtZSI6IiIsInNGaWxlSWQiOiIiLCJhdHRJZCI6IjcxMjA1MDczIiwiZGlhZ3JhbU5hbWUiOiJQYXlVSW5kaWFfcGF5c3NsX0NUIiwiYXNwZWN0IjoiIiwibGlua3MiOiJhdXRvIiwiY2VvTmFtZSI6IlBheVUgSW5kaWEiLCJ0YnN0eWxlIjoidG9wIiwiY2FuQ29tbWVudCI6ZmFsc2UsImRpYWdyYW1VcmwiOiIiLCJjc3ZGaWxlVXJsIjoiIiwiYm9yZGVyIjp0cnVlLCJtYXhTY2FsZSI6IjEiLCJvd25pbmdQYWdlSWQiOjI2MjQ3NjE4LCJlZGl0YWJsZSI6ZmFsc2UsImNlb0lkIjoyNjI0NzYxOCwicGFnZUlkIjoiIiwibGJveCI6dHJ1ZSwic2VydmVyQ29uZmlnIjp7ImVtYWlscHJldmlldyI6IjEifSwib2RyaXZlSWQiOiIiLCJyZXZpc2lvbiI6MCwibWFjcm9JZCI6Ijk4OWU3YzZkLTdlNWUtNDkxZC1iMjUyLWRjYjQxNDkzODgxZiIsInByZXZpZXdOYW1lIjoiUGF5VUluZGlhX3BheXNzbF9DVC5wbmciLCJsaWNlbnNlU3RhdHVzIjoiT0siLCJzZXJ2aWNlIjoiIiwiaXNUZW1wbGF0ZSI6IiIsIndpZHRoIjoiMTEwOSIsInNpbXBsZVZpZXdlciI6ZmFsc2UsImxhc3RNb2RpZmllZCI6Ik9jdCAxOCwgMjAyMiwgNzo1NDowMSBBTSIsImV4Y2VlZFBhZ2VXaWR0aCI6ZmFsc2UsIm9DbGllbnRJZCI6IiJ9

Process flow PayU India via form interface payssl.aspx

eyJleHRTcnZJbnRlZ1R5cGUiOiIiLCJnQ2xpZW50SWQiOiIiLCJjcmVhdG9yTmFtZSI6IkFkbWluIiwib3V0cHV0VHlwZSI6ImJsb2NrIiwibGFzdE1vZGlmaWVyTmFtZSI6IkFkbWluIiwibGFuZ3VhZ2UiOiJlbiIsInVpQ29uZmlnIjoie1wiY3VzdG9tUHJlc2V0Q29sb3JzXCI6W1wiMTQxOTMyXCIsXCIwMDVhOTZcIixcIjAwOWVmZlwiLFwiZTQwMDAwXCIsXCJhNWY3MjlcIixcImZmYjcwMFwiXSxcImRlZmF1bHRDdXN0b21MaWJyYXJpZXNcIjpbXCJBMVwiXSxcInZlcnNpb25cIjpcIjEuMFwifSIsImRpYWdyYW1EaXNwbGF5TmFtZSI6IiIsInNGaWxlSWQiOiIiLCJhdHRJZCI6IjcxMjA1MDY5IiwiZGlhZ3JhbU5hbWUiOiJQYXlVSW5kaWFfZGlyZWN0X0NUIiwiYXNwZWN0IjoiIiwibGlua3MiOiJhdXRvIiwiY2VvTmFtZSI6IlBheVUgSW5kaWEiLCJ0YnN0eWxlIjoidG9wIiwiY2FuQ29tbWVudCI6ZmFsc2UsImRpYWdyYW1VcmwiOiIiLCJjc3ZGaWxlVXJsIjoiIiwiYm9yZGVyIjp0cnVlLCJtYXhTY2FsZSI6IjEiLCJvd25pbmdQYWdlSWQiOjI2MjQ3NjE4LCJlZGl0YWJsZSI6ZmFsc2UsImNlb0lkIjoyNjI0NzYxOCwicGFnZUlkIjoiIiwibGJveCI6dHJ1ZSwic2VydmVyQ29uZmlnIjp7ImVtYWlscHJldmlldyI6IjEifSwib2RyaXZlSWQiOiIiLCJyZXZpc2lvbiI6MCwibWFjcm9JZCI6Ijc2NDM2NGI5LTRlYzUtNDNkMC1iNTMxLWQ0OGJhNjNjZTlhYiIsInByZXZpZXdOYW1lIjoiUGF5VUluZGlhX2RpcmVjdF9DVC5wbmciLCJsaWNlbnNlU3RhdHVzIjoiT0siLCJzZXJ2aWNlIjoiIiwiaXNUZW1wbGF0ZSI6IiIsIndpZHRoIjoiMTEwOSIsInNpbXBsZVZpZXdlciI6ZmFsc2UsImxhc3RNb2RpZmllZCI6Ik9jdCAxOCwgMjAyMiwgODowMzo0NiBBTSIsImV4Y2VlZFBhZ2VXaWR0aCI6ZmFsc2UsIm9DbGllbnRJZCI6IiJ9

Process flow PayU India via server-to-server interface direct.aspx

Configuration

For setting up the merchant for PayUIndia the Computop Helpdesk needs some information. These you can find in the PayU backend system for your own merchant account. Execute the command MyAccount and System Settings.

You need Salts and Login Alias from the system settings.

Transmit both values on a safe way to Computop Helpdesk.

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 India via Paygate form interface

To make a payment with PayU in India, please use the following URL:

https://www.computop-paygate.com/payuindia.aspx

Notice: For security reasons, Computop 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:

Key	Format	CND	Description
MerchantID	ans..30	M	MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too.

Key	Format	CND	Description
TransID	ans..64	M	TransactionID provided by you which should be unique for each payment

Key	Format	CND	Description
RefNr	ns..30	O	Merchant’s unique reference number (Must be unique for PayU)

Key	Format	CND	Description
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).

Key	Format	CND	Description
Currency	a3	M	Currency, three digits DIN / ISO 4217, e.g. EUR. Presently only INR, USD, GBP, CAD, EUR, AED, QAR, OMR, SGD, AUD, HKD permitted. Please find an overview here: A1 Currency table

Key	Format	CND	Description
MAC	an64	M	Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here: HMAC Authentication (Request) HMAC Authentication (Notify)

Key	Format	CND	Description
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. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.

Key	Format	CND	Description
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.

Key	Format	CND	Description
Response	a7	O	Status response sent by Paygate to URLSuccess and URLFailure, should be encrypted. For this purpose, transmit Response=encrypt parameter.

Key	Format	CND	Description
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. 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.

Key	Format	CND	Description
UserData	ans..1024	O	If specified at request, Paygate forwards the parameter with the payment result to the shop.

Key	Format	CND	Description
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.

Key	Format	CND	Description
OrderDesc	ans..100	M	Description of purchased goods, unit prices etc.
PayType	ans..25	O	Name of payment method to be executed

Key	Format	CND	Description
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.

Key	Format	CND	Description
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.

Key	Format	CND	Description
			Customer data
FirstName	ans..60	M	First name of the customer
LastName	ans..20	M	Last name of the customer
AddrStreet	ans..100	O	Customer’s street name
AddressAddition	ans..100	O	Customer´s address addition
AddrCity	ans..50	O	Town/city of the customer
AddrZip	ans..20	O	Postcode of the customer
AddrState	ans..50	O	Customer’s federal state
AddrCountryCode	a..3	O	Country code of the customer according to ISO 3166; alphanumeric 2 or 3 characters. Presently only India allowed.
CustomerID	ans..128	O	Customer number. If customer number is not submitted instead the email address is transferred to PayU. The customer number is used to identify the customer in order to be able to select credit card data which might be stored with PayU.
eMail	ans..128	O	Email address of the customer
Phone	ans..40	O	Customer’s phone number
			Credit card payment (in case of credit card payment the following parameters are mandatory)
CCNr	n..19	C	Credit card number at least 12-digit, numerical without spaces. You can optionally transmit also a pseudo card number (PCN)
CCCVC	n..4	C	Card verification number: The last 3 digits on the signature strip of the credit card. 4 numbers in the case of American Express.
CCExpiry	n6	C	Expiry date of the credit card in the format YYYYMM, e.g. 202807
CCBrand	a..22	C	Card brand: only VISA, MasterCard, AMEX, Diners, RuPay allowed. Please note the spelling!
CreditCardHolder	ans..60	C	Name of the credit card holder

Parameters for payments with PayU India WebCheckout

The following table gives the result parameters which Computop Paygate transmits to URLSuccess or URLFailure and URLNotify. If you have specified the Response=encrypt parameter, the following parameters are sent Blowfish encrypted to your system:

pls. be prepared to receive additional parameters at any time and do not check the order of parameters

the key (e.g. mid, RefNr) should not be checked case-sentive

Key	Format	CND	Description
mid	ans..30	M	MerchantID, assigned by Computop

Key	Format	CND	Description
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.

Key	Format	CND	Description
XID	an32	M	ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate

Key	Format	CND	Description
TransID	ans..64	M	TransactionID provided by you which should be unique for each payment

Key	Format	CND	Description
refnr	ans..30	O	Merchant’s unique reference number

Key	Format	CND	Description
Status	a..50	M	OK or AUTHORIZED (URLSuccess) as well as FAILED (URLFailure)

Key	Format	CND	Description
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!

Key	Format	CND	Description
Code	an8	M	Error code according to Paygate Response Codes (A4 Error codes)

Key	Format	CND	Description
MAC	an64	M	Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here: HMAC Authentication (Request) HMAC Authentication (Notify)

Key	Format	CND	Description
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

Key	Format	CND	Description
UserData	ans..1024	O	If specified at request, Paygate forwards the parameter with the payment result to the shop.

Key	Format	CND	Description
TransactionID	ans..64	O	Transaction ID from PayU
Channel	a..5	M	Name of payment category to be used with the following possible values: ‘NB’ for Net Banking, ‘CC’ for Credit Card, ‘DC’ for Debit Card, ‘CASH’ for Cash Card, ‘EMI’ for EMI, ‘wallet’ for PayUMoney, ‘IVR’ for IVR, ‘COD’ for Cash On Delivery
BankCode	a..5	M	Identification of the payment option used for the transaction: VISA, MAST, SAME, MAES, RUPAY, CC, AMEX, DINR
Brand	a..5	C	Specific card type: VISA, MAST, SAME, MAES, RUPAY, CC, AMEX, DINR

Key	Format	CND	Description
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.

Key	Format	CND	Description
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.

Return parameters for URLSuccess, URLFailure and URLNotify with PayU India WebCheckout

Credit card payment with PayU India via Paygate form interface

In order to execute a credit card payment in India with PayU India via a Paygate form, please use the following URL:

https://www.computop-paygate.com/payssl.aspx

Notice: For security reasons, Computop 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:

Key	Format	CND	Description
MerchantID	ans..30	M	MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too.

Key	Format	CND	Description
TransID	ans..64	M	TransactionID provided by you which should be unique for each payment

Key	Format	CND	Description
RefNr	ns..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!

Key	Format	CND	Description
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).

Key	Format	CND	Description
Currency	a3	M	Currency, three digits DIN / ISO 4217, e.g. EUR. Presently only INR, USD, GBP, CAD, EUR, AED, QAR, OMR, SGD, AUD, HKD permitted. Please find an overview here: A1 Currency table

Key	Format	CND	Description
MAC	an64	M	Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here: HMAC Authentication (Request) HMAC Authentication (Notify)

Key	Format	CND	Description
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. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.

Key	Format	CND	Description
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.

Key	Format	CND	Description
Response	a7	O	Status response sent by Paygate to URLSuccess and URLFailure, should be encrypted. For this purpose, transmit Response=encrypt parameter.

Key	Format	CND	Description
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. 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.

Key	Format	CND	Description
UserData	ans..1024	O	If specified at request, Paygate forwards the parameter with the payment result to the shop.

Key	Format	CND	Description
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.

Key	Format	CND	Description
OrderDesc	ans..100	M	Description of purchased goods, unit prices etc.
RTF	a1	O	„I“ for initializing recurrent payments

Key	Format	CND	Description
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.

Key	Format	CND	Description
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.

Key	Format	CND	Description
			Customer data
FirstName	ans..60	M	First name of the customer
LastName	ans..20	M	Last name of the customer
AddrStreet	ans..100	O	Customer’s street name
AddressAddition	ans..100	O	Customer´s address addition
AddrCity	ans..50	O	Town/city of the customer
AddrZip	ans..20	O	Postcode of the customer
AddrState	ans..50	O	Customer’s federal state
AddrCountryCode	a..3	O	Country code of the customer according to ISO 3166; alphanumeric 2 or 3 characters. Presently only India allowed.
CustomerID	ans..128	O	Customer number. The customer number is used to identify the customer at PayU. If this is submitted the PayU stores the card number. If CustomerID is transmitted to PayUIndia.aspx for subsequent payments the customer only needs to input the CVC within the form.
eMail	ans..128	O	Email address of the customer
Phone	ans..40	O	Customer’s phone number

Parameters for credit card payments with PayU India in India

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

Key Format CND Description
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”.

Key Format CND Description
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

Key Format CND Description
BGColor ans..7 O
Form background colour:
- HTML-colour value for background colour as HEX value or
- HTML-colour name

Key Format CND Description
BGImage
ans..256
O
Form background image:
URL for a background image
Please note that this value supersedes “BGColor”.

Key Format CND Description
FColor
ans..7
O
Text colour:
- HTML-colour value as HEX value or
- HTML-colour name

Key Format CND Description
FFace
a..10
O
HTML-name for the font

Key Format CND Description Beschreibung
FSize
n2
O
Number for font size
Zahl für die Schriftgröße

Key

Format

CND

Description

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, AMEX, Diners, RuPay

Key Format CND Description
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.

Key Format CND Description
Center
n1
O
By default the form is centered vertically and horizontally. The value <1> centres the form at the top.

Key Format CND Description
tWidth
ans..4
O
Width of table for input in the form as percent- (50%) or pixel values (320).

Key Format CND Description
tHeight
ans..4
O
Height of table for input of the payment data in the form as percent- (70%) or pixel values (480).

Layout parameters for Paygate forms for credit card payments with PayU India

The following table gives the result parameters which Computop Paygate transmits to URLSuccess or URLFailure and URLNotify. If you have specified the Response=encrypt parameter, the following parameters are sent Blowfish encrypted to your system:

pls. be prepared to receive additional parameters at any time and do not check the order of parameters

the key (e.g. mid, RefNr) should not be checked case-sentive

Key	Format	CND	Description
mid	ans..30	M	MerchantID, assigned by Computop

Key	Format	CND	Description
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.

Key	Format	CND	Description
XID	an32	M	ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate

Key	Format	CND	Description
TransID	ans..64	M	TransactionID provided by you which should be unique for each payment

Key	Format	CND	Description
refnr	ans..30	O	Merchant’s unique reference number

Key	Format	CND	Description
Status	a..50	M	OK or AUTHORIZED (URLSuccess) as well as FAILED (URLFailure)

Key	Format	CND	Description
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!

Key	Format	CND	Description
Code	an8	M	Error code according to Paygate Response Codes (A4 Error codes)

Key	Format	CND	Description
MAC	an64	M	Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here: HMAC Authentication (Request) HMAC Authentication (Notify)

Key	Format	CND	Description
CodeExt	ans..10	O	Error code from PayU, if agreed with Computop Helpdesk
ErrorText	ans..256	O	Error text from PayU, if agreed with Computop Helpdesk

Key	Format	CND	Description
UserData	ans..1024	O	If specified at request, Paygate forwards the parameter with the payment result to the shop.

Key	Format	CND	Description
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.

Key	Format	CND	Description
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.

Key	Format	CND	Description
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.
MaskedPan	an..19	OC	Masked card number 6x4
TransactionID	ans..64	C	Transaction ID from PayU
TokenExt	an..64	C	For recurring payments (RTF=I) the Token is transmitted for referencing the credit card data
Channel	a..5	M	Name of payment category to be used with the following possible values: ‘NB’ for Net Banking, ‘CC’ for Credit Card, ‘DC’ for Debit Card, ‘CASH’ for Cash Card, ‘EMI’ for EMI, ‘wallet’ for PayUMoney, ‘IVR’ for IVR, ‘COD’ for Cash On Delivery
BankCode	a..5	M	Identification of the payment option used for the transaction: VISA, MAST, SAME, MAES, RUPAY, CC, AMEX, DINR
Brand	a..5	C	Specific card type: VISA, MAST, SAME, MAES, RUPAY, CC, AMEX, DINR

Key	Format	CND	Description
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.

Key	Format	CND	Description
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.

Return parameters for URLSuccess, URLFailure and URLNotify with PayU India

Credit card payment via Server-to-Server connection

In order to execute a recurring credit card payment with PayU India in India via a server-to-server connection, please use the following URL:

https://www.computop-paygate.com/direct.aspx

Notice: For security reasons, Computop 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:

Key	Format	CND	Description
MerchantID	ans..30	M	MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too.

Key	Format	CND	Description
TransID	ans..64	M	TransactionID provided by you which should be unique for each payment

Key	Format	CND	Description
RefNr	ns..30	C	Merchant’s unique reference number (Must be unique for PayU). Mandatory for the initial payment of a new abo (RTF=I).

Key	Format	CND	Description
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).

Key	Format	CND	Description
Currency	a3	M	Currency, three digits DIN / ISO 4217, e.g. EUR. Presently only INR, USD, GBP, CAD, EUR, AED, QAR, OMR, SGD, AUD, HKD permitted. Please find an overview here: A1 Currency table

Key	Format	CND	Description
MAC	an64	M	Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here: HMAC Authentication (Request) HMAC Authentication (Notify)

Key

Format

CND

Description

Capture

an..6

OM

Determines the type and time of capture.

Capture Mode	Description
AUTO	Capturing immediately after authorisation (default value).
MANUAL	Capturing made by the merchant. Capture is normally initiated at time of delivery.
<Number>	Delay in hours until the capture (whole number; 1 to 696).

Key	Format	CND	Description
UserData	ans..1024	O	If specified at request, Paygate forwards the parameter with the payment result to the shop.

Key	Format	CND	Description
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.

Key	Format	CND	Description
OrderDesc	ans..100	M	Description of purchased goods, unit prices etc.
RTF	a1	O	„I“ for initializing recurrent payments
CCNr	n..19	M	Pseudo card number
CCExpiry	n6	M	Credit card expiry date (YYYYMM), e.g. 202807
CCBrand	a..22	M	Card brand: only VISA, MasterCard, AMEX, Diners, RuPay. Please note the spelling!
TokenExt	an..64	M	Token for referencing the credit card data with PayU
TransactionID	ans..64	M	TransactionID from PayU which is returned with the initial payment (RTF=I)
CustomerID	ans..128	O	Customer number. If customer number is not submitted instead the email address is transferred to PayU. The customer number is used to identify the customer in order to be able to select credit card data which might be stored with PayU.
eMail	ans..128	O	Email address of the customer

Parameters for credit card payments with PayU India via socket connection

The following table describes the result parameters with which the Computop Paygate responds to your system

pls. be prepared to receive additional parameters at any time and do not check the order of parameters

the key (e.g. mid, RefNr) should not be checked case-sentive

Key	Format	CND	Description
mid	ans..30	M	MerchantID, assigned by Computop

Key	Format	CND	Description
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.

Key	Format	CND	Description
XID	an32	M	ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate

Key	Format	CND	Description
TransID	ans..64	M	TransactionID provided by you which should be unique for each payment

Key	Format	CND	Description
refnr	ans..30	O	Merchant’s unique reference number

Key	Format	CND	Description
Status	a..50	M	OK or AUTHORIZED (URLSuccess) as well as FAILED (URLFailure)

Key	Format	CND	Description
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!

Key	Format	CND	Description
Code	an8	M	Error code according to Paygate Response Codes (A4 Error codes)

Key	Format	CND	Description
CodeExt	ans..10	O	Error code from PayU, if agreed with Computop Helpdesk
ErrorText	ans..256	O	Error text from PayU, if agreed with Computop Helpdesk

Key	Format	CND	Description
UserData	ans..1024	O	If specified at request, Paygate forwards the parameter with the payment result to the shop.

Key	Format	CND	Description
Channel	a..5	M	Name of payment category to be used with the following possible values: ‘NB’ for Net Banking, ‘CC’ for Credit Card, ‘DC’ for Debit Card, ‘CASH’ for Cash Card, ‘EMI’ for EMI, ‘wallet’ for PayUMoney, ‘IVR’ for IVR, ‘COD’ for Cash On Delivery
BankCode	a..5	M	Identification of the payment option used for the transaction: VISA, MAST, SAME, MAES, RUPAY, CC, AMEX, DINR
Brand	a..5	C	Specific card type: VISA, MAST, SAME, MAES, RUPAY, CC, AMEX, DINR

Result parameters for socket connection with PayU India

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:

https://www.computop-paygate.com/credit.aspx

Notice: For security reasons, Computop 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:

Key	Format	CND	Description
MerchantID	ans..30	M	MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too.

Key	Format	CND	Description
PayID	an32	M	ID assigned by Paygate for the payment to be credited

Key	Format	CND	Description
TransID	ans..64	M	TransactionID provided by you which should be unique for each payment

Key	Format	CND	Description
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).

Key	Format	CND	Description
Currency	a3	M	Currency, three digits DIN / ISO 4217, e.g. EUR. Presently only INR, USD, GBP, CAD, EUR, AED, QAR, OMR, SGD, AUD, HKD permitted. Please find an overview here: A1 Currency table

Key	Format	CND	Description
MAC	an64	M	Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here: HMAC Authentication (Request) HMAC Authentication (Notify)

Key	Format	CND	Description
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.

Key	Format	CND	Description
OrderDesc	ans..100	O	Description of refunded goods, unit prices, merchant’s comment etc.

Parameters for credit of credit card payments with PayU India via socket connection

The following table describes the result parameters with which the Computop Paygate responds to your system

pls. be prepared to receive additional parameters at any time and do not check the order of parameters

the key (e.g. mid, RefNr) should not be checked case-sentive

Key	Format	CND	Description
mid	ans..30	M	MerchantID, assigned by Computop

Key	Format	CND	Description
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.

Key	Format	CND	Description
XID	an32	M	ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate

Key	Format	CND	Description
TransID	ans..64	M	TransactionID provided by you which should be unique for each payment

Key	Format	CND	Description
Status	a..50	M	OK (URLSuccess) or FAILED (URLFailure)

Key	Format	CND	Description
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!

Key	Format	CND	Description
Code	an8	M	Error code according to Paygate Response Codes (A4 Error codes)

Key	Format	CND	Description
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

Response parameters for credit of credit card payments with PayU India via socket connection

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 India 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
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)
Reverse	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 India transaction within a Batch file to be submitted is as follows:

HEAD,<MerchantID>,<Date>,<Version>
CC,Credit,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>
CC,Reverse,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>
FOOT,<CountRecords>,<SumAmount>

Example for Master MID function:

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:

Key	Format	CND	Description
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: Credit Reverse

Key	Format	CND	Description
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).

Key	Format	CND	Description
Currency	a3	M	Currency, three digits DIN / ISO 4217, e.g. EUR. Presently only INR, USD, GBP, CAD, EUR, AED, QAR, OMR, SGD, AUD, HKD permitted. Please find an overview here: A1 Currency table

Key	Format	CND	Description
TransID	ans..64	M	TransactionID provided by you which should be unique for each payment

Key	Format	CND	Description
RefNr	ns..30	O	Merchant’s unique reference number (Must be unique for PayU)

Key	Format	CND	Description
PayID	an32	M	ID assigned by Paygate for this transaction

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>
CC,Credit,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>,<Status>,<Code>
CC,Reverse,<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):

Key	Format	CND	Description
Action	a..20	M	The parameter Action defines the type of transaction: Credit Reverse

Key	Format	CND	Description
PayID	an32	M	ID assigned by Paygate for this transaction

Key	Format	CND	Description
Status	a..50	M	OK (URLSuccess) or FAILED (URLFailure)

Key	Format	CND	Description
Code	an8	M	Error code according to Paygate Response Codes (A4 Error codes)

Description of result parameters within the record for Batch files

Space shortcuts

Page tree

About PayU India

General information about payment methods via PayU India

Process flow charts

Configuration

Paygate interface

Definitions

Data formats

Abbreviations

Payment with PayU India via Paygate form interface

Credit card payment with PayU India via Paygate form interface

Credit card payment via Server-to-Server connection

Credit with reference

Batch processing via the interface

Paygate

Computop

Help

Intranet Tools