#daniel_code
livid oreBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1438668255836504208
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
fluid bison
Some more info. We have multiple Stripe accounts per app, when initializing the apple pay form does it matter which stripe account I initialize it with? When creating the payment intent we pass in the stripe information to the backend at the moment of payment so that will always be the correct account, but it may initialize to a different Stripe account.
So far, in testing, it seems to be fine with the different Stripe initialization but I've yet to test in a Prod (or Prod like) environment.
gentle silo
Hi there!
So like you're using the same publishable key to initialize Stripe on the client but you may have one of n merchant ids, is that right?
fluid bison
hello, I have
Multiple stripe account ids
1 apple pay merchant id
the app has multiple "store-fronts" if you want to think of it that way so the accounting is routed to each store-front, but its all one app so one apple pay merchant id. I'm trying to think of the best way to handle this.
before, how it worked was, when you landed on the payment screen it would initialize apple pay THEN and just pass in the specific config
But now I'm tyring to centralize all the initialization code and am running into this issue. Again, in testing it seems to be working just fine, but I want to know if this is discouraged or would cause issues in non-testing environments.
flat oxide
👋 can you clarify why you do raw iOS/Swift calls in your code example?
Like the docs you linked say function App() { return ( <StripeProvider publishableKey="pk_test_123" merchantIdentifier="merchant.com.{{YOUR_APP_NAME}}" > // Your app code here </StripeProvider> ); } which makes sense to me so I don't get where your own code samples come from @fluid bison ?
livid oreBOT
fluid bison
we made a custom implementation due to ios app clip size restrictions
but the custom implementation is the same as the sdk, just minus a lot of the dom components that inflated the size
flat oxide
handing off to @junior lagoon who is taking over and can likely help you further
junior lagoon
Hi @fluid bison catching up
Yes, you need to specify a merchant ID if you want to support Apple Pay in your iOS applicaiton. https://docs.stripe.com/apple-pay?platform=ios#create-payment-request here's how you specify the merchant ID in native iOS Swift code
fluid bison
ok, thank you, it looks like publishable key or the stripe account id are not even used in the confirmApplePayPayment function
junior lagoon
You should use applePayContext.presentApplePay() to present the Apple Pay paymentSheet if you are using native Stripe iOS SDK.