#twinkle_error

1 messages ¡ Page 1 of 1 (latest)

leaden gyroBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1250463010032455741

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

uneven blaze
#

Hello, do you have the ID of a request where you got this error? (req_123)

#

And have you double checked that the payment method ID that you are passing is actually attached to that Customer?

manic oasis
#

req_tXYoCspxMZmhkS

#

yes, as soon as the customer saves the card, we attach it

uneven blaze
#

Thank you, looking in to this

#

I am actually seeing that that PM is attached to a different customer: cus_KnkcRri7raJpAZ

#

That customer and the PM appear to have been created a couple years ago so I can't find the calls again. Is it possible that that ID got mixed up with a more recent ID created for cus_Q7gy9N6e6iEseQ?

manic oasis
#

I am not sure how that's possible

#

Can it happen on your side?

uneven blaze
#

I don't think this was a mixup on our side. We don't change IDs of objects after creation. I can take a look at your logs again in a moment and see if there is an obvious other payment method involved here

uneven blaze