CasuallyCaffeinated

[jade violet]

Good question. Checking in to whether we have a property for this and will get back to you

[ruby flame]

Thank you kindly!

[jade violet]

Unfortunately it is looking like we don't have a property on our payment methods or other related object that would easily show this. My colleague found that you could listen to payment_intent.updated events and look for the next_action to indicate which is being used

  type: "verify_with_microdeposits",```
And then set metadata as you mentioned. But unfortunately it is looking like the Payment Methods and Intents themselves don't keep a permanent record of this

Can you tell me a bit about why you are looking in to this stat?

[ruby flame]

Ah, I see, well thank you for looking into this!

Well, we have functionality in place that sends an email to a user whenever they add a new payment method to their account. Whenever they add an ACH payment method we'd like to differentiate between manually_verified and instant because the emails will need to be different

Can you perhaps tell me what the next_action.type would look like for ACH methods added via Stripe Financial Connections?

[jade violet]

Good question checking in to this. I only see the type for microdeposits. It is possible that instant verification doesn't use a next_action state so the implication may have been that you will know it was microdeposits if you see that and instant verification if it does not happen

[ruby flame]

Got it! That makes sense. Thanks!

[ruby flame]

Spoke with another dev on our team and we'll try to burn in a custom verification method into the variables we sen to our backend, in order to differentiate

Thanks again!

[jade violet]

Sounds good! Glad you were able to find a good solution here!