View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007509 | module Unzer | General | public | 2023-08-04 12:13 | 2023-09-12 14:15 |
| Reporter | QA | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 1.1.0 | ||||
| Fixed in Version | 1.1.3 | ||||
| Summary | 0007509: Order number 0 is not updated when risk management transaction timeout in 3rd party API | ||||
| Description | An customer reported: It seems that the problem only occurs when a correct CC is specified and an error occurs during processing on the part of Unzer (e.g. a timeout during the risk check / Unzer API briefly unavailable). An investigation at Unzer showed that a RISKMANAGEMENT_ERROR (risk management transaction timeout) was logged on their side. The messages returned according to Unzer are also correct according to their log files. This means that the Unzer module should not allow the orders to pass. However, the module does let the orders through. As a result, the orders with order number 0 were created in the store and marked as completed. The internal status is "not finished". The analysis on the customer side of the log files has shown that at least no order confirmation was sent to the customers in question. However, the information provided by the customers themselves is contradictory. At least one customer thinks he has seen the thank you page, but has not received an order confirmation either. | ||||
| Tags | No tags attached. | ||||
| related to | 0007485 | resolved | [email protected] | Order number 0 is not updated when you get stuck in the payment process. |
