Error Handling / Logs

Various situations (e.g. no interface/internet connection, incorrect parameters) may result in a process failure (e.g. Convercus API-response or POS-timeout). These errors must not cause integration failure and must be handled appropriately. This applies especially to processes without loyalty connection, which must not be affected by loyalty-related errors.

Timeouts for different process steps should not exceed 1.5 seconds.

Critical or process-relevant errors (e.g. unrecognised card, no connection) must be clearly displayed to the operator. All error messages should be user-friendly and avoid technical jargon.

The system must be operable offline. Sending receipts once the connection is restored is essential to prevent reporting gaps. Only receipts with connection errors (5xx) should be resent; functional errors (4xx) must not be resent.

To support error analysis, failed requests and responses must be logged and made available to customer support contacts. Logs should preserve original request and response formats.

Summary

• Errors must not crash the integration
• Loyalty errors must not affect non-loyalty processes
• System must be offline-capable
• Transactions with connection issues must be automatically resent
  • Only 5xx errors are re-sent; 4xx errors are not
• Process-step timeouts should not exceed 1.5 seconds
• Error messages must be user-friendly
• Error handling must be documented
• Requests and responses must be accessible for support