#sargis-avetisyan_api
thorny swallowBOT
đ 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/1300797638526111817
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
ivory raptor
Yup, generic declines like that can happen as that API and way of saving a card with often perform an authorisation
The correct way to save/attach payment methods to a customer is via a Setup Intent: https://docs.stripe.com/payments/save-and-reuse
minor relic
Yes I have this logic integrated
ivory raptor
Specifically, that kind of request can trigger 3DS/authentication flows if the bank request it but the API is not designed to handle them. Setup Intents are
minor relic
but I am getting this error when trying to attach to customer
ivory raptor
Yes I have this logic integrated
Then you shouldn't need to call the attach endpoint
The Setup Intent will handle that on confirmation assuming you passed customer on creation
minor relic
ok thanks let me check and go back
ivory raptor
Yes I have this logic integrated
I don't see any evidence of that. pm_1QFBUrCNeX5rKcbUISc0CyC4 was not created with a Setup Intent
ivory raptor
Looks like you're using createPaymentMethod: https://dashboard.stripe.com/logs/req_m8MwEw2FP4a5LH