#birdy247

1 messages · Page 1 of 1 (latest)

verbal ermineBOT
summer nymph
#

Hi 👋 what's your question?

finite lance
#

We are a platform account

#

We let our connected accounts chose their own payment methods

#

Apple pay is disabled by default

#

If we were to enable this by default, would it work out the box?

#

I recall something about having to verify the domain name its used on?

summer nymph
finite lance
#

Assuming that we run a tenanted platform, each tenant will have a different subdomain/domain (if using their own domain on our product)

#

How can we scale this process for connected accounts?

summer nymph
#

You would need to help them set up Apple Pay on their own website using the same method that you used to set up Apple Pay on yours

finite lance
#

Would it be enough for us to verify our own domain

#

Or would each tenant also have to do this from their stripe account?

summer nymph
#

Good question, let me check

finite lance
#

thnx

summer nymph
#

So each of those domains counts as a sub-domain in this case, which means they would all need to be registered individually per Apple's rules

finite lance
#

and we cant automate this?

#

What about where two different clients use the same domain?

summer nymph
#

You might be able to automate it, though how that happens will depend on how your system is architected.

#

What about where two different clients use the same domain?
They would both be under the same domain registration. I'm not sure I understand the question

finite lance
#

If we (the parent account), verify ourdomain.com would that be enough for it to work with any connected account that uses that domain?

hearty wigeon
#

Yes if its the same domain (or subdomain) then only one registration is required

#

Are you using direct or destination charges?

finite lance
#

direct

hearty wigeon
#

(same would apply for unique subdomains)

finite lance
#

What is the payment request button?

hearty wigeon
#

That's Stripe's way of showing a standalone wallet pay button, but i'm sharing just for the connect domain registration aspect

finite lance
#

?

#

hello?

hearty wigeon
#

Yes, either the connected account needs to do this, or you need to do it for them, but it must be set up for each account

hearty wigeon
finite lance
#

Ok, so if the connected account is operating under a domain we have verified, we then need to add that domain via the API request you showed me

hearty wigeon
#

Yes, for each connected account, if you're using direct charges

finite lance
#

I am still a bit confused about exactly what we have to do and what we need to ask our clients to do

#

Assume the tenant is working on our subdomain, and we have verified our root domain

#

Could you kindly list the steps that would need to taken inorder to let a connected account use Apple pay

hearty wigeon
#

If you're using direct charges, you need to register the domain for each connected account, using the example i shared

#

Or the connected account can add it in their dashboard

finite lance
#

Ok, but what about the challenge?

vestal marten
finite lance
#

Where do we get the domain file?

#

Is that something that comes back from the API response?

hearty wigeon
finite lance
#

Is the domain association file unqiue to the stripe a/c

hearty wigeon
#

No - its the same for all stripe domain registrations

finite lance
#

oh, that makes this easier 🙂

#

Now it makes more sense

#

So the API is effectivley step 2

#

=

hearty wigeon
#

Yes exactly 🙂

finite lance
#

Awesome

#

On another note, right now, connected accounts have to turn on things like Klarna from their Stripe a/c

#

We are fine for them to control what they want to use

#

But can this be driven via the api

#

considering we are working with standard accounts