#mebezac_api

1 messages · Page 1 of 1 (latest)

frosty grottoBOT
#

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

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

blazing canyon
#

Hello, as far as I am aware, you can't set payment method metadata from the setup intent itself. So what you would need to do would be update the payment method object after it is created by the setup intent. It may potentially make sense to set the metadata on the intent, listen for the event about the intent succeeding, and update the new payment method at that point

serene citrus
#

But it is possible on any of the payment methods that have their own payment_method_data options, is that correct? Seems a bit odd to not be able to do it for cards ¯_(ツ)_/¯

blazing canyon
#

I think that that is because of PCI requirements, if you are passing numbers into that parameter that means you are handling raw card numbers. If you do have raw PAN access, I think this may exist for cards as a hidden parameter

serene citrus
#

Sorry for the confusion I don't want to pass card numbers or any other card data, I only want to pass metadata like you can for any other payment method type

blazing canyon
#

Have you successfully done that in an API call for another payment method type? As far as I'm aware, you can only pass metadata if you are passing the entire rest of the required data to payment_method_data and are confirming the intent with that call.

serene citrus
#

Nope, we only do cards, so I haven't tested other payment methods. My appologies if it doesn't work that way, the docs make it seem like metadata is a separate key that can be independently set. If it's possible to make a feature request, it would be awesome to be able to set the metadata of whatever payment method is created by the setup intent.

blazing canyon
#

Gotcha, I will definitely file a feature request! Just tested myself and it looks like I was remembering correctly that this only works when passing the other data and confirming. I thought the same as you when first coming across that parameter