#brandan_paymentmethod-delete
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/1489008117172797571
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Great good to know. Is it accurate to assume the second part of my question?
-- I would want to ensure that if we detached a payment method and a customer wanted to use that card again in the future (same card details) would they be able? Or would Stripe decline setting up that card because it's the same details as a detached payment method?
Then a follow up, is there any downside to detahing? Those payment methods just float out there detached for eternity or does Stripe clean those up.. not really sure if that impacts us in any way but just curious what happens with those detached cards
That specific PaymentMethod pm_1234 is not usable but they can add the same card number again as a new card
And yes those "float" in the sense that they are there forever, but they can't be used, they are here for papertrail/historical information
We are working on a "Redaction API" too to help remove PII
That redaction api would be used for us to hit Stripe servers and request PII to be removed from anywhere in stripes system? ie customer x go remove all PII? Is that something that our account exec would inform us about once that's available or if it will be required?
Okay great, so it would just generate a NEW pm with the same card details. Does the 'floating' impact us in any way ie if we have a bunch of detached pm's?
no impact
Oh cool, thanks for sharing that!
though best not to detach if the end customer wants to pay again
Right, our system currently is only supporting 1 card for a customer at a time so when they add a new card we are detaching their old one. We have plans to eventually use the customer sheet to allow users to manage their own cards which I assume if a user were to delete their card via the customer sheet is that doing a detach as well?
ah yeah I recommend supporting more than one if you can since it help increase conversions
and yes it detaches the same way