Call us:
353-1211-8666
Call us:
353-1211-8666
Woohoo Pay
PAY

Error Codes

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.SolutionsDescription
00API/HPPSuccessful – The transaction has been authorized successfully; you may proceed with the sale.
101API/HPPDecline – Generally insufficient funds or incorrect card data supplied, for example, expiry date or security code.
102API/HPPReferral 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.
103API/HPPReferral A – The card has been reported lost or stolen. Usually treated as a standard decline for ecommerce systems.
111API/HPPSoft 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.
120API/HPPReturn when the settlement amount is 200% or over of the original authorized amount. Only applicable to test accounts domiciled in North America (CA/US).
121API/HPPReturn when the settlement amount is 25% or less of the original authorized amount. Only applicable to test accounts domiciled in North America (CA/US).
13xAPI/HPPResponse from the Payment Declined Response Code (PDRC) service. See our PDRC article.
2xxAPI/HPPError with bank systems – generally you can tell the customer to try again later. The resolution time depends on the issue.
3xxAPI/HPPError with Global Payments systems – generally you can tell the customer to try again later. The resolution time depends on the issue.
5xxAPI/HPPInvalid content in request message. These can be due to a formatting issue or account configuration. Please see the various 5xx examples below.
666API/HPPAccount deactivated – your Global Payments account has been suspended. Please contact Global Payments.
501APIThis transaction has already been processed.
502APICompulsory field not present – cannot continue. Please check the Developer Documentation for compulsory fields
502APIType [type] not implemented. Please check the Developer Documentation for allowed types.
503APIRequest type not recognized.
503APIRequest type [type] not allowed for this merchant.
504APIThere is no such merchant id. Please contact Global Payments if you continue to experience this problem.
505APIsha1hash incorrect – check your code and the Developer’s Documentation.
505APIYou are not allowed to access this service from there! (xxx.xxx.xxx.xxx).
505APIYou are not allowed to access this service from there!(http://www.domain.com).
505APIThe refund password you entered was incorrect.
506APIInvalid MERCHANT_ID or ACCOUNT. Please contact the merchant.
506APIThere is no such merchant account. Please contact Global Payments if you continue to experience this problem.
506APINo XML in request.
506APIToo much data.
506APIBad XML Formation.
507APICurrency/card combination not allowed.
508APIZero, negative or insufficient amount specified.
508APILeading zeros or other error in amount field.
508APIInvalid characters in order id – please use only A-Z a-z 0-9 _ – .
508APIInvalid data in merchant ID field.
508APIInvalid data in account field.
508APIInvalid data in currency field.
508APIInvalid data in timestamp field.
508APIInvalid timestamp.
508APITransaction out of date.
508APIInvalid hash supplied.
508APIInvalid Auto Settle flag.
508APIInvalid Data in Billing code field.
508APIInvalid Data in Billing country field.
508APIInvalid Data in Shipping code field.
508APIInvalid Data in Shipping country field.
508APIInvalid characters in cust num – please use only A-Z a-z 0-9 _ – . , + @.
508APIInvalid characters in variable reference – please use only A-Z a-z 0-9 _ – . , + @.
508APIInvalid characters in product id – please use only A-Z a-z 0-9 _ – . , + @.
508APIInvalid data in card type field.
508APIThe original transaction failed! You can’t rebate a failed transaction.
508APIYou may only rebate up to 115% of the original amount.
508APIOriginal transaction not found.
508APICan’t find original transaction in database.
508APICan’t settle a settled transaction.
508APICan’t settle for more than 115% of that which you authorized.
509APINonNumeric in Credit card number.
509APIInvalid credit card length.
509APICard number fails Luhn Check.
509APIInvalid expiry date.
509APIInvalid expiry date.
509APICard Expiry date in past.
509APIExpiry month invalid.
509APIThat Card Number does not correspond to the card type you selected.
509APILength of CVV data is incorrect.
510APIThat amount is greater than the max allowed.
512APIThis transaction has already been rebated and cannot be rebated again.
512APIYou 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).
512APIOriginal transaction currency was not [currency].
513APICan’t void a settled transaction.
501HPPThis transaction (*Order ID*) has already been processed! If you feel this is incorrect please contact the merchant!
502HPPAMOUNT element not allowed for OTB transactions. Please contact the merchant.
503HPPCurrency [currency] not allowed. Please contact the merchant.
505HPPYou cannot use this service from there [[URL]]. Please contact the merchant.
506HPPInvalid MERCHANT_ID or ACCOUNT. Please contact the merchant.
506HPPYour account is in TEST mode, you cannot access the HPP live URL.
508HPPPayment method/currency combination not configured for the merchant. Please contact the merchant.
508HPPMandatory field SHA1HASH not present – cannot continue. Please check the Developer Documentation for mandatory fields.
508HPPIncorrect hash. Please check your code and the Developers Documentation.
508HPPUnknown hash. Please contact the merchant, or refer to your code and the Developer’s Documentation.
508HPPInvalid data in MERCHANT_ID field. Please contact the merchant.
508HPPInvalid data in ACCOUNT field. Please contact the merchant.
508HPPInvalid characters in order id – please use only A-Z a-z 0-9 _ – or contact the merchant.
508HPPToo many characters in the ORDER_ID field. Please contact the merchant.
508HPPInvalid TIMESTAMP: Not enough characters. Please contact the merchant or refer to the developer documentation.
508HPPInvalid TIMESTAMP: Too many characters. Please contact the merchant or refer to the developer documentation.
508HPPInvalid TIMESTAMP: Not enough characters. Please contact the merchant or refer to the developer documentation.
508HPPInvalid TIMESTAMP: Date invalid. Please contact the merchant or refer to the developer documentation.
508HPPInvalid TIMESTAMP: Time invalid. Please contact the merchant or refer to the developer documentation.
508HPPInvalid TIMESTAMP: Value exceeds allowable limit. Please contact the merchant or refer to the developer documentation.
508HPPInvalid characters in AMOUNT field. Please contact the merchant.
508HPPToo many digits in AMOUNT field. Please contact the merchant.
508HPPAMOUNT too large. Please contact the merchant.
508HPPInsufficient AMOUNT specified. Please contact the merchant.
508HPPLeading zeros not allowed in AMOUNT field. Please contact the merchant.
508HPPInvalid data in the AUTO_SETTLE_FLAG field. Please contact the merchant.
508HPPInvalid RETURN_TSS flag. Please contact the merchant.
508HPPIncorrect number of characters in CURRENCY field. Please contact the merchant.
508HPPInvalid currency specified in CURRENCY field. Please contact the merchant.
508HPPAMOUNT field is mandatory. Please contact the merchant.
508HPPInvalid ORDER_ID field. Not enough characters. Please contact the merchant.
508HPPInvalid TIMESTAMP: Possible unsafe character(s). Please contact the merchant or refer to the developers documentation.
508HPPExceeded character limit for CARD_PAYMENT_BUTTON field. Please contact merchant.
508HPPInvalid data in MERCHANT_DESCRIPTOR field. Please contact the merchant.
511HPPInvalid characters in MERCHANT_RESPONSE_URL. Please contact the merchant.
508HPPInvalid data in HPP_LANG field. Please contact the merchant.
510HPPToo Much Data sent from merchant response url.
510HPPUnable_to_connect_to_the_merchants_response_URL_ {2} ._Was_able_to_connect_to_alternate_URL.
508HPPUnable to connect to the merchant’s response URL [Response URL].
501SchedulerCannot insert. The Scheduled Payment Ref already exists
501SchedulerYou don’t have enough privileges for this operation
503SchedulerOnly auth transaction type is allowed for scheduled payments.
508SchedulerZero, negative or insufficient amount specified. Please contact the merchant.
530SchedulerInvalid value. The start date cannot be in the past.
531SchedulerInvalid start date value.
532SchedulerInvalid value. The end date cannot be in the past.
533SchedulerInvalid end date value.
534SchedulerInvalid value. The end date has to be greater than the start date.
535SchedulerInvalid value, numtimes cannot be set to zero.
535SchedulerInvalid value, numtimes cannot be greater than 999.
536Schedulernumtimes value should be -1 if enddate is specified.
537SchedulerThe schedule expression is not valid.
1103D SecureTransaction NOT permitted by merchant config.
5033D SecureNo 3D Secure details setup for merchant [merchant_id] with account [account_id] using [currency] as currency and card type [card type].
5083D SecureExceeded character limit for ECI field. Please contact the merchant.
5083D SecureInvalid data in ECI field. Please contact the merchant.
5093D SecureAn ECI value must be included for MPI enabled accounts.
5203D SecureMessage ID in VERes not the same as VEReq.
5203D SecureUndefined Element in Message before VERes.
5203D SecureInvalid Element in Message before PARes.
5203D SecureInvalid Root Element.
Woohoo Pay

Our purpose is to build solutions that remove barriers preventing people from doing their best work.

Melbourne, Australia
(Sat - Thursday)
(10am - 05 pm)