#nickdnk_api
undone palmBOT
👋 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/1484242852493135955
📝 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.
- nickdnk_api, 2 days ago, 51 messages
sinful sage
So my questons is if this is something legacy I should remove
This is what stripe passes back to my redirect_uri (all test data, dont worry). I add the token myself, but not redirect_status.
slim jetty
hmm i have to admit i am not super familiar with this, give me a bit to reproduce it
can you share an example of how you call stripe.confirmPayment()?
oh yes i definitely see that too
we document it here of all places
https://docs.stripe.com/payments/cash-app-pay/accept-a-payment?payment-ui=elements&api-integration=paymentintents#handle-redirect
sinful sage
but you don't add redirect_pm_type 😄
at least not for this payment flow I use
So the queston is; should I remove it?
(dont use cashapp)
If it's meant to be there, it should go in the documentation block I linked: https://docs.stripe.com/js/payment_intents/confirm_payment#confirm_payment_intent-options-confirmParams
I realize I can/should fetch the payment intent status to confirm, but it's good for early-exit scenarios if it's "failed" anyway
slim jetty
yep i agree we should add it to the stripe.js reference for sure. can you explain what you mean by "remove it"? like delete the query string when people are redirected? or stop relying on it?
sinful sage
I meant stop relying on; stop reading it, if it was deprecated and scheduled for removal
so delete the code
less code good
Even if discouraged from use for whatever reason, it should be documented