#uvid
1 messages · Page 1 of 1 (latest)
Let's look closer into it. Can you provide
- Your platform account id
- Your Connected account id
- Your domain
- Your public accessible URL
OK, wait a moment
- platform account id:
acct_19meNCI9qxn1A7eM - connected account id:
acct_1D58c0FWmrFHVcd4 - domain: uwiew.xyz
- public accessible url: https://uwiew.xyz/1610440173818/checkouts/c2c4a595a1c2d2c375f199e6d2c8a5c4?buyScence=detail&clientLang=en
{
"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_1D58c0FWmrFHVcd4/logs/req_r2cRphOM6vjeLC?t=1684983223",
"type": "invalid_request_error"
}
}
Okie, could you show me which publishable key and Stripe account header is being used? Which js file could I see it?
oh is this using Live key?
yes
Did it work with test key? (Can you plug the test key here to test?)
Domain name verification only supports live key
Is the test key a platform or a merchant?
Yes domain verification should be done via Live key, but you can still test with test key
Platform test Publishable key, and then stripe account header
Yes, The same code can be paid in our test environment with test key (verify the domain name through the live key), but the above-mentioned flashback problem will occur in production, so we doubt whether it is related to the configuration
Platform test Publishable key: pk_test_51IAoXWCmtCRIRJ3JmL2kjWEKN5lgE1orfMiifDnkLpUQl8pcsJ71I9L3nAH8TfrGS8QEMgSbWijg1vRy90nXhlXL003RVIhl2D
Okie, let's check the connection between Connected Account and Platform
was it connected via Live mode?
sry, wait a moment
Theoretically yes, how can I verify
Long wait, here is my platform public key
Um do you remember how did you connect them? Via an AccountLink or OAuth?
oauth
Can I provide any more information? The point of confusion is that the test key can be paid, but the live key crashes
Yes so I think this account was connected via Test mode, and that's because testing with a Test key works, but a Live key doesn't. But I am finding more log on when the connection be made
But, it work via merchant account sk_live_
This is different from the official way, because it relies on the merchant's secret key
What do you mean by "work via merchant account"?
That's without the Stripe Account header?
When I use the key of the merchant's secret key sk_live_xxx to verify the domain name, there will be no flashback problem
Sorry I am confused, wasn't that the way you registered the domain in the first place
When the live_key_xxx is from a platform account, it crashes. Then, if specify live_key_xxx which is the merchant account, i can complete the payment
When you use the key of the merchant account, you didn't specify the stripeAccount header, correct?
I specify the stripeAccount for all
so you set the Connected Account Id secret key, and also place the stripeAccount to it own?
Yes, That's what I tried, but it wasn't the way the documentation recommended, and I actually had no way to get the Connected Account Id secret key
That's a weird setup and not recommended to the Doc, so I am not sure how it works too. Let's ignore it for a moment
If you register the domain again using Platform live key and stripe account header, Does it stop working again?
I'll try later
To summarize what we have so far
- acct_1D58c0FWmrFHVcd4 is connected via OAuth to acct_19meNCI9qxn1A7eM on Feb 24 2023
- Your website use acct_19meNCI9qxn1A7eM (Platform) live Publishable Key, with account header to (acct_1D58c0FWmrFHVcd4)
- You registered the domain using Platform live Secret key, with account header to (acct_1D58c0FWmrFHVcd4)
- You can't finish an ApplePay transaction on your website https://uwiew.xyz/1610440173818/checkouts/c2c4a595a1c2d2c375f199e6d2c8a5c4?buyScence=detail&clientLang=en
- But if you swap the live Publishable Key to a test Publishable Key, then you can finish an ApplePay transaction
Thanks for the summary, I add cURL to troubleshoot the problem
# live key: invalid_request_error
curl 'https://api.stripe.com/v1/apple_pay/sessions' \
-X 'POST' \
--data 'validation_url=https%3A%2F%2Fcn-apple-pay-gateway-cert.apple.com%2Fpaymentservices%2FstartSession&domain_name=uwiew.xyz&display_name=Total&key=pk_live_JDH8nV5m95xdJ9eRar82KesE&_stripe_account=acct_1D58c0FWmrFHVcd4&_stripe_version=2020-08-27'
# test key: success
curl 'https://api.stripe.com/v1/apple_pay/sessions' \
-X 'POST' \
--data 'validation_url=https%3A%2F%2Fcn-apple-pay-gateway-cert.apple.com%2Fpaymentservices%2FstartSession&domain_name=uwiew.xyz&display_name=Total&key=pk_test_51IAoXWCmtCRIRJ3JmL2kjWEKN5lgE1orfMiifDnkLpUQl8pcsJ71I9L3nAH8TfrGS8QEMgSbWijg1vRy90nXhlXL003RVIhl2D&_stripe_account=acct_1D58c0FWmrFHVcd4&_stripe_version=2020-08-27'
can you share the request id for the invalid_request_error attempt?
ok
{
"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_1D58c0FWmrFHVcd4/logs/req_t6W5Zi9njq6p6X?t=1684995395",
"type": "invalid_request_error"
}
}
can you register the domain uwiew.xyz in livemode for your connected account? I don't see it registered on the connected account
Hello, I registered the domain name through the document https://stripe.com/docs/stripe-js/elements/payment-request-button?client=html#html-js-using-with-connect, the The domain uwiew.xyz will appear in the domain name of the platform account, not in the merchant account, I'm not sure if this works as expected
you need to do the registration with the connect account header also for it to appear in the connected account
Okay, I'll take a look
I want to confirm again, should the domain name appear in the domain name list of the platform account? Or only in the connect account
if you're using direct charges, then the domain name should appear in the connected account