#hogon_docs

1 messages ¡ Page 1 of 1 (latest)

coarse quailBOT
#

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

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

nocturne sedge
#

Hi, let me help you with this.

#

Why do you need to update the PaymentMethod details? If you don't have a Customer attached you won't be able to reuse the PM, so there is no reason to update the details.

#

In any case, as the error message suggests, it's not possible.

languid grove
#

We want to improve the data quality of 3DS verification

nocturne sedge
#

Are you updating it before making a charge?

languid grove
#

yes

nocturne sedge
#

Okay.
Where do you see this error message?
How are you collecting the PaymentMethod exactly?

languid grove
#

I encountered this error when calling the API locally. The PaymentMethod is created on the frontend and then passed to our backend with the PaymentMethod ID.

nocturne sedge
#

How did you create the PaymentMethod? Could you please share the PM ID?

languid grove
#

pmid: pm_1QhRAmB02sbMzSSPU4oji0WG

nocturne sedge
#

These can be provided via the customer object or the billing details field in a payment method object. These fields being populated should also contribute to better authentication rates.
As the docs suggest, you should use the Customer object.
You could use the billing details before you create the PaymentMethod, how exactly depends on your integration.

coarse quailBOT
languid grove
#

The PM ID already exists because I included the name and email when creating it locally. However, in our production environment, we are creating the payment method on the frontend without including the name and email. Therefore, we want to modify the payment method on the backend.

signal ermine
#

it's just not possible without attaching it to a customer. You should design the flow so that you know the address/email at the time when you create the PaymentMethod. The Update PaymentMethod API is designed for the use case of a returning customer updating their details on a customer details page etc.

languid grove
#

So, we only add the name and email when creating the payment method, is that correct?

signal ermine
#

yes