#stripe_connect_platform
waxen nymph
Is there any reason you couldn't simply create the Checkout Session after either A or B, so that you always have a fresh Checkout Session after the redirect?
summer root
My Session or your Checkout Session?
When someone clicks a Stripe Payment Link, it creates a Checkout Session with a Cash App QR code that unlocks when someone enters their info and clicks the "Reveal QR code". That is all happening on the web. But then the end customer has to pull out their cell phone while looking at the web UI, right? Now they are looking at the web UI but also taking a pic of the QR code with their mobile device so they are looking at both devices simultaneously.
And both of the devices have pages that redirect in the same way - to our endpoint / controller which redirects to our page which also has a session. I am confused. I don't know if our endpoint is getting hit once or twice - can you tell me?
Like does the web-based Checkout Session redirect and hit the endpoint and ALSO the mobile device sends a 2nd data packet to our endpoint. I haven't tested this. I am looking for a "best practice" on dealing with "payment methods that require mobile devices to complete the Checkout Session transaction"
The problem is that there are two different pages redirecting. One is the normal web Stripe Checkout Session. The other is that page that is for testing and supplied by Stripe where it has 2 buttons to authorize or fail the test payment. I have not processed a live transaction yet, but I imagine in livemode that this page is replaced by some Cash App UI but that also redirects after the Cash App payment is completed and also redirects? I don't want to process a livemode transaction and set up a Cash App account but can do so if you advise. Do you know if the livemode will also redirect in this way that the testmode flow redirects? Or does it just show a "your transaction is complete" and then this problem is not a problem since the end customer would just look back from their mobile device to the web UI and that will redirect to our hosted page so no issue exists. I am just guessing from the testmode flow how livemode will work....
summer root
I am imagining that you are testing this or something - is anyone there? it is nice if you say brb or "I am going to check on this and return to this message shortly. please stand by" or something. Otherwise i am confused and not sure if you just forgot or are working on this ticket. ????
waxen nymph
Was mostly making sure you had finished typing, but then got caught up in other threads (the server is a bit busy). Taking a look now
Yeah, the docs on Cash App could do with a bit more information than they currently have. Unfortunately I don't know the answer to your questions in this case. Let me see if someone on my team does and I'll circle back in a few
summer root
ok
limpid berry
👋 Hopping in here - give me a few minutes to check this out
summer root
ok
limpid berry
Just to confirm - you're just looking to confirm that when using CashApp w/ checkout that both the desktop page (that displayed the QR code) AND the mobile device used to scan the QR code will both redirect to the return_url after payment is complete?
summer root
Confirm that this is the case and if yes...
Then how to handle the fact that normally a redirect URL on web is clear - you just get redirected.
But with payments where you have two UIs open - one mobile and one desktop - how does Stripe recommend handling this?
Particularly if the redirect is a complex one with {CHECKOUT_SESSION} where we are directing to a page that was set up for other payment method types that don't have a mobile component with a unique session ID that fails on one of the two devices since it needs to be unique. I don't know - do people want to create a login and password on their mobile device after paying via Cash App's QR code or, do they want to create a login and password on the web/desktop. I don't know. Probably a mix. What's the recommended flow here Stripe?
Just looking for some benchmark/direction/best-practice for "payments that require a mobile device in addition to the web UI to complete payment"
What else is like this - I think WeChat Pay and maybe others??? But Cash App is what I'm looking at this week.
limpid berry
So yes, I can confirm that the redirect will happen in both mobile and on the desktop
In terms of how to handle it - I don't think we have a specific recommendation here, but I'd imagine that most users (if they had started the payment process on the web/desktop) would want to finish up there and just use the mobile device for payment
summer root
This is sort of a bug no?
Maybe the mobile device shouldn't redirct to the redirect_url?
So maybe we have to handle that in our controller? Like if we get the same Checkout Session ID twice to redirect the second one to???? Do you have a page that would make sense to redirect the mobile use to? Or not sure which one comes first.
Question: Is there a way to make sure the web one goes to our hosted Signup Form and the other one (the mobile device) goes somewhere else? Like does Stripe have a hosted page that says "Your payment is complete. Please go back to the web". I have to think this over. Has anyone on your team who is smarter than me and has a masters degree in something-or-other have thought this through yet? If not can you put someone on that koan?
Anyway, this is my dilemma so I am just checking with Stripe to see if this is a problem that someone has thought over and there is some best practice or just a flow that makes sense. i cannot think of one today. I will sleep on it and invent something i guess.
Any ideas?
It is a weird flow with desktop and mobile both needing to be used simultaneously by the end user.
And both redirecting to the redirect_url
do you see that?
it could just be that i am missing something. i am just checking with the experts at Stripe.
limpid berry
I wouldn't call it a bug per se - but I agree it's definitely a bit weird and I'll flag as feedback to some folks on our end that this is maybe not the behavior we want moving forward. In the mean time - can you give more detail on why this is such an issue? Is the problem that they're only logged in on the desktop site and so the redirect URL doesn't work on mobile?
summer root
session expired
they are getting a session expired
I am trying to think of a better way
We have a hosted page similar to Checkout Session and only allow one session so one device is getting a session expired
our session is for a page that we host which is for signing up and creating a username and password so non-technical people can add login to their website so customers who pay via Stripe can log in and do logged-in kind of stuff. That being going to members-only content on a website (like membership plugin-y stuff) and also get to Stripe Customer Portal to do customer-portaly kind of stuff without having to auth via a no-code customer portal via another email to their inbox - they are already logged in and we can use the API for them on their behalf so their customers get a API-enabled flow by connecting to us without having to code it up or deal with developers who are difficult humans and $$$$. lol
any interest in purchasing a wonderful SaaS for a good price. lol
Anyway, we redirect to that hosted signup form - and it's redirecting in two places and throwing our session expired error so i have to re-code this to make sense for these types of new payment methods that require a mobile device.
Anyway, that's all i can explain. That's the gist.
opal spearBOT
limpid berry
As a stop gap I'd catch that session expired error and just display a page saying if payment was completed please check the desktop site