#moistcode - PI & Connect
void swan
Payment Intents are the primary mechanism to collect payment and they work perfectly well with Connect. Do you know what account types and charge types you would be using?
wooden tulip
Not at the moment. I ask since I swore there was a time a few months back when they didn't work well together. It's been a while since I've used Stripe haha
wooden tulip
Does Stripe have a public roadmap somewhere? I'm curious if Stripe will provide automatic tax filing at some point in the future.
void swan
I don't think we have that on the horizon but I wouldn't know if it was a long term goal either.
With respect to Payment Intents, it depends on the type of charge
You can see our table of the types here: https://stripe.com/docs/connect/charges
And, for example, a snippet creating a Payment Intent on a Connected Account here: https://stripe.com/docs/connect/direct-charges#create-a-charge
wooden tulip
When creating a SetupIntent or a PaymentIntent to pass along the client_secret to the front-end to use with PaymentElement, does setting automatic_payment_methods automatically filter between what is supported with recurring payments and single payments? The SetupIntent and PaymentIntent doesn't seem to have a parameter that differentiates between the two.
hollow ginkgo
👋 I'm just hopping in since @void swan has to head out soon
wooden tulip
Hiya Karbi! No rush on my questions if you have more pressing matters.
hollow ginkgo
Yes, automatic payment methods should be able to differentiate between which payment method types can be used for recurring payments/be saved for future usage
wooden tulip
I'm curious how that would work. I believe the PaymentElement uses the client secret to determine what to show. The client secret is generated by the backend when creating the SetupIntent and PaymentIntent but when creating these Intents, the BE doesn't have a parameter to tell SetupIntent and PaymentIntent whether or not this is for something recurring so I'm not sure where that information would come from.
hollow ginkgo
With Payment Intents we check for setup_future_usage - with Setup Intents only some payment methods can be used with them. You can see a full chart of what's available here https://stripe.com/docs/payments/payment-methods/integration-options#additional-api-supportability
