#asrob

1 messages · Page 1 of 1 (latest)

oblique marshBOT
native inlet
#

What's the recommended way of dealing with the scenario in which a customer starts a transaction but the cart on the platform side expires before payment completes?
You should just make sure to update the expiration on the cart at the time of payment such that the payment has time to complete. There isn't really a recommended approach, since Stripe doesn't really work much with carts.

Is there a way to close or not allow the payment to go forward specifically with wallets (Google/Apple)?
I'm not sure what you mean by this.

lament shard
#
  1. Yea we had it such that the expiration got bumped at the time they clicked pay but it's currently causing problems with Apple pay.
#
  1. In the past calling event.complete('fail'); indicated (at least with Google) in the UI that they could no longer pay.
#

So dialog pops to pay. Customer takes too long. Dialog is changed via event.complete('fail'); to show that the transaction will need to be redone.

#

Right now once for example the Apple Pay dialog pops we have zero control so ATM we are "allowing" the payment to go through and then refunding it when we find out it's expired at the time the webhook comes in.

native inlet
#

I believe if you simply cancel the Payment Intent, it will error out if the customer attempts payment. That being said, I don't think there's a mechanism to surface this in the dialog that pops up. It would just be handled like any other failed payment in that case: https://stripe.com/docs/api/payment_intents/cancel