Bug #477
Payment File - Wrong response code
| Status: | Closed - End of life cycle | Start date: | September 21, 2010 | |
|---|---|---|---|---|
| Priority: | Urgent | Due date: | September 21, 2010 | |
| Assignee: |  Cheang Danniell | % Done: | 100% | |
| Category: | - | Spent time: | 0.50 hour | |
| Target version: | - |
Description
Steven reported from UAT:-
There seems to be a problem with the payment file generated by the end of day process. Please note that all response codes are set to “000†regardless of whether successful or not. Please look into this immediately and provide me with the patch as soon as possible. Thanks.
Response Code
- Contains Approval Code if approved.
- If not approved, this field contains the 2-digit Response Code per ISO8583 message specifications.
History
#1
Updated by Cheang Danniell about 14 years ago
- Status changed from New - Begin Life Cycle to Work Completed-End life cycle
- % Done changed from 0 to 100
Amendments on epaymenthostfile project:
*Change response code from 000 to px_approval_code for successful transactions
Snippets as following:
if(responseCode.equals ("000")){
// Danniell: 21-Sep-2010 Replace response code with approval code if successful
responseCode = rs.getString ("PX_APPROVAL_CODE") != null ? rs.getString ("PX_APPROVAL_CODE") : "";
decisionCode = "A";
totalApprove++;
totalApproveAmount = totalApproveAmount.add (new BigDecimal(rs.getString ("PX_PURCHASE_AMOUNT")));
}else{
decisionCode = "R";
totalReject++;
totalRejectAmount = totalRejectAmount.add (new BigDecimal(rs.getString ("PX_PURCHASE_AMOUNT")));
}
#2
Updated by Tan Lee Yong almost 14 years ago
- Status changed from Work Completed-End life cycle to Closed - End of life cycle
Assumed no more issue