#altairsama69
weary mural
marble jasper
Hi there 👋 I would expect the payment to proceed after verification, but I'm trying to confirm that to ensure I'm not mistaken.
brisk sinew
but microdeposits take upto 2 days to confirm right?
so it'll be async in this case
so how should we handle this case?
marble jasper
Even if the account is verified, paying with ACH is still an asynchronous process, which we refer to as delayed notification payment methods.
https://stripe.com/docs/payments/payment-methods#payment-notification
With those you use webhook endpoints to receive Events when flows progress, so you can take the appropriate actions.
The Payment Intent will go into a processing status and you could listen for payment_intent.succeeded or payment_intent.payment_failed Events
https://stripe.com/docs/payments/payment-methods#webhooks
Or you can listen to Checkout Session related Events like checkout.session.async_payment_succeeded or checkout.session.async_payment_failed
https://stripe.com/docs/payments/checkout/fulfill-orders#delayed-notification
brisk sinew
no I got that, thats how we have done the integration
but my question is, in that specific checkout session if a customer chooses to do a microdeposit verification
stripe will send them a cent to verify the account right?
but since the verification itself is async
will the payment proceed forward?
or will we have to wait for the bank method to be verified
and then create a checkout link again
and resume the normal flow?
marble jasper
Oh okay, gotcha, that's what I thought the question was initially. Out of curiosity, did you try testing this in test mode to see how it behaved? I'm still trying to see if I can find a documented explanation, but testing may be faster.
brisk sinew
I did and it proceeded forward, but I didnt receive any events for it, I'm guessing thats because the checkout url wasnt created from stripe-cli
and we were sucessfully redirected to the success url
marble jasper
Hm, being redirect to the success url sounds expected, but not seeing any Events be triggered doesn't sound expected. Do you have the ID of the Checkout Session from your testing?
brisk sinew
I'll create another one, give me 2 mins
cs_test_a1iihcMXiM3r8z2GkkdLgXClUobjXhUscgj1FEYf1mQIC6BPNZsNJbPyME
I picked this up from the url
since no event was received
marble jasper
It looks like the associated Payment Intent is still in a requires action state.
Can you try using the test email format shown here to trigger the microdeposit email for test mode?
https://stripe.com/docs/payments/ach-debit/accept-a-payment?platform=web&ui=checkout#send-transaction-emails-in-test-mode
I think you'll need to do so to trigger the verification portion of the test flow and progress it.
What type of Events are you listening for? I'm seeing related checkout.session.completed and payment_intent.requires_action Events being generated which are failing to be sent to your webhook endpoint.
brisk sinew
yeah checkout session completed and the async payment status ones
I'll try the guide out thanks
issue is I am on localhost, so the only viable way is to listen to events via stripe-cli
marble jasper
Gotcha
brisk sinew
also I cant send emails unless we activate our account and I'm not authorized for it, I'll get back once I can send an email. thanks!
just one last thing, how do I forward these events to stripe -cli
which in turn will forward it to my local endpoint
marble jasper
You don't forward Events to the CLI. You can use the stripe listen command to initialize the built-in listener offered in the Stripe CLI. It will automatically begin listening for Events that the account you're logged into the CLI as would receive. You can use the --forward-to (and --forward-to-connect if you're testing Connect related Events) parameter(s) to send those Events to endpoints on your local machine.
https://stripe.com/docs/cli/listen#listen-forward-to
brisk sinew
ah gotcha thanks!
marble jasper
Any time!