#mvaanbaak-apple-pay-connected-account
1 messages · Page 1 of 1 (latest)
hey there!
We let customers 'link' their stripe account as standard connected accounts on our platform, and use our SDK in their ios app. Now they want to have applepay as a payment option. Should we ask them to create a CSR, send it to us, have us sign it using a new merchant for their app and send the certificate back to them? Or can we do this work for them somehome ?
just copying here
How do you end up collecting payment? Is this all through an app you control?
@sage linden hello! this is unarchived
Thanks.
We use our api key, and use the user_id field to specify which connected account we create the payment_intent in
on IOS to confirm the payment intent and to show the payment sheets, we also use our publishable key to init the Stripe SDK and use the customer account id in the StripeAccount request header
catching up here one sec
sure thing
@sage linden you're using Direct Charges right (going off of what you mentioned)
yes
so here's what I recommend (and this might be a bit different from how other cards work on your integration but it will help make Apple Pay setup easy for you)
so the alternative is that you have each Connect account register a cert in their Stripe account which won't be scalable, you'd need each accounts unique CSR to do this and that won't scale plus Express and Custom accounts won't be able to give you the CSR
So what you can instead do is, only register Apple Pay on the Platform.
Then, you create the PaymentMethod for Apple Pay on the Platform too, but then you clone that PaymentMethod down to any Connect account and then you can use it on a Direct Charge there