View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007654 | module Amazon Pay | main | public | 2024-05-27 11:16 | 2024-08-15 16:38 |
| Reporter | MarkusMichalski | Assigned To | |||
| Priority | high | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 2.1.5 | ||||
| Fixed in Version | 2.1.6 | ||||
| Summary | 0007654: Caputre type is incorrectly evaluated | ||||
| Description | I have noticed an error/difference in the evaluation of the Amazon status between Normal and Express. The exact problem seems to be that if the capture type is set to two-stage in the configuration, the status is evaluated incorrectly. With Express, the DispatchController correctly checks what is configured and the two-stage process is executed, which leads to the status "AMZ_2STEP_AUTH_OK". With normal Amazon, the one-stage process is executed in the OrderController without checking the configuration, which leads to "AMZ_AUTH_AND_CAPT_OK". I think the check for the two-stage process should also be integrated there. | ||||
| Tags | Amazon Pay | ||||
| related to | 0007652 | resolved | [email protected] | When config isOneStepCapture and Authorization&Capture is not done, it is still possible to finish the order |
|
|
Thanks for reporting this issue, in table amazonpaylog the 2steps express order is shown with "completed" while all other (1 steps and 2 steps with amazon pay) are shown with "completed and captured", so there is an visibel misshandling of 2steps amazon pay order. Additionally or strangly: in backend you see a different in both capture types. the one has always the value of OSC_AMAZONPAY_LIVESTATUS_NONCHARGEABLE, which says there is an error. So please also check this message and behavoir. Best Regards QA -SG- |
|
|
We fixed this in this PR https://github.com/OXID-eSales/amazon-pay-module/pull/184 |
