Result codes and messages

Error codes are reserved up to 10.000, ensuring a dedicated range and reserving space for future codes. The range starting at 10,001 is reserved for TERP v5.

Validation and error messages, often called results, serve as the bridge between users and the intricate processes taking place behind the scenes. They are the means through which users receive feedback about the success, failure, or other outcome of their actions, offering a crucial layer of transparency and guidance. In this exploration, we delve into the significance of validation and error messages, examining the essential elements that contribute to user-centric interactions and the seamless integration of processes.

Global messages

Global messages are usually returned if incorrect or unknown identifiers are passed to the API.

If one of these results is returned, no further actions can be performed. The severity of these messages can be classified as high.

Validation messages

The validation of a cart can be called up at any time and contains various codes in response that reflect the status of the cart to be checked.

These results are informative messages. However, before a checkout is carried out, the validation result may no longer provide any results. Validation is carried out automatically before a checkout. The severity of these messages can be classified as low.

Cart messages

The cart area concerns all actions that modify or change a cart.

These results prevent the corresponding cart from being changed. Depending on the result, previous actions on the cart may be necessary. The severity of these messages can be classified as medium.

Payment messages

The payment area concerns all actions that link a payment provider to a cart. These are not yet problems or errors during the execution of a payment.

These results prevent the assignment of payment providers. In the case of a sales transaction, it is not possible to continue with a checkout. If a payment provider cannot be accepted and a checkout is carried out, this is prevented by the validation. The severity of these messages can be classified as medium.

Checkout messages

The results from the checkout area are exclusively errors that can occur during the completion of a sale or registration.

If one of these results occurs, the checkout cannot be continued. Depending on the result, this can lead to a support case. The severity of these messages can be classified as high.

Social events messages

The social event area concerns all actions, regarding all social interactions with the shop api.

Byndr messages

Byndr related processes and messages.

Remarks

The severity level is also used as the internal debugging levels.