Page Summary
-
The Error Response object provides details about errors encountered during API calls.
-
It includes fields for a common response header, error code, description for debugging, and an integrator-specific identifier.
-
The
errorDescriptionfield offers details for support and debugging but should not contain sensitive information or user-facing text. -
Integrators can utilize the
paymentIntegratorErrorIdentifierfor internal debugging purposes, mapping the error to their specific call.
Error Response object for all methods.
| JSON representation |
|---|
{ "responseHeader": { object ( |
| Fields | |
|---|---|
responseHeader |
REQUIRED: Common header for all responses. |
errorResponseCode |
OPTIONAL: A code that captures the type of error that occurred. |
errorDescription |
OPTIONAL: Provide a description of this status for support reps to debug errors. Note that this is never shown to users. It can contain descriptive, non-sensitive text used for debugging. Note that some values for errorResponseCode should be accompanied by additional detail in this field. For example, |
paymentIntegratorErrorIdentifier |
OPTIONAL: This identifier is specific to the integrator and is generated by the integrator. It is used for debugging purposes only in order to identify this call. This is the identifier that the integrator knows this call by. |