Error types, codes, and objects

Learn about error types, codes, and objects.

Change event error object

When DigitalRiver.js detects a problem with an element, its change event returns an error contains a type, code, and message.

    "type": "validation_error",
    "code": "invalid_card_number",
    "message": "Your card number is invalid."

Create source error object

If a problem occurs during the tokenization request, the createSource method and on source event returns an error with a type and an array of errors[], each containing a detailed message.

    "type": "bad_request",
    "errors": [{
           "code": "invalid_parameter",
           "parameter": "owner.firstName",
           "message": "'' is not a valid owner.firstname."
            "code": "currency_unsupported",
            "parameter": "currency",
            "message": "currency 'xyz' is not supported."

Error types

The following table contains a list of DigitalRiver.js error types.



The server could not process the request due to a client error (for example, malformed request syntax). Correct the problem and try again.


The server can't find the requested resource. No indication is given of whether the condition is temporary or permanent.


The client did not produce the request within the time that the server was prepared to wait. Resend the request without modifications at any later time.


The server encountered an unexpected problem that prevented it from fulfilling the request.


The request requires user authentication. Resend the request with valid user authentication.


The user sent too many requests in a given amount of time ("rate limiting"). The response should include details explaining the condition and may include a Retry-After header indicating how long to wait before sending a new request.


There is a request conflict with the current state of the server.

Conflicts are most likely to occur in response to a PUT request. For example, you may get a 409 response when uploading a file that is older than the one already on the server resulting in a version control conflict.


Errors triggered by our client-side libraries when failing to validate fields (for example, when a card number or expiration date is invalid or incomplete).

Used by: DigitalRiver.js


There is no network coverage or cellular data connection.

Error codes

The following table contains a list of DigitalRiver.js error codes.

You must only indicate that the payment has been declined, and you must not share the code or descriptions below with the customer.



There is a problem with your address.


The card is expired, or the expiration date is invalid.


The format of your request is invalid.


The parameter is invalid. Check the Commerce API Reference to see which values are valid and try again.


The string value is empty. Provide a valid string value and try again.


The method is not allowed. Provide a valid method value and try again.


A parameter is missing. Check the Commerce API Reference to see which values are required and try again.


The item requested was not found.


The source you have requested was not found.


An unknown error has occurred.

Last updated