#duranmla

1 messages · Page 1 of 1 (latest)

muted trenchBOT
sturdy belfry
#

👋 happy to help

#

would you mind sharing some examples?

bright lava
#

Sure, wondering if event log is something that I can share safely here.

sturdy belfry
#

you can share IDs

bright lava
#

Sorry, read late about the IDs. I can copy/paste ID of something you can work out.

#

I was trying to show you the example this customer we needed to refund for the unintended charges we did.

#

I am looking into the code of the organization and I see only a single place where the charge is being created.

sturdy belfry
#

you can delete the screenshot if you want

bright lava
#

Any of those IDs are useful? Or which ID is useful for you?

sturdy belfry
#

the evt_xxx or the Payment Intent ID pi_xxx

bright lava
#

Gotha... 1 sec

#

Ok, there are several evt in this transaction, I will attach only one evt and one payment just to start

  • pi_3MiIIgFm3D5E2CnB1UoAP8hI
  • evt_3MiIKcFm3D5E2CnB1cOmpAFG

Customer id: cus_NTEj2iqmrQbAoV (just in case it is useful)

sturdy belfry
#

ok thanks 🙂

#

taking a look

bright lava
#

Then you have:

  • evt_3MiIGMFm3D5E2CnB1Bowm6HV
  • evt_3MiIIgFm3D5E2CnB1OdocJlZ

As other two events with the uncapturable payment

#

Also as context we are using stripe.charges.create API to make the charge. I'm not the author but for what I see here the capture is being set to true. And the payment is being done in a embedded UI using stripe SDK in javascript.

sturdy belfry
#

so basically there were 3 PIs created at the same time for the same customer with the same data

bright lava
#

Yes, it seems like that. Although not extrictly the same time they have few seconds difference

#

There is a span of 4 minutes where the user seems to somehow create those three PIs

#

And this also happen to different users within the app. But not all, which makes me think this happens after some "payment errors". I have tried on the sandbox to replicate and I haven't being able using the test cards.

sturdy belfry
#

maybe each time they update their cart

bright lava
#

Could you elaborate on that? (Sorry)

sturdy belfry
#

I really don't have access to your code to see what's happening

#

it's just a theory

bright lava
#

Sure sure. I understand. But you have more context on Stripe so I can test the theory on my end

muted trenchBOT
bright lava
#

I guess that a good question to answer is “What are the possible reasons to create an ‘uncaptured payment’? And how I can reproduce that behavior on the sandbox?”

sturdy belfry
#

any created payment with capture_method: 'manual' is considered an uncaptured payment

bright lava
#

Ok, perhaps I will go back to the team and try to take a look to the “cart” if we are creating one and also under the hood of this flow.