#Daniele

1 messages · Page 1 of 1 (latest)

tawny stoneBOT
valid anchor
#

Practical case:
We have 4.5k connected accounts
We want apple pay to work at https://daniele.sellix-staging.io
https://daniele.sellix-staging.io/.well-known/apple-developer-merchantid-domain-association returns the correct domain association file
Apple Pay, however, returns this error

{
  "error": {
    "message": "Before you can start using Apple Pay on the Web, you need to first register your domain. For more information, see https://stripe.com/docs/stripe-js/elements/payment-request-button#verifying-your-domain-with-apple-pay.",
    "request_log_url": "https://dashboard.stripe.com/acct_1HoyqhDQ1vYID78v/logs/req_Drs6RjZMoiEutR?t=1666735563",
    "type": "invalid_request_error"
  }
}
native vessel
#

You'll need to make sure that Apple Pay is enabled for your Connect accounts. When you click on Edit settings for your connect accounts in that Dashboard view, do you see Apple Pay enabled?

valid anchor
#

Well it appears automatically when using the Stripe Element

#

see here

#

the error is returned only after i try to pay with apple pay

native vessel
#

Okay, that makes sense. How old is the error?

valid anchor
#

Just received it if that's what you mean

native vessel
#

Is it coming from the Connect account? Or the platform? When you visit that URL, does it show you logged in as the platform or the connected account?

valid anchor
#

The payment intent is created from the platform API through the connected account

native vessel
#

Got it. Is Apple Pay working when you go through the payment flow?

valid anchor
#

Yep, just closes after a few seconds with that error

#

let me try again

native vessel
valid anchor
#

yep same thing

#

i click apple pay -> click pay

#

the payment popup appears, but immediately closes

native vessel
#

Woops, wrong URL.

valid anchor
#

that's the wrong link

native vessel
#

Ah, okay that works.

valid anchor
#

sending screen recording

nimble fossil
#

Hi 👋

I'm stepping in for @native vessel Give me a sec to get caught up

#

Okay so that is the domain this is running on?

valid anchor
nimble fossil
#

That is the domain you have registered for Apple Pay?

valid anchor
#

yes

nimble fossil
#

The whole thing? Including the /invoice/xxxxxxx?

valid anchor
nimble fossil
#

Okay perfect, thanks

valid anchor
nimble fossil
#

Okay so you are hosting the domain association file. Can I get your account ID?

#

Wait, NVM.

#

Okay I see that domain registered but as a Platform. The only merchant registration is for cheatarmy.com

valid anchor
#

Yes, that’s what we were told to do since we can’t somehow force stores to register their apple pay domain on our site as i’d imagine the verification file would change and we can’t automate that

nimble fossil
#

Okay and how are you initializing Stripe.js?

valid anchor
#

We are doing everything through the connected account

#

we pass the stripe_account as the connected account

#

but the API credentials are the platform’s

#

we opened a ticket for this in march and we were told to do this

nimble fossil
#

The code snippet is what I'm looking for here. That's the next step in tracking down the error

valid anchor
#

which we did, now it’s not working anymore

#

Ok, one moment

#

setStripePromise(loadStripe(config.STRIPE_PUBLIC_KEY, { stripeAccount: stripe_user_id }))

nimble fossil
#

And you are using Direct Charges? Are you using cloned payment methods?

valid anchor
#

standard payment intents

nimble fossil
#

Sorry that isn't an answer to my question. Of the three charge types used for Connect integration https://stripe.com/docs/connect/charges are you using Direct Charges. Do you clone payment methods to your Connect Accounts or not?

valid anchor
#

one moment

#

we do this

nimble fossil
#

Okay, thanks.

#

Okay so this domain you are using is for a Connect Account? And you made the registration with the Stripe header?

valid anchor
#

Yep, correct

#

mh actually, let me double check please

#

damn

#

so that was a staging domain, and usually registration through the stripe header is automated
however, since it was a staging domain it was manually configured and no domain registration through the stripe header was done

#

i've added it again now and it's working as expected, sorry for wasting your time

#

all good now, thank you