#arden-malikb_api

1 messages · Page 1 of 1 (latest)

frosty zealotBOT
#

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

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

distant carbon
#

I'm talking about the PMD's

shut agate
#

Hello, when you say the checkout element, do you mean the Express Checkout Element, which is a bunch of buttons for wallets, or one of the Checkout elements that takes full PM details from payment methods like cards and ACH as well as these wallets?

distant carbon
#

I have enabled payment methods (Amazon Pay, Google Pay, Apple Pay) and registered the necessary payment method domains via both the API and the Stripe Dashboard. However, when I disable these domains from both the API and the dashboard, the payment methods still appear in the checkout UI.

Could you clarify:

  1. Why are payment methods still visible after disabling their associated domains?
  2. Does Stripe cache payment method domain settings, and if so, how can I force an update?
  3. Are there any additional steps required to completely remove a payment method based on domain settings?
#

Request ID for API logs: req_Z6u0VFqj5Zfier

shut agate
#

There are a couple checkout UIs that you may be talking about here, which changes how we want to tackle this more than the PMD and your payment settings. In your elements code, what is the name of the component that you pass to our elements.create method?

distant carbon
#

Let me give you URL

#

This is payment element form

#

this.cardNumberElement = elements.create('payment', {
fields: {
billingDetails: {
address: 'never'
}
},
wallets: {
applePay: 'auto',
googlePay: 'auto'
}
});

shut agate
#

Hello, thank you for the link, checking this out now

distant carbon
#

yes please

shut agate
#

Ah it looks like you are doing a direct charges flow and those payment methods are on for your connect payment method config that determines what direct charges look like pmc_1QeazSGNQ570gX7gM3CsU4k8

distant carbon
#

So Do i need to disable the payment methos too?

shut agate
distant carbon
#

Then what the mean for the enabling and disabiling the payment methods domain

shut agate
#

And click the edit settings link under "Your connected accounts"

#

That is set up properly here, you created the PMD on the connected account as well it looks like

distant carbon
#

I created but there is also disabled those PMDs

shut agate
#

Was this on the platform or connected account? I think only connected account would matter here

distant carbon
#

Yes right but

#

from both end I disabled connected and platform

#

Also did from the conected

shut agate
#

I'm bouncing between a few other threads but will be able to take a look in a few mins

#

This behavior does surprise me in this case

distant carbon
#

Yes no issue but I'm wondering this issue how it is possible

#

This is example I made a request from the API and also disabled each of the domains

#

But Keep my thread enable for while

shut agate
#

Yep, apologies just getting back here

frosty zealotBOT
shut agate
#

I'm seeing the same behavior with my PMD that is directly on my test account. I am trying to look into what disabling the PMD actually does

#

But it looks like the most sure way to disable the PMs is through the connect payment method settings that I linked to

distant carbon
#

Then what does exact mean of enable and disable?

shut agate
#

It looks like this should turn those PMs off, looks to be a bug that this is not working. I am escalating this

distant carbon
#

Okay could you please share me bug tickets any of them so I would convey accordingly

shut agate
#

@distant carbon Apologies for the delay. Don't have a public link to send around this. If you have to step out we can create a support ticket and I can get back to you through email there, otherwise I can watch and provide updates here for a bit

distant carbon
#

Could you please share the screenshot that you escalating the issue?

shut agate
#

My colleagues are getting back to me, it looks like this is currently expected to not apply to at least Google Pay. Our enforcement of PMD registration isn't fully rolled out for some payment methods, presumably because they didn't require it before so we want to make sure that anyone who wants them to stay on doesn't suddenly have them off. We will update our docs to be more accurate around this

For future reference around this kind of report: we don't have something that I am allowed to share a screenshot of externally like that. Creating a ticket and linking that to someone who can watch the escalation would be the way to get that followup.