#nickjw-applepay-connect

1 messages · Page 1 of 1 (latest)

high stone
#

hello, pasting your second question here too

# 
- We have over 1000 domains active on our service, so the 99 domain limit won’t work for us. If we have to add these domains to our platform account to be able to be used with Subscriptions and Destination Charges, is there any way we can get around this limit? Could we ask Apple for a higher limit? If not, do you have any suggestions?
- I’ve noticed that part of the domain authentication process involves putting a file on a particular ‘verification path’ for each domain (/.well-known/apple-developer-merchantid-domain-association). Does this mean that domains registered with Apple can’t be used with other accounts? If so, we couldn’t create the same Apple Pay Domain on both our Platform Account and the Connect Account. Is that right?

Appreciate your help here as I try and wrap my head around how we can incorporate Apple Pay with our service. Let me know if anything needs further clarification.```
#

reading over

scenic relic
#

Thanks!

high stone
#

[1] - If we allowed Apple Pay for organizations to subscribe to a plan with us, verifying that this ApplePayDomain would have to be added to our platform?

Yes

[2] - If we allowed Apple Pay for Direct Charges to Standard Connect Accounts, verifying that this ApplePayDomain would have to be added to the Standard Account?

you have to add Apple Pay domain via the Platform on the Connect acct. And also host the domain association file on the Connect account's domain.

[3] - If we allowed Apple Pay for Destination Charges to Custom Connect Accounts, would this ApplePayDomain have to be added to our platform or the Custom Account? Not sure if this would go on our platform or the connected accounts since technically the payment goes to us first.
Destination Charges mean the Charge happens on the Platform level. So Platform has to be set up for Apple Pay (same as [1])

#

reading the rest

#

but thanks for sharing clear details, your questions are well formed!

#
  • We have over 1000 domains active on our service, so the 99 domain limit won’t work for us. If we have to add these domains to our platform account to be able to be used with Subscriptions and Destination Charges, is there any way we can get around this limit? Could we ask Apple for a higher limit? If not, do you have any suggestions?
    what is the 99 domain limit?

and is this about adding to your Platform domains of the orgs/Connect accts? (if I read this right)

#

If so, we couldn’t create the same Apple Pay Domain on both our Platform Account and the Connect Account. Is that right?

you can, so test.com can be added as a domain for Apple Pay to n diff Stripe accounts

#

these are all complex questions and there potentially exist workarounds too so feel free to ask more! I (or colleagues) are around to help

scenic relic
#

Thanks for the answers! So it sounds like based on your answers, we'll need to add domains for Apple Pay to both our platform account, and to each Connect Standard Account.

#

I'm not sure if this only applies if we were doing a direct apple integration though. Can you confirm if this limit exists if we do this integration through Stripe?

ivory juniper
#
  1. You are the ones registering a domain with Apple Pay so their limits still apply. Apple Pay is just a convenience wrapper around using credit cards (with some extra security and nifty features to be sure) so the limits still apply as far as I know.
  2. I am not 100% certain but it looks like you can only register 99 domains per request. Is this something you could test out doing with multiple requests?
scenic relic
#

ohhhh

#

hmm

#

ok i'll test out with multiple requests

#

we'd need to have over 1000 domains registered on our platform for the Apple Pay integration to work with our web application for use with Subscriptions and Destination Charges to Custom Connect Accounts

#

so in theory this would work if we did this with over 1000 requests

ivory juniper
#

Well it's 99 as the max, so maybe you could cut down to say, 200 requests?

scenic relic
#

Well we'd still need to add a new domain for every customer that subscribes for service

#

So even after the initial requests, we'd have to add them 1 by 1 every day

#

Make sense?

ivory juniper
#

Ah, so you couldn't aggregate the requests.

scenic relic
#

We could for the initial ones

#

But I don't think it would help if in the end we'd have to add these one by one anyway

#

What I need is some kind of verification that we have 'unlimited' or a very high limit of requests available to us