Posted: January 1, 2023 at 4:16 pm
|
Hi there, We’re getting this recurring issue that the total amount due that is passed to Stripe is one cent short of the actual amount due. This leaves the registration as pending payment/incomplete. s/s of the transaction below. This has been happening the past couple of weeks and do not know why and do not know where to start. https://capture.dropbox.com/pqdFlLKTB3wmyokd https://capture.dropbox.com/pqdFlLKTB3wmyokd Thanks, Derek |
|
https://www.dropbox.com/s/zgxtnhifr398c8u/Screen%20Shot%202023-01-01%20at%203.12.31%20PM.png?dl=0 |
Hi Derek, I’ve just run a quick test registration on your site (it is under my name, you can cancel/remove it if preferred), stopping at the final step to pay via Stripe. The total amount shown on the Stripe checkout was correct for me, I didn’t complete payment to confirm from there, but do you happen to know if that is the case for the users this is happening to? (Longshot I know as most people won’t notice the 1-cent difference before clicking pay) Also, I noticed you are using the ‘legacy’ Stripe integration (Stripe Checkout) rather than Stripe elements (which is the recommended integration method for Stripe). Is that by choice or have you just not updated the setting to use the newer integration? |
|
|
Hi Tony, I just didn’t update the Stripe, but did just now. Then I performed two test transactions on the two events that have been having issues. Same result for each: This time, the registration was approved. However, it showed the full amount being charged on the EE side, but one cent short on the Stripe side. I’m at a loss on this… I’m obviously not worried about one penny, but it’s more that when people register we have to go in and manually approve their registrations. This is happening on 2 classes: Any ideas? Thanks, Derek |
|
Oh one thing to add, I looked at all of the registrations within those two events. Lino event – all transactions Nov 8 of earlier were calculated properly, all after Jan 1 were not. Barbara Callow event – all transactions before Nov calculated properly, all after Dec 28 were not. Not sure if that helps with anything. Thanks, Derek |
Ok, so just so you know Stripe elements is recommended because it supports 3DS and other authentication methods used by Stripe, without it your payments can fail.
I totally understand why this would be frustrating on your end and will happily investigate it, the problem is I can’t reproduce the same issue with those prices on my sites. So either something on the event/ticket setup is different or something on the server is different. Can you link me to one of the events so I can take a look? (You can mark your reply private if preferred) |
|
|
This reply has been marked as private. |
Yeah, same again. Can I take a look over the payment logs on your site? If so you can send temp login details using this form: |
|
|
Hi Tony, This seems to have been resolved with the updated payment gateway. We haven’t had a problem since. If we do, we’ll pick up on this thread. Thanks for your help. Derek |
Hi Derek, Apologies I had intended on replying to this thread to give after having a look over the site. In short, I still can’t see a reason for the above to happen, when I work through the code and output the values EE will be using through each step they are correct. Obviously, that’s not the case for some of your transactions, so if this does start happening again, please let me know, and I’ll try to work through it on your site (if thats ok!). |
|
The support post ‘Payment is 1 cent short’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.