#initialed85

1 messages · Page 1 of 1 (latest)

tired ibexBOT
misty anvil
#

The PaymentIntent which shipping address is null, was it confirmed successfully?

#

What's its status?

rare berry
#

It says the payment succeeded but (due to bugs in our system) the most recent webhooks were not handled successfully- could this block the progression in some way?

#

(is there a behaviour that hides the shipping address until the payment intent is complete?)

misty anvil
#

Not sure. How are you confirming the PaymentIntent? Checkout or PaymentElement?

rare berry
#

No idea- I see in our mobile app (the initiator of it all) we refer to a PaymentSheet

#

(stripe react native lib)

#

basically at some point we get a webhook on our side and (provided we don't hit a particular bug) we spit out a 200 and I guess all is fine

in some cases we hit a bug and that webhook is never happy and also those payment intents have no shipping address

so i'm theorizing that those cases are the ones that (despite having a payemt intent with a succeeded payment) are not revealing the shipping address to us for some reason

ultimately what i'm trying to work out is

  • do i have a bug that's losing a shipping address at the time of payment intent creation; or
  • is there a behaviour that hides the shipping address until a payment intent webhook has been handled with success
misty anvil
#

I don't think #2 is the case. Maybe the PaymentSheet in mobile has some branched out scenario, ie. if customer used a Card vs used Wallet like ApplePay/GooglePay

#

We may know if you provide 2 examples PaymentIntent Id (pi_xxx) for the having and not having cases

rare berry
#

failed: pi_3NIlUAHwT4akAWyk0NwrSlYR

for the failed one, payment succeeded but our webhook handling of it failed

succeeded: pi_3NIUzCHwT4akAWyk18wd8eze

for the succeeded one, payment succeeded and our webhook handling succeeded

image.png image.png image.png image.png
#

(hence my thinking about the correlation between the failed webhooks)

misty anvil
#

So if you look at the confirmation requests of those 2 PI
https://dashboard.stripe.com/logs/req_bRvnfq2abPd0L1 <- no shipping address passed in
https://dashboard.stripe.com/logs/req_sx4KhrcA0uP78M <- shipping address passed in

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

#

I believe that's only the differences based on client implementation

#

first one seems to be native iOS, second one is ReactNative on Android device

#

We would find out if you can get your client developers compare two implementation side by side

rare berry
#

oh very interesting- it should be the same, it's all Expo (sugar for React Native) but naturally we've got users of both flavours of devices