Response XML
Response xml is like following
<PaymentResponse>
<version>9.3</version>
<timeStamp></timeStamp>
<merchantID></merchantID>
<respCode></respCode>
<pan></pan>
<amt></amt>
<uniqueTransactionCode></uniqueTransactionCode>
<tranRef></tranRef>
<approvalCode></approvalCode>
<refNumber></refNumber>
<eci></eci>
<dateTime></dateTime>
<status></status>
<failReason></failReason>
<userDefined1></userDefined1>
<userDefined2></userDefined2>
<userDefined3></userDefined3>
<userDefined4></userDefined4>
<userDefined5></userDefined5>
<storeCardUniqueID></storeCardUniqueID>
<recurringUniqueID></recurringUniqueID>
</PaymentResponse>| Variable | Data Type | Length | Mandatory | Description | Remark |
|---|---|---|---|---|---|
| version | Character | 5 | Y | Version of the payment request | |
| timeStamp | Character | 22 | Y | Date and time of request message | Request DateTime in format of ddMMyyHHmmss |
| merchantID | Character | 15 | Y | Merchant ID | Payment request merchant ID. Provided by 2c2p. |
| respCode | Character | 2/3 | Y | The code whether the transaction is successful or not. |
For Card / Third Party Payment 00 = Approved; 05 = Do Not Honor; More detail at Payment Response Code For 123 Payment 001 = Success(Pending); 000 = Success(Paid); More detail at 123 Response Code |
| pan | Character | 16 | Y | Masked Credit Card Number | First 6 and last 4 digits of credit card number. Example : 444411xxxxxx1111 |
| amt | Numeric | 12 | Y | The amount that the customer want to convert. The amount from the Pay Request XML. | The amount will be padded with 0 from the left and include no decimal point. Example : 1.00 = 000000000100 1.50 = 000000000150 |
| uniqueTransactionCode | Character | 20 | Y | Invoice No. The invoice no from the Pay Request XML. | Provided by Merchant. The invoice number needs to be unique to trace the transaction. Please pad '0' to the left in the case of generated invoice number length is shorter than 20. |
| tranRef | Character | 28 | Y | Transaction Reference for the Payment Routing System. | Issued by System. This is to trace the transactions in the Routing System. |
| approvalCode | Character | 6 | Y | Transaction Approval Code from Credit Card Host | |
| refNumber | Character | 15 | Y | Transaction Reference Number from Credit Card Host. | |
| eci | Numeric | 2 | Y | ECI value. | |
| dateTime | Numeric | 14 | Y | Process Date Time value with ddMMyyHHmmss format | |
| status | Character | 1-3 | Y | Last status of transaction | Refer to Transaction Status |
| failReason | Character | 100 | N | Reason of failure | Refer to Response Code |
| userDefined1 | Character | 150 | N | User defined info from request message | |
| userDefined2 | Character | 150 | N | User defined info from request message | |
| userDefined3 | Character | 150 | N | User defined info from request message | |
| userDefined4 | Character | 150 | N | User defined info from request message | |
| userDefined5 | Character | 150 | N | User defined info from request message | |
| storeCardUniqueID | Character | 20 | N | Unique ID of store card info. | Unique ID of store card info will be generated by process if 'storeCard' parameter is set to 'Y' at payment request XML. |
| recurringUniqueID | Numeric | 20 | N | The unique id of recurrent payment cycle. | The id will be generated by 2C2P if merchant set the recurring parameters. |
| hashValue | Character | 150 | Y | Hash value computed by HMACSHA1 with secret key provided by 2C2P System. | Refer to hashing section |