Info |
---|
DRAFT - work in progress. |
Considerations:
Platform wide change, this should work on every market;
...
Create feature flag for this limit
Evaluate when creating PaymetMethods
Rule 3 - Repeated Delivery Failure
Status | ||||
---|---|---|---|---|
|
If the last order was paid in Physical Payments and there was a delivery failure (e.g. a joke order), the next order will only allow online payment
...
The tablet expeditor app has some order cancellations actions, these actions are sent through Delivery Events API but they are not stored in any of our databases.
We believe this ticket can potentially unblock us, to get the correct reason a delivery have failed:
, it’s currently at “To Do” statusJira Legacy server System Jira serverId 255417eb-03fa-3e2f-a6ba-05d325fec50d key IREQ-1123
Once we have the correct reason of order or delivery cancelations stored in the backend we’ll be able to identify, in the cash limitations methods, if the last delivery failed for some of the reasons we want and remove Physical Payments.
To dos:
Get together the cancelation reasons we want to consider for this rule
Create the feature flag for this rule
Implement on Cash Limitations check this rule