#mohannad57

1 messages · Page 1 of 1 (latest)

mild agateBOT
scarlet moon
#

Sure thing. Can you share the payment intent id's? Could be the customers just don't finish paying

#

Would be helpful if you share some successful ones too to compare

versed shell
#

pi_3Mrho2LsodYOIQPy1ZUWNilq

#

that was a failed one
and also these are failed
pi_3MrhniLsodYOIQPy0D1eWxRL
pi_3MrWTpLsodYOIQPy0q5NbcFv

#

here is a success from the same stipe account (hyde park success)

pi_3MrXokLsodYOIQPy12BlEZ2d

here are some other failed and success from another account (edmonton):
fail: pi_3MrZgkCV8vmA6JKt1QKwLAIK
fail: pi_3MrX48CV8vmA6JKt0XZKeTzn
success: pi_3MrZhCCV8vmA6JKt18XsA5BB

scarlet moon
#

So the failed PI's didn't fail. It's just we received no more api calls on them after creation.

#

They're in a status of requires_payment_method

#

So, I recommend improving logging within your integration so you can get some data on why the customers didn't complete payment

#

All we can see is the only API request that was made for those PIs is their creation request

versed shell
#

so these were not due to a connection error or something like that

#

??

scarlet moon
#

From our end we can't tell. We only received the initial creation api request. If there was a network issue on your end, only your logs would be able to indicate that

versed shell
#

we have seen one uncaptured PI
can we capture that from dashboard, as it is asking for authorisation?

scarlet moon
#

Hm can you share that ID?

#

You are doing separate auth and capture?

versed shell
#

one sec

#

I'm trying to get it back

scarlet moon
#

No rush

versed shell
#

pi_3MrXg7BAWeA01Zfu06MoUjBj

#

here it is

scarlet moon
#

Oh yeah

#

It's been authorized but not captured

#

So you need to call capture

versed shell
#

but why wasn't automatically captured as the rest?

#

or did we never sent the capture payment API?

scarlet moon
#

capture_method: "manual"

versed shell
#

Yes i noticed that,
but how did this get set as such?

#

oh ok thank

#

thank you very much will check the code on our side

#

bye