#mangell_terminal-error
1 messages ¡ Page 1 of 1 (latest)
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- mangel_terminal-error, 3 hours ago, 55 messages
- mangell03_code, 6 hours ago, 25 messages
- mangell03_code, 1 day ago, 16 messages
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1260729161740324916
đ Have more to share? Add details, code, screenshots, videos, etc. below.
mangell_terminal-error
So little amount of chars to describe.
@cosmic meadow looks like the same exact question than you had earlier. This error means the PaymentIntent was never confirmed successfully or paid
I have been cutoff with little help. I have many closed thread you can review.
Ok- your sim SUCKS.
Help me work thru your horribkle docs to get to a working position.
What is the secret to make a perfectly working Sim work with a WisPose that took payments, showed approval, put the transactions in my test location, and then just craps out after trying to transitioj to physical. That's all I need help with. The docs are terrible in this situation.
Unfortunately I don't understand the question. I get you are super frustrated but ultimately I still need to understand what is not working exactly.
I see the error you have, it's because you seem to actively try to capture a PaymentIntent that was never successfully confirmed.
I had a prefectly working Sim reader. Your adivce from this channel (you can look it up)- was just register the physical to your test location., and swap reader IDs. It will work. Nah dude. Now I just have a mess of code.
What is the best practice to migrate from. a working sim reader to a WisePose resgistered in a test Location? No one can help- and the docs are not helpful.
Please, focus on getting the help you need, not ranting. I will not read past threads, but I remember talking to you earlier and you were mixing up multiple parts
As far as I could tell at the time you did properly call processPaymentIntent() and got it successfully confirmed.
I don't have any best practice for migrating I'm sorry. So assume there is no such thing and focus on making your real reader work in Test mode.
So with that in mind: explain where you call processPaymentIntent() and what's not working
I am not ranting my firend. I am looking for realk honest help. How to migrtate from a working Sim reader to a physical WisePos.
Point at docs that make sense- becuase I can't find them.
Step 1- Integrate to our sim
Step2- Confirm Sim works (check)
Step3- Register you WisePos in you test Location (check)
Okay we have two options
- You move this conversation to 1:1 support over email, you get help async and they can look into your code and have the context of your email: https://support.stripe.com/contact
- You focus on getting something working, without the comments about how our docs suck and nothing works and this is bad. I get the frustration, I've been there, I don't even disagree that our docs are often not great. I am an engineer and I want to help you get there so ignore all the "noise"
Step4- Migrate you code to work with you new phsyical device in test mode (NOT checked)
Ok- so you have no recomendations, and you don't know how to help?
So with that in mind: explain where you call processPaymentIntent() and what's not working
It should be simple. Had amazing success with the sim. Now it's no one knows how to help.
Come on this is such a waste of both of our time
you're ranting about how everything is bad instead of spending 10 minutes with me to get it working
I can help you. I have now said the same thing 3 times. Please focus on my question, ignore the frustration and the docs nonsense.
- Where do you call
processPaymentIntent() - What is not working after that
This is literally the 4th time I've had this conversation today.
Please let me help you. You spend so much time saying how nothing helps instead of answering the question
Earlier today I did get you to a successful PaymentIntent.
I am not gonig to repeate myself. I know how you will get feedback. Pleae review all previous threads.
Sounds good. Then I am sorry but we can not help you on Discord. Please use our contact form to get 1:1 async support help moving forward: https://support.stripe.com/contact
Sounds good. Then I am sorry but we can not help you on Discord. Please use our contact form to get 1:1 async support help moving forward: https://support.stripe.com/contact
What? You aare shutting down and punting to you horrible docs?
This will not go well for your team.
I repeatedly tried to ask you to help me help you. I understand you are really frustrated and mad, but you have not said one thing in this thread to help you. I also am not sending you to our docs, I am sending you to our support team so that you can get 1:1 asynchronous help.
I have tried to work with you and I have asked questions to help you and if you read the thread from the start you will see you haven't shared anything.
I get that you demand that I read all past threads, but this is not something I will do especially as I was already with you in a past thread.
Can you connect me with someone more knowable and kinder?
I'm the person on shift right now so that's not possible sorry. All you need to do though is focus on your question. Share your exact code for the part I mentioned and I will get you there likely in a few minutes.