#tomralston-native-mobile-wallets

1 messages · Page 1 of 1 (latest)

ashen cairn
#

Hey! Is there a specific part you're struggling with?

hybrid spire
#

I can't find any documentation about best practice for handling this with the iOS and Android SDKs

ashen cairn
#

Handling what exactly? What are you looking to build?

hybrid spire
#

We have an app that allows ordering in one restaurant. It's set up with Stripe (+ Apple Pay and Google Pay)

#

We want to add a second restaurant, using a different Stripe account

#

Currently our app instantiates Stripe with restaurant 1 config at the start

#

But it's unclear what the best practices are for having multiple Stripe configurations in iOS and Android apps

#

Does that make sense?

#

(I should say, instantiating and switching between them)

#

And then I have more of an administrative question - do we need to go through the Apple Pay and Google Pay verifications with them for each config? Do they allow multiple configs inside one app?

ashen cairn
#

But it's unclear what the best practices are for having multiple Stripe configurations in iOS and Android apps
Well you would need to create a method by way to 'switch' between accounts when using the app I guess. Passing in the API key for the selected account

#

do we need to go through the Apple Pay and Google Pay verifications with them for each config?
For Apple Pay you'd need an Apple Merchant ID: https://stripe.com/docs/apple-pay?platform=ios#merchantid
I think 1 will be required per Stripe account

Allow customers to securely make payments using Apple Pay on their iPhone, iPad, and Apple Watch.

hybrid spire
ashen cairn
#

There isn't really any documentation around that I'm afraid

hybrid spire
ashen cairn
#

How you implement that just depends on your application. There's no specific guidance

ashen cairn