esiok1986_api

[clever saffron]

👋 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/1231970627729100845

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[late zenith]

Hi there 👋 if you're using an already set up CashApp Payment Method, passing setup_future_usage doesn't sound beneficial. What behavior do you see if you omit both setup_future_usage and mandate_data?

[opaque flume]

I agree, but when I omit both of these fields API returns 400 error with the following message:

"When confirming a PaymentIntent with a cashapp PaymentMethod and setup_future_usage, mandate_data is required."

[rotund veldt]

Hi there, can you provide that request ID as well where you omitted those parameters?

[opaque flume]

uh sorry, I've copied the same id 2 times 🤦‍♂️ Here's the actual id req_VtP2yCMhV1InyO

[rotund veldt]

Thanks, looking

That request still passes setup_future_usage?

See: https://dashboard.stripe.com/test/logs/req_VtP2yCMhV1InyO

[opaque flume]

Right, check this request then - it does not have setup_future_usage

req_Yw7JtWjJhWm9tm

[rotund veldt]

Thanks, looking

Can you test something for me? What if you use the /pay endpoint instead: https://docs.stripe.com/api/invoices/pay

Do you get the same error?

[opaque flume]

sure, give me a sec

ok so I used /pay endpoint on the following invoice in_1P8NlKF9R6Nkg8poFsXj81VA

req_NioAqXnH9hruOt

[rotund veldt]

Yeah okay so that seemeed to work

So that can be a workaround for now, it should also work on PaymentIntent confirmation so I'll file that internally as a bug

[opaque flume]

So if I understood correctly

• payment_intents/:id/confirm has a bug that forbids to complete request with cashapp
• for now we should use /pay endpoint as a workaround until the bug is fixed

[rotund veldt]

Yes that's correct. The reason I think this is happening is because the PaymentIntent is generated from a Subscription and thus it automatically has setup_future_usage set. So when you confirm the PaymentIntent that continues to be the case and thus the error, even though you aren't explcitly setting it (so we should ignore it and this should just work)

[opaque flume]

great, one more question - how do I know when the bug is fixed? Is there a way to get some notification or something?

[rotund veldt]

You can write into our Support team via https://support.stripe.com/contact/login and ask them to keep you updated if you like.

[opaque flume]

ok, thanks for your help

[rotund veldt]

Sure