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
Process flow for PayU India WebCheckout
Process flow PayU India via form interface payssl.aspx
Process flow PayU India via server-to-server interface direct.aspx
Configuration
For setting up the merchant for PayUIndia the Computop Support 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 Support.
Paygate interface
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 CND condition M mandatory O optional C conditional Notice: Please note that the names of parameters can be returned in upper or lower case.Definitions
Data formats
Abbreviations
Comment If a parameter is mandatory, then it must be present If a parameter is optional, then it can be present, but it is not required If a parameter is conditional, then there is a conditional rule which specifies whether it is mandatory or optional
Payment with PayU India via Paygate form interface
To make a payment with PayU in India, go to the following URL:
Notice: For security reasons, Paygate rejects all payment requests with formatting errors. Therefore please use the correct data type for each parameter.
The following table describes the encrypted payment request parameters:
Parameter | Format | CND | Description |
|---|---|---|---|
MerchantID | ans..30 | M | MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too. |
TransID | ans..64 | M | Merchant transaction number, which must be unique |
RefNr | ns..30 | M | Unique reference number |
Amount | n..10 | M | Amount in the smallest currency unit (e.g. EUR Cent) Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit). |
Currency | a3 | M | Currency, three digits DIN / ISO 4217. Presently only INR, USD, GBP, CAD, EUR, AED, QAR, OMR, SGD, AUD, HKD permitted. |
MAC | an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm |
URLSuccess | ans..256 | M | Complete URL which calls up Paygate if payment has been successful. The URL may be called up only via port 443 This URL may not contain parameters: In order to exchange values between Paygate and shop, please use the parameter UserData. |
URLFailure | ans..256 | M | Complete URL which calls up Paygate if payment has been unsuccessful. The URL may be called up only via port 443 This URL may not contain parameters: In order to exchange values between Paygate and shop, please use the parameter UserData. |
Response | a7 | O | Status response sent by Paygate to URLSuccess and URLFailure, should be encrypted. For this purpose, transmit Response=encrypt parameter. |
URLNotify | ans..256 | M | Complete URL which Paygate calls up in order to notify the shop about the payment result. The URL may be called up only via port 443 It may not contain parameters: Use the UserData parameter instead. |
UserData | ans..1024 | O | If specified at request, Paygate forwards the parameter with the payment result to the shop |
ReqID | ans..32 | O | To avoid double payments, enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction is submitted again with the same ReqID, Paygate will not carry out the payment, but will just return the status of the original transaction. Please note that the Paygate must have a finalized transaction status for the first initial action. Submissions with identical ReqID for an open status will be processed regularly. |
OrderDesc | ans..100 | M | Description of purchased goods, unit prices etc. |
PayType | ans..25 | O | Name of payment method to be executed |
Plain | ans..50 | O | A value to be set by the merchant to return some information unencrypted, e.g. the MID |
Custom | ans..1024 | O | The merchant can submit several values separated by | which are returned unencrypted and separated by &. Custom=session=123|id=456 will change in the answer to Session=123&id=456 |
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. |
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. 201807. |
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 describes the result parameters that the Paygate transmits to your URLSuccess, URLFailure or URLNotify. If you have specified the Response=encrypt parameter, the following parameters are forwarded Blowfish encrypted to your system:
Parameter | Format | CND | Description | |
|---|---|---|---|---|
MID | ans..30 | M | MerchantID, assigned by Computop | |
PayID | an32 | M | ID assigned by Paygate for the payment, e.g. for referencing in batch files. | |
XID | an32 | M | ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate | |
TransID | ans..64 | M | Merchant’s transaction number | |
Status | a..30 | 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 | n8 | M | Error code according to Paygate Response Codes (A4 Error codes) | |
RefNr | ns..30 | O | Merchant’s unique reference number | |
MAC | an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm | |
CodeExt | n..10 | O | Error code from PayU, if agreed with Computop support | |
ErrorText | ans..256 | O | Error text from PayU, if agreed with Computop support | |
UserData | ans..1024 | O | If specified at request, Paygate forwards the parameter with the payment result to the shop | |
TransactionID | ans..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 | |
Plain | ans..50 | O | A value to be set by the merchant to return some information unencrypted, e.g. the MID | |
Custom | ans..1024 | O | The merchant can submit several values separated by | which are returned unencrypted and separated by &. Custom=session=123|id=456 will change in the answer to Session=123&id=456 | |
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, visit the following URL:
Notice: For security reasons, Paygate rejects all payment requests with formatting errors. Therefore please use the correct data type for each parameter.
The following table describes the encrypted payment request parameters:
Parameter | Format | CND | Description |
|---|---|---|---|
MerchantID | ans..30 | M | MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too. |
TransID | ans..64 | M | TransactionID which should be unique for each payment |
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! |
Amount | n..10 | M | Amount in the smallest currency unit (e.g. EUR Cent) Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit). |
Currency | a3 | M | Currency, three digits DIN / ISO 4217. Presently only INR, USD, GBP, CAD, EUR, AED, QAR, OMR, SGD, AUD, HKD permitted. |
MAC | an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm |
OrderDesc | ans..100 | M | Description of purchased goods, unit prices etc. |
URLSuccess | ans..256 | M | Complete URL which calls up Paygate if payment has been successful. The URL may be called up only via port 443 This URL may not contain parameters: In order to exchange values between Paygate and shop, please use the parameter UserData. |
URLFailure | ans..256 | M | Complete URL which calls up Paygate if payment has been unsuccessful. The URL may be called up only via port 443 This URL may not contain parameters: In order to exchange values between Paygate and shop, please use the parameter UserData. |
Response | a7 | O | Status response sent by Paygate to URLSuccess and URLFailure, should be encrypted. For this purpose, transmit Response=encrypt parameter. |
URLNotify | ans..256 | M | Complete URL which Paygate calls up in order to notify the shop about the payment result. The URL may be called up only via port 443 It may not contain parameters: Use the UserData parameter instead. |
UserData | ans..1024 | O | If specified at request, Paygate forwards the parameter with the payment result to the shop |
ReqID | ans..32 | O | To avoid double payments, enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction is submitted again with the same ReqID, Paygate will not carry out the payment, but will just return the status of the original transaction. Please note that the Paygate must have a finalized transaction status for the first initial action. Submissions with identical ReqID for an open status will be processed regularly. |
RTF | a1 | O | „I“ for initializing recurrent payments |
Plain | ans..50 | O | A value to be set by the merchant to return some information unencrypted, e.g. the MID |
Custom | ans..1024 | O | The merchant can submit several values separated by | which are returned unencrypted and separated by &. Custom=session=123|id=456 will change in the answer to Session=123&id=456 |
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. |
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.
Parameter | Format | CND | Description |
|---|---|---|---|
Template | ans..20 | M | Name of XSLT-file with your own layout for the pay form. If you want to use the redesigned and downwards compatible Computop template, please transfer the template name “ct_compatible”. If you want to use the responsive Computop template for mobile devices, please transfer the template name “ct_responsive”. |
Background | ans..256 | M | Background ambiance of form: URL for a background image - HTML-colour value for background colour as HEX value or - HTML-colour name |
BGColor | ans..7 | M | Form background colour: - HTML-colour value for background colour as HEX value or - HTML-colour name |
BGImage | ans..256 | M | Form background image: URL for a background image Please note that this value supersedes “BGColor”. |
FColor | ans..6 | M | Text colour: - HTML-colour value as HEX value or - HTML-colour name |
FFace | a..10 | M | HTML-name for the font |
FSize | n2 | M | Number for font size |
Language | a2 (enum) | M | Language code: <de> German, <al> Albanian, <at> Austrian, <cz/cs> Czech, <dk> Danish, <en> English, <fi> Finish, <fr> French, <gr> Greek, <hu> Hungarian, <it> Italian, <jp> Japanese, <nl> Dutch, <no> Norwegian, <pl> Polish, No details means the language is German. |
CCSelect | a..10 | M | Determines preselected card type in the form: VISA, MasterCard, AMEX, Diners, RuPay |
URLBack | ans..256 | M | URL for "Cancel" button |
Center | n1 | M | By default the form is centered vertically and horizontally. The value <1> centres the form at the top. |
tWidth | ans..4 | M | Width of table for input of the credit card data as percent- (50%) or pixel values (320). |
tHeight | ans..4 | M | Height of table for input of the credit card data as percent- (70%) or pixel values (480). |
Layout parameters for Paygate forms for credit card payments with PayU India
The following table describes the result parameters that the Paygate transmits to your URLSuccess, URLFailure or URLNotify. If you have specified the Response=encrypt parameter, the following parameters are forwarded Blowfish encrypted to your system:
Parameter | Format | CND | Description |
|---|---|---|---|
MID | ans..30 | M | MerchantID, assigned by Computop |
PayID | an32 | M | ID assigned by Paygate for the payment, e.g. for referencing in batch files. |
XID | an32 | M | ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate |
TransID | ans..64 | M | Merchant’s transaction number |
Status | a..30 | 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 | n8 | M | Error code according to Paygate Response Codes (A4 Error codes) |
CodeExt | ans..10 | O | Error code from PayU, if agreed with Computop support |
ErrorText | ans..256 | O | Error text from PayU, if agreed with Computop support |
MAC | an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm |
UserData | ans..1024 | O | If specified at request, Paygate forwards the parameter with the payment result to the shop. |
RefNr | ans..30 | O | Merchant’s unique reference number |
PCNr | n..16 | O | Pseudo Card Number: Random number generated by Paygate which represents a genuine credit card number. The pseudo card number (PCN) starts with 0 and the last 3 digits correspond to those of the real card number. You can use the PCN like a genuine card number for authorisation, capture and credits. |
CCBrand | a..22 | O | In combination with PCNr: Name of credit card brand like Visa, MasterCard etc. |
CCExpiry | n6 | O | In combination with PCNr: Expiry date of the credit card in the format YYYYMM. |
MaskedPan | an..19 | 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 |
Plain | ans..50 | O | A value to be set by the merchant to return some information unencrypted, e.g. the MID |
Custom | ans..1024 | O | The merchant can submit several values separated by | which are returned unencrypted and separated by &. Custom=session=123|id=456 will change in the answer to Session=123&id=456 |
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, call the following URL:
Notice: For security reasons, Paygate rejects all payment requests with formatting errors. Therefore please use the correct data type for each parameter.
The following table describes the encrypted payment request parameters:
Parameter | Format | CND | Description |
|---|---|---|---|
MerchantID | ans..30 | M | MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too. |
TransID | ans..64 | M | Merchant’s transaction number |
RefNr | ns..30 | C | Merchant’s reference number. Mandatory for the initial payment of a new abo (RTF=I) |
Amount | n..10 | M | Amount in the smallest currency unit (e.g. EUR Cent) Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit). |
Currency | a3 | M | Currency, three digits DIN / ISO 4217. Presently only INR, USD, GBP, CAD, EUR, AED, QAR, OMR, SGD, AUD, HKD permitted. |
Capture | an..6 | OC | Determines the type and time of capture. AUTO: capturing immediately after authorisation (default value). MANUAL: capturing made by the merchant. <Number>: Delay in hours until the capture (whole number; 1 to 696). |
MAC | an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm |
OrderDesc | ans..100 | M | Description of purchased goods, unit prices etc. |
UserData | ans..1024 | O | If specified at request, Paygate forwards the parameter with the payment result to the shop |
CCNr | n..19 | M | Pseudo card number |
CCExpiry | n6 | M | Credit card expiry date (YYYYMM), e.g. 201807 |
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) |
ReqID | ans..32 | O | To avoid double payments, enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction is submitted again with the same ReqID, Paygate will not carry out the payment, but will just return the status of the original transaction. Please note that the Paygate must have a finalized transaction status for the first initial action. Submissions with identical ReqID for an open status will be processed regularly. |
RTF | a1 | O | „I“ for initializing recurrent payments |
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. |
ans..128 | O | Email address of the customer |
Parameters for credit card payments with PayU India via socket connection
The following table gives the parameters with which the Paygate responds:
Parameter | Format | CND | Description |
|---|---|---|---|
MID | ans..30 | M | MerchantID, assigned by Computop |
PayID | an32 | M | ID assigned by Paygate for the payment, e.g. for referencing in batch files. |
XID | an32 | M | ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate |
TransID | ans..64 | M | Merchant’s transaction number |
Status | a..30 | M | OK, AUTHORIZED or FAILED |
Description | ans..1024 | M | Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis! |
Code | n8 | M | Error code according to Paygate Response Codes (A4 Error codes) |
CodeExt | ans..10 | O | Error code from PayU, if agreed with Computop support |
ErrorText | ans..256 | O | Error text from PayU, if agreed with Computop support |
RefNr | ns..30 | O | Merchant’s unique reference number |
UserData | ans..1024 | O | If specified at request, Paygate forwards the parameter with the payment result to the shop. |
| 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, please use the following URL:
Notice: For security reasons, Paygate rejects all payment requests with formatting errors. Therefore please use the correct data type for each parameter.
The following table describes the encrypted payment request parameters:
Parameter | Format | CND | Description |
|---|---|---|---|
MerchantID | ans..30 | M | MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too. |
PayID | an32 | M | ID assigned by Paygate for the payment to be credited |
TransID | ans..64 | M | ID assigned by Merchant for the payment process to be credited |
Amount | n..10 | M | Amount in the smallest currency unit (e.g. USD Cent) Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit). |
Currency | a..3 | M | Currency, three digits DIN / ISO 4217. Presently only INR, USD, GBP, CAD, EUR, AED, QAR, OMR, SGD, AUD, HKD permitted. |
MAC | an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm |
OrderDesc | ans..100 | O | Description of refunded goods, unit prices, merchant’s comment etc. |
| ReqID | ans..32 | O | To avoid double payments, enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction is submitted again with the same ReqID, Paygate will not carry out the payment, but will just return the status of the original transaction. Please note that the Paygate must have a finalized transaction status for the first initial action. Submissions with identical ReqID for an open status will be processed regularly. |
Parameters for credit of credit card payments with PayU India via socket connection
The following table describes the Paygate response parameters:
Parameter | Format | CND | Description |
|---|---|---|---|
MID | ans..30 | M | MerchantID, assigned by Computop |
PayID | an32 | M | ID assigned by Paygate for the payment, e.g. for referencing in batch files |
XID | an32 | M | ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate |
TransID | ans..64 | M | Merchant’s transaction number |
Status | a..30 | M | OK or FAILED |
Description | ans..1024 | M | Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis! |
Code | n8 | M | Error code according to Paygate Response Codes (A4 Error codes) |
CodeExt | n..10 | O | Error code from PayU, if agreed with Computop support |
ErrorText | ans..256 | O | Error text from PayU, if agreed with Computop support |
Response parameters for credit 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 Funktion:
| HEAD,[Master]MerchantID,Date,2.x Type,Action,[Slave]MID,Amount,Currency,TransID,Data (depends on Action) FOOT,CountRecords,SumAmount |
The following table describes the individual fields and values used within the data set (record) in the batch file:
Parameter | Format | CND | Description |
|---|---|---|---|
Type | a..11 | M | HEAD for Header, FOOT for Footer, CC for credit card |
Action | a..20 | M | The parameter Action defines the type of transaction: Credit |
Amount | n..10 | M | Amount in the smallest currency unit (e.g. EUR Cent) Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit). |
Currency | a3 | M | Currency code, three digits DIN / ISO 4217. Presently only INR, USD, GBP, CAD, EUR, AED, QAR, OMR, SGD, AUD, HKD permitted. |
TransID | ans..64 | M | TransactionID which should be unique for each payment |
RefNr | ns..30 | O | Unique reference number |
PayID | an32 | M | ID for this transaction given by Paygate |
Description of fields within the record for Batch files
The record area within the response file for Batch transactions looks as follows:
HEAD,<MerchantID>,<Date>,<Version> 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):
Parameter | Format | CND | Description |
|---|---|---|---|
Action | a..20 | M | The parameter Action defines the type of transaction: Credit |
PayID | an32 | M | ID for this transaction given by Paygate |
Status | a..50 | M | OK or FAILED |
Code | n8 | M | Error code according to Paygate Response Codes (A4 Error codes) |
Description of result parameters within the record for Batch files