#sharina_40619
1 messages · Page 1 of 1 (latest)
Hi Thank you for helping me
No I am not. I am one of the Support person at Electrum Charging Solutions
Would you be able to help us figure out the issue why customers are getting charged multiple times in their bank account?
This channel is exclusively for developers looking for help while building/troubleshooting their Stripe integrations. Since it's a public channel, I can't discuss account-specific charges or personal details.
I understand that
I can try to point you in the right direction but, ultimately, our support team will be able to assist. You can contact them at: https://support.stripe.com/contact/
does it have to do with the payment intents?
Not sure I follow the question. PaymentIntents are used to track the state of a particular payment. If you see multiple PaymentIntents for a given customer, each of those represents a separate intent to charge them. Stripe doesn't create PaymentIntents automatically; these would be created by some other action (some custom code, a third party integration, for example)
I see
I dont know if you can provide me more information but apparently whenever customer taps their fob into the charger it is not working, but they are getting multiple charges in their bank account and getting negative balance in their electrum cloud account
i dont know if its our software glitch or stripe issue
is it an API issue what do you think?
I recommend checking in with your team internally to discuss with the team who built Electrum's integration with Stripe. They should be able to diagnose why multiple PaymentIntents are being created
that is the problem. They already left the company 😦
I can't reach out to them anymore
so im trying to diagnose everything by myself
Do you have a PaymentIntent ID or customer ID you could share?
Please don't share private contact details here. If you have access to a Stripe Dashboard, could you log in, find a customer who has had duplicate charges, and share their ID with me? The ID should be in the format "cus_..."; please don't share their email address or name.
Ohh thank you! I will do that
i dont see the customer id
but I can when they were created
I can see*
If you click into the customer, you should see the cus_ ID in the URL
Sorry im in a test mode the whole time
thats why i cant see them
cus_NpPoBIP77OcmUE
we have gave him a $1325 refund in total
Thanks. Looking at the charge history, it seems like you're referring to the duplicate charges on 12/30? All I can tell is these were created using some Node code. Only the team or individual who wrote this code will know how it's being triggered
are you saying they did it on purpose?
this is not a glitch?
Is there anything I can do to fix it?
From what I can see, some Node code created multiple PaymentIntents. I don't know why but we received multiple requests to create these
Are you aware of any code changes made on/around when you started to see duplicate charge reports from customers?
is there any way you Stripe can prevent this from happening again?
we are not aware at all until we get tons of phone calls from the customers saying they were charged hundred bucks to a thousand
No, this isn't something we control. Code owned/written on the Electrum side is responsible for creating these PaymentIntents
Something in your system is making requests out to the Stripe API using Node.
Sure thing!
Yep, programming language. So there's some custom code written in Node that is creating these PaymentIntents
perfect. Thank you for that information
I think I am good for now
you already answered a lot of question
how can I reach out to you again in the future?
If you need help in the future with any refunds or other account-specific issues, the best place to go is our support page: https://support.stripe.com/contact/
If you are able to identify the new owner of the Node code/of your team's Stripe integration and they have questions, you can direct them to this Discord channel
So what will happen if we change our IT team? Is it better to replace the system we are using?
Hello! I'm taking over and catching up...