Handle Errors

Status code: 400 – Bad request

An error response notifies the user that the action relating to the request has failed. Use the

error.reason

field to determine how to handle the error.

Error reasons and messages appear in a standard error structure, which is returned when the API request could not be handled. For programmatic actions, you should only rely on the value in the

error.reason

field. Errors include a description in the

error.message

field. You can use this field to understand the error. You can provide your own description based on the value in the

error.reason

field. In some cases, the

error.details.message

and

error.details.location

provide additional information.

Error Response Fields

Error Field	Type	Description
error.correlationId	String	Returns Correlation ID
error.details.location	String	The value of this field uses an XPATH expression to point to the field that fails validation.
error.details.message	String	The specific error associated with the field.
error.informationLink	String	Returns Information link
error.message	String	Returned from the backend call
error.reason	String	These options can be used to override transaction options for the DPA that were configured during the DPA Registration.

For a full capture context with all possible fields, their definitions, see

Unified Click to Pay Capture Context