Response & Error Codes
Response Codes
HTTP Status code | Code | Description | Example |
---|---|---|---|
2xx | 0 | Success | Returned if operation was successful |
503 | 950 | Operation Failed | Returned when an internal exception occurred on the Partner’s side (i.e. database connection error) which prevented operation from being completed |
400 | 951 | Invalid Request | Returned when GD’s request is missing a required parameter, malformed, etc. and cannot be completely parsed on Partner’s end. Should be accompanied with subCode 602 and include the missing or invalid values |
2xx | 954 | Rejected | Returned when Partner is explicitly rejecting or declining a transaction. Should be accompanied with the correct corresponding subCode |
Sub Codes
SubCode | Description |
---|---|
0 | Success |
600 | Timeout |
601 | System Error |
602 | Invalid or Missing |
603 | Barcode Expired |
604 | Barcode Cancelled |
605 | Barcode Already Consumed |
606 | Barcode Pending Consumption |
607 | Barcode Amount Exceeds Limits |
608 | Barcode Amount is Below the Minimum Amount Required |
609 | Barcode Amount is Above the Maximum Amount Allowed |
610 | Barcode Voided |
611 | Account Blocked |
612 | Account Not Eligible |
613 | Account Closed |
614 | Card Expired |
615 | Card Lost or Stolen |
616 | Customer Blocked |
617 | General Decline |
622 | Limit Exceeded - Monthly |
623 | Limit Exceeded - Per transaction |
624 | Potential Fraud Detected |
625 | Not Found |
626 | Limit Exceeded - Daily |
627 | Limit Exceeded - Weekly |
630 | Claim Code Status is Not in a Status which can be Cancelled |
632 | Already committed, cannot be Voided |
633 | Already Voided, cannot be Committed |
634 | Access Token Expired |
Updated 9 months ago