For AI agents: the complete documentation index is at /llms.txt, and the full text of every page is at /llms-full.txt. Most pages are also available as Markdown by adding .md to the URL.

Messages & Error Codes

See examples of what responses are returned

This guide documents the messages you might receive when integrating with our XML API.

Frequently occurring

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 when integrating with the following solutions:

Direct API integration
Hosted Payment Page
Both API and HPP
3D Secure
Scheduler

We have included insight into the cause of the errors and remedies to help troubleshoot should they arise.

Direct API integration

Solution	Error No.	Description
API	501	This transaction has already been processed.
API	502	Compulsory field not present – cannot continue. Please check the Developer Documentation for compulsory fields
API	502	Type [type] not implemented. Please check the Developer Documentation for allowed types.
API	503	Request type not recognized.
API	503	Request type [type] not allowed for this merchant.
API	504	There is no such merchant id. Please contact Global Payments if you continue to experience this problem.
API	505	sha1hash incorrect – check your code and the Developer’s Documentation.
API	505	You are not allowed to access this service from there! (xxx.xxx.xxx.xxx).
API	505	You are not allowed to access this service from there!(http://www.domain.com).
API	505	The refund password you entered was incorrect.
API	506	Invalid MERCHANT_ID or ACCOUNT. Please contact the merchant.
API	506	There is no such merchant account. Please contact Global Payments if you continue to experience this problem.
API	506	No XML in request.
API	506	Too much data.
API	506	Bad XML Formation.
API	507	Currency/card combination not allowed.
API	508	Zero, negative or insufficient amount specified.
API	508	Leading zeros or other error in amount field.
API	508	Invalid characters in order id - please use only A-Z a-z 0-9 _ - .
API	508	Invalid data in merchant ID field.
API	508	Invalid data in account field.
API	508	Invalid data in currency field.
API	508	Invalid data in timestamp field.
API	508	Invalid timestamp.
API	508

Hosted Payment Page

Solution	Error No.	Description
HPP	501	This transaction (Order ID) has already been processed! If you feel this is incorrect please contact the merchant!
HPP	502	AMOUNT element not allowed for OTB transactions. Please contact the merchant.
HPP	503	Currency [currency] not allowed. Please contact the merchant.
HPP	505	You cannot use this service from there [[URL]]. Please contact the merchant.
HPP	506	Invalid MERCHANT_ID or ACCOUNT. Please contact the merchant.
HPP	506	Your account is in TEST mode, you cannot access the HPP live URL.
HPP	508	Payment method/currency combination not configured for the merchant. Please contact the merchant.
HPP	508	Mandatory field SHA1HASH not present - cannot continue. Please check the Developer Documentation for mandatory fields.
HPP	508	Incorrect hash. Please check your code and the Developers Documentation.
HPP	508	Unknown hash. Please contact the merchant, or refer to your code and the Developer's Documentation.
HPP	508	Invalid data in MERCHANT_ID field. Please contact the merchant.
HPP	508	Invalid data in ACCOUNT field. Please contact the merchant.
HPP	508	Invalid characters in order id - please use only A-Z a-z 0-9 _ - or contact the merchant.
HPP	508	Too many characters in the ORDER_ID field. Please contact the merchant.
HPP	508	Invalid TIMESTAMP: Not enough characters. Please contact the merchant or refer to the developer documentation.
HPP	508	Invalid TIMESTAMP: Too many characters. Please contact the merchant or refer to the developer documentation.
HPP	508	Invalid TIMESTAMP: Not enough characters. Please contact the merchant or refer to the developer documentation.
HPP	508	Invalid TIMESTAMP: Date invalid. Please contact the merchant or refer to the developer documentation.
HPP	508	Invalid TIMESTAMP: Time invalid. Please contact the merchant or refer to the developer documentation.
HPP	508	Invalid TIMESTAMP: Value exceeds allowable limit. Please contact the merchant or refer to the developer documentation.

Both API and HPP

Solution	Error No.	Description
API/HPP	00	Successful – The transaction has been authorized successfully; you may proceed with the sale.
API/HPP	101	Decline - Generally insufficient funds or incorrect card data supplied, for example, expiry date or security code.
API/HPP	102	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.
API/HPP	103	Referral A - The card has been reported lost or stolen. Usually treated as a standard decline for ecommerce systems.
API/HPP	111	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.
API/HPP	120	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).
API/HPP	121	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).
API/HPP	13x	Response from the Payment Decline Reason Code (PDRC) service. See our PDRC guide.
API/HPP	2xx	Error with bank systems – generally you can tell the customer to try again later. The resolution time depends on the issue.
API/HPP	205	Comms Error - installment connection error.
API/HPP	3xx	Error with Global Payments systems – generally you can tell the customer to try again later. The resolution time depends on the issue.
API/HPP	5xx	Invalid content in request message. These can be due to a formatting issue or account configuration. Please see the various 5xx examples below.
API/HPP	666	Account deactivated – your Global Payments account has been suspended. Please contact Global Payments.

3D Secure

Solution	Error No.	Description
3D Secure	110	Transaction NOT permitted by merchant config.
3D Secure	503	No 3D Secure details setup for merchant [merchant_id] with account [account_id] using [currency] as currency and card type [card type].
3D Secure	508	Exceeded character limit for ECI field. Please contact the merchant.
3D Secure	508	Invalid data in ECI field. Please contact the merchant.
3D Secure	509	An ECI value must be included for MPI enabled accounts.
3D Secure	520	Message ID in VERes not the same as VEReq.
3D Secure	520	Undefined Element in Message before VERes.
3D Secure	520	Invalid Element in Message before PARes.
3D Secure	520	Invalid Root Element.

Scheduler

Solution	Error No.	Description
Scheduler	534	Invalid value. The end date has to be greater than the start date.
Scheduler	535	Invalid value, numtimes cannot be set to zero.
Scheduler	535	Invalid value, numtimes cannot be greater than 999.
Scheduler	536	numtimes value should be -1 if enddate is specified.
Scheduler	537	The schedule expression is not valid.

Policies

Connect

Additional Resources