Messages & Error Codes
Updated February, 2022
This article documents the messages that can be returned by the Hosted Payment Page (HPP) and the Global Payments Ecommerce solution. If you are using GP-API, more information on responses is available in the API Explorer under API Definitions.
Frequently occurring messages
101
Declined by Bank
Generally insufficient funds or incorrect card data supplied, for example, expiry date or security code.
501
This transaction has already been processed!
Each transaction must have a unique Order ID. This includes those that have been processed but were declined (for example, a 101 Decline).
505
You cannot use this service from there [[URL/IP]].
In Production transactions will only be accepted from designated IPs or URLs. If a transaction doesn’t, it will be blocked.
505
The refund password you entered was incorrect.
Refunds (Rebates) and Credits must be signed with a unique SHA-1 hash. This error indicates that the hashed value was incorrect.
508
Incorrect hash. Please check your code and the Developers Documentation.
The hash included in the request was not the one expected. Usually indicates it has not has been constructed correctly or the Shared Secret is wrong. (505 for API)
511
Unable to connect to the merchant’s response URL [URL].
The HPP was unable to connect to the Response URL. Your application or website will not have received the transaction response. Common causes of this include firewall rules or server availability.
Everything else
Below are the success and error codes and corresponding messages that both users and developers will come across. We have included insight into the cause of the errors and remedies to help troubleshoot should they arise.
| Error No. | Solutions | Description |
|---|---|---|
| 00 | API/HPP | Successful – The transaction has been authorized successfully; you may proceed with the sale. |
| 101 | API/HPP | Decline – Generally insufficient funds or incorrect card data supplied, for example, expiry date or security code. |
| 102 | API/HPP | Referral B – Contact the Authorization Center. Usually treated as a standard decline for Ecommerce systems, the transaction can still be processed using a Manual request once an authorization code is obtained. |
| 103 | API/HPP | Referral A – The card has been reported lost or stolen. Usually treated as a standard decline for ecommerce systems. |
| 111 | API/HPP | Soft Decline – Indicates that the Issuer requires Strong Customer Authentication (SCA) for a transaction. In order to avoid this outcome, please ensure you enable 3D Secure 2. |
| 120 | API/HPP | Return when the settlement amount is 200% or over of the original authorized amount. Only applicable to test accounts domiciled in North America (CA/US). |
| 121 | API/HPP | Return when the settlement amount is 25% or less of the original authorized amount. Only applicable to test accounts domiciled in North America (CA/US). |
| 13x | API/HPP | Response from the Payment Declined Response Code (PDRC) service. See our PDRC article. |
| 2xx | API/HPP | Error with bank systems – generally you can tell the customer to try again later. The resolution time depends on the issue. |
| 3xx | API/HPP | Error with Global Payments systems – generally you can tell the customer to try again later. The resolution time depends on the issue. |
| 5xx | API/HPP | Invalid content in request message. These can be due to a formatting issue or account configuration. Please see the various 5xx examples below. |
| 666 | API/HPP | Account deactivated – your Global Payments account has been suspended. Please contact Global Payments. |
| 501 | API | This transaction has already been processed. |
| 502 | API | Compulsory field not present – cannot continue. Please check the Developer Documentation for compulsory fields |
| 502 | API | Type [type] not implemented. Please check the Developer Documentation for allowed types. |
| 503 | API | Request type not recognized. |
| 503 | API | Request type [type] not allowed for this merchant. |
| 504 | API | There is no such merchant id. Please contact Global Payments if you continue to experience this problem. |
| 505 | API | sha1hash incorrect – check your code and the Developer’s Documentation. |
| 505 | API | You are not allowed to access this service from there! (xxx.xxx.xxx.xxx). |
| 505 | API | You are not allowed to access this service from there!(http://www.domain.com). |
| 505 | API | The refund password you entered was incorrect. |
| 506 | API | Invalid MERCHANT_ID or ACCOUNT. Please contact the merchant. |
| 506 | API | There is no such merchant account. Please contact Global Payments if you continue to experience this problem. |
| 506 | API | No XML in request. |
| 506 | API | Too much data. |
| 506 | API | Bad XML Formation. |
| 507 | API | Currency/card combination not allowed. |
| 508 | API | Zero, negative or insufficient amount specified. |
| 508 | API | Leading zeros or other error in amount field. |
| 508 | API | Invalid characters in order id – please use only A-Z a-z 0-9 _ – . |
| 508 | API | Invalid data in merchant ID field. |
| 508 | API | Invalid data in account field. |
| 508 | API | Invalid data in currency field. |
| 508 | API | Invalid data in timestamp field. |
| 508 | API | Invalid timestamp. |
| 508 | API | Transaction out of date. |
| 508 | API | Invalid hash supplied. |
| 508 | API | Invalid Auto Settle flag. |
| 508 | API | Invalid Data in Billing code field. |
| 508 | API | Invalid Data in Billing country field. |
| 508 | API | Invalid Data in Shipping code field. |
| 508 | API | Invalid Data in Shipping country field. |
| 508 | API | Invalid characters in cust num – please use only A-Z a-z 0-9 _ – . , + @. |
| 508 | API | Invalid characters in variable reference – please use only A-Z a-z 0-9 _ – . , + @. |
| 508 | API | Invalid characters in product id – please use only A-Z a-z 0-9 _ – . , + @. |
| 508 | API | Invalid data in card type field. |
| 508 | API | The original transaction failed! You can’t rebate a failed transaction. |
| 508 | API | You may only rebate up to 115% of the original amount. |
| 508 | API | Original transaction not found. |
| 508 | API | Can’t find original transaction in database. |
| 508 | API | Can’t settle a settled transaction. |
| 508 | API | Can’t settle for more than 115% of that which you authorized. |
| 509 | API | NonNumeric in Credit card number. |
| 509 | API | Invalid credit card length. |
| 509 | API | Card number fails Luhn Check. |
| 509 | API | Invalid expiry date. |
| 509 | API | Invalid expiry date. |
| 509 | API | Card Expiry date in past. |
| 509 | API | Expiry month invalid. |
| 509 | API | That Card Number does not correspond to the card type you selected. |
| 509 | API | Length of CVV data is incorrect. |
| 510 | API | That amount is greater than the max allowed. |
| 512 | API | This transaction has already been rebated and cannot be rebated again. |
| 512 | API | You can’t refund a delayed transaction that has not been sent for settlement. (You are refunding money to a customer that has not and never will be charged). |
| 512 | API | Original transaction currency was not [currency]. |
| 513 | API | Can’t void a settled transaction. |
| 501 | HPP | This transaction (*Order ID*) has already been processed! If you feel this is incorrect please contact the merchant! |
| 502 | HPP | AMOUNT element not allowed for OTB transactions. Please contact the merchant. |
| 503 | HPP | Currency [currency] not allowed. Please contact the merchant. |
| 505 | HPP | You cannot use this service from there [[URL]]. Please contact the merchant. |
| 506 | HPP | Invalid MERCHANT_ID or ACCOUNT. Please contact the merchant. |
| 506 | HPP | Your account is in TEST mode, you cannot access the HPP live URL. |
| 508 | HPP | Payment method/currency combination not configured for the merchant. Please contact the merchant. |
| 508 | HPP | Mandatory field SHA1HASH not present – cannot continue. Please check the Developer Documentation for mandatory fields. |
| 508 | HPP | Incorrect hash. Please check your code and the Developers Documentation. |
| 508 | HPP | Unknown hash. Please contact the merchant, or refer to your code and the Developer’s Documentation. |
| 508 | HPP | Invalid data in MERCHANT_ID field. Please contact the merchant. |
| 508 | HPP | Invalid data in ACCOUNT field. Please contact the merchant. |
| 508 | HPP | Invalid characters in order id – please use only A-Z a-z 0-9 _ – or contact the merchant. |
| 508 | HPP | Too many characters in the ORDER_ID field. Please contact the merchant. |
| 508 | HPP | Invalid TIMESTAMP: Not enough characters. Please contact the merchant or refer to the developer documentation. |
| 508 | HPP | Invalid TIMESTAMP: Too many characters. Please contact the merchant or refer to the developer documentation. |
| 508 | HPP | Invalid TIMESTAMP: Not enough characters. Please contact the merchant or refer to the developer documentation. |
| 508 | HPP | Invalid TIMESTAMP: Date invalid. Please contact the merchant or refer to the developer documentation. |
| 508 | HPP | Invalid TIMESTAMP: Time invalid. Please contact the merchant or refer to the developer documentation. |
| 508 | HPP | Invalid TIMESTAMP: Value exceeds allowable limit. Please contact the merchant or refer to the developer documentation. |
| 508 | HPP | Invalid characters in AMOUNT field. Please contact the merchant. |
| 508 | HPP | Too many digits in AMOUNT field. Please contact the merchant. |
| 508 | HPP | AMOUNT too large. Please contact the merchant. |
| 508 | HPP | Insufficient AMOUNT specified. Please contact the merchant. |
| 508 | HPP | Leading zeros not allowed in AMOUNT field. Please contact the merchant. |
| 508 | HPP | Invalid data in the AUTO_SETTLE_FLAG field. Please contact the merchant. |
| 508 | HPP | Invalid RETURN_TSS flag. Please contact the merchant. |
| 508 | HPP | Incorrect number of characters in CURRENCY field. Please contact the merchant. |
| 508 | HPP | Invalid currency specified in CURRENCY field. Please contact the merchant. |
| 508 | HPP | AMOUNT field is mandatory. Please contact the merchant. |
| 508 | HPP | Invalid ORDER_ID field. Not enough characters. Please contact the merchant. |
| 508 | HPP | Invalid TIMESTAMP: Possible unsafe character(s). Please contact the merchant or refer to the developers documentation. |
| 508 | HPP | Exceeded character limit for CARD_PAYMENT_BUTTON field. Please contact merchant. |
| 508 | HPP | Invalid data in MERCHANT_DESCRIPTOR field. Please contact the merchant. |
| 511 | HPP | Invalid characters in MERCHANT_RESPONSE_URL. Please contact the merchant. |
| 508 | HPP | Invalid data in HPP_LANG field. Please contact the merchant. |
| 510 | HPP | Too Much Data sent from merchant response url. |
| 510 | HPP | Unable_to_connect_to_the_merchants_response_URL_ {2} ._Was_able_to_connect_to_alternate_URL. |
| 508 | HPP | Unable to connect to the merchant’s response URL [Response URL]. |
| 501 | Scheduler | Cannot insert. The Scheduled Payment Ref already exists |
| 501 | Scheduler | You don’t have enough privileges for this operation |
| 503 | Scheduler | Only auth transaction type is allowed for scheduled payments. |
| 508 | Scheduler | Zero, negative or insufficient amount specified. Please contact the merchant. |
| 530 | Scheduler | Invalid value. The start date cannot be in the past. |
| 531 | Scheduler | Invalid start date value. |
| 532 | Scheduler | Invalid value. The end date cannot be in the past. |
| 533 | Scheduler | Invalid end date value. |
| 534 | Scheduler | Invalid value. The end date has to be greater than the start date. |
| 535 | Scheduler | Invalid value, numtimes cannot be set to zero. |
| 535 | Scheduler | Invalid value, numtimes cannot be greater than 999. |
| 536 | Scheduler | numtimes value should be -1 if enddate is specified. |
| 537 | Scheduler | The schedule expression is not valid. |
| 110 | 3D Secure | Transaction NOT permitted by merchant config. |
| 503 | 3D Secure | No 3D Secure details setup for merchant [merchant_id] with account [account_id] using [currency] as currency and card type [card type]. |
| 508 | 3D Secure | Exceeded character limit for ECI field. Please contact the merchant. |
| 508 | 3D Secure | Invalid data in ECI field. Please contact the merchant. |
| 509 | 3D Secure | An ECI value must be included for MPI enabled accounts. |
| 520 | 3D Secure | Message ID in VERes not the same as VEReq. |
| 520 | 3D Secure | Undefined Element in Message before VERes. |
| 520 | 3D Secure | Invalid Element in Message before PARes. |
| 520 | 3D Secure | Invalid Root Element. |
