Overview - APIs

Pinelab's Billing System Integration SDK supports both CSV and JSON format message protocol between the POS System and the Payment terminal. This section describes the message format followed by the POS Lib's doTransaction API to process transaction with Payment device

Message Protocol

The messages that are transmitted between the POS and the Terminal will use the following structure. Both request and response messages exchanged shall follow the same structure

Message Structure


Request Packet Structure
Byte Number Type Content Description
1 to 2 BYTE Source ID Identification Number for client (e.g. 0x1000)
3 to 4 BYTE Function Code 0x0997 Refer Function Codes
5 to 6 BYTE Data Length Excluding ETX E.g. 0x0032 for a data length of 50 bytes
7 to N ASCII Data 4001,TX1234567890,215400,,,,,,,
N+1 BYTE ETX 0xFF

Response Packet Structure
Byte Number Type Content Description
1 to 2 BYTE Source ID Identification Number for client (e.g. 0x1000)
3 to 4 BYTE Function Code 0x0997 Refer Function Codes
5 to 6 BYTE Error Code 0x0001 - valid response, 0x0000 - invalid response
0x0002 - Cancel response
7 to 8 BYTE Data Length Excluding ETX E.g. 0x0032 for a data length of 50 bytes
9 to N ASCII Data "T1/1234567890,""000059"",""APPROVED"",
""401152******15 69"",""XXXX"",
""AXIS BANK GIFT CARD"",""VISA"",370,203,
""78569456"",0,""PROCESSED"",""HDFC BANK"",
"""",""000020"",1,1,""PINE LABS PVT.LTD."",
""Testing Server"",""NOIDA - INDIA"",
""Plutus v1.49.1 MT HDFC BANK"",01,00,
"""","""","""",,"""","""","""","""",""08012012"",""150118"""
N+1 BYTE ETX 0xFF

CSV requests and responses, data fields are separated by commas (,). There are 23 fields in total, where some are mandatory while others are optional depending on the transaction type.

For instance, in a sale request, fields 1 and 3 are mandatory, and the merchant billing application must provide the data for these fields. The remaining fields, which are optional, can either be filled with data or left empty based on specific requirements.
Example:
4001,,1000

Here's an example for a sale request, if the merchant billing application need to send fields 1, 2, 3, and 16, where 2 and 16 are optional, it can leave fields 4 to 15 empty using commas, like this:
Example:
4001,2,1000,,,,,,,,,,,,,16

In the above example, field 1 represents the transaction code, field 3 represents the transaction amount, and fields 2 and 16 are optional and filled as needed. The remaining fields from 4 to 15 are left empty with commas

Sale Transaction

A transaction between two parties where the buyer receives goods (tangible or intangible),services and/or assets in exchange for money.

Message Format


Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer the Transaction Types Range: 4001-4216 4001 Mandatory
2 Billing reference number String 0 – 25 Transaction reference number from external “TX12345678” Optional
3 Total EFT Amount Long Integer 0 - 8 Amount to be charged to card – expressed as a whole number in lowest currency unit (ie. in paisa) 999999 Mandatory
15 Reward\Cash amount Long Integer 1 – 8 Amount to be paid by reward points or in cash in paise (or in lowest currency) 999999 Optional
16 Customer Mobile Number String 1 – 100 Customer mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
17 Customer email id(s) String 1 – 500 Customer email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
18 Merchant mobile number(s) String 1 – 100 Merchant mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
19 Merchant email id(s) String 1 – 500 Merchant email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
20 Consent to send charge slip on customer mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her mobile number(s). TRUE Optional
21 Consent to send charge slip on customer email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her email id(s). TRUE Optional
22 Consent to send charge slip on merchant mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her mobile number. TRUE Optional
23 Consent to send charge slip on merchant email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her email id(s). TRUE Optional

Response Parameters

Position in CSV Field Name Data Type Length Description Sample
Value
Mandatory/
Optional
1 Billing Reference Number String 0 - 25 Transaction reference number from external application. TX12345678 Mandatory
2 Approval Code String 1 - 6 Credit card authorization code, if transaction was approved. Otherwise empty string. Presence of non-zero length approval code string indicates successful authorization of transaction. This logic holds true for Pine 360 transactions as well. “5261AJ” Mandatory
3 Host Response String 0 - 50 Response string if a response for transaction was received from bank switch. Otherwise, if any error occurs before response is received, this is an empty string. “APPROVED” Mandatory
4 Card Number String 0 - 19 Card number is valid if card was swiped. Otherwise, empty string. “************2802” Mandatory
5 Expiration Date String 0 or 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. “XXXX” Mandatory
6 Cardholder’s Name String 0 - 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string. “AMIT MOHAN” Mandatory
7 Card Type String 0 - 12 Card association name, if valid card was swiped. Otherwise, empty string. “VISA” Mandatory
8 Invoice Number/EDC ROC (in case of Reward Transaction) Long Integer 0 - 6 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on charge slip). Range 0 - 999999 / 101 - 999 (in case of Reward Transaction) 78/101 Mandatory
9 Batch Number/EDC Batch ID (in case of Reward Transaction) Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction). Mandatory
10 Terminal ID String 0 or 8 EFT TID, if transaction authorized. Otherwise, empty string. “30000001” Mandatory
11 Loyalty Points Awarded Long 0 - 8 RFU – not used.
Range: 0 – 99999999
0 Mandatory
12 Remark String 0 - 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization. “Failed to dial modem” Mandatory
13 Transaction Acquirer Name String 0 - 48 Name of acquirer to which transaction was routed. “ICICI BANK” Mandatory
14 Merchant ID String 0 - 15 EFT ME ID, if transaction authorized. Otherwise, empty string. “000100090015607” Mandatory
15 Retrieval Reference Number String 0 - 12 EFT RRN, if transaction authorized. Otherwise, empty string. “000000012843” Mandatory
16 Card Entry Mode Integer 0 - 5 Enumeration of possible values: 0 – Manual entry 1 – Swipe entry 2 – Chip card entry Any other value – card not validated
Range: 0 – 32767
1 Mandatory
17 Print Cardholder's Name on receipt Integer 0 - 5 Enumeration of possible values: 0 – Do not print cardholder’s name 1 – Print cardholder’s name Any other value – card not validated. This is used if external application is to print Plutus charge slip.
Range: 0 – 32767
0 Mandatory
18 Merchant Name String 0 - 23 Merchant name, if transaction authorized. Otherwise, empty string. “NOBLE MOTORS” Mandatory
19 Merchant Address String 0 - 23 Merchant address line, if transaction authorized. Otherwise, empty string. “HAJI ALI” Mandatory
20 Merchant City String 0 - 23 Merchant city line, if transaction authorized. Otherwise, empty string. “MUMBAI” Mandatory
21 Plutus Version String 0 - 40 Plutus version. “v1.54 (for ICICI BANK)” Mandatory
22 Acquiring Bank Code Integer 0 - 999 Code for bank used for processing transaction. Enumeration of possible values: 01 – HDFC BANK, 02 – ICICI BANK, 03 – AMERICAN EXPRESS, 04 – CITIBANK, 05 – AXIS BANK, 06 – SBI, 07 – HSBC, 09 – CORP BANK, 10 – CUB (City Union Bank), 14 – IDBI Bank, 17 – LVB (Lakshmi Vilas Bank), 51 - PINE 360, 301 - Sodexo, 81 – Loyalty Reward, 82 – Aimia, 85 – SBI Rewards Mandatory
23 Reward Redeemed Amount Long Integer 0 - 10 Redeemed Amount in Paisa or in lowest currency. “10000” Optional
24 Reward Redeemed Points Double 0 - 15 Redeemed Points. “400.00” Optional
25 Reward Balance Amount String 0 - 10 Balance Amount. “1000000” Optional
26 Reward Balance Points Double 0 - 15 Balance Point. “40000.00” Optional
27 Charge slip print data in tag value format (Optional)* String Charge slip data in form of tag and value separated with : and new pair separated with |*(Only present if charge slip data on merchant is enabled) Charge slip print data in tag value format(Optional)* Mandatory
28 RFU1/Coupon code/Loyalty Card Number String 0 - 23 Card Processing Fee in Rs (decimal) Or Coupon Code. Coupon code is the value which will be coming as a response to voucher redemption. This field will be present in case of voucher redemption. Or Loyalty number fetched if the transaction type is 4301. “5.50” Mandatory
29 Amount processed successfully by Plutus/ Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 - 99 Amount will always be in paisa or lowest currency. “100000” Mandatory
30 RFU3 String 0 - 23 Reserved for future use Mandatory
31 RFU String Specific for merchant Alhanumeric Optional
32 Date of Transaction String 0 - 8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format. “02012011” Mandatory
33 Time of Transaction String 0 - 6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24-hour format. “210403” Mandatory
34 PineLabs Client ID Integer 0 - 6 Unique ID assigned to Pine Labs EDC. 12345 Mandatory
42 Transcation Cuurency String 3 Indicates the currency code of the transaction AED Mandatory
43 Exchange Rate Double 0-15 This field is the relative value at which one currency can be exchanged for another currency 11.1 Mandatory
44 DCC Amount Double 0-15 Total amount processed for a transaction presented to a cardholder using Dynamic Currency Conversion 12.11 Mandatory
45 Markup Fee Double 0-15 A markup fee is an additional charge applied to the cost of a product or service to cover the seller's overhead costs, profit margin, and other expenses 5.5 Mandatory
46 Trace Number String 0-15 A unique sequence number assigned by the message initiator to uniquely identify a transaction. 11 Mandatory
47 AID String 0-15 EMV AID A00000000310 Mandatory
48 TVR String 0-15 EMV TVR 48000 Mandatory
49 ARQC String 0-16 Authorization Request Cryptogram is a cryptographic code generated by the card's chip during a payment transaction and is used to authenticate the legitimacy of the transaction request A2F8CD0C107F910 Mandatory


Request

HEX String Format
ASCII Format
10000997001D343030312C545831323334353637382C3130313030302C2C2C2C2C2C2CFF
— 4001,TX12345678,101000,,,,,,,ÿ

Response

HEX String Format
ASCII Format
999919970001015E012254583132333435363738222C223030222C22415050524F564544222C222A2A2A2A2A2A2A2A2A2A2A2A36373933222C2258585858222C224E494B48494C205020504154494C20202020202020202020202F222C2256495341222C313131382C32332C223939383030303236222C302C2250524F434553534544222C2249434943492042414E4B222C22202020202020202020202020202020222C22303030303030303030303230222C322C312C224C4F564520434F4D4D554E49434154494F4E222C224A414E414B50555249222C224E45572044454C48492020202044454C20202020202020222C22506C757475732076322E3132204D542049434943492042414E4B222C30322C22222C22222C22222C22222C22222C22222C22222C22222C22222C223036323332303233222C22313334333131222C2234323935323233303633222C22313030222C2234303031222C22434152445F4348495022FF
™™— ^"TX12345678","00","APPROVED","**6793","XXXX","NIKHIL P PATIL /","VISA",1118,23,"99800026",0,"PROCESSED","ICICI BANK","","000000000020",2,1,"LOVE COMMUNICATION","JANAKPURI","NEW DELHI DEL ","Plutus v2.12 MT ICICI BANK",02,"","","","","","","","","","06232023","134311","4295223063","100","4001","CARD_CHIP"ÿ

JSON Request:
 
    
Coming Soon
  

JSON Response:
 
    

Coming Soon




Please refer Error code and Error messages

Refund Transaction

Compensation paid to the customer for over-invoicing or for returned goods.

Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/ Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer the Transaction Types. Range: 4001-4216 4002 Mandatory
2 Billing reference number String 0 – 25 Transaction reference number from external application. Plutus will only use this value for printing on charge slip. “TX12345678” Optional
3 Total EFT Amount Long Integer 0 - 8 Amount to be charged to card – expressed as a whole number in lowest currency unit (ie. in paisa). 999999 Mandatory
12 EDC Batch ID Integer 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Batch Id of parent transition. Optional
13 EDC ROC Integer 3 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Roc of parent transition. 201 Optional
14 Transaction log ID Long Integer 01-12 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Transaction log of parent transition. 123234 Optional
15 Reward/Cash amount Long Integer 1 – 8 Amount to be paid by reward points or in cash in paise (or in lowest currency). 999999 Optional
16 Customer Mobile Number String 1 – 100 Customer mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
17 Customer email id(s) String 1 – 500 Customer email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
18 Merchant mobile number(s) String 1 – 100 Merchant mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
19 Merchant email id(s) String 1 – 500 Merchant email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
20 Consent to send charge slip on customer mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her mobile number(s). TRUE Optional
21 Consent to send charge slip on customer email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her email id(s). TRUE Optional
22 Consent to send charge slip on merchant mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her mobile number. TRUE Optional
23 Consent to send charge slip on merchant email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her email id(s). TRUE Optional

Response Parameters

Position in CSV Field Name Data Type Length Description Sample
Value
Mandatory/
Optional
1 Billing Reference Number String 0 - 25 Transaction reference number from external application. TX12345678 Mandatory
2 Approval Code String 1 - 6 Credit card authorization code, if transaction was approved. Otherwise empty string. Presence of non-zero length approval code string indicates successful authorization of transaction. This logic holds true for Pine 360 transactions as well. “5261AJ” Mandatory
3 Host Response String 0 - 50 Response string if a response for transaction was received from bank switch. Otherwise, if any error occurs before response is received, this is an empty string. “APPROVED” Mandatory
4 Card Number String 0 - 19 Card number is valid if card was swiped. Otherwise, empty string. “************2802” Mandatory
5 Expiration Date String 0 or 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. “XXXX” Mandatory
6 Cardholder’s Name String 0 - 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string. “AMIT MOHAN” Mandatory
7 Card Type String 0 - 12 Card association name, if valid card was swiped. Otherwise, empty string. “VISA” Mandatory
8 Invoice Number/EDC ROC (in case of Reward Transaction) Long Integer 0 - 6 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on charge slip). Range 0 - 999999 / 101 - 999 (in case of Reward Transaction) 78/101 Mandatory
9 Batch Number/EDC Batch ID (in case of Reward Transaction) Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction). Mandatory
10 Terminal ID String 0 or 8 EFT TID, if transaction authorized. Otherwise, empty string. “30000001” Mandatory
11 Loyalty Points Awarded Long 0 - 8 RFU – not used.
Range: 0 – 99999999
0 Mandatory
12 Remark String 0 - 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization. “Failed to dial modem” Mandatory
13 Transaction Acquirer Name String 0 - 48 Name of acquirer to which transaction was routed. “ICICI BANK” Mandatory
14 Merchant ID String 0 - 15 EFT ME ID, if transaction authorized. Otherwise, empty string. “000100090015607” Mandatory
15 Retrieval Reference Number String 0 - 12 EFT RRN, if transaction authorized. Otherwise, empty string. “000000012843” Mandatory
16 Card Entry Mode Integer 0 - 5 Enumeration of possible values: 0 – Manual entry 1 – Swipe entry 2 – Chip card entry Any other value – card not validated
Range: 0 – 32767
1 Mandatory
17 Print Cardholder's Name on receipt Integer 0 - 5 Enumeration of possible values: 0 – Do not print cardholder’s name 1 – Print cardholder’s name Any other value – card not validated. This is used if external application is to print Plutus charge slip.
Range: 0 – 32767
0 Mandatory
18 Merchant Name String 0 - 23 Merchant name, if transaction authorized. Otherwise, empty string. “NOBLE MOTORS” Mandatory
19 Merchant Address String 0 - 23 Merchant address line, if transaction authorized. Otherwise, empty string. “HAJI ALI” Mandatory
20 Merchant City String 0 - 23 Merchant city line, if transaction authorized. Otherwise, empty string. “MUMBAI” Mandatory
21 Plutus Version String 0 - 40 Plutus version. “v1.54 (for ICICI BANK)” Mandatory
22 Acquiring Bank Code Integer 0 - 999 Code for bank used for processing transaction. Enumeration of possible values: 01 – HDFC BANK, 02 – ICICI BANK, 03 – AMERICAN EXPRESS, 04 – CITIBANK, 05 – AXIS BANK, 06 – SBI, 07 – HSBC, 09 – CORP BANK, 10 – CUB (City Union Bank), 14 – IDBI Bank, 17 – LVB (Lakshmi Vilas Bank), 51 - PINE 360, 301 - Sodexo, 81 – Loyalty Reward, 82 – Aimia, 85 – SBI Rewards Mandatory
23 Reward Redeemed Amount Long Integer 0 - 10 Redeemed Amount in Paisa or in lowest currency. “10000” Optional
24 Reward Redeemed Points Double 0 - 15 Redeemed Points. “400.00” Optional
25 Reward Balance Amount String 0 - 10 Balance Amount. “1000000” Optional
26 Reward Balance Points Double 0 - 15 Balance Point. “40000.00” Optional
27 Charge slip print data in tag value format (Optional)* String Charge slip data in form of tag and value separated with : and new pair separated with |*(Only present if charge slip data on merchant is enabled) Charge slip print data in tag value format(Optional)* Mandatory
28 RFU1/Coupon code/Loyalty Card Number String 0 - 23 Card Processing Fee in Rs (decimal) Or Coupon Code. Coupon code is the value which will be coming as a response to voucher redemption. This field will be present in case of voucher redemption. Or Loyalty number fetched if the transaction type is 4301. “5.50” Mandatory
29 Amount processed successfully by Plutus/ Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 - 99 Amount will always be in paisa or lowest currency. “100000” Mandatory
30 RFU3 String 0 - 23 Reserved for future use Mandatory
31 RFU String Settlement Summary (NA for Sodexo) Mandatory
32 Date of Transaction String 0 - 8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format. “02012011” Mandatory
33 Time of Transaction String 0 - 6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24-hour format. “210403” Mandatory
34 PineLabs Client ID Integer 0 - 6 Unique ID assigned to Pine Labs EDC. 12345 Mandatory


Request

HEX String Format
ASCII Format
10000997001A343030322C545831323334353637382C3130302C2C2C2C2C2C2CFF
— 4002,TX12345678,100,,,,,,,ÿ

Response

HEX String Format
ASCII Format
9999199700010179012254583132333435363738222C22222C225472616E73616374696F6E206E6F7420737570706F7274656420666F72207468652073656C6563746564206163717569726572222C222A2A2A2A2A2A2A2A2A2A2A2A35313834222C2258585858222C22222C2220222C302C302C223939383030303236222C302C225472616E73616374696F6E206E6F7420737570706F7274656420666F72207468652073656C6563746564206163717569726572222C2249434943492042414E4B222C22202020202020202020202020202020222C22303030303030303030303030222C322C312C224C4F564520434F4D4D554E49434154494F4E222C224A414E414B50555249222C224E45572044454C48492020202044454C20202020202020222C22506C757475732076322E3132204D542049434943492042414E4B222C30322C22222C22222C22222C22222C22222C22222C22222C22222C22222C22222C22222C2230222C22313030222C2234303032222C22434152445F4348495022FF
™™— y"TX12345678","","Transaction not supported for the selected acquirer","**5184","XXXX",""," ",0,0,"99800026",0,"Transaction not supported for the selected acquirer","ICICI BANK"," ","000000000000",2,1,"LOVE COMMUNICATION","JANAKPURI","NEW DELHI DEL ","Plutus v2.12 MT ICICI BANK",02,"","","","","","","","","","","","0","100","4002","CARD_CHIP"ÿ

JSON Request:
 
    
Coming Soon
  

JSON Response:
 
    

Coming Soon



Void Transaction

The Void transaction is used to reverse a previously approved Sale transaction.

Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample
Value
Mandatory/
Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer the Transaction Types. 4006 Mandatory
2 Billing reference number String 0 – 25 Transaction reference number from external TX12345678 Optional
3 Total EFT Amount Long Integer 0 - 8 Amount to be charged to card – expressed as a whole number in lowest currency unit (ie. in paisa). 999999 Mandatory
7 Invoice Number Long Integer 1 – 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Invoice number of parent transition. 12 Mandatory
12 EDC Batch ID Integer 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Batch Id of parent transition. Mandatory
13 EDC ROC Integer 3 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Roc of parent transition. 201 Optional
14 Transaction log ID Long Integer 01-12 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Transaction log of parent transition. 123234 Optional
15 Reward/Cash amount Long Integer 1 – 8 Amount to be paid by reward points or in cash in paise (or in lowest currency). 999999 Optional
16 Customer Mobile Number String 1 – 100 Customer mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
17 Customer email id(s) String 1 – 500 Customer email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
18 Merchant mobile number(s) String 1 – 100 Merchant mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
19 Merchant email id(s) String 1 – 500 Merchant email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
20 Consent to send charge slip on customer mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her mobile number(s). TRUE Optional
21 Consent to send charge slip on customer email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her email id(s). TRUE Optional
22 Consent to send charge slip on merchant mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her mobile number. TRUE Optional
23 Consent to send charge slip on merchant email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her email id(s). TRUE Optional

Response Parameters

Position in CSV Field Name Data Type Length Description Sample
Value
Mandatory/
Optional
1 Billing Reference Number String 0 - 25 Transaction reference number from external application. TX12345678 Optional
2 Approval Code String 1 - 6 Credit card authorization code, if transaction was approved. Otherwise empty string. Presence of non-zero length approval code string indicates successful authorization of transaction. This logic holds true for Pine 360 transactions as well. “5261AJ” Optional
3 Host Response String 0 - 50 Response string if a response for transaction was received from bank switch. Otherwise, if any error occurs before response is received, this is an empty string. “APPROVED” Mandatory
4 Card Number String 0 - 19 Card number is valid if card was swiped. Otherwise, empty string. “************2802” Optional
5 Expiration Date String 0 or 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. “XXXX” Optional
6 Cardholder’s Name String 0 - 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string. “AMIT MOHAN” Optional
7 Card Type String 0 - 12 Card association name, if valid card was swiped. Otherwise, empty string. “VISA” Optional
8 Invoice Number/EDC ROC (in case of Reward Transaction) Long Integer 0 - 6 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on charge slip). Range 0 - 999999 / 101 - 999 (in case of Reward Transaction) 78/101 Optional
9 Batch Number/EDC Batch ID (in case of Reward Transaction) Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction). Optional
10 Terminal ID String 0 or 8 EFT TID, if transaction authorized. Otherwise, empty string. “30000001” Optional
11 Loyalty Points Awarded Long 0 - 8 RFU – not used.
Range: 0 – 99999999
0 Mandatory
12 Remark String 0 - 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization. “Failed to dial modem” Optional
13 Transaction Acquirer Name String 0 - 48 Name of acquirer to which transaction was routed. “ICICI BANK” Optional
14 Merchant ID String 0 - 15 EFT ME ID, if transaction authorized. Otherwise, empty string. “000100090015607” Optional
15 Retrieval Reference Number String 0 - 12 EFT RRN, if transaction authorized. Otherwise, empty string. “000000012843” Mandatory
16 Card Entry Mode Integer 0 - 5 Enumeration of possible values: 0 – Manual entry 1 – Swipe entry 2 – Chip card entry Any other value – card not validated
Range: 0 – 32767
1 Optional
17 Print Cardholder's Name on receipt Integer 0 - 5 Enumeration of possible values: 0 – Do not print cardholder’s name 1 – Print cardholder’s name Any other value – card not validated. This is used if external application is to print Plutus charge slip.
Range: 0 – 32767
0 Optional
18 Merchant Name String 0 - 23 Merchant name, if transaction authorized. Otherwise, empty string. “NOBLE MOTORS” Optional
19 Merchant Address String 0 - 23 Merchant address line, if transaction authorized. Otherwise, empty string. “HAJI ALI” Optional
20 Merchant City String 0 - 23 Merchant city line, if transaction authorized. Otherwise, empty string. “MUMBAI” Optional
21 Plutus Version String 0 - 40 Plutus version. “v1.54 (for ICICI BANK)” Optional
22 Acquiring Bank Code Integer 0 - 999 Code for bank used for processing transaction. Enumeration of possible values: 01 – HDFC BANK, 02 – ICICI BANK, 03 – AMERICAN EXPRESS, 04 – CITIBANK, 05 – AXIS BANK, 06 – SBI, 07 – HSBC, 09 – CORP BANK, 10 – CUB (City Union Bank), 14 – IDBI Bank, 17 – LVB (Lakshmi Vilas Bank), 51 - PINE 360, 301 - Sodexo, 81 – Loyalty Reward, 82 – Aimia, 85 – SBI Rewards Optional
23 Reward Redeemed Amount Long Integer 0 - 10 Redeemed Amount in Paisa or in lowest currency. “10000” Optional
24 Reward Redeemed Points Double 0 - 15 Redeemed Points. “400.00” Optional
25 Reward Balance Amount String 0 - 10 Balance Amount. “1000000” Optional
26 Reward Balance Points Double 0 - 15 Balance Point. “40000.00” Optional
27 Charge slip print data in tag value format (Optional)* String Charge slip data in form of tag and value separated with : and new pair separated with |*(Only present if charge slip data on merchant is enabled) Charge slip print data in tag value format(Optional)* Optional
28 RFU1/Coupon code/Loyalty Card Number String 0 - 23 Card Processing Fee in Rs (decimal) Or Coupon Code. Coupon code is the value which will be coming as a response to voucher redemption. This field will be present in case of voucher redemption. Or Loyalty number fetched if the transaction type is 4301. “5.50” Mandatory
29 Amount processed successfully by Plutus/ Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 - 99 Amount will always be in paisa or lowest currency. “100000” Optional
30 RFU3 String 0 - 23 Reserved for future use Mandatory
31 RFU String Specific for merchant Alhanumeric Optional
32 Date of Transaction String 0 - 8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format. “02012011” Optional
33 Time of Transaction String 0 - 6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24-hour format. “210403” Optional
34 PineLabs Client ID Integer 0 - 6 Unique ID assigned to Pine Labs EDC. 12345 Optional


Request

HEX String Format
ASCII Format
10000997001A343030362C545831323334353637382C3130302C2C2C2C2C2C2CFF
— 4006,TX12345678,100,,,,,,,ÿ

Response

HEX String Format
ASCII Format
999919970001003701496E76616C696420496E766F696365204E756D626572206F722064657461696C7320666F722074686973207472616E73616374696F6EFF
™™— 7Invalid Invoice Number or details for this transactionÿ

JSON Request:
 
    
Coming Soon
  

JSON Response:
 
    

Coming Soon



Pre Auth Transaction

A pre-authorization is a transaction to determine and block if cardholder have a maximum available credit line, which will not be actually charged.

Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer the Transaction Types. Range: 4001-4216 4007 Mandatory
2 Billing reference number String 0 – 25 Transaction reference number from external “TX12345678” Optional
3 Total EFT Amount Long Integer 0 - 8 Amount to be charged to card – expressed as a whole number in lowest currency unit (ie. in paisa) 999999 Mandatory
15 Reward/Cash amount Long Integer 1 – 8 Amount to be paid by reward points or in cash in paise (or in lowest currency) 999999 Optional
16 Customer Mobile Number String 1 – 100 Customer mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
17 Customer email id(s) String 1 – 500 Customer email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
18 Merchant mobile number(s) String 1 – 100 Merchant mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
19 Merchant email id(s) String 1 – 500 Merchant email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
20 Consent to send charge slip on customer mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her mobile number(s). TRUE Optional
21 Consent to send charge slip on customer email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her email id(s). TRUE Optional
22 Consent to send charge slip on merchant mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her mobile number. TRUE Optional
23 Consent to send charge slip on merchant email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her email id(s). TRUE Optional

Response Parameters

Position in CSV Field Name Data Type Length Description Sample
Value
Mandatory/
Optional
1 Billing Reference Number String 0 - 25 Transaction reference number from external application. TX12345678 Mandatory
2 Approval Code String 1 - 6 Credit card authorization code, if transaction was approved. Otherwise empty string. Presence of non-zero length approval code string indicates successful authorization of transaction. This logic holds true for Pine 360 transactions as well. “5261AJ” Mandatory
3 Host Response String 0 - 50 Response string if a response for transaction was received from bank switch. Otherwise, if any error occurs before response is received, this is an empty string. “APPROVED” Mandatory
4 Card Number String 0 - 19 Card number is valid if card was swiped. Otherwise, empty string. “************2802” Mandatory
5 Expiration Date String 0 or 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. “XXXX” Mandatory
6 Cardholder’s Name String 0 - 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string. “AMIT MOHAN” Mandatory
7 Card Type String 0 - 12 Card association name, if valid card was swiped. Otherwise, empty string. “VISA” Mandatory
8 Invoice Number/EDC ROC (in case of Reward Transaction) Long Integer 0 - 6 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on charge slip). Range 0 - 999999 / 101 - 999 (in case of Reward Transaction) 78/101 Mandatory
9 Batch Number/EDC Batch ID (in case of Reward Transaction) Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction). Mandatory
10 Terminal ID String 0 or 8 EFT TID, if transaction authorized. Otherwise, empty string. “30000001” Mandatory
11 Loyalty Points Awarded Long 0 - 8 RFU – not used.
Range: 0 – 99999999
0 Mandatory
12 Remark String 0 - 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization. “Failed to dial modem” Mandatory
13 Transaction Acquirer Name String 0 - 48 Name of acquirer to which transaction was routed. “ICICI BANK” Mandatory
14 Merchant ID String 0 - 15 EFT ME ID, if transaction authorized. Otherwise, empty string. “000100090015607” Mandatory
15 Retrieval Reference Number String 0 - 12 EFT RRN, if transaction authorized. Otherwise, empty string. “000000012843” Mandatory
16 Card Entry Mode Integer 0 - 5 Enumeration of possible values: 0 – Manual entry 1 – Swipe entry 2 – Chip card entry Any other value – card not validated
Range: 0 – 32767
1 Mandatory
17 Print Cardholder's Name on receipt Integer 0 - 5 Enumeration of possible values: 0 – Do not print cardholder’s name 1 – Print cardholder’s name Any other value – card not validated. This is used if external application is to print Plutus charge slip.
Range: 0 – 32767
0 Mandatory
18 Merchant Name String 0 - 23 Merchant name, if transaction authorized. Otherwise, empty string. “NOBLE MOTORS” Mandatory
19 Merchant Address String 0 - 23 Merchant address line, if transaction authorized. Otherwise, empty string. “HAJI ALI” Mandatory
20 Merchant City String 0 - 23 Merchant city line, if transaction authorized. Otherwise, empty string. “MUMBAI” Mandatory
21 Plutus Version String 0 - 40 Plutus version. “v1.54 (for ICICI BANK)” Mandatory
22 Acquiring Bank Code Integer 0 - 999 Code for bank used for processing transaction. Enumeration of possible values: 01 – HDFC BANK, 02 – ICICI BANK, 03 – AMERICAN EXPRESS, 04 – CITIBANK, 05 – AXIS BANK, 06 – SBI, 07 – HSBC, 09 – CORP BANK, 10 – CUB (City Union Bank), 14 – IDBI Bank, 17 – LVB (Lakshmi Vilas Bank), 51 - PINE 360, 301 - Sodexo, 81 – Loyalty Reward, 82 – Aimia, 85 – SBI Rewards Mandatory
23 Reward Redeemed Amount Long Integer 0 - 10 Redeemed Amount in Paisa or in lowest currency. “10000” Optional
24 Reward Redeemed Points Double 0 - 15 Redeemed Points. “400.00” Optional
25 Reward Balance Amount String 0 - 10 Balance Amount. “1000000” Optional
26 Reward Balance Points Double 0 - 15 Balance Point. “40000.00” Optional
27 Charge slip print data in tag value format (Optional)* String Charge slip data in form of tag and value separated with : and new pair separated with |*(Only present if charge slip data on merchant is enabled) Charge slip print data in tag value format(Optional)* Mandatory
28 RFU1/Coupon code/Loyalty Card Number String 0 - 23 Card Processing Fee in Rs (decimal) Or Coupon Code. Coupon code is the value which will be coming as a response to voucher redemption. This field will be present in case of voucher redemption. Or Loyalty number fetched if the transaction type is 4301. “5.50” Mandatory
29 Amount processed successfully by Plutus/ Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 - 99 Amount will always be in paisa or lowest currency. “100000” Mandatory
30 RFU3 String 0 - 23 Reserved for future use Mandatory
31 RFU String Specific for merchant Alhanumeric Optional
32 Date of Transaction String 0 - 8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format. “02012011” Mandatory
33 Time of Transaction String 0 - 6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24-hour format. “210403” Mandatory
34 PineLabs Client ID Integer 0 - 6 Unique ID assigned to Pine Labs EDC. 12345 Mandatory


Request

HEX String Format
ASCII Format
10000997001A343030372C545831323334353637382C3130302C2C2C2C2C2C2CFF
— 4007,TX12345678,100,,,,,,,ÿ

Response

HEX String Format
ASCII Format
9999199700010144012254583132333435363738222C223030222C22415050524F564544222C222A2A2A2A2A2A2A2A2A2A2A2A35313834222C2258585858222C22222C2256495341222C313132322C32332C223939383030303236222C302C2250524F434553534544222C2249434943492042414E4B222C22202020202020202020202020202020222C22303030303030303030303230222C322C312C224C4F564520434F4D4D554E49434154494F4E222C224A414E414B50555249222C224E45572044454C48492020202044454C20202020202020222C22506C757475732076322E3132204D542049434943492042414E4B222C30322C22222C22222C22222C22222C22222C22222C22222C22222C22222C223036323332303233222C22313535323237222C2234323935323233313437222C22313030222C2234303037222C22434152445F4348495022FF
™™— D"TX12345678","00","APPROVED","**5184","XXXX","","VISA",1122,23,"99800026",0,"PROCESSED","ICICI BANK","","000000000020",2,1,"LOVE COMMUNICATION","JANAKPURI","NEW DELHI DEL ","Plutus v2.12 MT ICICI BANK",02,"","","","","","","","","","06232023","155227","4295223147","100","4007","CARD_CHIP"ÿ

JSON Request:
 
    
Coming Soon
  

JSON Response:
 
    

Coming Soon



Sale Complete Transaction

Completion is the transaction to process or complete the Pre authorized transaction. Completion can be for the full pre authorized amount or diffrent amount.

Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer the Transaction Types.
Range: 4001-4216
4008 Mandatory
2 Billing reference number String 0 – 25 Transaction reference number from external “TX12345678” Optional
3 Total EFT Amount Long Integer 0 - 8 Amount to be charged to card – expressed as a whole number in lowest currency unit (ie. in paisa) 999999 Mandatory
7 Invoice Number Long Integer 1 – 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Invoice number of parent transition. 12 Mandatory
12 EDC Batch ID Integer 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Batch Id of parent transition. Mandatory
13 EDC ROC Integer 3 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Roc of parent transition.
Range: 101-999
201 Optional
14 Transaction log ID Long Integer 01-12 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Transaction log of parent transition.
Range: 1-184467440737
123234 Optional
15 Reward\\Cash amount Long Integer 1 – 8 Amount to be paid by reward points or in cash in paise (or in lowest currency). 999999 Optional
16 Customer Mobile Number String 1 – 100 Customer mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
17 Customer email id(s) String 1 – 500 Customer email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
18 Merchant mobile number(s) String 1 – 100 Merchant mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
19 Merchant email id(s) String 1 – 500 Merchant email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
20 Consent to send charge slip on customer mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her mobile number(s). TRUE Optional
21 Consent to send charge slip on customer email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her email id(s). TRUE Optional
22 Consent to send charge slip on merchant mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her mobile number. TRUE Optional
23 Consent to send charge slip on merchant email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her email id(s). TRUE Optional

Response Parameters

Position in CSV Field Name Data Type Length Description Sample
Value
Mandatory/
Optional
1 Billing Reference Number String 0 - 25 Transaction reference number from external application. TX12345678 Mandatory
2 Approval Code String 1 - 6 Credit card authorization code, if transaction was approved. Otherwise empty string. Presence of non-zero length approval code string indicates successful authorization of transaction. This logic holds true for Pine 360 transactions as well. “5261AJ” Mandatory
3 Host Response String 0 - 50 Response string if a response for transaction was received from bank switch. Otherwise, if any error occurs before response is received, this is an empty string. “APPROVED” Mandatory
4 Card Number String 0 - 19 Card number is valid if card was swiped. Otherwise, empty string. “************2802” Mandatory
5 Expiration Date String 0 or 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. “XXXX” Mandatory
6 Cardholder’s Name String 0 - 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string. “AMIT MOHAN” Mandatory
7 Card Type String 0 - 12 Card association name, if valid card was swiped. Otherwise, empty string. “VISA” Mandatory
8 Invoice Number/EDC ROC (in case of Reward Transaction) Long Integer 0 - 6 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on charge slip). Range 0 - 999999 / 101 - 999 (in case of Reward Transaction) 78/101 Mandatory
9 Batch Number/EDC Batch ID (in case of Reward Transaction) Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction). Mandatory
10 Terminal ID String 0 or 8 EFT TID, if transaction authorized. Otherwise, empty string. “30000001” Mandatory
11 Loyalty Points Awarded Long 0 - 8 RFU – not used.
Range: 0 – 99999999
0 Mandatory
12 Remark String 0 - 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization. “Failed to dial modem” Mandatory
13 Transaction Acquirer Name String 0 - 48 Name of acquirer to which transaction was routed. “ICICI BANK” Mandatory
14 Merchant ID String 0 - 15 EFT ME ID, if transaction authorized. Otherwise, empty string. “000100090015607” Mandatory
15 Retrieval Reference Number String 0 - 12 EFT RRN, if transaction authorized. Otherwise, empty string. “000000012843” Mandatory
16 Card Entry Mode Integer 0 - 5 Enumeration of possible values: 0 – Manual entry 1 – Swipe entry 2 – Chip card entry Any other value – card not validated
Range: 0 – 32767
1 Mandatory
17 Print Cardholder's Name on receipt Integer 0 - 5 Enumeration of possible values: 0 – Do not print cardholder’s name 1 – Print cardholder’s name Any other value – card not validated. This is used if external application is to print Plutus charge slip.
Range: 0 – 32767
0 Mandatory
18 Merchant Name String 0 - 23 Merchant name, if transaction authorized. Otherwise, empty string. “NOBLE MOTORS” Mandatory
19 Merchant Address String 0 - 23 Merchant address line, if transaction authorized. Otherwise, empty string. “HAJI ALI” Mandatory
20 Merchant City String 0 - 23 Merchant city line, if transaction authorized. Otherwise, empty string. “MUMBAI” Mandatory
21 Plutus Version String 0 - 40 Plutus version. “v1.54 (for ICICI BANK)” Mandatory
22 Acquiring Bank Code Integer 0 - 999 Code for bank used for processing transaction. Enumeration of possible values: 01 – HDFC BANK, 02 – ICICI BANK, 03 – AMERICAN EXPRESS, 04 – CITIBANK, 05 – AXIS BANK, 06 – SBI, 07 – HSBC, 09 – CORP BANK, 10 – CUB (City Union Bank), 14 – IDBI Bank, 17 – LVB (Lakshmi Vilas Bank), 51 - PINE 360, 301 - Sodexo, 81 – Loyalty Reward, 82 – Aimia, 85 – SBI Rewards Mandatory
23 Reward Redeemed Amount Long Integer 0 - 10 Redeemed Amount in Paisa or in lowest currency. “10000” Optional
24 Reward Redeemed Points Double 0 - 15 Redeemed Points. “400.00” Optional
25 Reward Balance Amount String 0 - 10 Balance Amount. “1000000” Optional
26 Reward Balance Points Double 0 - 15 Balance Point. “40000.00” Optional
27 Charge slip print data in tag value format (Optional)* String Charge slip data in form of tag and value separated with : and new pair separated with |*(Only present if charge slip data on merchant is enabled) Charge slip print data in tag value format(Optional)* Mandatory
28 RFU1/Coupon code/Loyalty Card Number String 0 - 23 Card Processing Fee in Rs (decimal) Or Coupon Code. Coupon code is the value which will be coming as a response to voucher redemption. This field will be present in case of voucher redemption. Or Loyalty number fetched if the transaction type is 4301. “5.50” Mandatory
29 Amount processed successfully by Plutus/ Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 - 99 Amount will always be in paisa or lowest currency. “100000” Mandatory
30 RFU3 String 0 - 23 Reserved for future use Mandatory
31 RFU String Specific for merchant Alhanumeric Optional
32 Date of Transaction String 0 - 8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format. “02012011” Mandatory
33 Time of Transaction String 0 - 6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24-hour format. “210403” Mandatory
34 PineLabs Client ID Integer 0 - 6 Unique ID assigned to Pine Labs EDC. 12345 Mandatory


Request

HEX String Format
ASCII Format
10000997001A343030382C545831323334353637382C3130302C2C2C2C2C2C2CFF
— 4008,TX12345678,100,,,,,,,ÿ

Response

HEX String Format
ASCII Format
999919970001010C012254583132333435363738222C22222C22496E76616C696420496E766F696365204E756D626572206F722064657461696C7320666F722074686973207472616E73616374696F6E222C22222C2258585858222C22222C2220222C313132322C302C2220222C302C22496E76616C696420496E766F696365204756D626572206F722064657461696C7320666F722074686973207472616E73616374696F6222C2242414E4B222C2220222C22303030303030303030303030222C312C312C2220222C2220222C2220222C22312E312E312E31222C30302C22222C22222C22222C22222C22222C22222C22222C22222C22222C22222C22222C2230222C22313030222C2234303038222C2222FF
™™— "TX12345678","","Invalid Invoice Number or details for this transaction","","XXXX",""," ",1122,0," ",0,"Invalid Invoice Number or details for this transaction","BANK"," ","000000000000",1,1," "," "," ","1.1.1.1",00,"","","","","","","","","","","","0","100","4008",""ÿ

JSON Request:
 
    
Coming Soon
  

JSON Response:
 
    

Coming Soon



Brand EMI Transaction

A Brand EMI transaction is an equated monthly installment (EMI) payment option offered by a bank or non-banking financial company (NBFC) in association with a particular brand. This allows customers to purchase products from the brand on credit and repay the amount in monthly installments.

The interest rate and tenure of the EMI are decided by the bank or NBFC in consultation with the brand. The customer can choose the EMI tenure depending on their affordability

EMI Related Parameters:
Index Sample Data Description
1 999113881 Pine Labs Product code
2 7 Brand OEM ID provided by Pine Labs
3 463 Pine Labs Rule Id
4 106 Pine Labs Rule Type ID
5 753 Pine Labs Scheme Code
6 3 Tenure
7 233 Pine Labs Issuer ID
8 29489583 IMEI number/SERIAL NO
9 9900336400 Mobile number

• EMI-related fields are transmitted in a pipe-separated format from the merchant billing system. The majority of these parameters are optional. In cases where the billing system does not provide certain parameters, the Electronic Data Capture (EDC) system will prompt the user to manually enter or select the required details through a screen.

• Fields like Rule ID, Rule Type ID, Scheme Code and Issuer ID are NA for merchants who do not have Scheme information.

Use Cases for Brand EMI

Brand EMI can be performed in two ways where Merchant can either select the product and EMI details on the Merchant Billing Application or they can be selected on android payment terminal. Below section describes both use cases

Product and EMI details selection on Merchant Billing Application

Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer the Transaction Types
Range: 4001-4216
5002 Mandatory
2 Billing reference number String 0 – 25 Transaction reference number from external “TX12345678” Optional
3 Total EFT Amount Long Integer 0 - 8 Amount to be charged to card – expressed as a whole number in lowest currency unit (ie. in paisa)
Range: 1-99999999
999999 Mandatory
4 Bank Code String 1 – 2 The bank code to which transaction will be routed 1 Optional
5 Track 1 data/Card PAN Number String 1 – 76 Track1 data of the card or Card number if manual entry. If empty then Plutus will ask for card input. Optional
6 Track 2 data / Expiry date String 1 – 37 "Track2 data of the card or Expiry date if manual entry. If empty then Plutus will ask for card input. Expiry date is in YYMM format. In case of Pine 360, if Track 1 consists of mobile or GV number, this field will indicate the card entry mode. Mobile Number – 01 Barcode – 02 Manual - 03" Optional
7 Invoice Number Long Integer 1 – 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Invoice number of parent transition. 12 Optional
8 Is Swipe entry String TRUE or FALSE By default it is TRUE. TRUE Optional
9 Terminal ID String 1-8 Reserved for future use Optional
10 Operator String 1-31 Reserved for future use Optional
11 RFU2 String Reserved for future use Optional
12 EDC Batch ID Integer 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Batch Id of parent transition. Optional
13 EDC ROC Integer 3 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Roc of parent transition.
Range: 101-999
201 Optional
14 EMI Parameter String 1 - 100 These fields are pipe separated, Product code, OEM ID, Rule ID, Rule Type ID, Scheme Code, Tenure, Issuer ID, IMEI number/SERIAL NO, Mobile Number 999113881|7|463|106|753|3|233|29489583|9900336400| Optional
15 Reward\Cash amount Long Integer 1 – 8 Amount to be paid by reward points or in cash in paise (or in lowest currency)
Range: 1 – 99999999
999999 Optional
16 Customer Mobile Number String 1 – 100 Customer mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Mandatory/td>
17 Customer email id(s) String 1 – 500 Customer email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
18 Merchant mobile number(s) String 1 – 100 Merchant mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
19 Merchant email id(s) String 1 – 500 Merchant email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
20 Consent to send charge slip on customer mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her mobile number(s). TRUE Optional
21 Consent to send charge slip on customer email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her email id(s). TRUE Optional
22 Consent to send charge slip on merchant mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her mobile number. TRUE Optional
23 Consent to send charge slip on merchant email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her email id(s). TRUE Optional

Response Parameters

Position in CSV Field Name Data Type Length Description Sample Value
1 Billing Reference Number Integer 1 – 32768 Transaction reference number from external application. TX12345678
2 Approval Code String 1 – 6 Credit card authorization code, if transaction was approved. Otherwise empty string. 5261AJ
3 Host Response String Length: 0 – 50 Response string if a response for transaction was received from bank switch. Otherwise, if any error occurs before response is received, this is an empty string. APPROVED
4 Card Number String Length: 0– 19 Card number is valid if card was swiped. Otherwise, empty string. ************2802
5 Expiration Date String 0, 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. XXXX
6 Cardholder's Name String 0 – 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string. AMIT MOHAN
7 Card Type String 0 – 12 Card association name, if valid card was swiped. Otherwise, empty string. VISA
8 Invoice Number/EDC ROC (in case of Reward Transaction) Long Integer 6 or 3 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on charge slip) 78/101
9 Batch Number/EDC Batch ID (in case of Reward Transaction) Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction)
10 Terminal ID String 0, 8 EFT TID, if transaction authorized. Otherwise, empty string 30000001
11 Loyalty Points Awarded Long 0 - 8 RFU – not used. Range: 0 – 99999999 0
12 Remark String 0 – 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization Failed to dial modem
13 Transaction Acquirer Name String 0 – 48 Name of acquirer to which transaction was routed ICICI BANK
14 Merchant ID String 0 – 15 EFT ME ID, if transaction authorized. Otherwise, empty string 000100090 015607
15 Retrieval Reference Number String 0 – 12 EFT RRN, if transaction authorized. Otherwise, empty string 000000012 843
16 Card Entry Mode Integer 0 – 5 Enumeration of possible values: 0 – Manual entry, 1 – Swipe entry, 2 – Chip card entry. Any other value – card not validated. Range: 0 – 32767 1
17 Print Cardholder's Name on receipt Integer 0 – 5 Enumeration of possible values: 0 – Do not print cardholder’s name, 1 – Print cardholder’s name. Any other value – card not validated. This is used if external application is to print Plutus charge slip. Range: 0 – 32767 0
18 Merchant Name String 0 – 23 Merchant name, if transaction authorized. Otherwise, empty string NOBLE MOTORS
19 Merchant Address String 0 – 23 Merchant address line, if transaction authorized. Otherwise, empty string HAJI ALI
20 Merchant City String 0 – 23 Merchant city line, if transaction authorized. Otherwise, empty string MUMBAI
21 Plutus Version String 0 – 40 Plutus version v1.54 (for ICICI BANK)
22 Acquiring Bank Code Integer 0 - 999 Code for bank used for processing transaction. Enumeration of possible values: 01 – HDFC BANK, 02 – ICICI BANK, 03 – AMERICAN EXPRESS, 04 – CITIBANK, 05 – AXIS BANK, 06 – SBI, 07 – HSBC, 09 – CORP BANK, 10 – CUB (City Union Bank), 14 – IDBI Bank, 17 – LVB (Lakshmi Vilas Bank), 51- PINE 360, 301 – Sodexo, 81 – Loyalty Reward, 82 – Aimia, 85 – SBI Rewards
23 Reward Redeemed Amount Long Integer 10 Redeemed Amount in Paisa or in lowest currency 10000
24 Reward Redeemed Points Double 15 Redeemed Points 400.00
25 Reward Balance Amount String 10 Balance Amount 1000000
26 Reward Balance Points Double 15 Balance Point 40000.00
27 Charge slip print data in tag value format (Optional)* String Charge slip data in form of tag and value separated with : and new pair separated with |*(Only present if charge slip data on merchant is enabled) Charge slip print data in tag value format (Optional)*
28 EMI Parameter String 0 – 23 Brand EMI 106.These fields are pipe separated. Brand Type,Tenuar ID,Issuer Bank,Base Amount,EMI amount, Addinital case back,Rule ID,Sechma ID, OEM ID, OEM Name,Pine Product code,SKU code,IMEI no,Mobile No 106|3|HDFC BANK|1000000|337787|0|1037|1612|7|Apple iPhone|999113876|MT9E2HN/A|568282|9911072148
29 Amount processed successfully by Plutus/ Amount Loaded on cards or wallets/a mount voided/Amount loaded on cards/wallets String 0 – 99 Amount will always be in paisa or lowest currency. 100000
30 RFU3 String 0 – 23 Reserved for future use
31 RFU String Specific for merchant Alhanumeric Optional
32 Date of Transaction String 0 - 8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format. 02012011
33 Time of Transaction String 0 - 6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24-hour format. 210403
34 PineLabs Client ID Integer 0 - 6 Unique ID assigned to Pine Labs EDC. 12345


Request

HEX String Format
ASCII Format
100009970086353030322C545831323334353637382C3130303030302C2C2C2C2C2C2C2C2C2C2C3939393131333838317C377C3436337C3130367C3735337C337C3233337C32393438393538337C393930303333363430307C2C2C2CFF
— †5002,TX12345678,100000,,,,,,,,,,,999113881|7|463|106|753|3|233|29489583|9900336400|,,,ÿ

Response

HEX String Format
ASCII Format
99991997000101792254583132333435363738222C22303030303030222C22415050524F564544222C222A2A2A2A2A2A2A2A2A2A2A2A38303739222C2258585858222C2231323230303031363131393030333035202F222C224D415354455243415244222C322C312C223532313435363235222C302C2250524F434553534544222C22415849532042414E4B222C22303337303131303031373931373038222C22303030303030303030303230222C322C312C225257414D524954534152222C225257414D524954534152222C22414D524954534152222C22506C757475732076322E353520415849532042414E4B222C30352C22222C22222C22222C22222C22222C223130367C337C484446432042414E4B7C313030303030307C3333373738377C307C313033377C313631327C377C4170706C65206950686F6E657C3939393131333837367C4D54394532484E2F417C3536383238327C39393131303732313438222C22222C22222C22222C223031313032303230222C2231333434313822FF
™™— y"TX12345678","000000","APPROVED","************8079","XXXX","1220001611900305 /","MASTERCARD",2,1,"52145625",0,"PROCESSED","AXIS BANK","037011001791708","000000000020",2,1,"RWAMRITSAR","RWAMRITSAR","AMRITSAR","Plutus v2.55 AXIS BANK",05,"","","","","","106|3|HDFC BANK|1000000|337787|0|1037|1612|7|Apple iPhone|999113876|MT9E2HN/A|568282|9911072148","","","","01102020","134418"ÿ

JSON Request:
 
        
    Coming Soon
      
    

JSON Response:
 
        
    
    Coming Soon
    
    


Product and EMI details selection on Android Payment Terminal.

Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer the Transaction Types
Range: 4001-4216
4001 Mandatory
2 Billing reference number String 0 – 25 Transaction reference number from external “TX12345678” Optional
3 Total EFT Amount Long Integer 0 - 8 Amount to be charged to card – expressed as a whole number in lowest currency unit (ie. in paisa)
Range: 1-99999999
999999 Mandatory
4 Bank Code String 1 – 2 The bank code to which transaction will be routed 1 Optional
5 Track 1 data/Card PAN Number String 1 – 76 Track1 data of the card or Card number if manual entry. If empty then Plutus will ask for card input. Optional
6 Track 2 data / Expiry date String 1 – 37 "Track2 data of the card or Expiry date if manual entry. If empty then Plutus will ask for card input. Expiry date is in YYMM format. In case of Pine 360, if Track 1 consists of mobile or GV number, this field will indicate the card entry mode. Mobile Number – 01 Barcode – 02 Manual - 03" Optional
7 Invoice Number Long Integer 1 – 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Invoice number of parent transition. 12 Optional
8 Is Swipe entry String TRUE or FALSE By default it is TRUE. TRUE Optional
9 Terminal ID String 1-8 Reserved for future use Optional
10 Operator String 1-31 Reserved for future use Optional
11 RFU2 String Reserved for future use Optional
12 EDC Batch ID Integer 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Batch Id of parent transition. Optional
13 EDC ROC Integer 3 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Roc of parent transition.
Range: 101-999
201 Optional
14 EMI Parameter String 1 - 100 These fields are pipe separated, Product code, OEM ID, Rule ID, Rule Type ID, Scheme Code, Tenure, Issuer ID, IMEI number/SERIAL NO, Mobile Number 999113881|7|463|106|753|3|233|29489583|9900336400| Optional
15 Reward\Cash amount Long Integer 1 – 8 Amount to be paid by reward points or in cash in paise (or in lowest currency)
Range: 1 – 99999999
999999 Optional
16 Customer Mobile Number String 1 – 100 Customer mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
17 Customer email id(s) String 1 – 500 Customer email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
18 Merchant mobile number(s) String 1 – 100 Merchant mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
19 Merchant email id(s) String 1 – 500 Merchant email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
20 Consent to send charge slip on customer mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her mobile number(s). TRUE Optional
21 Consent to send charge slip on customer email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her email id(s). TRUE Optional
22 Consent to send charge slip on merchant mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her mobile number. TRUE Optional
23 Consent to send charge slip on merchant email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her email id(s). TRUE Optional

Response Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/ Optional
1 Billing Reference Number Integer 1 – 32768 Transaction reference number from external application. TX12345678 Mandatory
2 Approval Code String 1 – 6 Credit card authorization code, if transaction was approved. Otherwise empty string. Presence of non-zero length approval code string indicates successful authorization of transaction. This logic holds true for Pine 360 transactions as well 5261AJ Mandatory
3 Host Response String 0 – 50 Response string if a response for transaction was received from bank switch. Otherwise, if any error occurs before response is received, this is an empty string. APPROVED Mandatory
4 Card Number String 0 – 19 Card number is valid if card was swiped. Otherwise, empty string. ************2802 Mandatory
5 Expiration Date String 0, 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. XXXX Mandatory
6 Cardholder’s Name String 0 – 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string AMIT MOHAN Mandatory
7 Card Type String 0 – 12 Card association name, if valid card was swiped. Otherwise, empty string VISA Mandatory
8 Invoice Number/EDC ROC (in case of Reward Transaction) Long Integer 6 or 3 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on charge slip) 78/101 Mandatory
9 Batch Number/EDC Batch ID (in case of Reward Transaction) Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction) Mandatory
10 Terminal ID String 0, 8 EFT TID, if transaction authorized. Otherwise, empty string 30000001 Mandatory
11 Loyalty Points Awarded Long 0 - 8 RFU – not used. Range: 0 – 99999999 0 Mandatory
12 Remark String 0 – 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization Failed to dial modem Mandatory
13 Transaction Acquirer Name String 0 – 48 Name of acquirer to which transaction was routed ICICI BANK Mandatory
14 Merchant ID String 0 – 15 EFT ME ID, if transaction authorized. Otherwise, empty string 000100090 015607 Mandatory
15 Retrieval Reference Number String 0 – 12 EFT RRN, if transaction authorized. Otherwise, empty string 000000012 843 Mandatory
16 Card Entry Mode Integer 0 – 5 Enumeration of possible values: 0 – Manual entry, 1 – Swipe entry, 2 – Chip card entry. Any other value – card not validated. Range: 0 – 32767 1 Mandatory
17 Print Cardholder’s Name on receipt Integer 0 – 5 Enumeration of possible values: 0 – Do not print cardholder’s name, 1 – Print cardholder’s name. Any other value – card not validated. This is used if external application is to print Plutus charge slip. Range: 0 – 32767 0 Mandatory
18 Merchant Name String 0 – 23 Merchant name, if transaction authorized. Otherwise, empty string NOBLE MOTORS Mandatory
19 Merchant Address String 0 – 23 Merchant address line, if transaction authorized. Otherwise, empty string HAJI ALI Mandatory
20 Merchant City String 0 – 23 Merchant city line, if transaction authorized. Otherwise, empty string MUMBAI Mandatory
21 Plutus Version String 0 – 40 Plutus version v1.54 (for ICICI BANK) Mandatory
22 Acquiring Bank Code Integer 0 - 999 Code for bank used for processing transaction. Enumeration of possible values: 01 – HDFC BANK, 02 – ICICI BANK, 03 – AMERICAN EXPRESS, 04 – CITIBANK, 05 – AXIS BANK, 06 – SBI, 07 – HSBC, 09 – CORP BANK, 10 – CUB (City Union Bank), 14 – IDBI Bank, 17 – LVB (Lakshmi Vilas Bank), 51- PINE 360, 301 – Sodexo, 81 – Loyalty Reward, 82 – Aimia, 85 – SBI Rewards Mandatory
23 Reward Redeemed Amount Long Integer 10 Redeemed Amount in Paisa or in lowest currency 10000 Mandatory
24 Reward Redeemed Points Double 15 Redeemed Points 400.00 Mandatory
25 Reward Balance Amount String 10 Balance Amount 1000000 Mandatory
26 Reward Balance Points Double 15 Balance Point 40000.00 Mandatory
27 Charge slip print data in tag value format (Optional)* String Charge slip data in form of tag and value separated with : and new pair separated with |*(Only present if charge slip data on merchant is enabled) Charge slip print data in tag value format(Optional)* Optional
28 EMI Parameter String 0 – 23 Bank EMI 105, Brand .These fields are pipe separated. Brand Type, Tenuar ID, Issuer Bank, Base Amount, EMI amount, Addinital case back, Rule ID, Sechma ID, OEM ID, OEM Name, Pine Product code, SKU code, IMEI no, Mobile No 106|3|HDFC BANK|1000000|337787|0|1037|1612|7|Apple iPhone|999113876|MT9E2HN/A|568282|9911072148 Mandatory
29 Amount processed successfully by Plutus/Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 – 99 Amount will always be in paisa or lowest currency. 100000 Mandatory
30 RFU3 String 0 – 23 Reserved for future use Optional
31 RFU String Specific for merchant Alhanumeric Optional Optional
32 Date of Transaction String 0 - 8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format. 02012011 Mandatory
33 Time of Transaction String 0 - 6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24hour format. 210403 Mandatory
34 PineLabs Client ID Integer 0 - 6 Unique ID assigned to Pine Labs EDC. 12345 Mandatory


Request

HEX String Format
ASCII Format
100009970021353030322C545831323334353637382C3130303030302C2C2C2C2C2C2C2C2C2C2CFF
5002,TX12345678,100000,,,,,,,,,,,

Response

HEX String Format
ASCII Format
99991997000101792254583132333435363738222C22303030303030222C22415050524F564544222C222A2A2A2A2A2A2A2A2A2A2A2A38303739222C2258585858222C2231323230303031363131393030333035202F222C224D415354455243415244222C322C312C223532313435363235222C302C2250524F434553534544222C22415849532042414E4B222C22303337303131303031373931373038222C22303030303030303030303230222C322C312C225257414D524954534152222C225257414D524954534152222C22414D524954534152222C22506C757475732076322E353520415849532042414E4B222C30352C22222C22222C22222C22222C22222C223130367C337C484446432042414E4B7C313030303030307C3333373738377C307C313033377C313631327C377C4170706C65206950686F6E657C3939393131333837367C4D54394532484E2F417C3536383238327C39393131303732313438222C22222C22222C22222C223031313032303230222C2231333434313822FF
TX12345678","000000","APPROVED","************8079","XXXX","1220001611900305 /","MASTERCARD",2,1,"52145625",0,"PROCESSED","AXIS BANK","037011001791708","000000000020",2,1,"RWAMRITSAR","RWAMRITSAR","AMRITSAR","Plutus v2.55 AXIS BANK",05,"","","","","","106|3|HDFC BANK|1000000|337787|0|1037|1612|7|Apple iPhone|999113876|MT9E2HN/A|568282|9911072148","","","","01102020","134418"

JSON Request:
 
      
  Coming Soon
    
  

JSON Response:
 
      
  
  Coming Soon
  
  



Bank EMI Transaction

A Bank EMI transaction is an equated monthly installment (EMI) payment option offered by a bank to its customers. This allows customers to purchase products or services from any merchant and repay the amount in monthly installments.

The interest rate and tenure of the EMI are decided by the bank. The customer can choose the EMI tenure depending on their affordability

Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer the Transaction Types
Range: 4001-4216
5101 Mandatory
2 Billing reference number String 0 – 25 Transaction reference number from external “TX12345678” Optional
3 Total EFT Amount Long Integer 0 - 8 Amount to be charged to card – expressed as a whole number in lowest currency unit (ie. in paisa)
Range: 1-99999999
999999 Mandatory
4 Bank Code String 1 – 2 The bank code to which transaction will be routed 1 Optional
5 Track 1 data/Card PAN Number String 1 – 76 Track1 data of the card or Card number if manual entry. If empty then Plutus will ask for card input. Optional
6 Track 2 data / Expiry date String 1 – 37 "Track2 data of the card or Expiry date if manual entry. If empty then Plutus will ask for card input. Expiry date is in YYMM format. In case of Pine 360, if Track 1 consists of mobile or GV number, this field will indicate the card entry mode. Mobile Number – 01 Barcode – 02 Manual - 03" Optional
7 Invoice Number Long Integer 1 – 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Invoice number of parent transition. 12 Optional
8 Is Swipe entry String TRUE or FALSE By default it is TRUE. TRUE Optional
9 Terminal ID String 1-8 Reserved for future use Optional
10 Operator String 1-31 Reserved for future use Optional
11 RFU2 String Reserved for future use Optional
12 EDC Batch ID Integer 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Batch Id of parent transition. Optional
13 EDC ROC Integer 3 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Roc of parent transition.
Range: 101-999
201 Optional
14 Transaction log ID Long Integer 1 - 12 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Transaction log of parent transition.
Range: 1-184467440737
123234 Optional
15 Reward\Cash amount Long Integer 1 – 8 Amount to be paid by reward points or in cash in paise (or in lowest currency)
Range: 1 – 99999999
999999 Optional
16 Customer Mobile Number String 1 – 100 Customer mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
17 Customer email id(s) String 1 – 500 Customer email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
18 Merchant mobile number(s) String 1 – 100 Merchant mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
19 Merchant email id(s) String 1 – 500 Merchant email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
20 Consent to send charge slip on customer mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her mobile number(s). TRUE Optional
21 Consent to send charge slip on customer email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her email id(s). TRUE Optional
22 Consent to send charge slip on merchant mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her mobile number. TRUE Optional
23 Consent to send charge slip on merchant email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her email id(s). TRUE Optional

Response Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/ Optional
1 Billing Reference Number Integer 1 – 32768 Transaction reference number from external application. TX12345678 Mandatory
2 Approval Code String 1 – 6 Credit card authorization code, if transaction was approved. Otherwise empty string. Presence of non-zero length approval code string indicates successful authorization of transaction. This logic holds true for Pine 360 transactions as well 5261AJ Mandatory
3 Host Response String 0 – 50 Response string if a response for transaction was received from bank switch. Otherwise, if any error occurs before response is received, this is an empty string. APPROVED Mandatory
4 Card Number String 0 – 19 Card number is valid if card was swiped. Otherwise, empty string. ************2802 Mandatory
5 Expiration Date String 0, 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. XXXX Mandatory
6 Cardholder’s Name String 0 – 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string AMIT MOHAN Mandatory
7 Card Type String 0 – 12 Card association name, if valid card was swiped. Otherwise, empty string VISA Mandatory
8 Invoice Number/EDC ROC (in case of Reward Transaction) Long Integer 6 or 3 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on charge slip) 78/101 Mandatory
9 Batch Number/EDC Batch ID (in case of Reward Transaction) Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction) Mandatory
10 Terminal ID String 0, 8 EFT TID, if transaction authorized. Otherwise, empty string 30000001 Mandatory
11 Loyalty Points Awarded Long 0 - 8 RFU – not used. Range: 0 – 99999999 0 Mandatory
12 Remark String 0 – 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization Failed to dial modem Mandatory
13 Transaction Acquirer Name String 0 – 48 Name of acquirer to which transaction was routed ICICI BANK Mandatory
14 Merchant ID String 0 – 15 EFT ME ID, if transaction authorized. Otherwise, empty string 000100090 015607 Mandatory
15 Retrieval Reference Number String 0 – 12 EFT RRN, if transaction authorized. Otherwise, empty string 000000012 843 Mandatory
16 Card Entry Mode Integer 0 – 5 Enumeration of possible values: 0 – Manual entry, 1 – Swipe entry, 2 – Chip card entry. Any other value – card not validated. Range: 0 – 32767 1 Mandatory
17 Print Cardholder’s Name on receipt Integer 0 – 5 Enumeration of possible values: 0 – Do not print cardholder’s name, 1 – Print cardholder’s name. Any other value – card not validated. This is used if external application is to print Plutus charge slip. Range: 0 – 32767 0 Mandatory
18 Merchant Name String 0 – 23 Merchant name, if transaction authorized. Otherwise, empty string NOBLE MOTORS Mandatory
19 Merchant Address String 0 – 23 Merchant address line, if transaction authorized. Otherwise, empty string HAJI ALI Mandatory
20 Merchant City String 0 – 23 Merchant city line, if transaction authorized. Otherwise, empty string MUMBAI Mandatory
21 Plutus Version String 0 – 40 Plutus version v1.54 (for ICICI BANK) Mandatory
22 Acquiring Bank Code Integer 0 - 999 Code for bank used for processing transaction. Enumeration of possible values: 01 – HDFC BANK, 02 – ICICI BANK, 03 – AMERICAN EXPRESS, 04 – CITIBANK, 05 – AXIS BANK, 06 – SBI, 07 – HSBC, 09 – CORP BANK, 10 – CUB (City Union Bank), 14 – IDBI Bank, 17 – LVB (Lakshmi Vilas Bank), 51- PINE 360, 301 – Sodexo, 81 – Loyalty Reward, 82 – Aimia, 85 – SBI Rewards Mandatory
23 Reward Redeemed Amount Long Integer 10 Redeemed Amount in Paisa or in lowest currency 10000 Mandatory
24 Reward Redeemed Points Double 15 Redeemed Points 400.00 Mandatory
25 Reward Balance Amount String 10 Balance Amount 1000000 Mandatory
26 Reward Balance Points Double 15 Balance Point 40000.00 Mandatory
27 Charge slip print data in tag value format (Optional)* String Charge slip data in form of tag and value separated with : and new pair separated with |*(Only present if charge slip data on merchant is enabled) Charge slip print data in tag value format(Optional)* Optional
28 EMI Parameter String 0 – 23 Bank EMI 105, Brand .These fields are pipe separated. Brand Type,Tenuar ID,Issuer Bank,Base Amount,EMI amount 105|3|HDFC BANK|100000|33890|0 Mandatory
29 Amount processed successfully by Plutus/Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 – 99 Amount will always be in paisa or lowest currency. 100000 Mandatory
30 RFU3 String 0 – 23 Reserved for future use Optional
31 RFU String Specific for merchant Alhanumeric Optional
32 Date of Transaction String 0 - 8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format. 02012011 Mandatory
33 Time of Transaction String 0 - 6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24hour format. 210403 Mandatory
34 PineLabs Client ID Integer 0 - 6 Unique ID assigned to Pine Labs EDC. 12345 Mandatory


Request

HEX String Format
ASCII Format
10000997002135313031202C545831323334353637382C3130303030302C2C2C2C2C2C2C2C2C2CFF
 — !5101 ,TX12345678,100000,,,,,,,,,,ÿ

Response

HEX String Format
ASCII Format
99991997000101512254583132333435363738222C223030222C22415050524F564544222C222A2A2A2A2A2A2A2A2A2A2A2A39383537222C2258585858222C2253414E44454550204B554D4152202F222C224D415354455243415244222C33322C302C223938393338343933222C302C2250524F434553534544222C2249434943492042414E4B222C2220222C22303030303030303030303230222C322C312C224C4F564520434F4D4D554E49434154494F4E222C224A414E414B50555249222C224E45572044454C48492044454C20222C22506C757475732076322E3132204D54222C30322C22222C22222C22222C22222C22222C223130357C337C484446432042414E4B7C3130303030307C33333839307C30222C22222C22222C22222C223039313732303230222C22313132363237222C2232363831353331222C22313030303030222C2235313031222C22434152445F4348495022FF
™™— Q"TX12345678","00","APPROVED","************9857","XXXX","SANDEEP KUMAR /","MASTERCARD",32,0,"98938493",0,"PROCESSED","ICICI BANK"," ","000000000020",2,1,"LOVE COMMUNICATION","JANAKPURI","NEW DELHI DEL ","Plutus v2.12 MT",02,"","","","","","105|3|HDFC BANK|100000|33890|0","","","","09172020","112627","2681531","100000","5101","CARD_CHIP"ÿ

JSON Request:
 
      
  Coming Soon
    
  

JSON Response:
 
      
  
  Coming Soon
  
  




EMI as Single Transaction for Brand & Bank EMI

This transaction is similar to EMI transactions here user will select the type of EMI(Brand/Bank EMI) at the terminal based on the user selection application will process the selected EMI mode(Brand/Bank EMI).

Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer the Transaction Types
Range: 4001-4216
5005 Mandatory
2 Billing reference number String 0 – 25 Transaction reference number from external “TX12345678” Optional
3 Total EFT Amount Long Integer 0 - 8 Amount to be charged to card – expressed as a whole number in lowest currency unit (ie. in paisa)
Range: 1-99999999
999999 Mandatory
4 Bank Code String 1 – 2 The bank code to which transaction will be routed 1 Optional
5 Track 1 data/Card PAN Number String 1 – 76 Track1 data of the card or Card number if manual entry. If empty then Plutus will ask for card input. Optional
6 Track 2 data / Expiry date String 1 – 37 "Track2 data of the card or Expiry date if manual entry. If empty then Plutus will ask for card input. Expiry date is in YYMM format. In case of Pine 360, if Track 1 consists of mobile or GV number, this field will indicate the card entry mode. Mobile Number – 01 Barcode – 02 Manual - 03" Optional
7 Invoice Number Long Integer 1 – 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Invoice number of parent transition. 12 Optional
8 Is Swipe entry String TRUE or FALSE By default it is TRUE. TRUE Optional
9 Terminal ID String 1-8 Reserved for future use Optional
10 Operator String 1-31 Reserved for future use Optional
11 RFU2 String Reserved for future use Optional
12 EDC Batch ID Integer 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Batch Id of parent transition. Optional
13 EDC ROC Integer 3 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Roc of parent transition.
Range: 101-999
201 Optional
14 Transaction log ID Long Integer 1 - 12 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Transaction log of parent transition.
Range: 1-184467440737
123234 Optional
15 Reward\Cash amount Long Integer 1 – 8 Amount to be paid by reward points or in cash in paise (or in lowest currency)
Range: 1 – 99999999
999999 Optional
16 Customer Mobile Number String 1 – 100 Customer mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
17 Customer email id(s) String 1 – 500 Customer email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
18 Merchant mobile number(s) String 1 – 100 Merchant mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
19 Merchant email id(s) String 1 – 500 Merchant email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
20 Consent to send charge slip on customer mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her mobile number(s). TRUE Optional
21 Consent to send charge slip on customer email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her email id(s). TRUE Optional
22 Consent to send charge slip on merchant mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her mobile number. TRUE Optional
23 Consent to send charge slip on merchant email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her email id(s). TRUE Optional

Response Parameters

Position in CSV Field Name Data Type Length Description Sample
Value
Mandatory/
Optional
1 Billing Reference Number String 0 - 25 Transaction reference number from external application. TX12345678 Mandatory
2 Approval Code String 1 - 6 Credit card authorization code, if transaction was approved. Otherwise empty string. Presence of non-zero length approval code string indicates successful authorization of transaction. This logic holds true for Pine 360 transactions as well. “5261AJ” Mandatory
3 Host Response String 0 - 50 Response string if a response for transaction was received from bank switch. Otherwise, if any error occurs before response is received, this is an empty string. “APPROVED” Mandatory
4 Card Number String 0 - 19 Card number is valid if card was swiped. Otherwise, empty string. “************2802” Mandatory
5 Expiration Date String 0 or 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. “XXXX” Mandatory
6 Cardholder’s Name String 0 - 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string. “AMIT MOHAN” Mandatory
7 Card Type String 0 - 12 Card association name, if valid card was swiped. Otherwise, empty string. “VISA” Mandatory
8 Invoice Number/EDC ROC (in case of Reward Transaction) Long Integer 0 - 6 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on charge slip). Range 0 - 999999 / 101 - 999 (in case of Reward Transaction) 78/101 Mandatory
9 Batch Number/EDC Batch ID (in case of Reward Transaction) Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction). Mandatory
10 Terminal ID String 0 or 8 EFT TID, if transaction authorized. Otherwise, empty string. “30000001” Mandatory
11 Loyalty Points Awarded Long 0 - 8 RFU – not used.
Range: 0 – 99999999
0 Mandatory
12 Remark String 0 - 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization. “Failed to dial modem” Mandatory
13 Transaction Acquirer Name String 0 - 48 Name of acquirer to which transaction was routed. “ICICI BANK” Mandatory
14 Merchant ID String 0 - 15 EFT ME ID, if transaction authorized. Otherwise, empty string. “000100090015607” Mandatory
15 Retrieval Reference Number String 0 - 12 EFT RRN, if transaction authorized. Otherwise, empty string. “000000012843” Mandatory
16 Card Entry Mode Integer 0 - 5 Enumeration of possible values: 0 – Manual entry 1 – Swipe entry 2 – Chip card entry Any other value – card not validated
Range: 0 – 32767
1 Mandatory
17 Print Cardholder's Name on receipt Integer 0 - 5 Enumeration of possible values: 0 – Do not print cardholder’s name 1 – Print cardholder’s name Any other value – card not validated. This is used if external application is to print Plutus charge slip.
Range: 0 – 32767
0 Mandatory
18 Merchant Name String 0 - 23 Merchant name, if transaction authorized. Otherwise, empty string. “NOBLE MOTORS” Mandatory
19 Merchant Address String 0 - 23 Merchant address line, if transaction authorized. Otherwise, empty string. “HAJI ALI” Mandatory
20 Merchant City String 0 - 23 Merchant city line, if transaction authorized. Otherwise, empty string. “MUMBAI” Mandatory
21 Plutus Version String 0 - 40 Plutus version. “v1.54 (for ICICI BANK)” Mandatory
22 Acquiring Bank Code Integer 0 - 999 Code for bank used for processing transaction. Enumeration of possible values: 01 – HDFC BANK, 02 – ICICI BANK, 03 – AMERICAN EXPRESS, 04 – CITIBANK, 05 – AXIS BANK, 06 – SBI, 07 – HSBC, 09 – CORP BANK, 10 – CUB (City Union Bank), 14 – IDBI Bank, 17 – LVB (Lakshmi Vilas Bank), 51 - PINE 360, 301 - Sodexo, 81 – Loyalty Reward, 82 – Aimia, 85 – SBI Rewards Mandatory
23 Reward Redeemed Amount Long Integer 0 - 10 Redeemed Amount in Paisa or in lowest currency. “10000” Optional
24 Reward Redeemed Points Double 0 - 15 Redeemed Points. “400.00” Optional
25 Reward Balance Amount String 0 - 10 Balance Amount. “1000000” Optional
26 Reward Balance Points Double 0 - 15 Balance Point. “40000.00” Optional
27 Charge slip print data in tag value format (Optional)* String Charge slip data in form of tag and value separated with : and new pair separated with |*(Only present if charge slip data on merchant is enabled) Charge slip print data in tag value format(Optional)* Mandatory
28 RFU1/Coupon code/Loyalty Card Number String 0 - 23 Card Processing Fee in Rs (decimal) Or Coupon Code. Coupon code is the value which will be coming as a response to voucher redemption. This field will be present in case of voucher redemption. Or Loyalty number fetched if the transaction type is 4301. “5.50” Mandatory
29 Amount processed successfully by Plutus/ Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 - 99 Amount will always be in paisa or lowest currency. “100000” Mandatory
30 RFU3 String 0 - 23 Reserved for future use Mandatory
31 RFU String Specific for merchant Alhanumeric Optional
32 Date of Transaction String 0 - 8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format. “02012011” Mandatory
33 Time of Transaction String 0 - 6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24-hour format. “210403” Mandatory
34 PineLabs Client ID Integer 0 - 6 Unique ID assigned to Pine Labs EDC. 12345 Mandatory


Request

HEX String Format
ASCII Format
10000997001B353030352C20545831323334353637382C3130302C2C2C2C2C2C2CFF
 — 5005, TX12345678,100,,,,,,,ÿ

Response

HEX String Format
ASCII Format
999919970001016D54312F313233343536373839302C223030222C22415050524F564544222C222A2A2A2A2A2A2A2A2A2A2A2A36383031222C2258585858222C22474155524156204B554D4152222C2256495341222C3134382C35382C223735373736383939222C302C2250524F434553534544222C2249434943492042414E4B222C22202020202020202020202020202020222C22303030303030303030303230222C322C312C224C4F564520434F4D4D554E49434154494F4E222C224A414E414B50555249222C224E45572044454C48492020202044454C20202020202020222C22506C757475732076322E3132204D542049434943492042414E4B222C30322C22222C22222C22222C22222C22222C223130357C337C484446432042414E4B7C31303030307C333338397C30222C22222C22222C22222C223038303132303233222C22313733373030222C2234323935323331313932222C223130303030222C2235303035222C22434152445F4348495022FF
™™— mT1/1234567890,"00","APPROVED","************6801","XXXX","GAURAV KUMAR","VISA",148,58,"75776899",0,"PROCESSED","ICICI BANK"," ","000000000020",2,1,"LOVE COMMUNICATION","JANAKPURI","NEW DELHI DEL ","Plutus v2.12 MT ICICI BANK",02,"","","","","","105|3|HDFC BANK|10000|3389|0","","","","08012023","173700","4295231192","10000","5005","CARD_CHIP"ÿ

JSON Request:
 
    
Coming Soon
  

JSON Response:
 
    

Coming Soon



Tip Adjust Transaction

The Tip Adjust transaction is used to notify the host that there has been an addition to the amount of a previous transaction

Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/ Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer the Transaction Types.
Range: 4001-4216
4015 Mandatory
2 Billing reference number String 0 – 25 Transaction reference number from external “TX12345678” Optional
3 Total EFT Amount Long Integer 0 - 8 Amount to be charged to card – expressed as a whole number in lowest currency unit (ie. in paisa) 999999 Mandatory
7 Invoice Number Long Integer 1 – 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Invoice number of parent transition. 12 Optional
12 EDC Batch ID Integer 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Batch Id of parent transition. Optional
13 EDC ROC Integer 3 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Roc of parent transition.
Range: 101-999
201 Optional
14 Transaction log ID Long Integer 01-12 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Transaction log of parent transition.
Range: 1-184467440737
123234 Optional
15 Reward\\Cash amount Long Integer 1 – 8 Amount to be paid by reward points or in cash in paise (or in lowest currency). 999999 Optional
16 Customer Mobile Number String 1 – 100 Customer mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
17 Customer email id(s) String 1 – 500 Customer email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
18 Merchant mobile number(s) String 1 – 100 Merchant mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
19 Merchant email id(s) String 1 – 500 Merchant email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
20 Consent to send charge slip on customer mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her mobile number(s). TRUE Optional
21 Consent to send charge slip on customer email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her email id(s). TRUE Optional
22 Consent to send charge slip on merchant mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her mobile number. TRUE Optional
23 Consent to send charge slip on merchant email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her email id(s). TRUE Optional

Response Parameters

Position in CSV Field Name Data Type Length Description Sample
Value
Mandatory/
Optional
1 Billing Reference Number String 0 - 25 Transaction reference number from external application. TX12345678 Mandatory
2 Approval Code String 1 - 6 Credit card authorization code, if transaction was approved. Otherwise empty string. Presence of non-zero length approval code string indicates successful authorization of transaction. This logic holds true for Pine 360 transactions as well. “5261AJ” Mandatory
3 Host Response String 0 - 50 Response string if a response for transaction was received from bank switch. Otherwise, if any error occurs before response is received, this is an empty string. “APPROVED” Mandatory
4 Card Number String 0 - 19 Card number is valid if card was swiped. Otherwise, empty string. “************2802” Mandatory
5 Expiration Date String 0 or 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. “XXXX” Mandatory
6 Cardholder’s Name String 0 - 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string. “AMIT MOHAN” Mandatory
7 Card Type String 0 - 12 Card association name, if valid card was swiped. Otherwise, empty string. “VISA” Mandatory
8 Invoice Number/EDC ROC (in case of Reward Transaction) Long Integer 0 - 6 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on charge slip). Range 0 - 999999 / 101 - 999 (in case of Reward Transaction) 78/101 Mandatory
9 Batch Number/EDC Batch ID (in case of Reward Transaction) Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction). Mandatory
10 Terminal ID String 0 or 8 EFT TID, if transaction authorized. Otherwise, empty string. “30000001” Mandatory
11 Loyalty Points Awarded Long 0 - 8 RFU – not used.
Range: 0 – 99999999
0 Mandatory
12 Remark String 0 - 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization. “Failed to dial modem” Mandatory
13 Transaction Acquirer Name String 0 - 48 Name of acquirer to which transaction was routed. “ICICI BANK” Mandatory
14 Merchant ID String 0 - 15 EFT ME ID, if transaction authorized. Otherwise, empty string. “000100090015607” Mandatory
15 Retrieval Reference Number String 0 - 12 EFT RRN, if transaction authorized. Otherwise, empty string. “000000012843” Mandatory
16 Card Entry Mode Integer 0 - 5 Enumeration of possible values: 0 – Manual entry 1 – Swipe entry 2 – Chip card entry Any other value – card not validated
Range: 0 – 32767
1 Mandatory
17 Print Cardholder's Name on receipt Integer 0 - 5 Enumeration of possible values: 0 – Do not print cardholder’s name 1 – Print cardholder’s name Any other value – card not validated. This is used if external application is to print Plutus charge slip.
Range: 0 – 32767
0 Mandatory
18 Merchant Name String 0 - 23 Merchant name, if transaction authorized. Otherwise, empty string. “NOBLE MOTORS” Mandatory
19 Merchant Address String 0 - 23 Merchant address line, if transaction authorized. Otherwise, empty string. “HAJI ALI” Mandatory
20 Merchant City String 0 - 23 Merchant city line, if transaction authorized. Otherwise, empty string. “MUMBAI” Mandatory
21 Plutus Version String 0 - 40 Plutus version. “v1.54 (for ICICI BANK)” Mandatory
22 Acquiring Bank Code Integer 0 - 999 Code for bank used for processing transaction. Enumeration of possible values: 01 – HDFC BANK, 02 – ICICI BANK, 03 – AMERICAN EXPRESS, 04 – CITIBANK, 05 – AXIS BANK, 06 – SBI, 07 – HSBC, 09 – CORP BANK, 10 – CUB (City Union Bank), 14 – IDBI Bank, 17 – LVB (Lakshmi Vilas Bank), 51 - PINE 360, 301 - Sodexo, 81 – Loyalty Reward, 82 – Aimia, 85 – SBI Rewards Mandatory
23 Reward Redeemed Amount Long Integer 0 - 10 Redeemed Amount in Paisa or in lowest currency. “10000” Optional
24 Reward Redeemed Points Double 0 - 15 Redeemed Points. “400.00” Optional
25 Reward Balance Amount String 0 - 10 Balance Amount. “1000000” Optional
26 Reward Balance Points Double 0 - 15 Balance Point. “40000.00” Optional
27 Charge slip print data in tag value format (Optional)* String Charge slip data in form of tag and value separated with : and new pair separated with |*(Only present if charge slip data on merchant is enabled) Charge slip print data in tag value format(Optional)* Mandatory
28 RFU1/Coupon code/Loyalty Card Number String 0 - 23 Card Processing Fee in Rs (decimal) Or Coupon Code. Coupon code is the value which will be coming as a response to voucher redemption. This field will be present in case of voucher redemption. Or Loyalty number fetched if the transaction type is 4301. “5.50” Mandatory
29 Amount processed successfully by Plutus/ Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 - 99 Amount will always be in paisa or lowest currency. “100000” Mandatory
30 RFU3 String 0 - 23 Reserved for future use Mandatory
31 RFU String Specific for merchant Alhanumeric Optional
32 Date of Transaction String 0 - 8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format. “02012011” Mandatory
33 Time of Transaction String 0 - 6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24-hour format. “210403” Mandatory
34 PineLabs Client ID Integer 0 - 6 Unique ID assigned to Pine Labs EDC. 12345 Mandatory

Adjust Transaction

Adjust transaction is used to notify the host that there has been an addition/correction to the amount of a previous transaction

Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer the Transaction Types
Range: 4001-4216
4005 Mandatory
2 Billing reference number String 0 – 25 Transaction reference number from external “TX12345678” Optional
3 Total EFT Amount Long Integer 0 - 8 Amount to be charged to card – expressed as a whole number in lowest currency unit (ie. in paisa)
Range: 1-99999999
999999 Mandatory
4 Bank Code String 1 – 2 The bank code to which transaction will be routed 1 Optional
5 Track 1 data/Card PAN Number String 1 – 76 Track1 data of the card or Card number if manual entry. If empty then Plutus will ask for card input. Optional
6 Track 2 data / Expiry date String 1 – 37 "Track2 data of the card or Expiry date if manual entry. If empty then Plutus will ask for card input. Expiry date is in YYMM format. In case of Pine 360, if Track 1 consists of mobile or GV number, this field will indicate the card entry mode. Mobile Number – 01 Barcode – 02 Manual - 03" Optional
7 Invoice Number Long Integer 1 – 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Invoice number of parent transition. 12 Optional
8 Is Swipe entry String TRUE or FALSE By default it is TRUE. TRUE Optional
9 Terminal ID String 1-8 Reserved for future use Optional
10 Operator String 1-31 Reserved for future use Optional
11 RFU2 String Reserved for future use Optional
12 EDC Batch ID Integer 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Batch Id of parent transition. Optional
13 EDC ROC Integer 3 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Roc of parent transition.
Range: 101-999
201 Optional
14 Transaction log ID Long Integer 1 - 12 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Transaction log of parent transition.
Range: 1-184467440737
123234 Optional
15 Reward\Cash amount Long Integer 1 – 8 Amount to be paid by reward points or in cash in paise (or in lowest currency)
Range: 1 – 99999999
999999 Optional
16 Customer Mobile Number String 1 – 100 Customer mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
17 Customer email id(s) String 1 – 500 Customer email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
18 Merchant mobile number(s) String 1 – 100 Merchant mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
19 Merchant email id(s) String 1 – 500 Merchant email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
20 Consent to send charge slip on customer mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her mobile number(s). TRUE Optional
21 Consent to send charge slip on customer email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her email id(s). TRUE Optional
22 Consent to send charge slip on merchant mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her mobile number. TRUE Optional
23 Consent to send charge slip on merchant email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her email id(s). TRUE Optional

Response Parameters

Position in CSV Field Name Data Type Length Description Sample
Value
Mandatory/
Optional
1 Billing Reference Number String 0 - 25 Transaction reference number from external application. TX12345678 Mandatory
2 Approval Code String 1 - 6 Credit card authorization code, if transaction was approved. Otherwise empty string. Presence of non-zero length approval code string indicates successful authorization of transaction. This logic holds true for Pine 360 transactions as well. “5261AJ” Mandatory
3 Host Response String 0 - 50 Response string if a response for transaction was received from bank switch. Otherwise, if any error occurs before response is received, this is an empty string. “APPROVED” Mandatory
4 Card Number String 0 - 19 Card number is valid if card was swiped. Otherwise, empty string. “************2802” Mandatory
5 Expiration Date String 0 or 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. “XXXX” Mandatory
6 Cardholder’s Name String 0 - 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string. “AMIT MOHAN” Mandatory
7 Card Type String 0 - 12 Card association name, if valid card was swiped. Otherwise, empty string. “VISA” Mandatory
8 Invoice Number/EDC ROC (in case of Reward Transaction) Long Integer 0 - 6 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on charge slip). Range 0 - 999999 / 101 - 999 (in case of Reward Transaction) 78/101 Mandatory
9 Batch Number/EDC Batch ID (in case of Reward Transaction) Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction). Mandatory
10 Terminal ID String 0 or 8 EFT TID, if transaction authorized. Otherwise, empty string. “30000001” Mandatory
11 Loyalty Points Awarded Long 0 - 8 RFU – not used.
Range: 0 – 99999999
0 Mandatory
12 Remark String 0 - 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization. “Failed to dial modem” Mandatory
13 Transaction Acquirer Name String 0 - 48 Name of acquirer to which transaction was routed. “ICICI BANK” Mandatory
14 Merchant ID String 0 - 15 EFT ME ID, if transaction authorized. Otherwise, empty string. “000100090015607” Mandatory
15 Retrieval Reference Number String 0 - 12 EFT RRN, if transaction authorized. Otherwise, empty string. “000000012843” Mandatory
16 Card Entry Mode Integer 0 - 5 Enumeration of possible values: 0 – Manual entry 1 – Swipe entry 2 – Chip card entry Any other value – card not validated
Range: 0 – 32767
1 Mandatory
17 Print Cardholder's Name on receipt Integer 0 - 5 Enumeration of possible values: 0 – Do not print cardholder’s name 1 – Print cardholder’s name Any other value – card not validated. This is used if external application is to print Plutus charge slip.
Range: 0 – 32767
0 Mandatory
18 Merchant Name String 0 - 23 Merchant name, if transaction authorized. Otherwise, empty string. “NOBLE MOTORS” Mandatory
19 Merchant Address String 0 - 23 Merchant address line, if transaction authorized. Otherwise, empty string. “HAJI ALI” Mandatory
20 Merchant City String 0 - 23 Merchant city line, if transaction authorized. Otherwise, empty string. “MUMBAI” Mandatory
21 Plutus Version String 0 - 40 Plutus version. “v1.54 (for ICICI BANK)” Mandatory
22 Acquiring Bank Code Integer 0 - 999 Code for bank used for processing transaction. Enumeration of possible values: 01 – HDFC BANK, 02 – ICICI BANK, 03 – AMERICAN EXPRESS, 04 – CITIBANK, 05 – AXIS BANK, 06 – SBI, 07 – HSBC, 09 – CORP BANK, 10 – CUB (City Union Bank), 14 – IDBI Bank, 17 – LVB (Lakshmi Vilas Bank), 51 - PINE 360, 301 - Sodexo, 81 – Loyalty Reward, 82 – Aimia, 85 – SBI Rewards Mandatory
23 Reward Redeemed Amount Long Integer 0 - 10 Redeemed Amount in Paisa or in lowest currency. “10000” Optional
24 Reward Redeemed Points Double 0 - 15 Redeemed Points. “400.00” Optional
25 Reward Balance Amount String 0 - 10 Balance Amount. “1000000” Optional
26 Reward Balance Points Double 0 - 15 Balance Point. “40000.00” Optional
27 Charge slip print data in tag value format (Optional)* String Charge slip data in form of tag and value separated with : and new pair separated with |*(Only present if charge slip data on merchant is enabled) Charge slip print data in tag value format(Optional)* Mandatory
28 RFU1/Coupon code/Loyalty Card Number String 0 - 23 Card Processing Fee in Rs (decimal) Or Coupon Code. Coupon code is the value which will be coming as a response to voucher redemption. This field will be present in case of voucher redemption. Or Loyalty number fetched if the transaction type is 4301. “5.50” Mandatory
29 Amount processed successfully by Plutus/ Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 - 99 Amount will always be in paisa or lowest currency. “100000” Mandatory
30 RFU3 String 0 - 23 Reserved for future use Mandatory
31 RFU String Specific for merchant Alhanumeric Optional
32 Date of Transaction String 0 - 8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format. “02012011” Mandatory
33 Time of Transaction String 0 - 6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24-hour format. “210403” Mandatory
34 PineLabs Client ID Integer 0 - 6 Unique ID assigned to Pine Labs EDC. 12345 Mandatory

Reward Redemption

A transaction between two parties where the buyer receives goods (tangible or intangible),services and/or assets in exchange for Reward points

Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer the Transaction Types
Range: 4001-4216
4101 Mandatory
2 Billing reference number String 0 – 25 Transaction reference number from external “TX12345678” Optional
3 Total EFT Amount Long Integer 0 - 8 Amount to be charged to card – expressed as a whole number in lowest currency unit (ie. in paisa)
Range: 1-99999999
999999 Mandatory
4 Bank Code String 1 – 2 The bank code to which transaction will be routed 1 Optional
5 Track 1 data/Card PAN Number String 1 – 76 Track1 data of the card or Card number if manual entry. If empty then Plutus will ask for card input. Optional
6 Track 2 data / Expiry date String 1 – 37 "Track2 data of the card or Expiry date if manual entry. If empty then Plutus will ask for card input. Expiry date is in YYMM format. In case of Pine 360, if Track 1 consists of mobile or GV number, this field will indicate the card entry mode. Mobile Number – 01 Barcode – 02 Manual - 03" Optional
7 Invoice Number Long Integer 1 – 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Invoice number of parent transition. 12 Optional
8 Is Swipe entry String TRUE or FALSE By default it is TRUE. TRUE Optional
9 Terminal ID String 1-8 Reserved for future use Optional
10 Operator String 1-31 Reserved for future use Optional
11 RFU2 String Reserved for future use Optional
12 EDC Batch ID Integer 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Batch Id of parent transition. Optional
13 EDC ROC Integer 3 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Roc of parent transition.
Range: 101-999
201 Optional
14 Transaction log ID Long Integer 1 - 12 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Transaction log of parent transition.
Range: 1-184467440737
123234 Optional
15 Reward\Cash amount Long Integer 1 – 8 Amount to be paid by reward points or in cash in paise (or in lowest currency)
Range: 1 – 99999999
999999 Optional
16 Customer Mobile Number String 1 – 100 Customer mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
17 Customer email id(s) String 1 – 500 Customer email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
18 Merchant mobile number(s) String 1 – 100 Merchant mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
19 Merchant email id(s) String 1 – 500 Merchant email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
20 Consent to send charge slip on customer mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her mobile number(s). TRUE Optional
21 Consent to send charge slip on customer email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her email id(s). TRUE Optional
22 Consent to send charge slip on merchant mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her mobile number. TRUE Optional
23 Consent to send charge slip on merchant email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her email id(s). TRUE Optional

Response Parameters

Position in CSV Field Name Data Type Length Description Sample
Value
Mandatory/
Optional
1 Billing Reference Number String 0 - 25 Transaction reference number from external application. TX12345678 Mandatory
2 Approval Code String 1 - 6 Credit card authorization code, if transaction was approved. Otherwise empty string. Presence of non-zero length approval code string indicates successful authorization of transaction. This logic holds true for Pine 360 transactions as well. “5261AJ” Mandatory
3 Host Response String 0 - 50 Response string if a response for transaction was received from bank switch. Otherwise, if any error occurs before response is received, this is an empty string. “APPROVED” Mandatory
4 Card Number String 0 - 19 Card number is valid if card was swiped. Otherwise, empty string. “************2802” Mandatory
5 Expiration Date String 0 or 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. “XXXX” Mandatory
6 Cardholder’s Name String 0 - 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string. “AMIT MOHAN” Mandatory
7 Card Type String 0 - 12 Card association name, if valid card was swiped. Otherwise, empty string. “VISA” Mandatory
8 Invoice Number/EDC ROC (in case of Reward Transaction) Long Integer 0 - 6 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on charge slip). Range 0 - 999999 / 101 - 999 (in case of Reward Transaction) 78/101 Mandatory
9 Batch Number/EDC Batch ID (in case of Reward Transaction) Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction). Mandatory
10 Terminal ID String 0 or 8 EFT TID, if transaction authorized. Otherwise, empty string. “30000001” Mandatory
11 Loyalty Points Awarded Long 0 - 8 RFU – not used.
Range: 0 – 99999999
0 Mandatory
12 Remark String 0 - 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization. “Failed to dial modem” Mandatory
13 Transaction Acquirer Name String 0 - 48 Name of acquirer to which transaction was routed. “ICICI BANK” Mandatory
14 Merchant ID String 0 - 15 EFT ME ID, if transaction authorized. Otherwise, empty string. “000100090015607” Mandatory
15 Retrieval Reference Number String 0 - 12 EFT RRN, if transaction authorized. Otherwise, empty string. “000000012843” Mandatory
16 Card Entry Mode Integer 0 - 5 Enumeration of possible values: 0 – Manual entry 1 – Swipe entry 2 – Chip card entry Any other value – card not validated
Range: 0 – 32767
1 Mandatory
17 Print Cardholder's Name on receipt Integer 0 - 5 Enumeration of possible values: 0 – Do not print cardholder’s name 1 – Print cardholder’s name Any other value – card not validated. This is used if external application is to print Plutus charge slip.
Range: 0 – 32767
0 Mandatory
18 Merchant Name String 0 - 23 Merchant name, if transaction authorized. Otherwise, empty string. “NOBLE MOTORS” Mandatory
19 Merchant Address String 0 - 23 Merchant address line, if transaction authorized. Otherwise, empty string. “HAJI ALI” Mandatory
20 Merchant City String 0 - 23 Merchant city line, if transaction authorized. Otherwise, empty string. “MUMBAI” Mandatory
21 Plutus Version String 0 - 40 Plutus version. “v1.54 (for ICICI BANK)” Mandatory
22 Acquiring Bank Code Integer 0 - 999 Code for bank used for processing transaction. Enumeration of possible values: 01 – HDFC BANK, 02 – ICICI BANK, 03 – AMERICAN EXPRESS, 04 – CITIBANK, 05 – AXIS BANK, 06 – SBI, 07 – HSBC, 09 – CORP BANK, 10 – CUB (City Union Bank), 14 – IDBI Bank, 17 – LVB (Lakshmi Vilas Bank), 51 - PINE 360, 301 - Sodexo, 81 – Loyalty Reward, 82 – Aimia, 85 – SBI Rewards Mandatory
23 Reward Redeemed Amount Long Integer 0 - 10 Redeemed Amount in Paisa or in lowest currency. “10000” Mandatory
24 Reward Redeemed Points Double 0 - 15 Redeemed Points. “400.00” Mandatory
25 Reward Balance Amount String 0 - 10 Balance Amount. “1000000” Mandatory
26 Reward Balance Points Double 0 - 15 Balance Point. “40000.00” Mandatory
27 Charge slip print data in tag value format (Optional)* String Charge slip data in form of tag and value separated with : and new pair separated with |*(Only present if charge slip data on merchant is enabled) Charge slip print data in tag value format(Optional)* Mandatory
28 RFU1/Coupon code/Loyalty Card Number String 0 - 23 Card Processing Fee in Rs (decimal) Or Coupon Code. Coupon code is the value which will be coming as a response to voucher redemption. This field will be present in case of voucher redemption. Or Loyalty number fetched if the transaction type is 4301. “5.50” Mandatory
29 Amount processed successfully by Plutus/ Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 - 99 Amount will always be in paisa or lowest currency. “100000” Mandatory
30 RFU3 String 0 - 23 Reserved for future use Mandatory
31 RFU String Specific for merchant Alhanumeric Optional
32 Date of Transaction String 0 - 8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format. “02012011” Mandatory
33 Time of Transaction String 0 - 6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24-hour format. “210403” Mandatory
34 PineLabs Client ID Integer 0 - 6 Unique ID assigned to Pine Labs EDC. 12345 Mandatory


Request

HEX String Format
ASCII Format
1000099700242234313031222C2254583132333435363738222C2239393939303030222C2C2C2C2C2C2CFF
 — $"4101","TX12345678","9999000",,,,,,,ÿ

Response

HEX String Format
ASCII Format
9999199700010139545831323334353637382C22373236314139222C225452414E53414354494F4E205355434345535346554C222C222A2A2A2A2A2A2A2A2A2A2A2A32383032222C2230343036222C2252616D53696E6768222C22222C37382C3530322C223330303030303031222C302C225020524F434553534544222C20224C4F59414C545920524557415244222C2022303030313030303930303135363037222C2220363234363135333433303032222C312C20312C22204850434C2041726561203138222C22204B616D6C61204D696C6C73222C224E6F696461222C22762E30312E30302E3030222C38312C223130303030222C223430302E3030222C2231303030303030222C2234303030302E3030222C22222C22222C22222C22222C2222202C223032303132303131222C2232313034303322544350204353563A20FF
™™— 9TX12345678,"7261A9","TRANSACTION SUCCESSFUL","************2802","0406","RamSingh","",78,502,"30000001",0,"P ROCESSED", "LOYALTY REWARD", "000100090015607"," 624615343002",1, 1," HPCL Area 18"," Kamla Mills","Noida","v.01.00.00",81,"10000","400.00","1000000","40000.00","","","","","" ,"02012011","210403"TCP CSV: ÿ

JSON Request:
 
  
Coming Soon


JSON Response:
 
  

Coming Soon



Reward Void

The Reward Void transaction is used to reverse a previously approved Reward redemption transaction

Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer the Transaction Types
Range: 4001-4216
4102 Mandatory
2 Billing reference number String 0 – 25 Transaction reference number from external “TX12345678” Optional
3 Total EFT Amount Long Integer 0 - 8 Amount to be charged to card – expressed as a whole number in lowest currency unit (ie. in paisa)
Range: 1-99999999
999999 Mandatory
4 Bank Code String 1 – 2 The bank code to which transaction will be routed 1 Optional
5 Track 1 data/Card PAN Number String 1 – 76 Track1 data of the card or Card number if manual entry. If empty then Plutus will ask for card input. Optional
6 Track 2 data / Expiry date String 1 – 37 "Track2 data of the card or Expiry date if manual entry. If empty then Plutus will ask for card input. Expiry date is in YYMM format. In case of Pine 360, if Track 1 consists of mobile or GV number, this field will indicate the card entry mode. Mobile Number – 01 Barcode – 02 Manual - 03" Optional
7 Invoice Number Long Integer 1 – 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Invoice number of parent transition. 12 Optional
8 Is Swipe entry String TRUE or FALSE By default it is TRUE. TRUE Optional
9 Terminal ID String 1-8 Reserved for future use Optional
10 Operator String 1-31 Reserved for future use Optional
11 RFU2 String Reserved for future use Optional
12 EDC Batch ID Integer 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Batch Id of parent transition. Optional
13 EDC ROC Integer 3 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Roc of parent transition.
Range: 101-999
201 Optional
14 Transaction log ID Long Integer 1 - 12 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Transaction log of parent transition.
Range: 1-184467440737
123234 Optional
15 Reward\Cash amount Long Integer 1 – 8 Amount to be paid by reward points or in cash in paise (or in lowest currency)
Range: 1 – 99999999
999999 Optional
16 Customer Mobile Number String 1 – 100 Customer mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
17 Customer email id(s) String 1 – 500 Customer email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
18 Merchant mobile number(s) String 1 – 100 Merchant mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
19 Merchant email id(s) String 1 – 500 Merchant email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
20 Consent to send charge slip on customer mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her mobile number(s). TRUE Optional
21 Consent to send charge slip on customer email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her email id(s). TRUE Optional
22 Consent to send charge slip on merchant mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her mobile number. TRUE Optional
23 Consent to send charge slip on merchant email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her email id(s). TRUE Optional

Response Parameters

Position in CSV Field Name Data Type Length Description Sample
Value
Mandatory/
Optional
1 Billing Reference Number String 0 - 25 Transaction reference number from external application. TX12345678 Mandatory
2 Approval Code String 1 - 6 Credit card authorization code, if transaction was approved. Otherwise empty string. Presence of non-zero length approval code string indicates successful authorization of transaction. This logic holds true for Pine 360 transactions as well. “5261AJ” Mandatory
3 Host Response String 0 - 50 Response string if a response for transaction was received from bank switch. Otherwise, if any error occurs before response is received, this is an empty string. “APPROVED” Mandatory
4 Card Number String 0 - 19 Card number is valid if card was swiped. Otherwise, empty string. “************2802” Mandatory
5 Expiration Date String 0 or 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. “XXXX” Mandatory
6 Cardholder’s Name String 0 - 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string. “AMIT MOHAN” Mandatory
7 Card Type String 0 - 12 Card association name, if valid card was swiped. Otherwise, empty string. “VISA” Mandatory
8 Invoice Number/EDC ROC (in case of Reward Transaction) Long Integer 0 - 6 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on charge slip). Range 0 - 999999 / 101 - 999 (in case of Reward Transaction) 78/101 Mandatory
9 Batch Number/EDC Batch ID (in case of Reward Transaction) Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction). Mandatory
10 Terminal ID String 0 or 8 EFT TID, if transaction authorized. Otherwise, empty string. “30000001” Mandatory
11 Loyalty Points Awarded Long 0 - 8 RFU – not used.
Range: 0 – 99999999
0 Mandatory
12 Remark String 0 - 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization. “Failed to dial modem” Mandatory
13 Transaction Acquirer Name String 0 - 48 Name of acquirer to which transaction was routed. “ICICI BANK” Mandatory
14 Merchant ID String 0 - 15 EFT ME ID, if transaction authorized. Otherwise, empty string. “000100090015607” Mandatory
15 Retrieval Reference Number String 0 - 12 EFT RRN, if transaction authorized. Otherwise, empty string. “000000012843” Mandatory
16 Card Entry Mode Integer 0 - 5 Enumeration of possible values: 0 – Manual entry 1 – Swipe entry 2 – Chip card entry Any other value – card not validated
Range: 0 – 32767
1 Mandatory
17 Print Cardholder's Name on receipt Integer 0 - 5 Enumeration of possible values: 0 – Do not print cardholder’s name 1 – Print cardholder’s name Any other value – card not validated. This is used if external application is to print Plutus charge slip.
Range: 0 – 32767
0 Mandatory
18 Merchant Name String 0 - 23 Merchant name, if transaction authorized. Otherwise, empty string. “NOBLE MOTORS” Mandatory
19 Merchant Address String 0 - 23 Merchant address line, if transaction authorized. Otherwise, empty string. “HAJI ALI” Mandatory
20 Merchant City String 0 - 23 Merchant city line, if transaction authorized. Otherwise, empty string. “MUMBAI” Mandatory
21 Plutus Version String 0 - 40 Plutus version. “v1.54 (for ICICI BANK)” Mandatory
22 Acquiring Bank Code Integer 0 - 999 Code for bank used for processing transaction. Enumeration of possible values: 01 – HDFC BANK, 02 – ICICI BANK, 03 – AMERICAN EXPRESS, 04 – CITIBANK, 05 – AXIS BANK, 06 – SBI, 07 – HSBC, 09 – CORP BANK, 10 – CUB (City Union Bank), 14 – IDBI Bank, 17 – LVB (Lakshmi Vilas Bank), 51 - PINE 360, 301 - Sodexo, 81 – Loyalty Reward, 82 – Aimia, 85 – SBI Rewards Mandatory
23 Reward Redeemed Amount Long Integer 0 - 10 Redeemed Amount in Paisa or in lowest currency. “10000” Optional
24 Reward Redeemed Points Double 0 - 15 Redeemed Points. “400.00” Optional
25 Reward Balance Amount String 0 - 10 Balance Amount. “1000000” Optional
26 Reward Balance Points Double 0 - 15 Balance Point. “40000.00” Optional
27 Charge slip print data in tag value format (Optional)* String Charge slip data in form of tag and value separated with : and new pair separated with |*(Only present if charge slip data on merchant is enabled) Charge slip print data in tag value format(Optional)* Mandatory
28 RFU1/Coupon code/Loyalty Card Number String 0 - 23 Card Processing Fee in Rs (decimal) Or Coupon Code. Coupon code is the value which will be coming as a response to voucher redemption. This field will be present in case of voucher redemption. Or Loyalty number fetched if the transaction type is 4301. “5.50” Mandatory
29 Amount processed successfully by Plutus/ Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 - 99 Amount will always be in paisa or lowest currency. “100000” Mandatory
30 RFU3 String 0 - 23 Reserved for future use Mandatory
31 RFU String Specific for merchant Alhanumeric Optional
32 Date of Transaction String 0 - 8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format. “02012011” Mandatory
33 Time of Transaction String 0 - 6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24-hour format. “210403” Mandatory
34 PineLabs Client ID Integer 0 - 6 Unique ID assigned to Pine Labs EDC. 12345 Mandatory


Request

HEX String Format
ASCII Format
100009970038343030362C545831323334353637382C393939393030302C30312C2C2C2C2C2C2C2CE2809D39303032E2809D2CE2809D323031E2809D0D0AFF
 — 84006,TX12345678,9999000,01,,,,,,,,”9002”,”201” ÿ

Response

HEX String Format
ASCII Format
999919970001016E545831323334353637382CE2809C373236314139E2809D2CE2809D5452414E53414354494F4E205355434345535346554CE2809D2CE2809D2A2A2A2A2A2A2A2A2A2A2A2A32383032E2809D2CE2809D30343036E2809D2CE2809D52616D53696E6768E2809D2CE2809DE2809D2C37382C3530322CE2809D3330303030303031E2809D2C302CE2809D5020524F434553534544E2809D2C20E2809D4C4F59414C545920524557415244E2809D2C20E2809D303030313030303930303135363037E2809D2CE2809D20363234363135333433303032E2809D2C312C20312CE2809D204850434C2041726561203138E2809D2CE2809D204B616D6C61204D696C6C73E2809D2CE2809D4E6F696461E2809D2CE2809D762E30312E30302E3030E2809D2C38312C223130303030222C223430302E3030222C2231303030303030222C2234303030302E3030222C22222C22222C22222C22222C2222202C223032303132303131222C22323130343033220D0AFF
™™— nTX12345678,“7261A9”,”TRANSACTION SUCCESSFUL”,”************2802”,”0406”,”RamSingh”,””,78,502,”30000001”,0,”P ROCESSED”, ”LOYALTY REWARD”, ”000100090015607”,” 624615343002”,1, 1,” HPCL Area 18”,” Kamla Mills”,”Noida”,”v.01.00.00”,81,"10000","400.00","1000000","40000.00","","","","","" ,"02012011","210403" ÿ

JSON Request:
 
  
Coming Soon


JSON Response:
 
  

Coming Soon



Transaction Validation

Transaction Validation transaction is used to validate the previous completed Sale transactions.
This transaction can be used if the user wants to know the status on previous completed Sale transaction

Note*
  1. For Sale, transaction-id is mandatory.
  2. If PTRN/BillingRefNumber is provided, other transaction identifiers (Transaction Id, Client Id, Batch Id, Roc) should not be passed.
  3. Last tranascation of EDC batch response will pending until next txn will done or batch settled.
  4. Validation api will send response of only 2 (48 Hours) days txn.

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer the Transaction Types Range: 4001-4216 7001 Mandatory
2 Merchant ID Long 0 - 15 PLUTUS Merchant ID 000100090015607 Mandatory
3 Transaction Type Identifier STRING 1 - 100 String that identifies txn type. Valid values are: SALE, PARTIAL_SALE, REWARDS, PINE360, PAYBACK SALE Mandatory
4 Transaction Amount Long 0 - 8 Total Transaction amount in paise 800 Mandatory
5 Transaction Id Long 0 - 19 Plutus transaction ID if a card transaction is involved. If TxnId is not available, "ClientID, BatchID, and Roc" must be sent. 30000000100001 Conditional
6 Client Id Long 0 - 6 ID of transacting POS 14782 Conditional
7 Batch Id Long 6 Transaction Batch 9398 Conditional
8 Roc Long 3 - 6 Transaction ROC.
Rang 101 - 999999
172 Conditional
9 Billing Reference Number string 0 - 25 Billing Integration Number TX12345678 Optional
10 PTRN LONG 1 - 8 Plutus Cloud Based Transaction Reference ID 0 Optional
11 Security Token string 1 - 100 Merchant Security Token 511D5FB5-F16D-4CD2-88F2-86A64D8FE Mandatory
12 Host Url string 1 - 100 Host Url https://www.plutuscloudserviceuat.in:8201/api/CloudBasedIntegration/V1/PerformTxnValidation Mandatory

Response Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Transaction Type String 4 Transaction request type to Plutus application. Please refer the Transaction 7001 Mandatory
2 Response Message String 0 - 50 Transaction response message SUCCESS/FAILURE Mandatory
3 Original Transaction Type String 1 Original Transaction type 1-Sale , 2-UPI , 3-Reward, 4-Payback, 5-Pine360 Mandatory
4 Billing Reference Number String 0-25 Transaction reference number from external application. TX12345678 Mandatory
5 PTRN Long 1 - 8 Plutus transaction reference number of the uploaded bill 0 Mandatory
6 Host Transaction Number String 1 - 100 Transaction number of the uploaded bill SEQ-513 Mandatory
7 Bank Response Message String 1 - 100 Response message from Bank Success Mandatory
8 Transaction Status String 1 - 50 Status of transaction PASS Mandatory
9 Card Transaction Type String 1 - 100 Type of transaction (Eg. SALE) SALE Mandatory
10 Transaction Date Time String 1 - 100 Date and time of transaction 44910.8428 Mandatory
11 RRN String 0 - 12 Transaction reference number 000020 Mandatory
12 Auth Code String 0 - 6 Transaction auth code 0 Mandatory
13 Acquirer Name String 0 - 48 Card acquirer name ICICI Mandatory
14 Transaction Amount String 0 - 8 Transaction amount in paise 100 Mandatory
15 Masked Pan Number String 0 - 19 Masked Card number ************6954 Mandatory
16 Card Holder Name String 0 - 25 Card Holder name VIKASH KUMAR Mandatory
17 Bank Mid String 0 - 15 Bank merchant ID for uploaded bill 0 Mandatory
18 Bank Tid String 0 - 8 Bank Terminal ID for uploaded bill 65743567 Mandatory
19 Batch Number String 6 Batch number 17 Mandatory
20 Invoice Number String 1 - 6 Invoice number for uploaded bill
Range 0 - 999999
59 Mandatory
21 Card Type String 0 - 12 Type of card (Eg. VISA) VISA Mandatory
22 Card Entry Mode String 1 - 5 Card Entry Mode
Range 0 - 32767
CARD_CHIP Mandatory
23 Acquirer Code String 1 - 8 Card acquirer code 2 Mandatory
24 Merchant Name String 0 - 23 Name of merchant PINELABS Mandatory
25 Merchant Address String 0 - 23 Address of merchant PINELABS Mandatory
26 Merchant City String 0 - 23 City of merchant PINELABS Mandatory
27 Batch Status String 4 or 6 Status of batch (eg. OPEN) OPEN or CLOSE Mandatory
28 Additional Information Tag1 String 1 - 100 AdditionalInfo tag 1 NA Mandatory
29 Additional Information Val1 String 1 - 100 AdditionalInfo value 1 NA Mandatory
30 Additional Information Tag2 String 1 - 100 AdditionalInfo tag 2 NA Mandatory
31 Additional Information Val2 String 1 - 100 AdditionalInfo value 2 NA Mandatory


Request

HEX String Format
ASCII Format
021000099700B9373030312C343239353230333735372C53414C452C3130302C33303030303030303130303030312C31343738322C393339382C3137322C2C2C31364439414639442D394132332D343038462D393732312D3145364534383032433145302C68747470733A2F2F7777772E706C75747573636C6F7564736572766963657561742E696E3A383230312F6170692F436C6F75644261736564496E746567726174696F6E2F56312F506572666F726D54786E56616C69646174696F6E0323
 — ¹7001,4295203757,SALE,100,30000000100001,14782,9398,172,,,16D9AF9D-9A23-408F-9721-

Response

HEX String Format
ASCII Format
0299991997000100DE01373030312C535543434553532C312C545831323334353637382C302C5345512D3531332C535543434553532C504153532C53414C452C32312D30362D323032312031393A33353A323720504D2C34323433313237302C30302C49434943492C313630303030302C3432303733392A2A2A2A2A2A343735302C5445535420434152442C3030303030303030303030303030302C38303031323435382C33332C3136342C4D41455354524F2C434152445F434849502C30322C50494E454C4142532C50494E454C4142532C50494E454C4142532C434C4F5345442C2C2C2C2C037B
™™—  Þ7001,SUCCESS,1,TX12345678,0,SEQ-513,SUCCESS,PASS,SALE,21-06-2021 19:35:27 PM,42431270,00,ICICI,1600000,420739******4750,TEST CARD,000000000000000,80012458,33,164,MAESTRO,CARD_CHIP,02,PINELABS,PINELABS,PINELABS,CLOSED,,,,,{

JSON Request:
 

Coming Soon


JSON Response:
 


Coming Soon



Settlement

Settlement transaction is used to settle the open batch in the terminal.

Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer the Transaction Types.
Range: 4001-4216
6001 Mandatory

Response Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
31 Settlement Summary (Optional) String - Settlement summary - Mandatory


Request

HEX String Format
ASCII Format
10000997001A363030312C2C2C2C2C2C2C2C2C2C2CFF
 — 6001,,,,,,,,,,,ÿ

Response

HEX String Format
ASCII Format
9999199700010221012C2C2C2C2C2C2C2C2C2C2C2C2C2C2C2C2C2C2C2C2C2C2C2C2C2C2031303030303A317C31303030313A49434943497C31303035303A50696E65206D65726368616E742073746F72657C31303835313A536574746C656D656E74205265706F72747C31303035313A526F68696E69205365632031327C31303930303A42616E67616C6F72657C31303130303A30372F30312F323031357C31303130313A31322D31322D32337C31303135303A3939363534353435343534313835317C31303135313A36353835343137387C31303230303A3030303031307C31303930313A44657461696C73205265706F72747C31303935313A494E564F494345204E554D424552205452414E53414354494F4E2054595045204155544820434F44452043415244204E554D4245522043415244205459504520414D4F554E547C31313030303A31302053414C4520303030303030202A2A2A2A2A2A2A2A2A2A2A2A3238303220564953412052532E313030302E31317C31313030313A534554544C454D454E5420434F4D504C4554457C31313035303A332052533930322E39377C31313035313A302052532E302E30307C31313130303A302052532E302E30307C31313130313A2052533930322E39377C31313135303A302052532E302E30307C31313135313A2052532E302E30307C31313230303A52532E3930322E39372C2C2C2C2049434943492C312C31313135393837342C312C323534322E30302C302C302E30302C2CFF
™™— !,,,,,,,,,,,,,,,,,,,,,,,,,, 10000:1|10001:ICICI|10050:Pine merchant store|10851:Settlement Report|10051:Rohini Sec 12|10900:Bangalore|10100:07/01/2015|10101:12-12-23|10150:996545454541851|10151:65854178|10200:000010|10901:Details Report|10951:INVOICE NUMBER TRANSACTION TYPE AUTH CODE CARD NUMBER CARD TYPE AMOUNT|11000:10 SALE 000000 ************2802 VISA RS.1000.11|11001:SETTLEMENT COMPLETE|11050:3 RS902.97|11051:0 RS.0.00|11100:0 RS.0.00|11101: RS902.97|11150:0 RS.0.00|11151: RS.0.00|11200:RS.902.97,,,, ICICI,1,11159874,1,2542.00,0,0.00,,ÿ

JSON Request:
 
    
  Coming Soon
  
  

JSON Response:
 
    
  
  Coming Soon
  
  


Wallet

In integrated mode, wallet payments transactions can be launched directly from external billing / retail applications – avoiding the need for dual amount input. Also, the transaction response details are passed to the external application. Transaction completion can be used to automatically link the EFT payment transaction with the billing sale transaction for reconciliation.

Sr. No. Type of Transactions Transaction type CSV Field 1
1 WalletPay 5102
2 WalletLoad 5103
2 WalletVoid 5104

Wallet Pay

A transaction between two parties where the buyer receives goods (tangible or intangible),services and/or assets in exchange for wallet money.

Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer the Transaction Types. Range: 4001-4216 5102 Mandatory
2 Billing reference number String 0 – 25 Transaction reference number from external application. Plutus will only use this value for printing on charge slip. “TX12345678” Optional
3 Total EFT amount Long Integer 1 to 8 Amount to be charged to card – expressed as a whole number in lowest currency unit (ie. in paisa). Range: 1 – 99999999 999999 Mandatory
4 Wallet Program ID Integer 1-999 This ID will be assigned by Pine Labs to each wallet program type. While performing any Wallet transaction, this field needs to be set to identify wallet host. For Jio Money, this value will be 101. 101 Optional
5 Wallet Identifier Data(card/ mobile/barcode) String 1 – 76 Mobile/Barcode/Card Number. If not set, terminal will prompt to capture these values. For Jio Money, Barcode needs to be captured at Billing POS and sent in this field. Optional
6 Type of Wallet Input Identifier String 1 – 37 Type of Wallet identifier Contained in Field 4. Mobile Number – 01, Barcode – 02, Swipe - 03 1 Optional
8 Is Swipe entry String TRUE or FALSE By default, it is TRUE. TRUE Optional
10 Operator String 1 – 31 Operator Optional

Response Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Billing Reference Number String 0 - 25 Transaction reference number from external application. TX12345678 Mandatory
2 Approval Code String 1 – 6 Credit card authorization code, if transaction was approved. Otherwise empty string. Presence of non-zero length approval code string indicates successful authorization of transaction. This logic holds true for Pine 360 transactions as well. “5261AJ” Mandatory
3 Host Response String 0 – 50 Response string if a response for transaction was received from bank switch. Otherwise, if any error occurs before response is received, this is an empty string. “APPROVED” Mandatory
4 Card Number String 0 – 19 Card number is valid if card was swiped. Otherwise, empty string. “************2802” Mandatory
5 Expiration Date String 0 or 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. “XXXX” Mandatory
6 Cardholder’s Name String 0 – 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string “AMIT MOHAN” Mandatory
7 Card Type String 0 – 12 Card association name, if valid card was swiped. Otherwise, empty string “VISA” Mandatory
8 Invoice Number/EDC ROC(in case of Reward Transaction) Long Integer 0 - 6 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on charge slip) 78/101 Mandatory
9 Batch Number/EDC Batch ID(in case of Reward Transaction) Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction) Optional
10 Terminal ID String 0 or 8 EFT TID, if transaction authorized. Otherwise, empty string “30000001” Optional
11 Loyalty Points Awarded Long 0 - 8 RFU – not used. 0 Optional
12 Remark String 0 – 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization “Failed to dial modem” Optional
13 Transaction Acquirer Name String 0 – 48 Name of acquirer to which transaction was routed “ICICI BANK” Optional
14 Merchant ID String 0 – 15 EFT ME ID, if transaction authorized. Otherwise, empty string “000100090015607” Optional
15 Retrieval Reference Number String 0 – 12 EFT RRN, if transaction authorized. Otherwise, empty string “000000012843” Optional
16 Card Entry Mode Integer 0 - 5 Enumeration of possible values: 0 – Manual entry, 1 – Swipe entry, 2 – Chip card entry Any other value – card not validated 1 Optional
17 Print Cardholder's Name on receipt Integer 0 - 5 Enumeration of possible values: 0 – Do not print cardholder’s name, 1 – Print cardholder’s name Any other value – card not validated. This is used if external application is to print Plutus charge slip. 0 Optional
18 Merchant Name String 0 – 23 Merchant name, if transaction authorized. Otherwise, empty string “NOBLE MOTORS” Optional
19 Merchant Address String 0 – 23 Merchant address line, if transaction authorized. Otherwise, empty string “HAJI ALI” Optional
20 Merchant City String 0 – 23 Merchant city line, if transaction authorized. Otherwise, empty string “MUMBAI” Optional
21 Plutus Version String 0 – 40 Plutus version “v1.54 (for ICICI BANK)” Optional
22 Wallet Code Integer 0 – 999 Wallet Code for which transaction was processed. For Jio Money value will be 101. 101 Optional
24 Reward Redeemed Points Double 0 - 15 Redeemed Points “400.00” Optional
25 Reward Balance Amount String 0 - 10 Balance Amount “1000000” Optional
26 Reward Balance Points Double 0 - 15 Balance Point “40000.00” Optional
27 Charge slip print data in tag value format (Optional)* String Charge slip data in form of tag and value separated with : and new pair separated with |*(Only present if charge slip data on merchant is enabled) Charge slip print data in tag value format(Optional)* Optional
28 RFU1/Coupon code/Loyalty Card Number String 0 – 23 Card Processing Fee in Rs (decimal) Or Coupon Code. Coupon code is the value which will be coming as a response to voucher redemption. This field will be present in case of voucher redemption. Or Loyalty number fetched if the transaction type is 4301. “5.50” Optional
29 Amount processed successfully by Plutus/ Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 – 99 Amount will always be in paisa or lowest currency. “100000” Optional
32 Date of Transaction String 0 - 8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format. “02012011” Optional
33 Time of Transaction String 0 - 6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24hour format. “210403” Optional
34 PineLabs Client ID Integer 0 - 6 Unique ID assigned to Pine Labs EDC. 12345 Optional



Request

HEX String Format
ASCII Format
100009970019353130322C545831323334353637382C203130302C3130312CFF
— 5102,TX12345678, 100,101,ÿ

Response

HEX String Format
ASCII Format
999919970001010A22313233222C22303438363638222C22415050524F564544222C222A2A2A2A2A2A2A2A2A2A2A2A37363639222C2239383037222C22435553544F4D45522F4A494F204D4F4E4559222C202257414C4C4554222C22313038222C2239303232222C223130303031313430222C22222C22222C20224A494F204D4F4E4559222C22313030303031303030303030303938222C22303134383937303030353236222C2231222C2230222C22524C454E4F564F53746F7265222C22536563746F72203632222C224E4F494441222C2276312E302E30222C22313031222C22222C22222C22222C22222C22222C22222C22313030222C22222C22222C223131303532303135222C2231393338343822FF
™™— "123","048668","APPROVED","************7669","9807","CUSTOMER/JIO MONEY", "WALLET","108","9022","10001140","","", "JIO MONEY","100001000000098","014897000526","1","0","RLENOVOStore","Sector 62","NOIDA","v1.0.0","101","","","","","","","100","","","11052015","193848"ÿ

JSON Request:
 
       
    Coming Soon
     
    

JSON Response:
 
       
    
    Coming Soon
    
    

Wallet Load

Wallet load transaction is used to load/top-up the wallet money

Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer the Transaction Types. Range: 4001-4216 5103 Mandatory
2 Billing reference number String 0 – 25 Transaction reference number from external application. Plutus will only use this value for printing on charge slip. “TX12345678” Optional
3 Total EFT amount Long Integer 1 to 8 Amount to be charged to card – expressed as a whole number in lowest currency unit (ie. in paisa). Range: 1 – 99999999 999999 Mandatory
4 Wallet Program ID Integer 1-999 This ID will be assigned by Pine Labs to each wallet program type. While performing any Wallet transaction, this field needs to be set to identify wallet host. For Jio Money, this value will be 101. 101 Optional
5 Wallet Identifier Data(card/ mobile/barcode) String 1 – 76 Mobile/Barcode/Card Number. If not set, terminal will prompt to capture these values. For Jio Money, Barcode needs to be captured at Billing POS and sent in this field. Optional
6 Type of Wallet Input Identifier String 1 – 37 Type of Wallet identifier Contained in Field 4. Mobile Number – 01, Barcode – 02, Swipe - 03 1 Optional
8 Is Swipe entry String TRUE or FALSE By default, it is TRUE. TRUE Optional
10 Operator String 1 – 31 Operator Optional

Response Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Billing Reference Number String 0 - 25 Transaction reference number from external application. TX12345678 Mandatory
2 Approval Code String 1 – 6 Credit card authorization code, if transaction was approved. Otherwise empty string. Presence of non-zero length approval code string indicates successful authorization of transaction. This logic holds true for Pine 360 transactions as well. “5261AJ” Mandatory
3 Host Response String 0 – 50 Response string if a response for transaction was received from bank switch. Otherwise, if any error occurs before response is received, this is an empty string. “APPROVED” Mandatory
4 Card Number String 0 – 19 Card number is valid if card was swiped. Otherwise, empty string. “************2802” Mandatory
5 Expiration Date String 0 or 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. “XXXX” Mandatory
6 Cardholder’s Name String 0 – 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string “AMIT MOHAN” Mandatory
7 Card Type String 0 – 12 Card association name, if valid card was swiped. Otherwise, empty string “VISA” Mandatory
8 Invoice Number/EDC ROC(in case of Reward Transaction) Long Integer 0 - 6 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on charge slip) 78/101 Mandatory
9 Batch Number/EDC Batch ID(in case of Reward Transaction) Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction) Optional
10 Terminal ID String 0 or 8 EFT TID, if transaction authorized. Otherwise, empty string “30000001” Optional
11 Loyalty Points Awarded Long 0 - 8 RFU – not used. 0 Optional
12 Remark String 0 – 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization “Failed to dial modem” Optional
13 Transaction Acquirer Name String 0 – 48 Name of acquirer to which transaction was routed “ICICI BANK” Optional
14 Merchant ID String 0 – 15 EFT ME ID, if transaction authorized. Otherwise, empty string “000100090015607” Optional
15 Retrieval Reference Number String 0 – 12 EFT RRN, if transaction authorized. Otherwise, empty string “000000012843” Optional
16 Card Entry Mode Integer 0 - 5 Enumeration of possible values: 0 – Manual entry, 1 – Swipe entry, 2 – Chip card entry Any other value – card not validated 1 Optional
17 Print Cardholder's Name on receipt Integer 0 - 5 Enumeration of possible values: 0 – Do not print cardholder’s name, 1 – Print cardholder’s name Any other value – card not validated. This is used if external application is to print Plutus charge slip. 0 Optional
18 Merchant Name String 0 – 23 Merchant name, if transaction authorized. Otherwise, empty string “NOBLE MOTORS” Optional
19 Merchant Address String 0 – 23 Merchant address line, if transaction authorized. Otherwise, empty string “HAJI ALI” Optional
20 Merchant City String 0 – 23 Merchant city line, if transaction authorized. Otherwise, empty string “MUMBAI” Optional
21 Plutus Version String 0 – 40 Plutus version “v1.54 (for ICICI BANK)” Optional
22 Wallet Code Integer 0 – 999 Wallet Code for which transaction was processed. For Jio Money value will be 101. 101 Optional
24 Reward Redeemed Points Double 0 - 15 Redeemed Points “400.00” Optional
25 Reward Balance Amount String 0 - 10 Balance Amount “1000000” Optional
26 Reward Balance Points Double 0 - 15 Balance Point “40000.00” Optional
27 Charge slip print data in tag value format (Optional)* String Charge slip data in form of tag and value separated with : and new pair separated with |*(Only present if charge slip data on merchant is enabled) Charge slip print data in tag value format(Optional)* Optional
28 RFU1/Coupon code/Loyalty Card Number String 0 – 23 Card Processing Fee in Rs (decimal) Or Coupon Code. Coupon code is the value which will be coming as a response to voucher redemption. This field will be present in case of voucher redemption. Or Loyalty number fetched if the transaction type is 4301. “5.50” Optional
29 Amount processed successfully by Plutus/ Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 – 99 Amount will always be in paisa or lowest currency. “100000” Optional
32 Date of Transaction String 0 - 8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format. “02012011” Optional
33 Time of Transaction String 0 - 6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24hour format. “210403” Optional
34 PineLabs Client ID Integer 0 - 6 Unique ID assigned to Pine Labs EDC. 12345 Optional



Request

HEX String Format
ASCII Format
100009970019353130332C545831323334353637382C203130302C3130312CFF
— 5103,TX12345678, 100,101,ÿ

Response

HEX String Format
ASCII Format
999919970001010A22313233222C22303438363638222C22415050524F564544222C222A2A2A2A2A2A2A2A2A2A2A2A37363639222C2239383037222C22435553544F4D45522F4A494F204D4F4E4559222C202257414C4C4554222C22313038222C2239303232222C223130303031313430222C22222C22222C20224A494F204D4F4E4559222C22313030303031303030303030303938222C22303134383937303030353236222C2231222C2230222C22524C454E4F564F53746F7265222C22536563746F72203632222C224E4F494441222C2276312E302E30222C22313031222C22222C22222C22222C22222C22222C22222C22313030222C22222C22222C223131303532303135222C2231393338343822FF
™™— "123","048668","APPROVED","************7669","9807","CUSTOMER/JIO MONEY", "WALLET","108","9022","10001140","","", "JIO MONEY","100001000000098","014897000526","1","0","RLENOVOStore","Sector 62","NOIDA","v1.0.0","101","","","","","","","100","","","11052015","193848"ÿ

JSON Request:
 
       
    Coming Soon
     
    

JSON Response:
 
       
    
    Coming Soon
    
    

Wallet Void

The Wallet Void transaction is used to reverse a previously approved Wallet Sale transaction

Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer the Transaction Types. Range: 4001-4216 5104 Mandatory
2 Billing reference number String 0 – 25 Transaction reference number from external application. Plutus will only use this value for printing on charge slip. “TX12345678” Optional
3 Total EFT amount Long Integer 1 to 8 Amount to be charged to card – expressed as a whole number in lowest currency unit (ie. in paisa). Range: 1 – 99999999 999999 Mandatory
4 Wallet Program ID Integer 1-999 This ID will be assigned by Pine Labs to each wallet program type. While performing any Wallet transaction, this field needs to be set to identify wallet host. For Jio Money, this value will be 101. 101 Optional
5 Wallet Identifier Data(card/ mobile/barcode) String 1 – 76 Mobile/Barcode/Card Number. If not set, terminal will prompt to capture these values. For Jio Money, Barcode needs to be captured at Billing POS and sent in this field. Optional
6 Type of Wallet Input Identifier String 1 – 37 Type of Wallet identifier Contained in Field 4. Mobile Number – 01, Barcode – 02, Swipe - 03 1 Optional
8 Is Swipe entry String TRUE or FALSE By default, it is TRUE. TRUE Optional
10 Operator String 1 – 31 Operator Optional

Response Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Billing Reference Number String 0 - 25 Transaction reference number from external application. TX12345678 Mandatory
2 Approval Code String 1 – 6 Credit card authorization code, if transaction was approved. Otherwise empty string. Presence of non-zero length approval code string indicates successful authorization of transaction. This logic holds true for Pine 360 transactions as well. “5261AJ” Mandatory
3 Host Response String 0 – 50 Response string if a response for transaction was received from bank switch. Otherwise, if any error occurs before response is received, this is an empty string. “APPROVED” Mandatory
4 Card Number String 0 – 19 Card number is valid if card was swiped. Otherwise, empty string. “************2802” Mandatory
5 Expiration Date String 0 or 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. “XXXX” Mandatory
6 Cardholder’s Name String 0 – 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string “AMIT MOHAN” Mandatory
7 Card Type String 0 – 12 Card association name, if valid card was swiped. Otherwise, empty string “VISA” Mandatory
8 Invoice Number/EDC ROC(in case of Reward Transaction) Long Integer 0 - 6 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on charge slip) 78/101 Mandatory
9 Batch Number/EDC Batch ID(in case of Reward Transaction) Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction) Optional
10 Terminal ID String 0 or 8 EFT TID, if transaction authorized. Otherwise, empty string “30000001” Optional
11 Loyalty Points Awarded Long 0 - 8 RFU – not used. 0 Optional
12 Remark String 0 – 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization “Failed to dial modem” Optional
13 Transaction Acquirer Name String 0 – 48 Name of acquirer to which transaction was routed “ICICI BANK” Optional
14 Merchant ID String 0 – 15 EFT ME ID, if transaction authorized. Otherwise, empty string “000100090015607” Optional
15 Retrieval Reference Number String 0 – 12 EFT RRN, if transaction authorized. Otherwise, empty string “000000012843” Optional
16 Card Entry Mode Integer 0 - 5 Enumeration of possible values: 0 – Manual entry, 1 – Swipe entry, 2 – Chip card entry Any other value – card not validated 1 Optional
17 Print Cardholder's Name on receipt Integer 0 - 5 Enumeration of possible values: 0 – Do not print cardholder’s name, 1 – Print cardholder’s name Any other value – card not validated. This is used if external application is to print Plutus charge slip. 0 Optional
18 Merchant Name String 0 – 23 Merchant name, if transaction authorized. Otherwise, empty string “NOBLE MOTORS” Optional
19 Merchant Address String 0 – 23 Merchant address line, if transaction authorized. Otherwise, empty string “HAJI ALI” Optional
20 Merchant City String 0 – 23 Merchant city line, if transaction authorized. Otherwise, empty string “MUMBAI” Optional
21 Plutus Version String 0 – 40 Plutus version “v1.54 (for ICICI BANK)” Optional
22 Wallet Code Integer 0 – 999 Wallet Code for which transaction was processed. For Jio Money value will be 101. 101 Optional
24 Reward Redeemed Points Double 0 - 15 Redeemed Points “400.00” Optional
25 Reward Balance Amount String 0 - 10 Balance Amount “1000000” Optional
26 Reward Balance Points Double 0 - 15 Balance Point “40000.00” Optional
27 Charge slip print data in tag value format (Optional)* String Charge slip data in form of tag and value separated with : and new pair separated with |*(Only present if charge slip data on merchant is enabled) Charge slip print data in tag value format(Optional)* Optional
28 RFU1/Coupon code/Loyalty Card Number String 0 – 23 Card Processing Fee in Rs (decimal) Or Coupon Code. Coupon code is the value which will be coming as a response to voucher redemption. This field will be present in case of voucher redemption. Or Loyalty number fetched if the transaction type is 4301. “5.50” Optional
29 Amount processed successfully by Plutus/ Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 – 99 Amount will always be in paisa or lowest currency. “100000” Optional
32 Date of Transaction String 0 - 8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format. “02012011” Optional
33 Time of Transaction String 0 - 6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24hour format. “210403” Optional
34 PineLabs Client ID Integer 0 - 6 Unique ID assigned to Pine Labs EDC. 12345 Optional



Request

HEX String Format
ASCII Format
100009970029353130342C313234352C3130302C2C2C2C2C2C2C2C2C393032332C3131392C2C2C2C2C2C2C2C2C2C2CFF
— )5104,1245,100,,,,,,,,,9023,119,,,,,,,,,,,ÿ

Response

HEX String Format
ASCII Format
99991997000101E32231323435222C22303035343336222C2253554343455353222C222A2A2A2A2A2A36343030222C2220222C22222C22222C22323630222C2239313032222C2241424344313233343636222C22222C22222C2250484F4E45205045222C224D32333036313630343833323230363735353739313430222C22222C22222C2230222C22766172756E73746F7265222C226A6169707572222C224144494C41424144222C2276312E302E30222C22313035222C22222C22222C2022222C22222C22222C22222C2233393030222C22222C22222C223034313332303137222C2231343330303322FF
™™— ã"1245","005436","SUCCESS","******6400"," ","","","260","9102","ABCD123466","","","PHONE PE","M2306160483220675579140","","","0","varunstore","jaipur","ADILABAD","v1.0.0","105","","", "","","","","3900","","","04132017","143003"ÿ

JSON Request:
 
       
    Coming Soon
     
    

JSON Response:
 
       
    
    Coming Soon
    
    

Sodexo Sale

A transaction between two parties where the buyer receives goods (tangible or intangible),services and/or assets in exchange for sodexo coupons/Points

Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer to the table above Values: 5120, 5121, 5122, 5123 5106 Mandatory
2 Billing ReferenceNumber String 0 - 25 Transaction reference number from external application. Plutus will use this value for only printing on chargeslip only. “TX12345678” Optional
3 Total EFT amount Long Integer 1 – 99999999 Amount to be charged to card – expressed as a whole number in lowest currency unit (i.e., in paisa) 999999 Mandatory
4 UPI/BHARAT QR Program ID Integer 1-999 This Id will be assigned by PineLabs to each UPI/BHARAT QR program types. While performing any UPI/BHARAT QR transaction, this field needs to be set to identify UPI/BHARAT QR host. Mandatory
5 UPI/BHARAT QR Identifier Data String 1 – 76 Optional
6 Track 2 data / Expiry date String 1 – 37 Track2 data of the card or expiry date if manual entry. If empty then Plutus will ask for card input. Expiry date is in YYMM format. In case of Pine 360 if Track1 consists of GV or mobile number, this field will indicate the card entry mode. (NA for Sodexo) Optional
7 Invoice number Long integer 1 – 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the invoice number of parent transaction. Mandatory
8 Is Swipe entry String TRUE or FALSE By default it is TRUE TRUE (NA for Sodexo) Mandatory
9 Terminal ID String 1 – 8 RFU (NA for Sodexo) Optional
10 Operator String 1-31 Operator (NA for Sodexo) Optional
11 RFU2 String RFU (NA for Sodexo) Optional
12 EDC Batch ID Integer ID 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the batch id of parent transaction. Optional
13 EDC ROC Integer 101-999 If independent transaction, then it is not required. Else in case of dependent transaction, it is the ROC of parent transaction. 201 Optional
14 Transaction log ID Long integer If independent transaction, then it is not required. Else in case of dependent transaction, it is the transaction log of parent transaction. Range: 1-184467440737 123234 (NA for Sodexo) Optional
15 Reward\Cash amount Long Integer Amount to be paid by reward points or in cash in paise (or in lowest currency). Range: 1 – 99999999 999999 (NA for Sodexo) Mandatory
16 Customer Mobile number String 1 – 100 Customer mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 (NA for Sodexo) Mandatory
17 Customer email id(s) String 1 – 500 Customer email id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com (NA for Sodexo) Mandatory
18 Merchant Mobile Number(s) String 1 – 100 Merchant mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 (NA for Sodexo) Mandatory
19 Merchant email id(s) String 1 – 500 Merchant email id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com (NA for Sodexo) Mandatory
20 Consent to send charge slip on customer mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from the customer for sending charge slip on his/her mobile number(s). TRUE (NA for Sodexo) Mandatory
21 Consent to send charge slip on customer email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant TRUE (NA for Sodexo) Mandatory
22 Consent to send charge slip on merchant mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from the customer for sending charge slip on his/her mobile number(s). TRUE (NA for Sodexo) Mandatory
23 Consent to send charge slip on merchant mobile email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from the customer for sending charge slip on his/her email id(s). TRUE (NA for Sodexo) Mandatory
24 Wallet Program ID Integer 3 This ID will be assigned by Pine labs to each wallet program type. While performing any Wallet transaction, this field needs to be set to identify wallet host. Range: 1-999 3 (NA for Sodexo) Mandatory

Response Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Billing Reference Number String 0 - 25 Transaction reference number from external application. Plutus will use this value for only printing on chargeslip only. TX12345678 Mandatory
2 Approval Code String 1 – 6 Credit card authorization code, if transaction was approved. Otherwise empty string. Presence of non-zero length approval code string indicates successful authorization of transaction. This logic holds true for Pine 360 transactions as well. 5261AJ Mandatory
3 Host Response String 0 – 50 Response string if a response for transaction was received from bank switch. Otherwise, if any error occurs before response is received, this is an empty string. APPROVED Mandatory
4 Card Number String 0 – 19 Card number is valid if card was swiped. Otherwise, empty string. ************2802 Mandatory
5 Expiration Date String 0 or 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. XXXX Mandatory
6 Cardholder’s Name String 0 – 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string. AMIT MOHAN Mandatory
7 Card Type String 0 – 12 Card association name, if valid card was swiped. Otherwise, empty string. VISA Mandatory
8 Invoice Number/EDC ROC(in case of Reward Transaction) Long Integer 0 - 6 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on charge slip) 78/101 Mandatory
9 Batch Number/EDC Batch ID(in case of Reward Transaction) Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction) Mandatory
10 Terminal ID String 0 or 8 EFT TID, if transaction authorized. Otherwise, empty string 30000001 Mandatory
11 Loyalty Points Awarded Long 0 - 8 RFU – not used. Range: 0 – 99999999 0 Mandatory
12 Remark String 0 – 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization Failed to dial modem Mandatory
13 Transaction Acquirer Name String 0 – 48 Name of acquirer to which transaction was routed ICICI BANK Mandatory
14 Merchant ID String 0 – 15 EFT ME ID, if transaction authorized. Otherwise, empty string 000100090015607 Mandatory
15 Retrieval Reference Number String 0 – 12 EFT RRN, if transaction authorized. Otherwise, empty string 000000012843 Mandatory
16 Card Entry Mode Integer 0 - 5 Enumeration of possible values: 0 – Manual entry 1 – Swipe entry 2 – Chip card entry Any other value – card not validated Range: 0 – 32767 1 Mandatory
17 Print Cardholder's Name on receipt Integer 0 - 5 Enumeration of possible values: 0 – Do not print cardholder’s name 1 – Print cardholder’s name Any other value – card not validated. This is used if external application is to print Plutus charge slip. Range: 0 – 32767 0 Mandatory
18 Merchant Name String 0 – 23 Merchant name, if transaction authorized. Otherwise, empty string NOBLE MOTORS Mandatory
19 Merchant Address String 0 – 23 Merchant address line, if transaction authorized. Otherwise, empty string HAJI ALI Mandatory
20 Merchant City String 0 – 23 Merchant city line, if transaction authorized. Otherwise, empty string MUMBAI Mandatory
21 Plutus Version String 0 – 40 Plutus version v1.54 (for ICICI BANK) Mandatory
22 Acquiring Bank Code Integer 0 - 999 Code for bank used for processing transaction. Enumeration of possible values:
01 – HDFC BANK
02 – ICICI BANK
03 – AMERICAN EXPRESS
04 – CITIBANK
05 – AXIS BANK
06 – SBI
07 – HSBC
09 – CORP BANK
10 – CUB (City Union Bank)
14 – IDBI Bank
17 – LVB (Lakshmi Vilas Bank)
51- PINE 360
301-Sodexo
81 – Loyalty Reward
82 – Aimia
85 – SBI Rewards
Mandatory
23 Reward Redeemed Amount Long Integer 0 - 10 Redeemed Amount in Paisa or in lowest currency. 10000 Mandatory
24 Reward Redeemed Points Double 0 - 15 Redeemed Points 400.00 Mandatory
25 Reward Balance Amount String 0 - 10 Balance Amount 1000000 Mandatory
26 Reward Balance Points Double 0 - 15 Balance Point 40000.00 Mandatory
27 Charge slip print data in tag value format (Optional)* String Charge slip data in form of tag and value separated with : and new pair separated with |*(Only present if charge slip data on merchant is enabled) Charge slip print data in tag value format(Optional)* Mandatory
28 RFU1/Coupon code/Loyalty Card Number String 0 – 23 Card Processing Fee in Rs (decimal) Or Coupon Code. Coupon code is the value which will be coming as a response to voucher redemption. This field will be present in case of voucher redemption. Or Loyalty number fetched if the transaction type is 4301. 5.50 Mandatory
29 Amount processed successfully by Plutus/ Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 – 99 Amount will always be in paisa or lowest currency. 100000 Mandatory
30 RFU3 String 0 – 23 Reserved for future use Mandatory
31 RFU String Specific for merchant Alhanumeric Optional
32 Date of Transaction String 0 - 8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format. 02012011 Mandatory
33 Time of Transaction String 0 - 6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24hour format. 210403 Mandatory
34 PineLabs Client ID Integer 0 - 6 Unique ID assigned to Pine Labs EDC. 12345 Mandatory


Request

HEX String Format
ASCII Format
10000997002A353130362C543030303135303130303030303333322C3130302C2C2C2C2C2C2C2C2C2C2C2C2C2C2C2C2CFF
— *5106,T000150100000332,100,,,,,,,,,,,,,,,,,ÿ

Response

HEX String Format
ASCII Format
99991997000101002254303030313530313030303030333332222C22313236393336222C22415050524F564544222C222A2A2A2A2A2A2A2A2A2A2A2A30303635222C2258585858222C22222C22222C22313031222C2239313237222C223730303030313136222C2230222C22415050524F564544222C22534F4445584F222C2232333431222C22313630313131303030303639222C2231222C2231222C2254657374537420726556696E6974222C226D617975722076696861722033222C224D4545525554222C22762E30312E30302E3030222C22333031222C22222C22222C22222C22222C22222C22222C22222C22222C22222C223037303132303136222C2231313132313822FF
™™—  "T000150100000332","126936","APPROVED","************0065","XXXX","","","101","9127","70000116","0","APPROVED","SODEXO","2341","160111000069","1","1","TestSt reVinit","mayur vihar 3","MEERUT","v.01.00.00","301","","","","","","","","","","07012016","111218"ÿ

JSON Request:
 
  
Coming Soon


JSON Response:
 
  

Coming Soon



Sodexo Void

The Sodexo Void transaction is used to reverse a previously approved Sodexo sale transaction

Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer to the table above Values: 5120, 5121, 5122, 5123 5107 Mandatory
2 Billing ReferenceNumber String 0 - 25 Transaction reference number from external application. Plutus will use this value for only printing on chargeslip only. “TX12345678” Optional
3 Total EFT amount Long Integer 1 – 99999999 Amount to be charged to card – expressed as a whole number in lowest currency unit (i.e., in paisa) 999999 Mandatory
4 UPI/BHARAT QR Program ID Integer 1-999 This Id will be assigned by PineLabs to each UPI/BHARAT QR program types. While performing any UPI/BHARAT QR transaction, this field needs to be set to identify UPI/BHARAT QR host. Mandatory
5 UPI/BHARAT QR Identifier Data String 1 – 76 Optional
6 Track 2 data / Expiry date String 1 – 37 Track2 data of the card or expiry date if manual entry. If empty then Plutus will ask for card input. Expiry date is in YYMM format. In case of Pine 360 if Track1 consists of GV or mobile number, this field will indicate the card entry mode. (NA for Sodexo) Optional
7 Invoice number Long integer 1 – 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the invoice number of parent transaction. Mandatory
8 Is Swipe entry String TRUE or FALSE By default it is TRUE TRUE (NA for Sodexo) Mandatory
9 Terminal ID String 1 – 8 RFU (NA for Sodexo) Optional
10 Operator String 1-31 Operator (NA for Sodexo) Optional
11 RFU2 String RFU (NA for Sodexo) Optional
12 EDC Batch ID Integer ID 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the batch id of parent transaction. Optional
13 EDC ROC Integer 101-999 If independent transaction, then it is not required. Else in case of dependent transaction, it is the ROC of parent transaction. 201 Optional
14 Transaction log ID Long integer If independent transaction, then it is not required. Else in case of dependent transaction, it is the transaction log of parent transaction. Range: 1-184467440737 123234 (NA for Sodexo) Optional
15 Reward\Cash amount Long Integer Amount to be paid by reward points or in cash in paise (or in lowest currency). Range: 1 – 99999999 999999 (NA for Sodexo) Mandatory
16 Customer Mobile number String 1 – 100 Customer mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 (NA for Sodexo) Mandatory
17 Customer email id(s) String 1 – 500 Customer email id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com (NA for Sodexo) Mandatory
18 Merchant Mobile Number(s) String 1 – 100 Merchant mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 (NA for Sodexo) Mandatory
19 Merchant email id(s) String 1 – 500 Merchant email id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com (NA for Sodexo) Mandatory
20 Consent to send charge slip on customer mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from the customer for sending charge slip on his/her mobile number(s). TRUE (NA for Sodexo) Mandatory
21 Consent to send charge slip on customer email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant TRUE (NA for Sodexo) Mandatory
22 Consent to send charge slip on merchant mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from the customer for sending charge slip on his/her mobile number(s). TRUE (NA for Sodexo) Mandatory
23 Consent to send charge slip on merchant mobile email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from the customer for sending charge slip on his/her email id(s). TRUE (NA for Sodexo) Mandatory
24 Wallet Program ID Integer 3 This ID will be assigned by Pine labs to each wallet program type. While performing any Wallet transaction, this field needs to be set to identify wallet host. Range: 1-999 3 (NA for Sodexo) Mandatory

Response Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Billing Reference Number String 0 - 25 Transaction reference number from external application. Plutus will use this value for only printing on chargeslip only. TX12345678 Mandatory
2 Approval Code String 1 – 6 Credit card authorization code, if transaction was approved. Otherwise empty string. Presence of non-zero length approval code string indicates successful authorization of transaction. This logic holds true for Pine 360 transactions as well. 5261AJ Mandatory
3 Host Response String 0 – 50 Response string if a response for transaction was received from bank switch. Otherwise, if any error occurs before response is received, this is an empty string. APPROVED Mandatory
4 Card Number String 0 – 19 Card number is valid if card was swiped. Otherwise, empty string. ************2802 Mandatory
5 Expiration Date String 0 or 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. XXXX Mandatory
6 Cardholder’s Name String 0 – 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string. AMIT MOHAN Mandatory
7 Card Type String 0 – 12 Card association name, if valid card was swiped. Otherwise, empty string. VISA Mandatory
8 Invoice Number/EDC ROC(in case of Reward Transaction) Long Integer 0 - 6 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on charge slip) 78/101 Mandatory
9 Batch Number/EDC Batch ID(in case of Reward Transaction) Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction) Mandatory
10 Terminal ID String 0 or 8 EFT TID, if transaction authorized. Otherwise, empty string 30000001 Mandatory
11 Loyalty Points Awarded Long 0 - 8 RFU – not used. Range: 0 – 99999999 0 Mandatory
12 Remark String 0 – 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization Failed to dial modem Mandatory
13 Transaction Acquirer Name String 0 – 48 Name of acquirer to which transaction was routed ICICI BANK Mandatory
14 Merchant ID String 0 – 15 EFT ME ID, if transaction authorized. Otherwise, empty string 000100090015607 Mandatory
15 Retrieval Reference Number String 0 – 12 EFT RRN, if transaction authorized. Otherwise, empty string 000000012843 Mandatory
16 Card Entry Mode Integer 0 - 5 Enumeration of possible values: 0 – Manual entry 1 – Swipe entry 2 – Chip card entry Any other value – card not validated Range: 0 – 32767 1 Mandatory
17 Print Cardholder's Name on receipt Integer 0 - 5 Enumeration of possible values: 0 – Do not print cardholder’s name 1 – Print cardholder’s name Any other value – card not validated. This is used if external application is to print Plutus charge slip. Range: 0 – 32767 0 Mandatory
18 Merchant Name String 0 – 23 Merchant name, if transaction authorized. Otherwise, empty string NOBLE MOTORS Mandatory
19 Merchant Address String 0 – 23 Merchant address line, if transaction authorized. Otherwise, empty string HAJI ALI Mandatory
20 Merchant City String 0 – 23 Merchant city line, if transaction authorized. Otherwise, empty string MUMBAI Mandatory
21 Plutus Version String 0 – 40 Plutus version v1.54 (for ICICI BANK) Mandatory
22 Acquiring Bank Code Integer 0 - 999 Code for bank used for processing transaction. Enumeration of possible values:
01 – HDFC BANK
02 – ICICI BANK
03 – AMERICAN EXPRESS
04 – CITIBANK
05 – AXIS BANK
06 – SBI
07 – HSBC
09 – CORP BANK
10 – CUB (City Union Bank)
14 – IDBI Bank
17 – LVB (Lakshmi Vilas Bank)
51- PINE 360
301-Sodexo
81 – Loyalty Reward
82 – Aimia
85 – SBI Rewards
Mandatory
23 Reward Redeemed Amount Long Integer 0 - 10 Redeemed Amount in Paisa or in lowest currency. 10000 Mandatory
24 Reward Redeemed Points Double 0 - 15 Redeemed Points 400.00 Mandatory
25 Reward Balance Amount String 0 - 10 Balance Amount 1000000 Mandatory
26 Reward Balance Points Double 0 - 15 Balance Point 40000.00 Mandatory
27 Charge slip print data in tag value format (Optional)* String Charge slip data in form of tag and value separated with : and new pair separated with |*(Only present if charge slip data on merchant is enabled) Charge slip print data in tag value format(Optional)* Mandatory
28 RFU1/Coupon code/Loyalty Card Number String 0 – 23 Card Processing Fee in Rs (decimal) Or Coupon Code. Coupon code is the value which will be coming as a response to voucher redemption. This field will be present in case of voucher redemption. Or Loyalty number fetched if the transaction type is 4301. 5.50 Mandatory
29 Amount processed successfully by Plutus/ Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 – 99 Amount will always be in paisa or lowest currency. 100000 Mandatory
30 RFU3 String 0 – 23 Reserved for future use Mandatory
31 RFU String Specific for merchant Alhanumeric Optional
32 Date of Transaction String 0 - 8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format. 02012011 Mandatory
33 Time of Transaction String 0 - 6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24hour format. 210403 Mandatory
34 PineLabs Client ID Integer 0 - 6 Unique ID assigned to Pine Labs EDC. 12345 Mandatory


Request

HEX String Format
ASCII Format
100009970032353130372C543030303135303130303030303333342C333036302C2C2C2C2C2C2C2C2C393030312C3130312C2C2C2C2C2C2CFF
 — 25107,T000150100000334,3060,,,,,,,,,9001,101,,,,,,,ÿ

Response

HEX String Format
ASCII Format
99991997000101002254303030313530313030303030333334222C22313230303038222C22415050524F564544222C222A2A2A2A2A2A2A2A2A2A2A2A30303635222C2258585858222C22222C22222C22313035222C2239313237222C223730303030313136222C2230222C22415050524F564544222C22534F4445584F222C2232333431222C22313630313131303030303731222C2231222C2231222C225465737453746F726556696E6974222C226D617975722076696861722033222C224D4545525554222C22762E30312E30302E3030222C22333031222C22222C22222C22222C22222C22222C22222C22222C22222C22222C223037303132303136222C2231313239333022FF
™™—  "T000150100000334","120008","APPROVED","************0065","XXXX","","","105","9127","70000116","0","APPROVED","SODEXO","2341","160111000071","1","1","TestStoreVinit","mayur vihar 3","MEERUT","v.01.00.00","301","","","","","","","","","","07012016","112930"ÿ

JSON Request:
 
  
Coming Soon


JSON Response:
 
  

Coming Soon



Sale With/Without Instant Discount

Earlier, when we take payment with the card which is not eligible for instant discount then the device displayed the message as “Instant discount not applicable. Initiate Normal Sale” and the transaction was not completed.
So, new transaction type has been included to complete the Sale transaction irrespective of whether instant discount is applicable or not.



Request

HEX String Format
ASCII Format
10000997002A343630332C546573743132332C3330303030302C2C2C2C2C2C2C2C2C2C2C2C2C3130312C2C2C2C2C2C2CFF
— *4603,Test123,300000,,,,,,,,,,,,,101,,,,,,,ÿ

Response - When Dicount Applicable

HEX String Format
ASCII Format
99991997000101582254657374313233222C223030222C22415050524F564544222C222A2A2A2A2A2A2A2A2A2A2A2A34393736222C2258585858222C2254455354204D45200D0A464F555254594E494E45222C224D41455354524F222C37392C31362C223536353637353638222C302C2250524F434553534544222C22484446432042414E4B222C222020202020202020202020202020200D0A222C22303030303030303030303230222C322C312C224C4F564520434F4D4D554E49434154494F4E222C224A414E412050555249222C224E45572044454C48492020202044454C20202020202020222C22506C757475732076312E34392E33200D0A4D5420484446432042414E4B222C30312C22222C22222C22222C22222C22222C223130317C3330303030307C3236303030307C34303030307C4943494349200D0A4465626974222C22222C22222C22222C223039303932303230222C2231343239303422FF
™™— X"Test123","00","APPROVED","************4976","XXXX","TEST ME FOURTYNINE","MAESTRO",79,16,"56567568",0,"PROCESSED","HDFC BANK"," ","000000000020",2,1,"LOVE COMMUNICATION","JANA PURI","NEW DELHI DEL ","Plutus v1.49.3 MT HDFC BANK",01,"","","","","","101|300000|260000|40000|ICICI Debit","","","","09092020","142904"ÿ

Response - When Dicount Not Applicable

HEX String Format
ASCII Format
999919970001013B2254657374313233222C223030222C22415050524F564544222C222A2A2A2A2A2A2A2A2A2A2A2A34363336222C2258585858222C22554441592043484F50524120202020202020202020202020200D0A2F222C224D41455354524F222C38382C31362C223536353637353638222C302C2250524F434553534544222C22484446432042414E4B222C22202020202020202020202020202020222C22303030303030303030303230222C322C312C224C4F5645200D0A434F4D4D554E49434154494F4E222C224A414E412050555249222C224E45572044454C48492020202044454C20202020202020222C22506C757475732076312E34392E33204D542048444643200D0A42414E4B222C30312C22222C22222C22222C22222C22222C22222C22222C22222C22222C223039303932303230222C2231363039313622FF
™™— ;"Test123","00","APPROVED","************4636","XXXX","UDAY CHOPRA /","MAESTRO",88,16,"56567568",0,"PROCESSED","HDFC BANK"," ","000000000020",2,1,"LOVE COMMUNICATION","JANA PURI","NEW DELHI DEL ","Plutus v1.49.3 MT HDFC BANK",01,"","","","","","","","","","09092020","160916"ÿ

JSON Request:
 
     
  Coming Soon
   
  

JSON Response:
 
     
  
  Coming Soon
  
  

QC Redemption

A transaction between two parties where the buyer receives goods (tangible or intangible),services and/or assets in exchange for customer Loyalty Points

Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer the Transaction Types
Range: 4001-4216
4205 Mandatory
2 Billing reference number String 0 – 25 Transaction reference number from external “TX12345678” Optional
3 Total EFT Amount Long Integer 0 - 8 Amount to be charged to card – expressed as a whole number in lowest currency unit (ie. in paisa)
Range: 1-99999999
999999 Mandatory
4 Bank Code String 1 – 2 The bank code to which transaction will be routed 1 Optional
5 Track 1 data/Card PAN Number String 1 – 76 Track1 data of the card or Card number if manual entry. If empty then Plutus will ask for card input. Optional
6 Track 2 data / Expiry date String 1 – 37 "Track2 data of the card or Expiry date if manual entry. If empty then Plutus will ask for card input. Expiry date is in YYMM format. In case of Pine 360, if Track 1 consists of mobile or GV number, this field will indicate the card entry mode. Mobile Number – 01 Barcode – 02 Manual - 03" Optional
7 Invoice Number Long Integer 1 – 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Invoice number of parent transition. 12 Optional
8 Is Swipe entry String TRUE or FALSE By default it is TRUE. TRUE Optional
9 Terminal ID String 1-8 Reserved for future use Optional
10 Operator String 1-31 Reserved for future use Optional
11 RFU2 String Reserved for future use Optional
12 EDC Batch ID Integer 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Batch Id of parent transition. Optional
13 EDC ROC Integer 3 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Roc of parent transition.
Range: 101-999
201 Optional
14 Transaction log ID Long Integer 1 - 12 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Transaction log of parent transition.
Range: 1-184467440737
123234 Optional
15 Reward\Cash amount Long Integer 1 – 8 Amount to be paid by reward points or in cash in paise (or in lowest currency)
Range: 1 – 99999999
999999 Optional
16 Customer Mobile Number String 1 – 100 Customer mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
17 Customer email id(s) String 1 – 500 Customer email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
18 Merchant mobile number(s) String 1 – 100 Merchant mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
19 Merchant email id(s) String 1 – 500 Merchant email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
20 Consent to send charge slip on customer mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her mobile number(s). TRUE Optional
21 Consent to send charge slip on customer email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her email id(s). TRUE Optional
22 Consent to send charge slip on merchant mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her mobile number. TRUE Optional
23 Consent to send charge slip on merchant email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her email id(s). TRUE Optional

Response Parameters

Position in CSV Field Name Data Type Length Description Sample
Value
Mandatory/
Optional
1 Billing Reference Number String 0 - 25 Transaction reference number from external application. TX12345678 Mandatory
2 Approval Code String 1 - 6 Credit card authorization code, if transaction was approved. Otherwise empty string. Presence of non-zero length approval code string indicates successful authorization of transaction. This logic holds true for Pine 360 transactions as well. “5261AJ” Mandatory
3 Host Response String 0 - 50 Response string if a response for transaction was received from bank switch. Otherwise, if any error occurs before response is received, this is an empty string. “APPROVED” Mandatory
4 Card Number String 0 - 19 Card number is valid if card was swiped. Otherwise, empty string. “************2802” Mandatory
5 Expiration Date String 0 or 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. “XXXX” Mandatory
6 Cardholder’s Name String 0 - 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string. “AMIT MOHAN” Mandatory
7 Card Type String 0 - 12 Card association name, if valid card was swiped. Otherwise, empty string. “VISA” Mandatory
8 Invoice Number/EDC ROC (in case of Reward Transaction) Long Integer 0 - 6 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on charge slip). Range 0 - 999999 / 101 - 999 (in case of Reward Transaction) 78/101 Mandatory
9 Batch Number/EDC Batch ID (in case of Reward Transaction) Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction). Mandatory
10 Terminal ID String 0 or 8 EFT TID, if transaction authorized. Otherwise, empty string. “30000001” Mandatory
11 Loyalty Points Awarded Long 0 - 8 RFU – not used.
Range: 0 – 99999999
0 Mandatory
12 Remark String 0 - 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization. “Failed to dial modem” Mandatory
13 Transaction Acquirer Name String 0 - 48 Name of acquirer to which transaction was routed. “ICICI BANK” Mandatory
14 Merchant ID String 0 - 15 EFT ME ID, if transaction authorized. Otherwise, empty string. “000100090015607” Mandatory
15 Retrieval Reference Number String 0 - 12 EFT RRN, if transaction authorized. Otherwise, empty string. “000000012843” Mandatory
16 Card Entry Mode Integer 0 - 5 Enumeration of possible values: 0 – Manual entry 1 – Swipe entry 2 – Chip card entry Any other value – card not validated
Range: 0 – 32767
1 Mandatory
17 Print Cardholder's Name on receipt Integer 0 - 5 Enumeration of possible values: 0 – Do not print cardholder’s name 1 – Print cardholder’s name Any other value – card not validated. This is used if external application is to print Plutus charge slip.
Range: 0 – 32767
0 Mandatory
18 Merchant Name String 0 - 23 Merchant name, if transaction authorized. Otherwise, empty string. “NOBLE MOTORS” Mandatory
19 Merchant Address String 0 - 23 Merchant address line, if transaction authorized. Otherwise, empty string. “HAJI ALI” Mandatory
20 Merchant City String 0 - 23 Merchant city line, if transaction authorized. Otherwise, empty string. “MUMBAI” Mandatory
21 Plutus Version String 0 - 40 Plutus version. “v1.54 (for ICICI BANK)” Mandatory
22 Acquiring Bank Code Integer 0 - 999 Code for bank used for processing transaction. Enumeration of possible values: 01 – HDFC BANK, 02 – ICICI BANK, 03 – AMERICAN EXPRESS, 04 – CITIBANK, 05 – AXIS BANK, 06 – SBI, 07 – HSBC, 09 – CORP BANK, 10 – CUB (City Union Bank), 14 – IDBI Bank, 17 – LVB (Lakshmi Vilas Bank), 51 - PINE 360, 301 - Sodexo, 81 – Loyalty Reward, 82 – Aimia, 85 – SBI Rewards Mandatory
23 Reward Redeemed Amount Long Integer 0 - 10 Redeemed Amount in Paisa or in lowest currency. “10000” Optional
24 Reward Redeemed Points Double 0 - 15 Redeemed Points. “400.00” Optional
25 Reward Balance Amount String 0 - 10 Balance Amount. “1000000” Optional
26 Reward Balance Points Double 0 - 15 Balance Point. “40000.00” Optional
27 Charge slip print data in tag value format (Optional)* String Charge slip data in form of tag and value separated with : and new pair separated with |*(Only present if charge slip data on merchant is enabled) Charge slip print data in tag value format(Optional)* Mandatory
28 RFU1/Coupon code/Loyalty Card Number String 0 - 23 Card Processing Fee in Rs (decimal) Or Coupon Code. Coupon code is the value which will be coming as a response to voucher redemption. This field will be present in case of voucher redemption. Or Loyalty number fetched if the transaction type is 4301. “5.50” Mandatory
29 Amount processed successfully by Plutus/ Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 - 99 Amount will always be in paisa or lowest currency. “100000” Mandatory
30 RFU3 String 0 - 23 Reserved for future use Mandatory
31 RFU String Specific for merchant Alhanumeric Optional
32 Date of Transaction String 0 - 8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format. “02012011” Mandatory
33 Time of Transaction String 0 - 6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24-hour format. “210403” Mandatory
34 PineLabs Client ID Integer 0 - 6 Unique ID assigned to Pine Labs EDC. 12345 Mandatory

This transaction has been included to accept QC Gift Card on Pine Labs terminal.


Request

HEX String Format
ASCII Format
10000997002C343230352C54584E31323334352C31303030302C2C2C2C2C2C2C2C2C2C2C2C2C2C2C2C2C2C2C2C2C2C2C2C2CFF
— ,4205,TXN12345,10000,,,,,,,,,,,,,,,,,,,,,,,,,ÿ

Response - With Card Number

HEX String Format
ASCII Format
99991997000100E32254584E3132333435222C223233363434333330222C22415050524F564544222C222A2A2A2A2A2A2A2A2A2A2A2A32393138222C22222C22222C22222C2231222C223932222C2235303338313839222C22222C2253756363657373222C22500D0A494E4520333630222C22363839222C22303030303035393432333131222C22222C2231222C22222C22222C22222C22506C757475732076312E302E302050494E45200D0A333630222C35312C22222C22222C22222C22222C22222C22222C22222C223233363434333330222C22222C223039303432303230222C2231333133343422FF
™™— 㢔XN12345","23644330","APPROVED","************2918","","","","1","92","5038189","","Success","P INE 360","689","000005942311","","1","","","","Plutus v1.0.0 PINE 360",51,"","","","","","","","23644330","","09042020","131344"ÿ

Response - With Card Swipe

HEX String Format
ASCII Format
999919970001011A2254584E3132333435222C223233363431333737222C22415050524F564544222C2239393939393939393939393332393138222C22222C222A2A2A2A2A2A2A2A2A2A2A2A32393138222C22222C2231222C223931222C22353033380D0A313839222C22222C2253756363657373222C2250494E4520333630222C22363839222C22303030303035393432333034222C22222C2231222C22222C22222C22222C22506C757475732076312E302E302050494E45200D0A333630222C35312C22222C22222C22222C22222C22222C2235327C3B393939393939393939393933323931383D3030303039393930393638343335353F7C222C22222C223233363431333737222C22222C223039303432303230222C223132203032303122FF
™™— "TXN12345","23641377","APPROVED","9999999999932918","","************2918","","1","91","5038 189","","Success","PINE 360","689","000005942304","","1","","","","Plutus v1.0.0 PINE 360",51,"","","","","","52|;9999999999932918=000099909684355?|","","23641377","","09042020","12 0201"ÿ

JSON Request:
 
    
Coming Soon
  

JSON Response:
 
    

Coming Soon



HDFC Flexipay - POS (Pay Later)

HDFC Flexipay POS is a new payment mode under Pine Labs BNPL offering in which customers will get options to choose 15,30,60 and 90 days tenure. HDFC bank’s Debit card customer can avail this facility and pay the amount with interest based on their convenient tenure. In this feature, HDFC Flexipay offers 15 days No Cost Interest to their customers.

Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer the Transaction Types
Range: 4001-4216
5030 Mandatory
2 Billing reference number String 0 – 25 Transaction reference number from external “TX12345678” Optional
3 Total EFT Amount Long Integer 0 - 8 Amount to be charged to card – expressed as a whole number in lowest currency unit (ie. in paisa)
Range: 1-99999999
999999 Mandatory
4 Bank Code String 1 – 2 The bank code to which transaction will be routed 1 Optional
5 Track 1 data/Card PAN Number String 1 – 76 Track1 data of the card or Card number if manual entry. If empty then Plutus will ask for card input. Optional
6 Track 2 data / Expiry date String 1 – 37 "Track2 data of the card or Expiry date if manual entry. If empty then Plutus will ask for card input. Expiry date is in YYMM format. In case of Pine 360, if Track 1 consists of mobile or GV number, this field will indicate the card entry mode. Mobile Number – 01 Barcode – 02 Manual - 03" Optional
7 Invoice Number Long Integer 1 – 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Invoice number of parent transition. 12 Optional
8 Is Swipe entry String TRUE or FALSE By default it is TRUE. TRUE Optional
9 Terminal ID String 1-8 Reserved for future use Optional
10 Operator String 1-31 Reserved for future use Optional
11 RFU2 String Reserved for future use Optional
12 EDC Batch ID Integer 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Batch Id of parent transition. Optional
13 EDC ROC Integer 3 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Roc of parent transition.
Range: 101-999
201 Optional
14 Transaction log ID Long Integer 1 - 12 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Transaction log of parent transition.
Range: 1-184467440737
123234 Optional
15 Reward\Cash amount Long Integer 1 – 8 Amount to be paid by reward points or in cash in paise (or in lowest currency)
Range: 1 – 99999999
999999 Optional
16 Customer Mobile Number String 1 – 100 Customer mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
17 Customer email id(s) String 1 – 500 Customer email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
18 Merchant mobile number(s) String 1 – 100 Merchant mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
19 Merchant email id(s) String 1 – 500 Merchant email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
20 Consent to send charge slip on customer mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her mobile number(s). TRUE Optional
21 Consent to send charge slip on customer email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her email id(s). TRUE Optional
22 Consent to send charge slip on merchant mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her mobile number. TRUE Optional
23 Consent to send charge slip on merchant email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her email id(s). TRUE Optional

Response Parameters

Position in CSV Field Name Data Type Length Description Sample
Value
Mandatory/
Optional
1 Billing Reference Number String 0 - 25 Transaction reference number from external application. TX12345678 Mandatory
2 Approval Code String 1 - 6 Credit card authorization code, if transaction was approved. Otherwise empty string. Presence of non-zero length approval code string indicates successful authorization of transaction. This logic holds true for Pine 360 transactions as well. “5261AJ” Mandatory
3 Host Response String 0 - 50 Response string if a response for transaction was received from bank switch. Otherwise, if any error occurs before response is received, this is an empty string. “APPROVED” Mandatory
4 Card Number String 0 - 19 Card number is valid if card was swiped. Otherwise, empty string. “************2802” Mandatory
5 Expiration Date String 0 or 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. “XXXX” Mandatory
6 Cardholder’s Name String 0 - 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string. “AMIT MOHAN” Mandatory
7 Card Type String 0 - 12 Card association name, if valid card was swiped. Otherwise, empty string. “VISA” Mandatory
8 Invoice Number/EDC ROC (in case of Reward Transaction) Long Integer 0 - 6 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on charge slip). Range 0 - 999999 / 101 - 999 (in case of Reward Transaction) 78/101 Mandatory
9 Batch Number/EDC Batch ID (in case of Reward Transaction) Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction). Mandatory
10 Terminal ID String 0 or 8 EFT TID, if transaction authorized. Otherwise, empty string. “30000001” Mandatory
11 Loyalty Points Awarded Long 0 - 8 RFU – not used.
Range: 0 – 99999999
0 Mandatory
12 Remark String 0 - 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization. “Failed to dial modem” Mandatory
13 Transaction Acquirer Name String 0 - 48 Name of acquirer to which transaction was routed. “ICICI BANK” Mandatory
14 Merchant ID String 0 - 15 EFT ME ID, if transaction authorized. Otherwise, empty string. “000100090015607” Mandatory
15 Retrieval Reference Number String 0 - 12 EFT RRN, if transaction authorized. Otherwise, empty string. “000000012843” Mandatory
16 Card Entry Mode Integer 0 - 5 Enumeration of possible values: 0 – Manual entry 1 – Swipe entry 2 – Chip card entry Any other value – card not validated
Range: 0 – 32767
1 Mandatory
17 Print Cardholder's Name on receipt Integer 0 - 5 Enumeration of possible values: 0 – Do not print cardholder’s name 1 – Print cardholder’s name Any other value – card not validated. This is used if external application is to print Plutus charge slip.
Range: 0 – 32767
0 Mandatory
18 Merchant Name String 0 - 23 Merchant name, if transaction authorized. Otherwise, empty string. “NOBLE MOTORS” Mandatory
19 Merchant Address String 0 - 23 Merchant address line, if transaction authorized. Otherwise, empty string. “HAJI ALI” Mandatory
20 Merchant City String 0 - 23 Merchant city line, if transaction authorized. Otherwise, empty string. “MUMBAI” Mandatory
21 Plutus Version String 0 - 40 Plutus version. “v1.54 (for ICICI BANK)” Mandatory
22 Acquiring Bank Code Integer 0 - 999 Code for bank used for processing transaction. Enumeration of possible values: 01 – HDFC BANK, 02 – ICICI BANK, 03 – AMERICAN EXPRESS, 04 – CITIBANK, 05 – AXIS BANK, 06 – SBI, 07 – HSBC, 09 – CORP BANK, 10 – CUB (City Union Bank), 14 – IDBI Bank, 17 – LVB (Lakshmi Vilas Bank), 51 - PINE 360, 301 - Sodexo, 81 – Loyalty Reward, 82 – Aimia, 85 – SBI Rewards Mandatory
23 Reward Redeemed Amount Long Integer 0 - 10 Redeemed Amount in Paisa or in lowest currency. “10000” Optional
24 Reward Redeemed Points Double 0 - 15 Redeemed Points. “400.00” Optional
25 Reward Balance Amount String 0 - 10 Balance Amount. “1000000” Optional
26 Reward Balance Points Double 0 - 15 Balance Point. “40000.00” Optional
27 Charge slip print data in tag value format (Optional)* String Charge slip data in form of tag and value separated with : and new pair separated with |*(Only present if charge slip data on merchant is enabled) Charge slip print data in tag value format(Optional)* Mandatory
28 RFU1/Coupon code/Loyalty Card Number String 0 - 23 Card Processing Fee in Rs (decimal) Or Coupon Code. Coupon code is the value which will be coming as a response to voucher redemption. This field will be present in case of voucher redemption. Or Loyalty number fetched if the transaction type is 4301. “5.50” Mandatory
29 Amount processed successfully by Plutus/ Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 - 99 Amount will always be in paisa or lowest currency. “100000” Mandatory
30 RFU3 String 0 - 23 Reserved for future use Mandatory
31 RFU String Specific for merchant Alhanumeric Optional
32 Date of Transaction String 0 - 8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format. “02012011” Mandatory
33 Time of Transaction String 0 - 6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24-hour format. “210403” Mandatory
34 PineLabs Client ID Integer 0 - 6 Unique ID assigned to Pine Labs EDC. 12345 Mandatory


Request

HEX String Format
ASCII Format
10000997001C353033302C54584E3132332C3130303030302C2C2C2C2C2C2C2C2C2CFF
— 5030,TXN123,100000,,,,,,,,,,ÿ

Response

HEX String Format
ASCII Format
999919970001015E2254584E313233222C223030222C22415050524F564544222C222A2A2A2A2A2A2A2A2A2A2A2A32383032222C2258585858222C224E4954494E20504F44444152202020202020202020202020200D0A2F222C224D41455354524F222C3332392C35342C223234333234333235222C302C2250524F434553534544222C22484446432042414E4B222C22202020202020202020202020202020222C22303030303030303030303230222C322C312C224C4F5645200D0A434F4D4D554E49434154494F4E222C224A414E412050555249222C224E45572044454C48492020202044454C20202020202020222C22506C757475732076312E34392E33204D542048444643200D0A42414E4B222C30312C22222C22222C22222C22222C22222C223131397C31357C484446432044656269747C39393636387C3130303030307C333332222C22222C22222C22222C223036333032303231222C223138353033352220FF
™™— ^"TXN123","00","APPROVED","************2802","XXXX","NITIN PODDAR /","MAESTRO",329,54,"24324325",0,"PROCESSED","HDFC BANK"," ","000000000020",2,1,"LOVE COMMUNICATION","JANA PURI","NEW DELHI DEL ","Plutus v1.49.3 MT HDFC BANK",01,"","","","","","119|15|HDFC Debit|99668|100000|332","","","","06302021","185035" ÿ

JSON Request:
 
    
  Coming Soon
  
  

JSON Response:
 
    
  
  Coming Soon
  
  


Zest Money

This section will define the request/response packet under integrated mode

Below are the transaction types under Zest Money:

Sr. No. Type of Transactions Transaction type CSV Field 1
1 Zest Money Invoice Sale 5367
2 Zest Money Product Sale 5370
3 Zest Money Void 5369

  • For Product Sale, OEM for entity needs to be configured using PCUI
  • New CSV Request/Response are created for new transaction type

Request Parameters:

CSV Request

Description Bank EMI (Invoice Sale) Brand EMI (Product Sale) Void
Transaction Type 5367 5370 5369
Billing Ref Number TXN1234 TXN1234 TXN1234
Amount 500000 500000 500000
EntityId optional(7, 8) optional(7, 8) optional(7, 8)
BankCode , , ,
Track1 , , ,
Track2 , , ,
Invoice Number , , ,
Card Swipe Required , , ,
Terminal ID , , ,
RFU1 , , ,
Clear PAN , , ,
EDC BatchID , , ,
EDC ROC , , Optional (any txn Roc: 120)
Product Scheme Parameters , , ,
Additional Amount , , ,
Card or MobileNumber , , ,
Card Expiry Date , , ,
Generic Data , , ,
Access Code , , ,
NII , , ,
Reporting Data , , ,
Billing App ID , , ,

  • For Product Sale, OEM for entity needs to be configured using PCUI
  • New CSV Request/Response are created for new transaction type

Response Parameters:

CSV RESPONSE

Description Bank EMI (Invoice Sale) Brand EMI (Product Sale)
bill num TXN1234, TXN1234,
approval code 00, 00,
response code APPROVED, APPROVED,
card number ******7890, ******7890,
expiry , ,
card holder name , ,
card type , ,
ROC 147, 177,
batch num 9008, 9008,
terminal ID 292386, 292386,
loyalty points awarded , ,
Host response INVOICE SALE, PRODUCT SALE,
Transaction Acquirer Name ZESTMONEY, ZESTMONEY,
Merchant ID 7263, 7263,
rrn , ,
entry mode Entry Mode : 3, Entry Mode : 3,
Print Cardholder’s Name on receipt , ,
merchant name Utkarsh Merchant 1 Store 1, Utkarsh Merchant 1 Store 1,
merchant address Indirapuram Indirapuram
merchant city GHAZIABAD, GHAZIABAD,
NBFC Txn Type INVOICE SALE, PRODUCT SALE,
NBFCV1Details( SchemeCode ROI Tenure EMIAmount LoanAmount DownPayment CashBack) 50795|104500|10months|52426 |5000.00|1660.28|242.50, 20007|180000|3 months|171691|5000.00|35 3.00|0.00,
response code APPROVED, APPROVED,
date 01252022, 01272022,
time 123555, 131052,
Txn Amount 500000, 500000,
product details( Brand Name Product Name Model Name ProductSKUCode ProdIMEINumber SchemeCode ROI Tenure EMIAmount) , APPLE|PHONE(WEB- MOBILE)|I PHONE|PHONE(WEB- MOBILE)||20007|180000|3| 171691

Zest Money - Invoice Sale

ZestMoney invoice sale" typically refers to a transaction where a customer uses ZestMoney as a payment option to convert their purchase into monthly EMIs.

Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer the Transaction Types
Range: 4001-4216
5367 Mandatory
2 Billing reference number String 0 – 25 Transaction reference number from external “TX12345678” Optional
3 Total EFT Amount Long Integer 0 - 8 Amount to be charged to card – expressed as a whole number in lowest currency unit (ie. in paisa)
Range: 1-99999999
999999 Mandatory
4 Bank Code String 1 – 2 The bank code to which transaction will be routed 1 Optional
5 Track 1 data/Card PAN Number String 1 – 76 Track1 data of the card or Card number if manual entry. If empty then Plutus will ask for card input. Optional
6 Track 2 data / Expiry date String 1 – 37 "Track2 data of the card or Expiry date if manual entry. If empty then Plutus will ask for card input. Expiry date is in YYMM format. In case of Pine 360, if Track 1 consists of mobile or GV number, this field will indicate the card entry mode. Mobile Number – 01 Barcode – 02 Manual - 03" Optional
7 Invoice Number Long Integer 1 – 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Invoice number of parent transition. 12 Optional
8 Is Swipe entry String TRUE or FALSE By default it is TRUE. TRUE Optional
9 Terminal ID String 1-8 Reserved for future use Optional
10 Operator String 1-31 Reserved for future use Optional
11 RFU2 String Reserved for future use Optional
12 EDC Batch ID Integer 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Batch Id of parent transition. Optional
13 EDC ROC Integer 3 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Roc of parent transition.
Range: 101-999
201 Optional
14 Transaction log ID Long Integer 1 - 12 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Transaction log of parent transition.
Range: 1-184467440737
123234 Optional
15 Reward\Cash amount Long Integer 1 – 8 Amount to be paid by reward points or in cash in paise (or in lowest currency)
Range: 1 – 99999999
999999 Optional
16 Customer Mobile Number String 1 – 100 Customer mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
17 Customer email id(s) String 1 – 500 Customer email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
18 Merchant mobile number(s) String 1 – 100 Merchant mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
19 Merchant email id(s) String 1 – 500 Merchant email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
20 Consent to send charge slip on customer mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her mobile number(s). TRUE Optional
21 Consent to send charge slip on customer email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her email id(s). TRUE Optional
22 Consent to send charge slip on merchant mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her mobile number. TRUE Optional
23 Consent to send charge slip on merchant email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her email id(s). TRUE Optional

Response Parameters

Position in CSV Field Name Data Type Length Description Sample
Value
Mandatory/
Optional
1 Billing Reference Number String 0 - 25 Transaction reference number from external application. TX12345678 Mandatory
2 Approval Code String 1 - 6 Credit card authorization code, if transaction was approved. Otherwise empty string. Presence of non-zero length approval code string indicates successful authorization of transaction. This logic holds true for Pine 360 transactions as well. “5261AJ” Mandatory
3 Host Response String 0 - 50 Response string if a response for transaction was received from bank switch. Otherwise, if any error occurs before response is received, this is an empty string. “APPROVED” Mandatory
4 Card Number String 0 - 19 Card number is valid if card was swiped. Otherwise, empty string. “************2802” Mandatory
5 Expiration Date String 0 or 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. “XXXX” Mandatory
6 Cardholder’s Name String 0 - 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string. “AMIT MOHAN” Mandatory
7 Card Type String 0 - 12 Card association name, if valid card was swiped. Otherwise, empty string. “VISA” Mandatory
8 Invoice Number/EDC ROC (in case of Reward Transaction) Long Integer 0 - 6 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on charge slip). Range 0 - 999999 / 101 - 999 (in case of Reward Transaction) 78/101 Mandatory
9 Batch Number/EDC Batch ID (in case of Reward Transaction) Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction). Mandatory
10 Terminal ID String 0 or 8 EFT TID, if transaction authorized. Otherwise, empty string. “30000001” Mandatory
11 Loyalty Points Awarded Long 0 - 8 RFU – not used.
Range: 0 – 99999999
0 Mandatory
12 Remark String 0 - 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization. “Failed to dial modem” Mandatory
13 Transaction Acquirer Name String 0 - 48 Name of acquirer to which transaction was routed. “ICICI BANK” Mandatory
14 Merchant ID String 0 - 15 EFT ME ID, if transaction authorized. Otherwise, empty string. “000100090015607” Mandatory
15 Retrieval Reference Number String 0 - 12 EFT RRN, if transaction authorized. Otherwise, empty string. “000000012843” Mandatory
16 Card Entry Mode Integer 0 - 5 Enumeration of possible values: 0 – Manual entry 1 – Swipe entry 2 – Chip card entry Any other value – card not validated
Range: 0 – 32767
1 Mandatory
17 Print Cardholder's Name on receipt Integer 0 - 5 Enumeration of possible values: 0 – Do not print cardholder’s name 1 – Print cardholder’s name Any other value – card not validated. This is used if external application is to print Plutus charge slip.
Range: 0 – 32767
0 Mandatory
18 Merchant Name String 0 - 23 Merchant name, if transaction authorized. Otherwise, empty string. “NOBLE MOTORS” Mandatory
19 Merchant Address String 0 - 23 Merchant address line, if transaction authorized. Otherwise, empty string. “HAJI ALI” Mandatory
20 Merchant City String 0 - 23 Merchant city line, if transaction authorized. Otherwise, empty string. “MUMBAI” Mandatory
21 Plutus Version String 0 - 40 Plutus version. “v1.54 (for ICICI BANK)” Mandatory
22 Acquiring Bank Code Integer 0 - 999 Code for bank used for processing transaction. Enumeration of possible values: 01 – HDFC BANK, 02 – ICICI BANK, 03 – AMERICAN EXPRESS, 04 – CITIBANK, 05 – AXIS BANK, 06 – SBI, 07 – HSBC, 09 – CORP BANK, 10 – CUB (City Union Bank), 14 – IDBI Bank, 17 – LVB (Lakshmi Vilas Bank), 51 - PINE 360, 301 - Sodexo, 81 – Loyalty Reward, 82 – Aimia, 85 – SBI Rewards Mandatory
23 Reward Redeemed Amount Long Integer 0 - 10 Redeemed Amount in Paisa or in lowest currency. “10000” Optional
24 Reward Redeemed Points Double 0 - 15 Redeemed Points. “400.00” Optional
25 Reward Balance Amount String 0 - 10 Balance Amount. “1000000” Optional
26 Reward Balance Points Double 0 - 15 Balance Point. “40000.00” Optional
27 Charge slip print data in tag value format (Optional)* String Charge slip data in form of tag and value separated with : and new pair separated with |*(Only present if charge slip data on merchant is enabled) Charge slip print data in tag value format(Optional)* Mandatory
28 RFU1/Coupon code/Loyalty Card Number String 0 - 23 Card Processing Fee in Rs (decimal) Or Coupon Code. Coupon code is the value which will be coming as a response to voucher redemption. This field will be present in case of voucher redemption. Or Loyalty number fetched if the transaction type is 4301. “5.50” Mandatory
29 Amount processed successfully by Plutus/ Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 - 99 Amount will always be in paisa or lowest currency. “100000” Mandatory
30 RFU3 String 0 - 23 Reserved for future use Mandatory
31 RFU String Specific for merchant Alhanumeric Optional
32 Date of Transaction String 0 - 8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format. “02012011” Mandatory
33 Time of Transaction String 0 - 6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24-hour format. “210403” Mandatory
34 PineLabs Client ID Integer 0 - 6 Unique ID assigned to Pine Labs EDC. 12345 Mandatory


Request

HEX String Format
ASCII Format
10000997001A353336372C54584E313233342C3530303030302C2C2C2C2C2C2CFF
— 5367,TXN1234,500000,,,,,,,ÿ

Response

HEX String Format
ASCII Format
99991997000101F154584E313233342C30302C415050524F5645442C2A2A2A2A2A2A373839302C2C2C2C3134372C393030382C3239323338362C2C494E564F4943452053414C452C5A4553544D4F4E45592C373236332C2C456E747279204D6F6465203A20332C2C55746B61727368204D65726368616E7420312053746F726520312C496E64697261707572616D2C4748415A49414241442C494E564F4943452053414C452C35303739357C3130343530307C31306D6F6E7468737C35323432367C353030302E30307C313636302E32387C3234322E35302C415050524F5645442C30313235323032322C3132333535352C3530303030302CFF
™™— ñTXN1234,00,APPROVED,******7890,,,,147,9008,292386,,INVOICE SALE,ZESTMONEY,7263,,Entry Mode : 3,,Utkarsh Merchant 1 Store 1,Indirapuram,GHAZIABAD,INVOICE SALE,50795|104500|10months|52426|5000.00|1660.28|242.50,APPROVED,01252022,123555,500000,ÿ

JSON Request:
 
    
  Coming Soon
  
  

JSON Response:
 
    
  
  Coming Soon
  
  


Zest Money – Product Sale

ZestMoney product sale allows customers to finance their purchases over time, making it more affordable and accessible, especially for those who may not have access to traditional credit cards or prefer not to use them for online shopping.

Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer the Transaction Types
Range: 4001-4216
5370 Mandatory
2 Billing reference number String 0 – 25 Transaction reference number from external “TX12345678” Optional
3 Total EFT Amount Long Integer 0 - 8 Amount to be charged to card – expressed as a whole number in lowest currency unit (ie. in paisa)
Range: 1-99999999
999999 Mandatory
4 Bank Code String 1 – 2 The bank code to which transaction will be routed 1 Optional
5 Track 1 data/Card PAN Number String 1 – 76 Track1 data of the card or Card number if manual entry. If empty then Plutus will ask for card input. Optional
6 Track 2 data / Expiry date String 1 – 37 "Track2 data of the card or Expiry date if manual entry. If empty then Plutus will ask for card input. Expiry date is in YYMM format. In case of Pine 360, if Track 1 consists of mobile or GV number, this field will indicate the card entry mode. Mobile Number – 01 Barcode – 02 Manual - 03" Optional
7 Invoice Number Long Integer 1 – 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Invoice number of parent transition. 12 Optional
8 Is Swipe entry String TRUE or FALSE By default it is TRUE. TRUE Optional
9 Terminal ID String 1-8 Reserved for future use Optional
10 Operator String 1-31 Reserved for future use Optional
11 RFU2 String Reserved for future use Optional
12 EDC Batch ID Integer 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Batch Id of parent transition. Optional
13 EDC ROC Integer 3 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Roc of parent transition.
Range: 101-999
201 Optional
14 Transaction log ID Long Integer 1 - 12 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Transaction log of parent transition.
Range: 1-184467440737
123234 Optional
15 Reward\Cash amount Long Integer 1 – 8 Amount to be paid by reward points or in cash in paise (or in lowest currency)
Range: 1 – 99999999
999999 Optional
16 Customer Mobile Number String 1 – 100 Customer mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
17 Customer email id(s) String 1 – 500 Customer email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
18 Merchant mobile number(s) String 1 – 100 Merchant mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
19 Merchant email id(s) String 1 – 500 Merchant email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
20 Consent to send charge slip on customer mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her mobile number(s). TRUE Optional
21 Consent to send charge slip on customer email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her email id(s). TRUE Optional
22 Consent to send charge slip on merchant mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her mobile number. TRUE Optional
23 Consent to send charge slip on merchant email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her email id(s). TRUE Optional

Response Parameters

Position in CSV Field Name Data Type Length Description Sample
Value
Mandatory/
Optional
1 Billing Reference Number String 0 - 25 Transaction reference number from external application. TX12345678 Mandatory
2 Approval Code String 1 - 6 Credit card authorization code, if transaction was approved. Otherwise empty string. Presence of non-zero length approval code string indicates successful authorization of transaction. This logic holds true for Pine 360 transactions as well. “5261AJ” Mandatory
3 Host Response String 0 - 50 Response string if a response for transaction was received from bank switch. Otherwise, if any error occurs before response is received, this is an empty string. “APPROVED” Mandatory
4 Card Number String 0 - 19 Card number is valid if card was swiped. Otherwise, empty string. “************2802” Mandatory
5 Expiration Date String 0 or 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. “XXXX” Mandatory
6 Cardholder’s Name String 0 - 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string. “AMIT MOHAN” Mandatory
7 Card Type String 0 - 12 Card association name, if valid card was swiped. Otherwise, empty string. “VISA” Mandatory
8 Invoice Number/EDC ROC (in case of Reward Transaction) Long Integer 0 - 6 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on charge slip). Range 0 - 999999 / 101 - 999 (in case of Reward Transaction) 78/101 Mandatory
9 Batch Number/EDC Batch ID (in case of Reward Transaction) Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction). Mandatory
10 Terminal ID String 0 or 8 EFT TID, if transaction authorized. Otherwise, empty string. “30000001” Mandatory
11 Loyalty Points Awarded Long 0 - 8 RFU – not used.
Range: 0 – 99999999
0 Mandatory
12 Remark String 0 - 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization. “Failed to dial modem” Mandatory
13 Transaction Acquirer Name String 0 - 48 Name of acquirer to which transaction was routed. “ICICI BANK” Mandatory
14 Merchant ID String 0 - 15 EFT ME ID, if transaction authorized. Otherwise, empty string. “000100090015607” Mandatory
15 Retrieval Reference Number String 0 - 12 EFT RRN, if transaction authorized. Otherwise, empty string. “000000012843” Mandatory
16 Card Entry Mode Integer 0 - 5 Enumeration of possible values: 0 – Manual entry 1 – Swipe entry 2 – Chip card entry Any other value – card not validated
Range: 0 – 32767
1 Mandatory
17 Print Cardholder's Name on receipt Integer 0 - 5 Enumeration of possible values: 0 – Do not print cardholder’s name 1 – Print cardholder’s name Any other value – card not validated. This is used if external application is to print Plutus charge slip.
Range: 0 – 32767
0 Mandatory
18 Merchant Name String 0 - 23 Merchant name, if transaction authorized. Otherwise, empty string. “NOBLE MOTORS” Mandatory
19 Merchant Address String 0 - 23 Merchant address line, if transaction authorized. Otherwise, empty string. “HAJI ALI” Mandatory
20 Merchant City String 0 - 23 Merchant city line, if transaction authorized. Otherwise, empty string. “MUMBAI” Mandatory
21 Plutus Version String 0 - 40 Plutus version. “v1.54 (for ICICI BANK)” Mandatory
22 Acquiring Bank Code Integer 0 - 999 Code for bank used for processing transaction. Enumeration of possible values: 01 – HDFC BANK, 02 – ICICI BANK, 03 – AMERICAN EXPRESS, 04 – CITIBANK, 05 – AXIS BANK, 06 – SBI, 07 – HSBC, 09 – CORP BANK, 10 – CUB (City Union Bank), 14 – IDBI Bank, 17 – LVB (Lakshmi Vilas Bank), 51 - PINE 360, 301 - Sodexo, 81 – Loyalty Reward, 82 – Aimia, 85 – SBI Rewards Mandatory
23 Reward Redeemed Amount Long Integer 0 - 10 Redeemed Amount in Paisa or in lowest currency. “10000” Optional
24 Reward Redeemed Points Double 0 - 15 Redeemed Points. “400.00” Optional
25 Reward Balance Amount String 0 - 10 Balance Amount. “1000000” Optional
26 Reward Balance Points Double 0 - 15 Balance Point. “40000.00” Optional
27 Charge slip print data in tag value format (Optional)* String Charge slip data in form of tag and value separated with : and new pair separated with |*(Only present if charge slip data on merchant is enabled) Charge slip print data in tag value format(Optional)* Mandatory
28 RFU1/Coupon code/Loyalty Card Number String 0 - 23 Card Processing Fee in Rs (decimal) Or Coupon Code. Coupon code is the value which will be coming as a response to voucher redemption. This field will be present in case of voucher redemption. Or Loyalty number fetched if the transaction type is 4301. “5.50” Mandatory
29 Amount processed successfully by Plutus/ Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 - 99 Amount will always be in paisa or lowest currency. “100000” Mandatory
30 RFU3 String 0 - 23 Reserved for future use Mandatory
31 RFU String Specific for merchant Alhanumeric Optional
32 Date of Transaction String 0 - 8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format. “02012011” Mandatory
33 Time of Transaction String 0 - 6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24-hour format. “210403” Mandatory
34 PineLabs Client ID Integer 0 - 6 Unique ID assigned to Pine Labs EDC. 12345 Mandatory


Request

HEX String Format
ASCII Format
10000997001A353337302C54584E313233342C3530303030302C2C2C2C2C2C2CFF
— 5370,TXN1234,500000,,,,,,,ÿ

Response

HEX String Format
ASCII Format
999919970001013354584E313233342C30302C415050524F5645442C2A2A2A2A2A2A373839302C2C2C3137372C393030382C3239323338362C2C50524F445543542053414C452C5A4553544D4F4E45592C373236332C2C456E747279204D6F6465203A20332C2C55746B61727368204D65726368616E7420312053746F726520312C496E64697261707572616D2C4748415A49414241442C50524F445543542053414C452C32303030377C38303030307C336D6F6E7468737C3137313639317C353030302E30307C3335332E30307C302E30302C415050524F5645442C30313237323032322C3133313035322C3530303030302C4150504C457C50484F4E45285745422D4D4F42494C45297C4950484F4E457C50484F4E45285745422D4D4F42494C45297C7C32303030377C3138303030307C337C313731363931FF
™™— 3TXN1234,00,APPROVED,******7890,,,177,9008,292386,,PRODUCT SALE,ZESTMONEY,7263,,Entry Mode : 3,,Utkarsh Merchant 1 Store 1,Indirapuram,GHAZIABAD,PRODUCT SALE,20007|80000|3months|171691|5000.00|353.00|0.00,APPROVED,01272022,131052,500000,APPLE|PHONE(WEB-MOBILE)|IPHONE|PHONE(WEB-MOBILE)||20007|180000|3|171691ÿ

JSON Request:
 
    
  Coming Soon
  
  

JSON Response:
 
    
  
  Coming Soon
  
  


Zest Money – Void

The Zest Money Void transaction is used to reverse a previously approved Zest Money transaction



Request

HEX String Format
ASCII Format
100009970027353336392C54584E313233342C3530303030302C2C2C2C2C2C2C2C2C2C2C3134372C2C2C2C2C2CFF
— '5369,TXN1234,500000,,,,,,,,,,,147,,,,,,ÿ

Response

HEX String Format
ASCII Format
999919970001012B2274786E31323322222C222230303030303522222C2222415050524F56454422222C2222393536303331323532354079626C22222C222222222C222222222C222255504922222C222231323622222C22223930373522222C2222343133303332303122222C22223022222C2222415050524F5620454422222C222222222C22224844464330303030303031373433313822222C222230303538333236383437353222222C222222222C22223022222C22225052414248415422222C222250696E656C61627322222C22224E4F49444122222C222276312E302E3022222C2222313922222C222222222C22222222202C222222222C222222222C222222222C222222222C222231303022222C222222222C222222222C2222303232373230323022222C222231363338313522FF
™™— +"txn123"",""000005"",""APPROVED"",""9560312525@ybl"","""","""",""UPI"",""126"",""9075"",""41303201"",""0"",""APPROV ED"","""",""HDFC000000174318"",""005832684752"","""",""0"",""PRABHAT"",""Pinelabs"",""NOIDA"",""v1.0.0"",""19"","""","""" ,"""","""","""","""",""100"","""","""",""02272020"",""163815"ÿ

JSON Request:
 
     
  Coming Soon
   
  

JSON Response:
 
     
  
  Coming Soon
  
  

UPI Sale Request

In integrated mode, UPI transactions can be launched directly from external billing / retail applications – avoiding the need for dual amount input. Also, the transaction response details are passed to the external application. Transaction completion can be used to automatically link the EFT payment transaction with the billing transaction for reconciliation.


Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/ Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer to the table above. 5120,5121,5122,5123 Mandatory
2 Billing Reference Number String 0 – 25 Transaction reference number from external application. Plutus will use this value for only printing on charge slip only. TX12345678 Optional
3 Total EFT Amount Long Integer 0 to 8 Amount to be charged to card – expressed as a whole number in lowest currency unit (i.e. in paisa) 999999 Mandatory
4 UPI/BHARAT QR Program ID Integer 1 to 3 This Id will be assigned by PineLabs to each UPI/BHARAT QR program types. While performing any UPI/BHARAT QR transaction this field needs to set to identify P/BHARAT QR host. Mandatory
5 UPI/BHARAT QR Identifier Data String 1 – 76 Optional
6 Type of UPI/BHARAT QR input Identifier String 1 – 37 NA Optional
7 Invoice Number Long Integer 1 – 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the invoice number of parent transaction. Optional
12 EDC Batch ID Integer 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the batch id of parent transaction. Optional
13 EDC ROC ID Integer 101-999 If independent transaction, then it is not required. Else in case of dependent transaction, it is the ROC of parent transaction. 201 Optional

Response Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/ Optional
1 Billing Ref ID String 0 – 25 Transaction reference number from external application TX12345678 Mandatory
2 Approval Code String 0 – 6 Authorization code, if transaction was approved. Otherwise empty string. 5261AJ Mandatory
3 Host Response String 0 – 50 Response string if a response for transaction was received from host. Otherwise, if any error occurs before response is received, this is an empty string. APPROVED Mandatory
4 Card Number String 0 – 19 Card number is valid if card was swiped. Otherwise, empty string. ************2802 Mandatory
5 Expiration Date String 0, 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. XXXX Mandatory
6 Cardholder’s Name String 0 – 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string AMIT MOHAN Mandatory
7 Card Type String 0 – 12 Card association name, if valid card was swiped. Otherwise, empty string UPI Mandatory
8 Invoice Number/EDC Long Integer 0 – 6 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on chargeslip) 78/101 Mandatory
9 Batch Number/EDC Batch ID Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction) Mandatory
10 Terminal ID String 0, 8 EFT TID, if transaction authorized. Otherwise, empty string 30000001 Mandatory
12 Remark String 0 – 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization Failed to dial modem Mandatory
13 Transaction Acquirer Name String 0 – 48 Name of host to which transaction was routed AXIS UPI Mandatory
14 Merchant ID String 0 – 15 EFT ME ID, if transaction authorized. Otherwise, empty string 000100090015607 Mandatory
15 Retrieval Reference Number String 0 – 12 EFT RRN, if transaction authorized. Otherwise, empty string 000000012843 Mandatory
18 Merchant Name String 0 – 23 Merchant name, if transaction authorized. Otherwise, empty string NOBLE MOTORS Mandatory
19 Merchant Address String 0 – 23 Merchant address line, if transaction authorized. Otherwise, empty string HAJI ALI Mandatory
20 Merchant City String 0 – 23 Merchant city line, if transaction authorized. Otherwise, empty string MUMBAI Mandatory
21 Plutus Version String 0 – 40 Plutus version v1.0.0 Mandatory
22 UPI/Bharat QR Integer 0 – 999 UPI/Bharat QR program type for which transaction was processed. 1 Mandatory
29 Amount processed successfully by Plutus/ Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 – 99 Amount will always be in paisa or lowest currency. 100000 Mandatory
32 Date of Transaction String 0/8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format 02012011 Mandatory
33 Time of Transaction String 0 /6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24 hour format. 210403 Mandatory
34 Plutus Transaction Id Long Integer 0-19 Transaction Id Generated by PL 30000000100001 Mandatory
38 OrigBillDetails String 0-100 EDCBatchId + "|" + OrigEDCRoc + "|" + OrigBillingRefNumber 9001101PL981445456 Mandatory


Request

HEX String Format
ASCII Format
10000997001B353132302C20545831323334353637382C3130302C2C2C2C2C2C2CFF
— 5120, TX12345678,100,,,,,,,ÿ

Response

HEX String Format
ASCII Format
99991997000100DA313234352C22303032313935222C2253554343455353222C22222C2220222C22222C22555049222C22323331222C2239313032222C2241424344313233343636222C22222C22222C2220555049204158495320222C224D32333036313630343833323230363735353739313430222C22222C22222C2230222C22766172756E73746F7265222C226A6169707572222C224144494C41424144222C2276312E302E30222C2233222C22222C22222C22222C22222C2220222C22222C2232353030222C22222C22222C223034313132303137222C2231363138333522
™™— Ú1245,"002195","SUCCESS",""," ","","UPI","231","9102","ABCD123466","",""," UPI AXIS ","M2306160483220675579140","","","0","varunstore","jaipur","ADILABAD","v1.0.0","3","","","",""," ","","2500","","","04112017","161835"

JSON Request:
 
    
  Coming Soon
  
  

JSON Response:
 
    
  
  Coming Soon
  
  


Bharat QR Sale request

In integrated mode, Bharat QR transactions can be launched directly from external billing / retail applications – avoiding the need for dual amount input. Also, the transaction response details are passed to the external application. Transaction completion can be used to automatically link the EFT payment transaction with the billing transaction for reconciliation.

Message Formate

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/ Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer to the table above. 5123 Mandatory
2 Billing Reference Number String 0 – 25 Transaction reference number from external application. Plutus will use this value for only printing on charge slip only. TX12345678 Optional
3 Total EFT Amount Long Integer 0 to 8 Amount to be charged to card – expressed as a whole number in lowest currency unit (i.e. in paisa) 999999 Mandatory
4 UPI/BHARAT QR Program ID Integer 1 to 3 This Id will be assigned by PineLabs to each UPI/BHARAT QR program types. While performing any UPI/BHARAT QR transaction this field needs to set to identify P/BHARAT QR host. Mandatory
5 UPI/BHARAT QR Identifier Data String 1 – 76 Optional
6 Type of UPI/BHARAT QR input Identifier String 1 – 37 NA Optional
7 Invoice Number Long Integer 1 – 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the invoice number of parent transaction. Optional
12 EDC Batch ID Integer 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the batch id of parent transaction. Optional
13 EDC ROC ID Integer 101-999 If independent transaction, then it is not required. Else in case of dependent transaction, it is the ROC of parent transaction. 201 Optional

Response Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/ Optional
1 Billing Ref ID String 0 – 25 Transaction reference number from external application TX12345678 Mandatory
2 Approval Code String 0 – 6 Authorization code, if transaction was approved. Otherwise empty string. 5261AJ Mandatory
3 Host Response String 0 – 50 Response string if a response for transaction was received from host. Otherwise, if any error occurs before response is received, this is an empty string. APPROVED Mandatory
4 Card Number String 0 – 19 Card number is valid if card was swiped. Otherwise, empty string. ************2802 Mandatory
5 Expiration Date String 0, 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. XXXX Mandatory
6 Cardholder’s Name String 0 – 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string AMIT MOHAN Mandatory
7 Card Type String 0 – 12 Card association name, if valid card was swiped. Otherwise, empty string UPI Mandatory
8 Invoice Number/EDC Long Integer 0 – 6 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on chargeslip) 78/101 Mandatory
9 Batch Number/EDC Batch ID Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction) Mandatory
10 Terminal ID String 0, 8 EFT TID, if transaction authorized. Otherwise, empty string 30000001 Mandatory
12 Remark String 0 – 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization Failed to dial modem Mandatory
13 Transaction Acquirer Name String 0 – 48 Name of host to which transaction was routed AXIS UPI Mandatory
14 Merchant ID String 0 – 15 EFT ME ID, if transaction authorized. Otherwise, empty string 000100090015607 Mandatory
15 Retrieval Reference Number String 0 – 12 EFT RRN, if transaction authorized. Otherwise, empty string 000000012843 Mandatory
18 Merchant Name String 0 – 23 Merchant name, if transaction authorized. Otherwise, empty string NOBLE MOTORS Mandatory
19 Merchant Address String 0 – 23 Merchant address line, if transaction authorized. Otherwise, empty string HAJI ALI Mandatory
20 Merchant City String 0 – 23 Merchant city line, if transaction authorized. Otherwise, empty string MUMBAI Mandatory
21 Plutus Version String 0 – 40 Plutus version v1.0.0 Mandatory
22 UPI/Bharat QR Integer 0 – 999 UPI/Bharat QR program type for which transaction was processed. 1 Mandatory
29 Amount processed successfully by Plutus/ Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 – 99 Amount will always be in paisa or lowest currency. 100000 Mandatory
32 Date of Transaction String 0/8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format 02012011 Mandatory
33 Time of Transaction String 0 /6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24 hour format. 210403 Mandatory
34 Plutus Transaction Id Long Integer 0-19 Transaction Id Generated by PL 30000000100001 Mandatory
38 OrigBillDetails String 0-100 EDCBatchId + "|" + OrigEDCRoc + "|" + OrigBillingRefNumber 9001101PL981445456 Mandatory



Request

HEX String Format
ASCII Format
10000997001B353132332C20545831323334353637382C3130302C2C2C2C2C2C2CFF
— 5123, TX12345678,100,,,,,,,ÿ

Response

HEX String Format
ASCII Format
99991997000100DA313234352C22303032313935222C2253554343455353222C22222C2220222C22222C22555049222C22323331222C2239313032222C2241424344313233343636222C22222C22222C2220555049204158495320222C224D32333036313630343833323230363735353739313430222C22222C22222C2230222C22766172756E73746F7265222C226A6169707572222C224144494C41424144222C2276312E302E30222C2233222C22222C22222C22222C22222C2220222C22222C2232353030222C22222C22222C223034313132303137222C2231363138333522
™™— ڱ245,"002195","SUCCESS",""," ","","UPI","231","9102","ABCD123466","",""," UPI AXIS ","M2306160483220675579140","","","0","varunstore","jaipur","ADILABAD","v1.0.0","3","","","",""," ","","2500","","","04112017","161835"

JSON Request:
 
     
  Coming Soon
   
  

JSON Response:
 
     
  
  Coming Soon
  
  

Airtel Sale

The requirement is to enable Airtel Payment Bank Integration through PineLabs solution. Customer will enter their mobile number and receive an OTP from the bank. Customer will enter the OTP on the terminal and transaction will be completed after successful response received from the Host.

Sr. No. Type of Transactions Transaction type CSV Field 1
1 Airtel Sale 5127

Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer the Transaction Types
Range: 4001-4216
5127 Mandatory
2 Billing reference number String 0 – 25 Transaction reference number from external “TX12345678” Optional
3 Total EFT Amount Long Integer 0 - 8 Amount to be charged to card – expressed as a whole number in lowest currency unit (ie. in paisa)
Range: 1-99999999
999999 Mandatory
4 Bank Code String 1 – 2 The bank code to which transaction will be routed 1 Optional
5 Track 1 data/Card PAN Number String 1 – 76 Track1 data of the card or Card number if manual entry. If empty then Plutus will ask for card input. Optional
6 Track 2 data / Expiry date String 1 – 37 "Track2 data of the card or Expiry date if manual entry. If empty then Plutus will ask for card input. Expiry date is in YYMM format. In case of Pine 360, if Track 1 consists of mobile or GV number, this field will indicate the card entry mode. Mobile Number – 01 Barcode – 02 Manual - 03" Optional
7 Invoice Number Long Integer 1 – 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Invoice number of parent transition. 12 Optional
8 Is Swipe entry String TRUE or FALSE By default it is TRUE. TRUE Optional
9 Terminal ID String 1-8 Reserved for future use Optional
10 Operator String 1-31 Reserved for future use Optional
11 RFU2 String Reserved for future use Optional
12 EDC Batch ID Integer 6 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Batch Id of parent transition. Optional
13 EDC ROC Integer 3 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Roc of parent transition.
Range: 101-999
201 Optional
14 Transaction log ID Long Integer 1 - 12 If independent transaction, then it is not required. Else in case of dependent transaction, it is the Transaction log of parent transition.
Range: 1-184467440737
123234 Optional
15 Reward\Cash amount Long Integer 1 – 8 Amount to be paid by reward points or in cash in paise (or in lowest currency)
Range: 1 – 99999999
999999 Optional
16 Customer Mobile Number String 1 – 100 Customer mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
17 Customer email id(s) String 1 – 500 Customer email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
18 Merchant mobile number(s) String 1 – 100 Merchant mobile number if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. 9900000000|8800000000 Optional
19 Merchant email id(s) String 1 – 500 Merchant email Id if required to be captured. Can be used for sending SMS for charge slip. If there are more than one value pipe separated format can be used. abc@xyz.com|efg@xyz.com Optional
20 Consent to send charge slip on customer mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her mobile number(s). TRUE Optional
21 Consent to send charge slip on customer email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant has taken consent from customer for sending charge slip on his/her email id(s). TRUE Optional
22 Consent to send charge slip on merchant mobile number(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her mobile number. TRUE Optional
23 Consent to send charge slip on merchant email id(s) String TRUE or FALSE By default, this is FALSE. If this parameter is set as TRUE, it is assumed that the merchant gives consent for sending charge slip on his/her email id(s). TRUE Optional

Response Parameters

Position in CSV Field Name Data Type Length Description Sample
Value
Mandatory/
Optional
1 Billing Reference Number String 0 - 25 Transaction reference number from external application. TX12345678 Mandatory
2 Approval Code String 1 - 6 Credit card authorization code, if transaction was approved. Otherwise empty string. Presence of non-zero length approval code string indicates successful authorization of transaction. This logic holds true for Pine 360 transactions as well. “5261AJ” Mandatory
3 Host Response String 0 - 50 Response string if a response for transaction was received from bank switch. Otherwise, if any error occurs before response is received, this is an empty string. “APPROVED” Mandatory
4 Card Number String 0 - 19 Card number is valid if card was swiped. Otherwise, empty string. “************2802” Mandatory
5 Expiration Date String 0 or 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. “XXXX” Mandatory
6 Cardholder’s Name String 0 - 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string. “AMIT MOHAN” Mandatory
7 Card Type String 0 - 12 Card association name, if valid card was swiped. Otherwise, empty string. “VISA” Mandatory
8 Invoice Number/EDC ROC (in case of Reward Transaction) Long Integer 0 - 6 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on charge slip). Range 0 - 999999 / 101 - 999 (in case of Reward Transaction) 78/101 Mandatory
9 Batch Number/EDC Batch ID (in case of Reward Transaction) Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction). Mandatory
10 Terminal ID String 0 or 8 EFT TID, if transaction authorized. Otherwise, empty string. “30000001” Mandatory
11 Loyalty Points Awarded Long 0 - 8 RFU – not used.
Range: 0 – 99999999
0 Mandatory
12 Remark String 0 - 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization. “Failed to dial modem” Mandatory
13 Transaction Acquirer Name String 0 - 48 Name of acquirer to which transaction was routed. “ICICI BANK” Mandatory
14 Merchant ID String 0 - 15 EFT ME ID, if transaction authorized. Otherwise, empty string. “000100090015607” Mandatory
15 Retrieval Reference Number String 0 - 12 EFT RRN, if transaction authorized. Otherwise, empty string. “000000012843” Mandatory
16 Card Entry Mode Integer 0 - 5 Enumeration of possible values: 0 – Manual entry 1 – Swipe entry 2 – Chip card entry Any other value – card not validated
Range: 0 – 32767
1 Mandatory
17 Print Cardholder's Name on receipt Integer 0 - 5 Enumeration of possible values: 0 – Do not print cardholder’s name 1 – Print cardholder’s name Any other value – card not validated. This is used if external application is to print Plutus charge slip.
Range: 0 – 32767
0 Mandatory
18 Merchant Name String 0 - 23 Merchant name, if transaction authorized. Otherwise, empty string. “NOBLE MOTORS” Mandatory
19 Merchant Address String 0 - 23 Merchant address line, if transaction authorized. Otherwise, empty string. “HAJI ALI” Mandatory
20 Merchant City String 0 - 23 Merchant city line, if transaction authorized. Otherwise, empty string. “MUMBAI” Mandatory
21 Plutus Version String 0 - 40 Plutus version. “v1.54 (for ICICI BANK)” Mandatory
22 Acquiring Bank Code Integer 0 - 999 Code for bank used for processing transaction. Enumeration of possible values: 01 – HDFC BANK, 02 – ICICI BANK, 03 – AMERICAN EXPRESS, 04 – CITIBANK, 05 – AXIS BANK, 06 – SBI, 07 – HSBC, 09 – CORP BANK, 10 – CUB (City Union Bank), 14 – IDBI Bank, 17 – LVB (Lakshmi Vilas Bank), 51 - PINE 360, 301 - Sodexo, 81 – Loyalty Reward, 82 – Aimia, 85 – SBI Rewards Mandatory
23 Reward Redeemed Amount Long Integer 0 - 10 Redeemed Amount in Paisa or in lowest currency. “10000” Optional
24 Reward Redeemed Points Double 0 - 15 Redeemed Points. “400.00” Optional
25 Reward Balance Amount String 0 - 10 Balance Amount. “1000000” Optional
26 Reward Balance Points Double 0 - 15 Balance Point. “40000.00” Optional
27 Charge slip print data in tag value format (Optional)* String Charge slip data in form of tag and value separated with : and new pair separated with |*(Only present if charge slip data on merchant is enabled) Charge slip print data in tag value format(Optional)* Mandatory
28 RFU1/Coupon code/Loyalty Card Number String 0 - 23 Card Processing Fee in Rs (decimal) Or Coupon Code. Coupon code is the value which will be coming as a response to voucher redemption. This field will be present in case of voucher redemption. Or Loyalty number fetched if the transaction type is 4301. “5.50” Mandatory
29 Amount processed successfully by Plutus/ Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 - 99 Amount will always be in paisa or lowest currency. “100000” Mandatory
30 RFU3 String 0 - 23 Reserved for future use Mandatory
31 RFU String Specific for merchant Alhanumeric Optional
32 Date of Transaction String 0 - 8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format. “02012011” Mandatory
33 Time of Transaction String 0 - 6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24-hour format. “210403” Mandatory
34 PineLabs Client ID Integer 0 - 6 Unique ID assigned to Pine Labs EDC. 12345 Mandatory



Request

HEX String Format
ASCII Format
100009970024353132372C543030303934303130303030303031392C353030302C2C2C2C2C2C2C2C2C2CFF
— $5127,T000940100000019,5000,,,,,,,,,,ÿ

Response - a Successful Airtel Bank transaction

HEX String Format
ASCII Format
99991997000101FB22313233222C22303030303534222C22415050524F564544222C22222C22222C22222C2241697274656C2042616E6B222C22313036222C2239303233222C223835303033222C2230222C22415050524F564544222C2241495254454C200D0A42414E4B222C22313830373034222C22343738323730222C22222C2230222C225461746120537461726275636B732053746F7265222C2250696E65204C61627320507674204C746420200D0A4E6F696461222C2244656C6869222C2276312E302E30222C223131222C22222C22222C22222C22222C22222C22222C22313030222C22222C22222C223039303632303138222C22313531313233E2809DFF
™™— û"123","000054","APPROVED","","","","Airtel Bank","106","9023","85003","0","APPROVED","AIRTEL BANK","180704","478270","","0","Tata Starbucks Store","Pine Labs Pvt Ltd Noida","Delhi","v1.0.0","11","","","","","","","100","","","09062018","151123”ÿ

Response - a Failed Airtel Bank transaction

HEX String Format
ASCII Format
999919970001012822313233222C22222C2241495254454C2042414E4B204F545020564552494649434154494F4E204641494C4544222C22222C22222C22222C2241697274656C200D0A42616E6B222C22313035222C2239303233222C223835303033222C2230222C2241495254454C2042414E4B204F545020564552494649434154494F4E204641494C4544222C2241495254454C200D0A42414E4B222C22313830373034222C22222C22222C2230222C225461746120537461726275636B732053746F7265222C2250696E65204C61627320507674204C746420200D0A4E6F696461222C2244656C6869222C2276312E302E30222C223131222C22222C22222C22222C22222C22222C22222C22313030222C22222C22222C223039303632303138222C22313530393532E2809D20FF
™™— ("123","","AIRTEL BANK OTP VERIFICATION FAILED","","","","Airtel Bank","105","9023","85003","0","AIRTEL BANK OTP VERIFICATION FAILED","AIRTEL BANK","180704","","","0","Tata Starbucks Store","Pine Labs Pvt Ltd Noida","Delhi","v1.0.0","11","","","","","","","100","","","09062018","150952” ÿ

JSON Request:
 
       
    Coming Soon
     
    

JSON Response:
 
       
    
    Coming Soon
    
    

Amazon Pay Request

In integrated mode, Amazon Pay transactions can be launched directly from external billing / retail applications –avoiding the need for dual amount input. Also, the transaction response details are passed to the external application. Transaction completion can be used to automatically link the EFT payment transaction with the billing transaction for reconciliation.

TRANSCATION TYPES

Sr. No. Type of Transactions lTxnType Value
1 Amazon Pay Request 5129
2 Get Status 5122

Message Format

Request Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/
Optional
1 Transaction Type Long Integer 4 Transaction request type to Plutus application. Please refer the Transaction Types. Range: 4001-4216 5129 Mandatory
2 Billing reference number String 0 – 25 Transaction reference number from external application. Plutus will only use this value for printing on charge slip. “TX12345678” Optional
3 Total EFT amount Long Integer 1 to 99999999 Amount to be charged to card – expressed as a whole number in lowest currency unit (ie. in paisa). Range: 1 – 99999999 999999 Mandatory
4 Wallet Program ID Integer 1-999 This ID will be assigned by Pine Labs to each wallet program type. While performing any Wallet transaction, this field needs to be set to identify wallet host. For Jio Money, this value will be 101. 101 Optional
5 Wallet Identifier Data(card/ mobile/barcode) String 1 – 76 Mobile/Barcode/Card Number. If not set, terminal will prompt to capture these values. For Jio Money, Barcode needs to be captured at Billing POS and sent in this field. Optional
6 Type of Wallet Input Identifier String 1 – 37 Type of Wallet identifier Contained in Field 4. Mobile Number – 01, Barcode – 02, Swipe - 03 1 Optional
7 Invoice Number Long Integer 1 – 6 Not Applicable 000012
8 Is Swipe entry String TRUE or FALSE By default, it is TRUE. TRUE Optional
9 Terminal ID String 1 – 8 Not Applicable
10 Operator String 1 – 31 Operator Optional
11 RFU 2 String 1 – 8 Reserved for future use Optional

Response Parameters

Position in CSV Field Name Data Type Length Description Sample Value Mandatory/ Optional
1 Billing Reference Number String 0 - 25 Transaction reference number from external application. TX12345678 Mandatory
2 Approval Code String 1 – 6 Credit card authorization code, if transaction was approved. Otherwise empty string. Presence of non-zero length approval code string indicates successful authorization of transaction. This logic holds true for Pine 360 transactions as well. 5261AJ Mandatory
3 Host Response String 0 – 50 Response string if a response for transaction was received from bank switch. Otherwise, if any error occurs before response is received, this is an empty string. APPROVED Mandatory
4 Card Number String 0 – 19 Card number is valid if card was swiped. Otherwise, empty string. ************2802 Mandatory
5 Expiration Date String 0 or 4 Card expiration date, expressed in format YYMM, if valid card was swiped. Otherwise, empty string. Some acquirers mandate Expiry date to be masked, in that case a value of “XXXX” will be returned. XXXX Mandatory
6 Cardholder’s Name String 0 – 25 Cardholder’s name from card track 1, if valid card was swiped and card holder name present on Track 1. Otherwise, empty string. AMIT MOHAN Mandatory
7 Card Type String 0 – 12 Card association name, if valid card was swiped. Otherwise, empty string. VISA Mandatory
8 Invoice Number/EDC ROC (in case of Reward Transaction) Long Integer 0 - 6 EFT transaction invoice number, if transaction authorized. Otherwise, 0/EDC ROC (the same is printed on charge slip. Range: 0 – 999999/101 – 999 (in case of Reward Transaction) 78/101 Mandatory
9 Batch Number/EDC Batch ID (in case of Reward Transaction) Integer 6 EFT transaction batch number, if transaction authorized. Otherwise, 0/EDC Batch ID (in case of Reward transaction) Mandatory
10 Terminal ID String 0 or 8 EFT TID, if transaction authorized. Otherwise, empty string. 30000001 Mandatory
11 Loyalty Points Awarded Long 0 - 8 RFU – not used. Range: 0 – 99999999 0 Mandatory
12 Remark String 0 – 100 Description of error, if an error occurs. Otherwise, empty string. An empty string in this field DOES NOT imply successful transaction authorization Failed to dial modem Mandatory
13 Transaction Acquirer Name String 0 – 48 Name of acquirer to which transaction was routed ICICI BANK Mandatory
14 Merchant ID String 0 – 15 EFT ME ID, if transaction authorized. Otherwise, empty string 000100090015607 Mandatory
15 Retrieval Reference Number String 0 – 12 EFT RRN, if transaction authorized. Otherwise, empty string 000000012843 Mandatory
16 Card Entry Mode Integer 0 - 5 Enumeration of possible values: 0 – Manual entry, 1 – Swipe entry, 2 – Chip card entry. Any other value – card not validated. Range: 0 – 32767 1 Mandatory
17 Print Cardholder's Name on receipt Integer 0 - 5 Enumeration of possible values: 0 – Do not print cardholder’s name, 1 – Print cardholder’s name. Any other value – card not validated. This is used if external application is to print Plutus charge slip. Range: 0 – 32767 0 Mandatory
18 Merchant Name String 0 – 23 Merchant name, if transaction authorized. Otherwise, empty string NOBLE MOTORS Mandatory
19 Merchant Address String 0 – 23 Merchant address line, if transaction authorized. Otherwise, empty string HAJI ALI Mandatory
20 Merchant City String 0 – 23 Merchant city line, if transaction authorized. Otherwise, empty string MUMBAI Mandatory
21 Plutus Version String 0 – 40 Plutus version v1.54 (for ICICI BANK) Mandatory
22 Wallet Code Integer 0 – 999 Wallet Code for which transaction was processed. For Jio Money value will be 101. 101 Mandatory
23 Reward Redeemed Points Double 0 - 15 Redeemed Points 400.00 Mandatory
24 Reward Balance Amount String 0 - 10 Balance Amount 1000000 Mandatory
25 Reward Balance Points Double 0 - 15 Balance Point 40000.00 Mandatory
26 Charge slip print data in tag value format (Optional)* String Charge slip data in form of tag and value separated with : and new pair separated with | (Only present if charge slip data on merchant is enabled) Charge slip print data in tag value format (Optional)* Mandatory
27 RFU1/Coupon code/Loyalty Card Number String 0 – 23 Card Processing Fee in Rs (decimal) Or Coupon Code. Coupon code is the value which will be coming as a response to voucher redemption. This field will be present in case of voucher redemption. Or Loyalty number fetched if the transaction type is 4301. 5.50 Mandatory
28 Amount processed successfully by Plutus/ Amount Loaded on cards or wallets/amount voided/Amount loaded on cards/wallets String 0 – 99 Amount will always be in paisa or lowest currency. 100000 Mandatory
29 Date of Transaction String 0 - 8 Date of the Transaction as per acquiring host. Date to be printed on charge slip. In MMDDYYYY Format. 02012011 Mandatory
30 Time of Transaction String 0 - 6 Time of the Transaction as per acquiring host. Time to be printed on charge slip. HHMMSS where HH in 24-hour format. 210403 Mandatory
31 PineLabs Client ID Integer 0 - 6 Unique ID assigned to Pine Labs EDC. 12345 Mandatory
32 PineLabs Batch ID Integer 6 Batch ID of Pine Labs EDC Mandatory
33 PineLabs ROC Integer 45080 ROC of Pine Labs EDC. Range: 101 - 999999 105 Mandatory


CASE 1: If billing application just triggers the transaction without Amazon Pay program id


Request

HEX String Format
ASCII Format
100009970026353132392C54583132332C323130302C2C393435353136303734322C30312C2C2C2C2C2C2C2CFF
— &5129,TX123,2100,,9455160742,01,,,,,,,,ÿ

Response

There will be 2 cases

CASE 1: Sale charge request is initiated, and sale completion is pending

HEX String Format
ASCII Format
9999199700010154225458313233222C22222C225452414E53414354494F4E20494E4954494154454420434845434B20474554200D0A535441545553222C22222C22222C22222C22222C22313137222C2239303334222C223137303030303633222C2230222C225452414E53414354494F4E20494E4954494154454420434845434B20474554200D0A535441545553222C22416D617A6F6E506179222C2241333133485957514D5358364354222C22222C22222C2230222C224A616672695F53746F72655F4E65775F33222C224A616672695F53746F72655F4E65775F33222C224E4F49440D0A41222C2276312E302E30222C223137222C22222C22222C22222C22222C22222C22222C22313030222C22222C22222C223131323232303139222C22313235353035222C223137303030303633303030353038222C22313030222C2235313239222C22222C2220393033347C3131377C545831323322FF
™™— T"TX123","","TRANSACTION INITIATED CHECK GET STATUS","","","","","117","9034","17000063","0","TRANSACTION INITIATED CHECK GET STATUS","AmazonPay","A313HYWQMSX6CT","","","0","Jafri_Store_New_3","Jafri_Store_New_3","NOIDA","v1.0.0","17","","","","","","","100","","","11222019","125505","17000063000508","100","5129",""," 9034|117|TX123"ÿ

CASE 2: Sale charge is complete through callback URL in one step

HEX String Format
ASCII Format
999919970001010A225458313233222C22303030303838222C22415050524F564544222C22222C22222C22222C22222C22313038222C2239333733222C22222C2230222C22415050524F564544222C22416D617A6F6E506179222C224132584D4E4F51410D0A4E384D433634222C22363139383837362D32373230363139222C22222C2230222C2241716962200D0A53746F726532222C224E4352222C2244656C6869222C2276312E302E30222C223137222C22222C22222C22222C22222C22222C22222C2232313030222C22222C22222C223037303932303139222C22313235373235222C22313730303030303130303030382038222C22222C22222C22222C22393337337C3130387C54583132332220FF
™™— "TX123","000088","APPROVED","","","","","108","9373","","0","APPROVED","AmazonPay","A2XMNOQA N8MC64","6198876-2720619","","0","Aqib Store2","NCR","Delhi","v1.0.0","17","","","","","","","2100","","","07092019","125725","1700000100008 8","","","","9373|108|TX123" ÿ

JSON Request:
 
    
Coming Soon
  

JSON Response:
 
    

Coming Soon



GET STATUS OF Amazon Pay SALE CHARGE


CASE 1: If billing application just triggers the get status with only Transaction type and amount

HEX String Format
ASCII Format
10000997001B353132322C20545831323334353637382C3130302C2C2C2C2C2C2CFF
— 5122, TX12345678,100,,,,,,,ÿ

Note : In this case status of only Last transaction will be given by above CSV. No terminal input is required

CASE 2: If billing application provides batch ID and ROC along with amount and transaction type 5122,1245,100,,,,,,,,,9296,108,,,,,,,,,,,

HEX String Format
ASCII Format
100009970029353132322C313234352C3130302C2C2C2C2C2C2C2C2C393239362C3130382C2C2C2C2C2C2C2C2C2C2CFF
— )5122,1245,100,,,,,,,,,9296,108,,,,,,,,,,,ÿ

Note : In this case the transaction will proceed to get status and no terminal input is required

Response

HEX String Format
ASCII Format
999919970001010B225458313233222C22222C224455504C49434154452042494C4C222C22222C22222C22222C22222C22313038222C2239333733222C22222C2230222C224455504C4943415445200D0A42494C4C222C22416D617A6F6E506179222C224132584D4E4F51414E384D433634222C22333238333039352D33323039343533222C22222C2230222C2241716962200D0A53746F726532222C224E4352222C2244656C6869222C2276312E302E30222C223137222C22222C22222C22222C22222C22222C22222C223132313030222C22222C22222C223037303932303139222C22313235313035222C22313730303030303130303030203837222C22222C22222C22222C22393337337C3130347C22FF
™™— "TX123","","DUPLICATE BILL","","","","","108","9373","","0","DUPLICATE BILL","AmazonPay","A2XMNOQAN8MC64","3283095-3209453","","0","Aqib Store2","NCR","Delhi","v1.0.0","17","","","","","","","12100","","","07092019","125105","170000010000 87","","","","9373|104|"ÿ

JSON Request:
 
     
  Coming Soon
   
  

JSON Response:
 
     
  
  Coming Soon
  
  

Paper POS

In Integration mode, PAPER POS charge slip can be launched directly from external billing / retail applications – avoiding the need for Multiple time selection of transaction charge slip printing. Also, the transaction response details are passed to the external application. Transaction charge slip completion can be used to automatically link the EFT payment transaction with the billing application transaction.

Sr. No. Type of Transactions lTxnType Value
1 Paper POS Print 5568
2 Paper POS RePrint 5569

Parameters Used in Paper Pos :
a) Txn Hat – Paper Pos Print/Reprint Transaction Hat
b) Billing Reference Number – Merchant Invoice number
c) Amount – Transaction Amount
d) Host Type – Unused
e) Entry Mode Data - PaperPos ID
f) Entry Mode - 5 (Last Y Mins Txns), 6 (Last N Txns)


CASE 1: If billing application just triggers the request without PAPER POS id


Request

HEX String Format
ASCII Format
10000997001B353536382C54584E3132332C3130302C2C2C2C2C2CFF
— 5568,TXN123,100,,,,,,ÿ