Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

DRAFT - work in progress.

Considerations:

  1. Platform wide change, this should work on every market;

...

  1. Create feature flag for this limit

  2. Evaluate when creating PaymetMethods


Rule 3 - Repeated Delivery Failure
Status
colourRed
titleBlocked

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:

    Jira Legacy
    serverSystem Jira
    serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
    keyIREQ-1123
    , it’s currently at “To Do” status

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:

  1. Get together the cancelation reasons we want to consider for this rule

  2. Create the feature flag for this rule

  3. Implement on Cash Limitations check this rule