#DeliveryTiem

1 messages · Page 1 of 1 (latest)

teal ledgeBOT
fervent basin
#

Hey there, we can't re-open threads. Can you just post a quick summary of your question? Then we would be happy to help

surreal pagoda
#

Hey there, so I have a duplicate payment method that I want to remove. The duplicate was added via the Stripe dashboard when we already had the bank account added but it was having an micro-deposit issue that we eventually solved with Stripe customer support. So now I want the remove the duplicate, but there is no 'remove' button, so I asked Stripe support to remove it and they told me I can do this via an API call (https://stripe.com/docs/api/payment_methods/detach)... I did this API call and I am getting an error: The payment method you provided is not attached to a customer so detachment is impossible. ... but the payment method is attached to a customer.

daring gust
#

Thanks for the info. Do you have the ID of the payment method that you are getting that error for?

surreal pagoda
#

No problem, yeah the ID is pm_1LpZ6UIUwLvVicLYVxPXY7rk

daring gust
#

Thank you, looking in to that PM

surreal pagoda
#

Thanks, failed API request ID is req_poYS0HbLAcYjg3

daring gust
#

Thank you, was going to ask for that as well. And do you have the ID of the customer you have been working with here? (cus_123)

surreal pagoda
#

No problem, yeah customer is cus_MXyhDKwdjBmW9b

daring gust
#

I am actually unsure how that payment method should properly be removed. I will consult my colleagues on this.

I feel like we probably have some internal process to remove this PM, maybe support didn't immediately know about it. I will definitely put in a feature request to allow deleting from your side any which way though as I don't think there is currently a good way to.

surreal pagoda
#

Okay cool, whatever way it can be removed is fine with me and a feature request too will be good I'm surprised if this hasn't occurred before.

#

Any chance the internal process exists and the removal can be done / queued?

daring gust
#

I did a bit more digging and found you can still cancel the original SetupIntent

#

And that will remove the payment method from your UI

surreal pagoda
#

Ty for the digging, that should disassociate it?

#

Ahhh

#

fantastic

daring gust
#

Yes it will be out of the UI and not usable/attached to the customer as it was never fully set up

surreal pagoda
#

I'll try that now to confirm.

#

That removed it!

#

Great to see, thanks for the extra digging @daring gust

daring gust
#

Awesome! Glad I could help

#

I will still put in a feature request or at least make sure we spell out what to do here in our docs a bit more explicitly. The PM showing up on the customer definitely makes it seem like it is attached so I'm sure this confusion happens a decent amount.

surreal pagoda
#

Agreed, from my POV as a customer & API consumer, it makes sense that the payment method shows up whether the method is directly linked to the customer or via a setup intent associated to the customer. I think the only missing piece of workflow is to make the payment_methods/detach understand that the PM is associated to a setup intent and cancel the setup intent.

#

And from a stripe dashboard perspective, add a 'remove' button that essentially calls the above mentioned logic.

#

plus or minus other use cases, but yeah some input from a Stripe customer.

#

And thanks again.

daring gust
#

Of course! And thanks for the feedback, that definitely puts it well and will help our devs understand how this affects users like you. I'll make sure to include it when I raise my requests