adr_error | Stripe Developers | Page 1

upper roseBOT Sep 9, 2025, 10:52 AM

#

👋 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/1414926348132028428

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

#

white leaf Sep 9, 2025, 10:55 AM

#

hi there!

drowsy valley Sep 9, 2025, 10:56 AM

#

hello, hope there's enough information, I wasn't sure what the correct category for this question is

white leaf Sep 9, 2025, 10:57 AM

#

which line of code is throwing that error?

drowsy valley Sep 9, 2025, 10:58 AM

#

it's thrown when attempting to show the payment sheet paymentRequest.show()

#

I believe the canMakePayment call returns null, when we don't expect it to

white leaf Sep 9, 2025, 11:00 AM

#

I believe the canMakePayment call returns null, when we don't expect it to
canMakePayment can return null for many reasons. one of them is if the user doesn't have a card saved in their Apple Wallet.

drowsy valley Sep 9, 2025, 11:00 AM

#

yes, we followed the docs, and the user does have the correct Safari version, apple wallet set up and a payment method inside it

#

FWIW, our old implementation, which we're replacing with Stripe, does work for affected users, i.e. Apple Pay session's canMakePayments call returns true

#

I guess my question is, is there a way to determine why it's not successful in some cases even though it should be, according to the requirements in the docs? maybe there are browser settings or Stripe's dashboard setup that we're missing?

white leaf Sep 9, 2025, 11:04 AM

#

so your question is: why canMakePayments sometimes returns null, even though it looks like everything is setup correctly for Apple Pay to work?

drowsy valley Sep 9, 2025, 11:05 AM

#

yes

white leaf Sep 9, 2025, 11:05 AM

#

maybe there are browser settings or Stripe's dashboard setup that we're missing?
based on your description the issue is on the customer's end, not your Stripe configuration.

#

yes there are browser settings that can impact this. for example:

drowsy valley Sep 9, 2025, 11:07 AM

#

we did find this setting, but changing it didn't have any impact

white leaf Sep 9, 2025, 11:08 AM

#

is the issue consistent? like the same users can never see Apple Pay, while others always see it?

drowsy valley Sep 9, 2025, 11:09 AM

#

yes, that's correct

#

our worry is, we tested it for 5 different users and it didn't work for 2 of them

#

which made us think there is an issue in the implementation

white leaf Sep 9, 2025, 11:10 AM

#

do you have a link where I can reproduce the issue?

drowsy valley Sep 9, 2025, 11:11 AM

#

I don't, sorry, it's in our internal development environment as of now

#

was hoping you have any ideas what we could check

white leaf Sep 9, 2025, 11:13 AM

#

the common things are:

make sure the device/browser is compatible with Apple Pay
double check that a valid card is saved in the Apple Wallet
enable the browser setting I mentioned above
make sure you are in a country that supports Apple Pay (including VPN)

#

also, you could ask the users if they see the Apple Pay button at the top of on this page: https://docs.stripe.com/stripe-js/elements/payment-request-button
if they do: it means there's an issue in your own integration. if they don't: it means there's an issue on the users's end.

#adr_error