#RichStoneIO-Checkout

1 messages · Page 1 of 1 (latest)

sand eagle
#

I am afraid there is no convenience way to enforce the relation. You are letting your Connected account to freely specify connected_accounts_selected_currency and connected_accounts_capabilities_types, and they can choose completely unrelated pair then that error is kind of expected.

#

I would recommend to widen the arrays of payment_method_types

keen tusk
#

hey, thanks for looking at it! May I ask, what do you mean by "widen the arrays"?

It seems like what we actually want to do is to narrow the available_capabilities_types by using this table: https://stripe.com/docs/payments/payment-methods/integration-options

but there doesn't seem to be an automated way to fetch this information and I'm not sure how reliable it would be to copy this stuff over to our app data...

Learn about the different ways to integrate payment methods.

sand eagle
#

I see. One way is to build and maintain a checker yourself based on the information in that page. But I understand it's not elegant. Let me check again the option for automatic decide payment methods

keen tusk
#

yeah exactly, either we scrape the page or it gets outdated at some point

we actually hoped that Stripe picks the right methods based on the enabled methods in or requested capabilities for the Connected Account and the given currency but if we don't pass payment_method_types at all, it always just defaults to card...

#

Thanks for looking at it in more detail!

sand eagle
#

There is a thing calls automatic decide on PaymentMethods

#

Do you have a conversation with Support?

#

It's more like a Beta feature, which seems to be useful to you. But really we can't talk about Beta here so let's continue on a thread in email, and I could flag it internally

keen tusk
#

yeah, I started a support ticket too 😬 you can ping me there in email (webinargeek)

sand eagle
#

Ah I see that. One moment

vast urchin
#

just jumping in, but automatic payment method support on Checkout is not a beta.

#

really, you just omit payment_method_types in the call to create the CheckoutSession. What happens then is that the CheckoutSession will only have payment methods that are compatible with the type of payments you make. So for example if you use GBP then only cards and payment methods that the connected account has activated and work for GBP will be presented as options in the Checkout page.

#

ah but I missed this for Connect. Yeah, technically this is beta on Connect but we're in the process of rolling it out.

#

but yeah until then you have to explicitly pass the enabled/compatible payment methods and there's not any API source of truth, just the docs, so for now you'd just hard code it

#

but we will soon launch a page in your platform's dashboard where you can choose exactly what payment methods can be used by connected account automatically when you don't specify a type.

#

but until that happens the automatic feature doesn't work for Connect, which is why you only see card when omitting payment_method_types . But hopefully won't be that way for long(it's a beta and the team hasn't decided on launch timing yet)

keen tusk
#

got it! Thanks a lot for the detailed insights and for the sneak preview! :))

We'll probably wait for this solution and warn the Connected Accounts when they configure currency/PaymentMethod types instead of baking our own automated solution.