#runefarer-cashapp
1 messages · Page 1 of 1 (latest)
👍 give me a few minutes to take a look
Thanks, sorry it took a while to get.
For that payment intent - can you give me some more details about why you believe it's not asking for confirming or scanning the QR code/redirecting? Was this a payment that someone on the US team was testing? As far as I can tell, it does seem like there was an intermediate step to actually finish confirming the payment (so it didn't transition directly to paying)
I was on a call with the US team member, she scanned the QR code, it just prompted her that the payment was processing without showing the amount.
After the payment was made, the popup that had the QR code showed something along the lines of 'payment successful', but the confirmCashappPayment method didn't return at all. Closing the popup returned a payment intent with action required status.
I don't have access to any of the US team members now, so I can't retry.
Ah, I thought you had meant they were not given the option to scan the QR code at all. In that case, I believe not needing an extra confirmation on the APP itself is expected and we mention that in our docs - https://stripe.com/docs/payments/cash-app-pay
During checkout from a mobile device, your site redirects customers to the Cash App mobile application for authentication. The payment is authenticated during the redirect. No additional action is needed in the Cash App mobile application to complete the purchase. The customer is then redirected back to your site.
But, it should show the amount, right? It even shows the amount in the GIF on the page you linked.
We don't show the amount if you pass in setup_future_usage with the Payment Intent (I don't think that's called out in the docs, I'll ask them to update that)
I see, I'll test with different values, then.
About confirmCashappPayment not returning even on success, is there something we can address?
Strange thing is that it does return and function fine with a test key, just not with actual Cash App.
Sorry for the wait - was looking into something else for another person. Give me a minute to check on your question
I'm not sure why that function returns when you're using a test key - by default stripe.confirmCashappPayment would only return a result if there was an error or you're using handleActions: false
So, the only way to know that the payment has succeeded on the client side would be to listen to webhook events and then communicate that to the client side?
If I modify the flow, and after creating a payment intent, I use the Payment Element on the client side instead of confirmCashappPayment, would that make for a better flow?
Payment Element would be pretty similar - it won't return after calling confirm. It'll redirect to the return_url after paymetn is complete
Okay, I guess I'll use handleActions: false and use retrievePaymentIntent to poll for status on the client side - that should work, right?
Yes that should work - but generally I wouldn't recommend polling client-side...
We listen to webhooks as well, we can setup a websocket to broadcast when there's a successful payment. I'll look into it and try to figure it out.
Thanks for your help!