#henning83_code

1 messages ¡ Page 1 of 1 (latest)

tranquil windBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1290584037299322931

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

astral sedge
#

hi! hmm, canMakePayment is for the PaymentRequestButton, not the ExpressCheckoutElement.

anyway if it's null it just means the browser does not have saved cards in the Google/Apple Pay wallet, etc.

knotty heath
#

Thats not possible, because if i try one of our other shops, i have the buttons

#

Oh okay, i have just moved from the PaymentRequestButton to the ExpressCheckout, because of that problem but it is still there.

#

Is there any code i can add to get a info why the button is not showing for that customer?

astral sedge
#

what browser are you testing in, what response are you expecting to see from canMakePayment/which payment methods

knotty heath
#

So its about Apple Pay and iam testing on Chrome

knotty heath
#

sorry on Safari Mac

astral sedge
#

maybe you didn't register the domain on that account then

knotty heath
#

maybe its because of the tld?

astral sedge
#

the customer connected account should not register it in their Dashboard, you as the platform need to do it in the API via the API call in the docs I linked. You should have the connected account delete the registration in their Dashboard, and then you make that API call.

knotty heath
#

Oh okay, i thought it doesnt make a difference if the user registers the domain through our api or directly on there account page. I will try that, thanks.

astral sedge
#

it does matter, it won't work unless the platform has done the registration on behalf of the connected account

knotty heath
#

okay

#

I have checked it and they have registered the domain through our api.

astral sedge
#

I'd still suggest what I suggested above, if the connected account can see the domain in their dashboard, they should delete it, and you should call the v1/payment_method_domains API on their account to register it(it's safe to call it multiple times if you're not sure you did it already).