Searched this topic and didn't really find a good answer to what seems like a pretty basic question. I am working with a third party payment gateway in this case Stripe. Stripe offers a sequence where they onboard connected accounts for you. So you place a link on your page, and redirect to their page sending identifying info with the redirect. They then redirect back to a url you provide after the onboarding at Stripe is complete .
So this can be done using an a5w confirmation page that would have a specific url, with code waiting to handle the redirect. However this is a mobile app, and don't want to mix in a5w pages at least visible ones anyway. I want the redirect coming from Stripe to hit a confirmation panel in my app.
Can this be done in a url? From what I gathered I would need js in a on render event to set a specific panel, but I am not controlling the redirect back to my url, so I guess I would have to test the redirect url in some way and use it to set my panel? Or is there something I'm missing. How might this be done?
Seems this could be required with many third party services. Moving outside the UX to cyberspace and then back into various landing panels, or alternate ux's within my app would be handy.
The returned url would have to be parsed it contains the result, but that seems secondary to getting to the right ux/panel within my app.
Stripe's onboarding sequence example
https://stripe.com/docs/connect/standard-accounts
Thanks,
Bob
So this can be done using an a5w confirmation page that would have a specific url, with code waiting to handle the redirect. However this is a mobile app, and don't want to mix in a5w pages at least visible ones anyway. I want the redirect coming from Stripe to hit a confirmation panel in my app.
Can this be done in a url? From what I gathered I would need js in a on render event to set a specific panel, but I am not controlling the redirect back to my url, so I guess I would have to test the redirect url in some way and use it to set my panel? Or is there something I'm missing. How might this be done?
Seems this could be required with many third party services. Moving outside the UX to cyberspace and then back into various landing panels, or alternate ux's within my app would be handy.
The returned url would have to be parsed it contains the result, but that seems secondary to getting to the right ux/panel within my app.
Stripe's onboarding sequence example
https://stripe.com/docs/connect/standard-accounts
Thanks,
Bob
Comment