#benbartling-setupintent-automaticpm

1 messages · Page 1 of 1 (latest)

quaint panther
#

hello, reading

#

yeah SetupIntents require passing each PaymentMethods type you want to support, it doesn't support the automatic PaymentMethods feature like PaymentIntents do

misty valve
#

Ok, I was afraid that would be the answer. Thanks for confirming!

#

I'm working on a Connect platform. Is there an endpoint for determining which payment methods have been enabled for an account?

quaint panther
misty valve
#

I don't think that's what I'm looking for. That seems to return "active" for all the payment methods whether they have been "turned on" or not within the Stripe dashboard. Is there a difference?

quaint panther
#

do you have an example? Like an Account object that has some PaymentMethod type at active but that PaymentMethod type is disabled in the Dashboard

misty valve
#

Yes, take a look at acct_1LZj0FCaMzFsvDro.

The capabilities response I get is: { "acss_debit_payments": "active", "affirm_payments": "active", "afterpay_clearpay_payments": "active", "bancontact_payments": "pending", "card_payments": "active", "eps_payments": "active", "giropay_payments": "active", "ideal_payments": "active", "link_payments": "active", "p24_payments": "pending", "sepa_debit_payments": "pending", "sofort_payments": "active", "transfers": "active", "us_bank_account_ach_payments": "active" }

However, the payment methods page in the dashboard looks like the attached screenshot.

echo swan
#

We don't have an endpoint for this beyond the capabilities