On our checkout, when you click the tip button it makes a background post to update the cart, the response for that post returns 2 errors:
TIP_ONLY_EMPTY_TERMS_ACCEPTED "This policy only accepts empty terms."
PAYMENTS_UNACCEPTABLE_PAYMENT_AMOUNT The sum of proposed payments cannot cover the total amount to be paid."
Here is our Store > https://admission.themobmuseum.org/
Has anyone had this problem or something similar to it?
We are also having this issue at https://myhealthypenguin.com
Support keep informing us that it is a theme issue however the problem still persists when setting the online store theme to the default.
If we inspect the request made with GraphQL in the network tab we can see that the tip is sent to the API however the response does not contain the tip. This is what causes the UI to flicker since we assume they pre-emptively update the UI then re-update the UI when the response comes back with the new cart data (Which is now missing the tip amount). The error array in the response also contains TIP_ONLY_EMPTY_TERMS_ACCEPTED & PAYMENTS_UNACCEPTABLE_PAYMENT_AMOUNT as described by the original poster.
Hopefully the technical team can get this one fixed soon.
Adding onto this with a potentially related issue. The following support thread was opened about subscriptions the day after we began experiencing this issue.
Similar errors about the checkout are being thrown there, however it's related to subscriptions.
I've attached a video where I replicate this issue. My theme is a fresh install of Breeze. This is not a theme issue which support keeps insisting it is.
We aren't doing anything with subscriptions, so that may be related somehow, but probably isn't the cause.
We have also tested the following themes which all experience the issue.
Origin, Craft, Dawn, and Refresh themes.
I dont believe subscriptions are the cause, but they're likely related since the issue began on the same day & is throwing the same errors. This is most definitely a server side issue on Shopify.
This looks like it has been fixed by Shopify. We're no longer experiencing this issue without making any changes on our end. The API is now no longer returning these errors.