#daniele_checkout-paymentmethod

1 messages · Page 1 of 1 (latest)

errant pivotBOT
#

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

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

desert lynx
#

i obtain this error 400 -- [invalid_request_error] The provided PaymentMethod was previously used with a PaymentIntent without Customer attachment, shared with a connected account without Customer attachment, or was detached from a Customer. It may not be used again. To use a Payme...

hidden quest
#

Hi 👋 what is the ID of the Payment Method you're trying to use?

desert lynx
#

and on the customer i don't see the payment method but i have setupped the future usage off session....

image.png
#

pm_1PLR5TG0HkO3ZPnpNjoF9xxx

desert lynx
#

that you confirm that you have received the message ?

hidden quest
#

Thank you, looking

#

Hm, I'm not quickly finding a request that errored when trying to use that Payment Method. Can you share the ID of that request?
https://support.stripe.com/questions/finding-the-id-for-an-api-request

Finding the ID for an API Request : Stripe: Help & Support

Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.

desert lynx
#

ok i have tried another things, to attach a payment method to a customer and i receive the same error

#

req_VEfhbnWiRvCPk7

hidden quest
#

Hm, I'm not sure why you're seeing this behavior offhand.

#

Trying to see if I can reproduce.

#

I'm not able to reproduce that behavior so far, having my teammates take a closer look.

desert lynx
#

it's simple if you try to attach a card to a customer later it's not possible

#

if you have a setup_future_usage: 'off_session', setted but the user in the ui don't toggle the saved_payment_method_options the card is not saved to the customer

#

i'm not able to charge my user and i'm not able to attach the card, i'm loosing time and money, i need a way to attach a card to a customer at least

hidden quest
#

My teammates are looking into this. I did not have this same problem stepping through this flow in my account, the cards were attached as expected. Are you able to reproduce this behavior in testmode? Did you notice it start to occur after incorporating a specific parameter in your requests? Was it working before?

desert lynx
#

yes i have received a mail form stripe saying that i need to introduce the saved_payment_method_options: {
allow_redisplay_filters: ['always'],
payment_method_save: 'enabled'
}, parameter in the checkout api

#

after that if the user doesn't toggle the flag in the ui the payment is not seved to the customer

#

ant it's not possible to attach it later

#

but it doesn't make sense that payment_method_save take precedence over off_Session setting

#

we are a subscreiption platform i need to charge my customer off session

#

also the mail stated that it was only for autofill purpose in the UI

hidden quest
#

Oh, so set payment_method_save to disabled. If you always need the card details, you don't want to let customers disable that.

desert lynx
#

yeah we discovered that but it's not what was written in the mail.

#

we just did that but I have 150 payment methods that are NOT attached to a customer

#

I need a way to fix this

errant pivotBOT
jaunty badgerBOT
iron saddle
#

daniele_checkout-paymentmethod

desert lynx
#

??

iron saddle
#

I'm sorry, there are over 15 people asking for help all in real time right now. We're trying to catch up but it will take a while for me to read all the words you shared.

iron saddle
#

(still digging into your ask, another developer has the same issue so I'm debugging)

iron saddle
#

Okay right now it seems this is on purpose. If you use the payment_method_save you give the option to the end customer to decide whether to save their card details or not.
I do agree this is confusing. It should at least error if you pass setup_future_usage: 'off_session' in my eyes.

I think you should stop using payment_method_save in this case if you need that card attached no matter what. There unfortunately won't be a way to fix the previously collected/consumed cards on our end.

iron saddle
#

We're working on improving the behaviour internally so that this doesn't happen on future Checkout Sessions too