#tassstors_webhooks
edgy mangoBOT
👋 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/1372542515978178561
📝 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.
- tassstors_webhooks, 30 minutes ago, 7 messages
wet forge
hi there!
earlier you shared an error message. you don't have the request ID associated with it?
which API call were you making exactly when you saw that error?
edgy mangoBOT
young dove
Hey Soma, we, use paymentIntents.create via node.js stripe SDK to create the payment intent. Inside the logs on dashboard I see that we make the following requests when successfully charging our customers. The problem is that I'm unable to find the POST requests in our stripe dashboard logs for the attempts that got that error response
So I can't really give the req id for the case I'm interested in :/
heavy gyro
👋 taking over for my colleague. Let me catch up.
would you mind sharing any request ID so that I can take a look?
young dove
sure, req_Nx6iVoEgbaI4t9 this one is for a succesful request. We however don't even get a request in stripe dashboard for the attempt we make via paymentIntents.create when we get that error back 😦
"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"
heavy gyro
what's the error then?
young dove
we however always attach customer ids when setting up the intents
heavy gyro
this means that you haven't setup the card for future usage
young dove
hmm, but it seems that a majority of our payment intents are setup correctly and are able to be billed. I've noticed that we get this errors for payment methods which failed to confirm the setup intent (we'll handle those by listening for the related webhook), however there's an interesting case where setup intents like seti_1R5ADGBVfuMTCR40Pfr21PkC are setup correctly (my guess this is via stripe connect integration), but we are not able to charge them and get the same error back
So I was wondering if maybe the customer themselves are able to prohibit usage for future payments ?
and maybe we can listen for this somehow ?
heavy gyro
nop that should work as expected
heavy gyro
I don't see the PM being used again
young dove
But generally even if we get that error we should be able to see the request in our logs ?
heavy gyro
but I think I know why you're not able to use it again
because it was detached https://dashboard.stripe.com/logs/req_UnhBgfK9tOdGvW
from Stripe Dashboard