We are using the ACTION_CLOVER_PAY intent in our fully integrated app to accept an additional payment on an existing order that had line items added via the REST API. The payment screen shows briefly but then closes and resumes in our app.
I suspect the following is happening.
- We have a paid clover order.
- Line item is added to that order via the REST API (making it partially paid)
- ACTION_CLOVER_PAY intent is started immediately after the item is added.
- The payment screen closes because the order has not caught up with the line item update from the REST API.
Is there a way we can manually trigger the order in the clover device to refresh it's data from the server so the new line item will be present and the user can add the payment for the new line item? Or do you suspect something else is going on?
NOTE: Opening the ACTION_CLOVER_PAY intent a second time or waiting a couple seconds then opening the ACTION_CLOVER_PAY intent works fine. This is why I suspect the order in the clover device is not being updated.
Thanks for the help.
