#wpgjetsfan13

1 messages · Page 1 of 1 (latest)

dawn vigilBOT
polar cliff
#

When you go through the "enter manually" flow that means you're not doing instant verification, and payment wouldn't actually proceed until verification is compelte (which is likely why you're aren't getting all the payment succeeded webhooks)

#

@vagrant shell please respond here and not in the main channel

vagrant shell
#

I clicked reply to myself, I'm not sure why it went in the main channel. Sorry about that!

polar cliff
#

no worries!

vagrant shell
#

Let me try again. The first flow:

2024-02-15_12-35.png 2024-02-15_12-38.png 2024-02-15_12-39.png
bleak kelp
#

Replies and threads are a bit different, but thank you 🙂 (also joining in here as karbi has to step away soon)

vagrant shell
#

The first flow makes sense, but the second one, I don't know how to test it to completion

#

So I wonder if I should expect to receive the same webhooks as in the first flow, and when should I receive them. Obviously, the payment intent has next_action, but it's a test, so I cannot perform the next action

bleak kelp
#

Yes, those two scenarios make sense. As karbi explained, the first case is using instanct verification so the payment can proceed. Using manual entry and microdeposits requires the customer to verify the code sent via microdeposite before the payment proceeds.

vagrant shell
#

right, so I should eventually receive payment_intent.succeeded once they complete this asynchronous process, does that make sense?

#

I just wondered if I could somehow test it I suppose. I mean, simulate this payment to completion

#

(in the second flow)

#

I suppose when it completes there should also be a checkout.session.async_completed or something

bleak kelp
bleak kelp
#

That allows you to complete the required action on the payment

vagrant shell
#

I saw that, I just don't know where to enter this info

#

Since I'm using checkout session

#

Because it automatically enter $0.01 for me as you see in the second flow, second photo

bleak kelp
#

Send transaction emails in test mode

After you collect the bank account details and accept a mandate, send the mandate confirmation and microdeposit verification emails in test mode. To do this, provide an email in the payment_method_data.billing_details[email] field in the form of {any-prefix}+test_email@{any_domain} when you collect the payment method details.

Common mistake
You need to activate your Stripe account before you can trigger these emails in Test mode.

vagrant shell
#

I'm not sure that will work with checkout as there is no payment_method_data field

#

But maybe customer_email would work? Not sure

#

It's ok. As long as I can listen for payment intent succeeded and failed I should be ok🤞

bleak kelp
#

I think this should work automatically when you use a matching customer email via checkout, yes, but you're right that note is a bit confusing in the Checkout context. I can share feedback internally to iomprove that!

vagrant shell
#

Thanks! I'm not sure because I used a test account with an email that I don't have access to. But now I'm curious so I wanna test that out

vagrant shell