Every request can, at any time, return an error as a response. Error responses always "complete" the request in the sense that no other responses will be sent after an error response has been sent.
As noted in the
DDPError definition, each
contains exactly two fields:
Error messages are human-readable messages that can help you to
understand exactly what's causing the error, but are likely to be too
specific and technical for you to show to users of your
system. Instead, you should map
error_codes to messages that make
sense in your context.
Error codes adhere to a simple hierarchical structure. There are
categories are exactly the
same as the top-level categories in the API Documentation
subcategories are groups of error
codes within a
category that relate to the same class of errors. For
Hardware errors contain both errors related to networking
hardware that connects the DotDashPay platform to the Internet and
errors related to payment peripherals. These are
category using the
1000's place and each subcategory uses the
100's place to provide for future error codes to be added without
having to break backwards compatibility.
Unable to connect to DotDashPay Platform.
DotDashPay Platform is unresponsive.
Malformed API request. This is usually due to not setting a required field.
Unhandled internal error.
Did not receive a response from payment processor.
Did not receive a response from cloud-based logging provider.
Did not receive a response from cloud-based database provider.
Unable to find payment data to authorize/settle payment. This error occurs when a settle payment or authorize payment request is made to the DotDashPay Platform, but the platform does not have the necessary payment data in order to proceed with the request. This might occur because too much time passes between the payer inputting payment data and your software requesting that the Chip authorize/settle the payment.
The processing request was unsuccessful, e.g. the preauth/settle/void/etc request was declined by the processor. The associated error message will contain additional information about why the processing request was unsuccessful.
Unhandled third party error.
Unable to establish internet connection over wifi.
Unable to establish internet connection over cell.
Unable to establish internet connection over ethernet.
Unable to connect to wifi hardware.
Unhandled network error.
Unable to establish connection to payment peripheral.
Did not receive response from payment peripheral.
Attempt to call ReceivePaymentData without the cents field, but it was required for the connected hardware (e.g. needed for Apple Pay.
Data read from peripheral was not in the expected form.
Unhandled payment peripheral error.