Testing before launching my new store and have come upon this error on checkout with varying amounts, first amount was $38.01, second amount was $62.17. I had a previous order go through for $62.17 but Stripe only charged $16.32 for the order. Had another order for $52.67 but Stripe only charged $51.17? Previously I've had 7 successful stripe orders until these problems started happening. Any idea what's up with these numbers not matching, and the following error which appears on the final checkout form on submit.

We received the following error processing your card. Please enter you information again or try a different card. Invalid amount. Amount must be a positive integer in cents.

Comments

bradhawkins’s picture

bradhawkins commented

Has this been resolved? Also, was this happening in the Stripe "testing" environment or a "live" setting?

I haven't seen this type of problem myself, can you give any other info? For example, are you using any other payment gateways, PayPal, etc.? Also, did you have any special taxes or coupons?

iler’s picture

iler commented
Status: Active » Postponed (maintainer needs more info)

@drupleg, could you give exact steps to reproduce this problem. This is something that I haven't faced before.

rowbotony’s picture

rowbotony commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Thank you for the response. I put this on the back burner for a few weeks as I was getting burned out on the project. I came back to it and still had the negative integer problem. I decided to disable, uninstall, and delete commerce_stripe. I then downloaded a fresh copy of the module, enabled it, and the problem was fixed. So now I cannot reproduce the error. I had a backup and diffed the old site code with the newly re-installed code and could not see anything that would have caused such an error. All I can figure is that - I had been experimenting with userpoints on checkout, perhaps some of those points were being applied on checkout even though the userpoints module was disabled... I just don't know what it was, and can't reproduce it. Closing this issue, will reopen if it occurs again.

Thank you,
--Tony