#Svetlana Ivanova

1 messages · Page 1 of 1 (latest)

ocean ridgeBOT
alpine ingot
#

Hi there!

#

I think that:

  • active the capability has been requested and is active
  • pending the capability has been requested but not active yet
  • inactive the capability has not been requested
minor root
#

is it possible to change the active state back to inactive? and how?

alpine ingot
minor root
#

So, it will work even when the capability has been requested by connected account user and successfully activated with no dependence of the account settings?

alpine ingot
#

Can you clarify what you mean? And what type of connected account are you using (Standard, Express, Custom)?

minor root
#

We use standart account. For example, SEPA is active for connected account by default with no additional actions. For PaymentIntent API Stripe has options in dashboard that help to manage the payment methods list that should be available for the connected accounts by turning the 'on', 'blocked' or 'off' in dashboard and passing 'auto' parameter in request of Payment Element. We can not do the same with SetupIntent because 'auto' option is not available in Payment Element with SetupIntent? So, we need to use 'manual'. But we still need to understand what options are available for our Connected account. We can't request the payment methods directly because there is such endpoint. The only parameter we can reques is list of capability options. But looks like there is no match between 'active'/ 'inactive' capabilities and 'on'/ 'off'/ 'blocked' options for connected account. So, I want to feagure out the way how we can match them. If we can. Means can we make 'inactive' capability that is 'blocked' in payment methods?

alpine ingot
#

We can not do the same with SetupIntent because 'auto' option is not available in Payment Element with SetupIntent?
Correct.

minor root
#

yes

alpine ingot
#

The only parameter we can reques is list of capability options. But looks like there is no match between 'active'/ 'inactive' capabilities and 'on'/ 'off'/ 'blocked' options for connected account.
So this means you get back capabilities that active on the connected account, but you actually cannot use them because some of them are off or blocked on the platform account?

minor root
#

correct. we want to know exactly what payment methods are currently available for particular connected account

alpine ingot
minor root
#

Can I share the accountID in private message, please?

alpine ingot
#

Sure, if you prefer you can send me a DM.

minor root
#

done

alpine ingot
#

Are you sure? I didn't receive anything.

minor root
#

a, you didn't recieve my message, because I am not your friend)

alpine ingot
#

Got it, give me a few minutes.

minor root
#

waiting. thanks a lot!

loud jewel
#

hi! taking over.

we want to know exactly what payment methods are currently available for particular connected account
you can list their capabilities(https://stripe.com/docs/api/capabilities/list) to see what payment methods they are onboarded to and would be able to use in an Intent.

#

But looks like there is no match between 'active'/ 'inactive' capabilities and 'on'/ 'off'/ 'blocked' options for connected account. So, I want to feagure out the way how we can match them. If we can. Means can we make 'inactive' capability that is 'blocked' in payment methods?
that's all irrelevant really since those settings are for the automatic payment method feature, which you're not using here since it's not supported for SetupIntents

#

so instead you, as the platform, choose what payment methods you want to support, and then the union set of "things you want to accept" and "things the connected account has an active capability for" are what you pass to payment_method_types when creating the SetupIntent

minor root
#

Thank you, guys!