#david2_webhooks

1 messages ¡ Page 1 of 1 (latest)

gaunt fulcrumBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1308211142736351234

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

daring gyro
#

Hello! Not sure I completely understand. This Payment Intent has several confirmation attempts, all of which resulted in requires_action, and all of which triggered a distinct payment_intent.requires_action Event. There are no separate updates to the Payment Intent which only changed the Payment Method.

inner plank
#

It's my understanding that this payment_intent is no longer in the next_action='verify_with_microdeposits' state

#

pi_3QMdI5AQbHn4ElzT2qSwrhs2

#

what I did was:
-try to pay with bank accoutn that will require microdeposits
-user says "nah, I want to pay with another bank account", and uses the stripejs provided collectBankAccountForPayment
-paymentIntent is moved out of "next action" state

daring gyro
#

Oh, I see. Hang on...

daring gyro
#

The Payment Intent is currently in requires_confirmation state, which is a bit odd because it seems to have happened on our side, not yours, so there's no way you'd be notified this happened. As you mentioned above, there is no event for this. It seems like this might be an oversight on our part, but give me a bit longer to investigate further...

daring gyro
#

I'm not sure if this Payment Intent being in this state is expected behavior or a bug. It seems like an edge case related to what the customer went through as far as selecting how to pay. You should be able to complete the payment by confirming the Payment Intent, though.

#

It does seem like a gap on our end, though, so I'll flag this internally for improvement.

inner plank
#

I think ideally there would be collectBankAccountAndJustCreateAPaymentMethod then we'd deal with updating relevant other objects and my own backend state.

#

is there a reference number for this ticket so I can plop it in some comments on my end, for future maintainers' sake?

daring gyro
#

To clarify, when you called collectBankAccountForPayment it should have returned the Payment Intent at the end of the process, and it should have been in requires_confirmation state at that point. Was that what happened, or did you get back something else?

inner plank
#

Not sure what I got back, but the paymentIntent is in the requires_confirmation state, as expected. I just wondered if I should expect to be informed of this asynchronously via a webhook event; I can synchronously ping my server about this change, but then the risk of client crashing is there.

gaunt fulcrumBOT
daring gyro
#

The only way you'd be aware of this server-side is if you set up some kind of polling, which isn't recommended.