Hosted Page Validation Errors
Hosted Page Validation Errors occur when initial form data validation fails before being processed by Zuora's business logic and the payment gateway. These errors are specified in the response object and can be customized for display.
In addition to the above types of errors, Payment Pages 2.0 has a set of errors, called Hosted Page Validation Errors. The form data that user inputs are validated before the input values are validated by Zuora's business logic and authorized by the payment gateway. If this initial validation fails, user receives a Hosted Page Validation error.
For Hosted Page Validation Errors, Zuora specifies each of the error fields in the response object, i.e., response.errorCode and response.errorField . You can customize how you want to display the messaging based on the fields that caused the error.
The following table lists the Hosted Page Validation Error codes.
|
Code |
Description |
Used In |
|---|---|---|
|
Attempt_Exceed_Limitation |
One of the following causes the error:
See Security Measures for Payment Pages 2.0 for more information. |
errorCode |
|
BusinessValidationError |
One or more business validation errors have occurred. An error message is typically returned from Zuora. For examples of typical business validation errors, see Examples of business validation errors. |
errorCode |
|
Decryption_Error |
An error happened during decryption. |
errorCode |
|
ExceededMaxLength |
Length of the value entered exceeds the maximum allowed. |
errorField |
|
GatewayTransactionError |
One or more gateway transaction errors have occurred, such as, an invalid account number, or an invalid username / password configured in Gateway Settings page. An error message is typically returned from the payment gateway. |
errorCode |
|
GeneralSystemError |
One or more general system errors have occurred. |
errorCode |
|
HostedPageFieldValidationError |
One or more field validation errors have occurred. These are the errors that occur from submitting the Payment Page without filling in one or more required fields. One or more |
errorCode |
|
Invalid_PaymentGateway |
The paymentGateway parameter specified a gateway name that does not exist. |
errorCode |
|
Invalid_Request_Method |
The Payment Page form was submitted using an invalid method. It should be POST. |
errorCode |
|
Invalid_Security |
Security validation error, such as an expired signature or incorrectly encrypted signature. A signature is expired:
|
errorCode |
|
InvalidFormat |
The input value was entered in an invalid format, such as Credit card number containing characters |
errorField |
|
NullValue |
No value has been entered for a required field. This includes detailed codes for HostedPageFieldValidationError. |
errorField |
|
ReCaptcha_Validation_Failed |
End users failed to pass CAPTCHA validation. |
errorCode |
|
Submit_Too_Quick |
One of the following scenarios causes the error:
For more detailed information, see Security measures for Payment Pages 2.0 |
errorCode |
|
Validate_Dynamic_Params_Failed |
The parameters in the request for rendering or submitting Payment Pages 2.0 do not match with the parameters in the request for generating the digital signature. For more detailed information, see Security measures for Payment Pages 2.0. The default error message is |
errorCode |
|
ThreeDs2_Authentication_Exception |
End users failed the strong customer authentication. For more detailed information, see Security measures for Payment Pages 2.0. The error code is common across all gateways, while the error message is gateway-specific. |
errorCode |