max-addington_api | Stripe Developers | Page 1

royal cradleBOT Nov 21, 2024, 2:32 PM

#

👋 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/1309164417149173781

📝 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.

max-addington_api, 1 day ago, 8 messages

#

steep pier Nov 21, 2024, 2:34 PM

#

Additional context: We will be using the financial connections product, not the Charges API

tacit spruce Nov 21, 2024, 2:34 PM

#

hi there!

#

I'm not completely sure, but that's something you could test in test mode and see if it works or not?

steep pier Nov 21, 2024, 2:36 PM

#

Sure, I will do that if there's nothing in the documentation about it. But it feels like this is an important thing to have in the developer docs

tacit spruce Nov 21, 2024, 2:37 PM

#

that's a good point, I'll notify the team working on this.

steep pier Nov 21, 2024, 2:43 PM

#

Thanks. And if you could find an answer for me in the meantime, that would be extremely helpful 🙏

#

My team is working on the backend functionality, and another team is creating the payment element and all the UI stuff. So it's hard for me to test this before we have a UI to work with. But I'm going to work on creating a local test frontend using the payment element to test the flow, it will just take me some time

tacit spruce Nov 21, 2024, 2:46 PM

#

just so I understand your flow:

first you try to save a us_bank_account payment method with the Payment Element
then, before the microdeposit has arrived, you want to try to chage the PaymentMethod?
now that I'm writing this out, I'm pretty sure this won't work. but I can give it a try.

royal cradleBOT Nov 21, 2024, 2:46 PM

#

stone kestrel Nov 21, 2024, 2:51 PM

#

👋 stepping in

#

Are you using a SetupIntent up front here to set up the US Bank Account PaymentMethod?

#

If so, then you can't attempt to charge it until microdeposit verficiation has been completed.

#

Similarly, if you are just attempting to charge it immediately, it will require microdeposit verification before the charge is actually created

#

So, mostly, the answer to what you are asking is "no, that's not possible".

steep pier Nov 21, 2024, 2:53 PM

#

Yep, we're using a SetupIntent

stone kestrel Nov 21, 2024, 2:53 PM

#

Gotcha, yeah you can't access the PaymentMethod until microdeposits are completed.

steep pier Nov 21, 2024, 2:53 PM

#

if you are just attempting to charge it immediately, it will require microdeposit verification before the charge is actually created

What do you mean by this?

stone kestrel Nov 21, 2024, 2:53 PM

#

If you just use a PaymentIntent instead of a SetupIntent

#

So you both are collecting, verifying, charging all in one step

#

It would first require microdeposit verification and then once that was completed a charge would automatically be created.

#

But the charge won't occur until microdeposit verification is completed.

#

As noted, the best thing to do here really is to test this all out

#

So you can get a feel for the flow.

steep pier Nov 21, 2024, 2:54 PM

#

I see, that makes sense. That would be using the Payment Element, right?

stone kestrel Nov 21, 2024, 2:54 PM

#

Yep

steep pier Nov 21, 2024, 2:55 PM

#

And if we use the Payment Element, then the payment methods themselves won't be reusable, correct? Since no SetupIntent is involved

stone kestrel Nov 21, 2024, 2:55 PM

#

They are, you just need to use setup_future_usage with your PaymentIntent.

#

https://docs.stripe.com/api/payment_intents/create#create_payment_intent-setup_future_usage

steep pier Nov 21, 2024, 2:56 PM

#

Got it, thank you

#

Will we receive webhooks at the setupIntent level for these setup_future_usage bank accounts?

stone kestrel Nov 21, 2024, 2:57 PM

#

Not exactly sure what you mean by that?

steep pier Nov 21, 2024, 2:58 PM

#

If we go with the route you just described (i.e. use the payment element with setup_future_usage), and the bank account entered requires micro deposit verification, will we receive webhook events when the verification process is completed?

stone kestrel Nov 21, 2024, 2:59 PM

#

Ah, yes, you would receive a payment_intent.processing Event: https://docs.stripe.com/api/events/types#event_types-payment_intent.processing

#

The PaymentIntent in this case would move from a status of requires_action to processing

#

And then succeeded once the charge succeeds.

steep pier Nov 21, 2024, 3:00 PM

#

Awesome. And how would we access the payment method for future usage in this scenario?

#

Sorry for all the questions, this is my last one I promise 😄

stone kestrel Nov 21, 2024, 3:02 PM

#

No worries -- we are here to help.

#

The PaymentMethod will be automatically attached to the Customer assuming you also pass a Customer ID to the PaymentIntent (which is necessary to re-use any PaymentMethod) so you can always just list PaymentMethods for hte Customer if you want using https://docs.stripe.com/api/payment_methods/customer_list

Or, the PaymentMethod will be directly associated to the PaymentIntent so you can get it from there: https://docs.stripe.com/api/payment_intents/object#payment_intent_object-payment_method

steep pier Nov 21, 2024, 3:04 PM

#

Heck yeah. Thank you so much!

#

Is there any benefit to using the SetupIntent object over just collecting the payment method in the payment element?

stone kestrel Nov 21, 2024, 3:14 PM

#

You use a SetupIntent with Payment Element as well?

#

So not sure what you are referring to there.

#

But you should only be using a SetupIntent if you want to save a PaymentMethod and not charge it immediately.

#

If you are going to be charging it immediately you should always be using a PaymentIntent.

steep pier Nov 21, 2024, 3:15 PM

#

I tried the demo here: https://docs.stripe.com/financial-connections

But it sounds like this is an optional UI element when using FC, because we can just collect the bank account information in the payment element, correct?

Stripe Financial Connections

Access permissioned data from your users' financial accounts.

stone kestrel Nov 21, 2024, 3:16 PM

#

You can indicate you only want to verify via microdeposits, yes. But both options are collected via Payment Element.

steep pier Nov 21, 2024, 3:16 PM

#

Ah. So is that UI component in the demo I linked actually just the payment element?

stone kestrel Nov 21, 2024, 3:16 PM

#

Yes

steep pier Nov 21, 2024, 3:17 PM

#

🤦‍♂️

stone kestrel Nov 21, 2024, 3:17 PM

#

That modal is triggered via Payment Element

steep pier Nov 21, 2024, 3:17 PM

#

Got it. Alright, I think I have all the information I need for now. Going to start working on testing this in Stripe's test env. Thanks again!

stone kestrel Nov 21, 2024, 3:17 PM

#

Sure thing

steep pier Nov 21, 2024, 3:17 PM

#

You can mark this as case-closed 😄 have a great day

#max-addington_api