#stripeconnectplatform-capabilities
cyan comet
It is 'alipay' or 'wechat_pay' , respectively, but we need to make a call to get the standard Stripe account's capabilities and there is no mention of what the keys are that we need to translate to the
'alipay' or 'wechat_pay' :payment_method_type?
lusty raft
checking
cyan comet
ok
Can you maybe add WeChat and Alipay to the account and get the capabilities response?
lusty raft
so apparently it works differently there, there are no capabilities for it (and I'll file internally for that, I think there should be capabilities for both)
Right now, there's no clear way of knowing if an account supports it or not, you just create the CheckoutSession with it and if it doesn't work, then you know the account doesn't support it
cyan comet
Hmmmm. OK, that won't work.
That definitely won't work b/c if we add 'wechat_pay' and 'alipay' to the :payment_method_types and they don't have those capabilites, Stripe throws a 400 yes?
lusty raft
yep, and that was what I meant earlier, that is the only way to know right now, that the request 400s and you try again without them
cyan comet
yikes. OK. Is there a way I can get notified when those 2 are added as capabilties?
2.) What is the :payment_method_type for "jcb_payments"
That one is the inverse. It is listed as a capability called "jcb_payments" but on the Checkout Session #create docs there is no :payment_method_type for it. Can you check. Is it just 'jcb' or something else?
3.) If a Connected customer make a Stripe "payment link",
a.) can we pull the URL of those links via the Stripe API to list in our UI?
b.) can we use the API to tag the link so we get the platform fee and add our metadata so we can pick up webhooks?
lusty raft
2.) What is the :payment_method_type for "jcb_payments"
JCBV are just card payments but they require a separate capability, they aren't a new payment method, they are justcardsof a specific type
a.) can we pull the URL of those links via the Stripe API to list in our UI?
PaymentLinks aren't API ready yet but they will be, teams are working on building an API for it
cyan comet
I thought it was a Japanese thing?
lusty raft
it is yes
b.) can we use the API to tag the link so we get the platform fee and add our metadata so we can pick up webhooks?
don't think PaymentLinks support metadata yet, they do still firecheckout.session.completedwebhook events
cyan comet
OK, so if the Stripe Account has "jcb_payments" == 'active' then we create a Checkout Session and pass in payment_method_type of ['card']
?
or payment_method_type of ['card',"jcb_payments"]
lusty raft
well you can pass payment_method_types: ['card'] anytime, just that for any users that enter JCB cards into CHeckout, those payments would only work if the Account has that capability enabled on them.So you just mostly ignore JCB capability as you don't have to manually create a payment_method_types for it, it is just a brand of cards
lusty raft
not yet no, but teams are working on it (though I don't have an ETA)
cyan comet
And for payment links is there a way to update them so if the account is connected to us we can (A) add metadata so we can easily pick up the webhook for customer.subscrption.created? And (B) can we update so we get the platform fee?
Or is that verboten
lusty raft
there isn't a way to add metadata to the PaymentLink. You cannot update the Platform fee either, did you wanna do this before or after the CheckoutSession is completed?