#asrob
edgy geyser
lusty vigil
Hello 👋
I can help take a look
lusty vigil
What differences are you seeing exactly?
sonic bay
The actual error:
"message": "This PaymentIntent's payment_method_options could not be updated because it has a status of succeeded. You may only update the payment_method_options of a PaymentIntent with one of the following statuses: requires_payment_method, requires_confirmation, requires_action."
"type": "invalid_request_error"
We can't update the Stripe meta data with the order id because of the above error
lusty vigil
Right, you said you talked to someone last week who said it wasn't possible once the payment intent had succeeded? So that sounds like expected behaviour no?
sonic bay
Every non-card present transaction happens using the method I described (adding meta data after the fact). That's what we'd like to do with card present and it is working sometimes. Bottom line we'd like to add the order id to the transaction and it only works sometimes. The conversation last week made me think updating CP transactions just was not possible.
Which now does not appear to be the case.
lusty vigil
Gotcha, let me take a deeper look
sonic bay
Thank you!
lusty vigil
So it looks like there was a bug that prevented the PaymentIntents from getting updated after succeeding, but a fix was released about a week ago and it should now work.
have you tried updating the PaymentIntent recently?
sonic bay
Possibly. Let me see if I can find out.
It doesn't look that way. I'm thinking you're asking to confirm the fix resolved the problem?
lusty vigil
Yes. You could try creating a test mode PaymentIntent
The example you shared is before the fix was deployed
sonic bay
I'll do some test transactions and circle back. Is there some way I can reference this conversation or perhaps the fix for someone else?
lusty vigil
You can link back to this thread
sonic bay
Sorry just found it. Sorry to make you do Discord tech support ;). Anyway thank you @lusty vigil