#gyungi_error
olive whaleBOT
đ 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/1318733681984143371
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
spiral inlet
Hello! Can you give me two request IDs, one for one of these before the change that succeeded, and one after the change that failed? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
viral patio
So I think the payment intent doesn't even get created is what it looks like- we just get an error back from hitting the endpoint. pi_3QXAnuJFfb8SRu7A0GSxSKhm This one succeeded as a card present payment WITHOUT the parameter when we weren't trying to save the card, but there's no payment intent in our stripe logs for ones where it failed
https://dashboard.stripe.com/logs/req_EvcuMzNb4M9fl0?t=1734117327 this is a request where it failed if it's helpful!
spiral inlet
If you look through https://dashboard.stripe.com/logs you can't find one that worked?
viral patio
I'll try and find one, it's just not a terribly commonly used feature for us so it might take me a while to find one where we wanted to save a card_present payment
give me a second
spiral inlet
Without seeing the other request, my guess would be that you didn't specify payment_method_data at all before. As far as I know you've never been able to use that to just set metadata and nothing else.
viral patio
I can see in our code we've never set payment_method_data at all you're right- it's always just been null
but in the past that was fine for setting SetupFutureUsage = "off_session" without the payment_method_data[type] being set, and now that's changed; apologies that I don't have a clearer sense for when that happened
spiral inlet
Wait, I think we're talking past each other a bit, let me clarify...
If you set payment_method_data in the request you're basically telling the API, "I'm going to provide you with all the data you need to create a Payment Method in this request" and then you get an error back because the first thing the API does is check to see if the required data is there, and it's not. See here: https://docs.stripe.com/api/payment_intents/create#create_payment_intent-payment_method_data
This has nothing to do with setting it up for future use or not.
In the request you shared the error you got back was Missing required param: payment_method_data[type]. because that's required, but you didn't provide it.
viral patio
Ahh I see what you're saying- so if we're setting some other field within PaymentMethodData then we need to fill out other required fields
so it's entirely unrelated to "saving the card" for future use
spiral inlet
Yeah, in fact you need to supply all of the required data, which you can't in this scenario, because you're using Terminal and the card info isn't something you have at this point. The Terminal reader provides that data directly to Stripe.
Basically, for this use case, there's no practical way for you to supply payment_method_data, period.
viral patio
cool yup that makes sense
spiral inlet
If you want to change the metadata on the resulting Payment Method you need to wait for the Payment Intent to succeed, then make a separate API call to update the metadata on the associated Payment Method.