#rena7ssance_docs
1 messages ¡ Page 1 of 1 (latest)
đ 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/1440130567491424368
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- rena7ssance_code, 5 days ago, 21 messages
Hi! Looking into your query!
You will get this 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 PaymentMethod multiple times, you must attach it to a Customer first.
type: "invalid_request_error"
to confirm: type: "invalid_request_error" is the error when detach fails?
I am not sure about that. I haven't come across that error and can't think off my head a reason why it might fail if the inputs (payment method ID, customer ID, etc) are correct.
any reference doc from Stripe that summarizes this part? (as i did not find any doc about it)
Sorry summarises which part exactly?
What's the potential error code if the detach fails in Stripe side (as https://docs.stripe.com/api/payment_methods/attach does not have any information)
Have you faced an issue with this detachment before?
no. we plan to integrate with Stripe with the detach endpoint. and wanna be prepared for potential error (e.g. how to handle the error)
There isn't a specific document that covers all scenarios where detaching a payment method might fail. However, if detaching fails, we will return an error response explaining why the request couldn't be completed.
These are some potential scenarios that may help you in your testing.
- Subscription: You cannot detach a payment method if it's the default payment method for an active subscription, as this would leave the subscription without a valid payment source.
- Invalid payment method ID: If the payment method ID doesn't exist or has already been detached.
- Insufficient permissions: If you're trying to detach a payment method from a different Stripe account by mistake.
However, you should test detaching based on your set up to ensure you cover your specific use cases,