#arpfel_best-practices
keen flaxBOT
👋 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/1366343411141185566
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
silk galleon
Hm, it should redirect to the MobilePay app for payment approval
This opens the MobilePay application directly (if present) or a webview showing the MobilePay landing page
https://docs.stripe.com/payments/mobilepay/accept-a-payment?web-or-mobile=mobile&payment-ui=ios#confirm-the-payment
sullen pawn
That´s what we thought as well, we have both MobilePay Apps installed but none of them is opened.
To mention it again, we are using the stripe native PaymentSheet via the corresponding ios and android sdks.
silk galleon
Can you share your code here when you init and present the sheet?
silk galleon
Is your return URL an actual deep link?
sullen pawn
Yes, i just changed it for sharing purpose.
silk galleon
Do you have an example intent you can share?
FWIW, we don't support universal links if that is how the return URL is set up
sullen pawn
Probably the dynamic approach might cause issues? What do you think? Will try to setup a direct setup.
silk galleon
Not familiar with that UI to be honest. What is that?
keen flaxBOT
sullen pawn
Thats the info Tab in the app targets xcode configuration where a dedicated URL scheme is defined for deep linking.
still chasm
Hey! Taking over for my colleague. Let me catch up.
sullen pawn
Hey, thank you!
still chasm
If your app didn't catched the deep link and a webview is opened that probably means a miss configuration in your app
Have you tried to test the link by your self ?
on a standalone app ? just the deeplink redirect
sullen pawn
Sure, but what could we configure so the correct deep link is recognized for the MobilePay app? The button with the entry-point is setup via the PaymentSheet.
I can enter the deep link URL in safari, safari asks me to open the correct app.
- our app.
So the deep link scheme itself works.
If i open the link that the stripe sdk opens in the webview, the system is not recognizing that any mobilepay app is installed. Could you confirm that the StripePaymentSheet is checking for the correct MobilePayApp URL scheme, or just opening a webview by default. I tried to find any reference in stripe-ios sdk but without success.
Ah it gets more precise. Probably MobilePay is using a universal link to handle that scenario? The webview shows the banner on top to open that app, so I need to correct my last sentence.
Its´ just hidden initially so the user needs to scroll up manually to see the entry-point.
I will demonstrate the flow.
Step 1: PaymentSheet
Step 2: Select MobilePay
Step 3: WebView appears
Step 4: Scrolling down shows recognized universal link by MobilePay.
Question? Is there a way the PaymentSheet could process this step and link straight into the MobilePay App?
still chasm
Ah thanks for providing these details
Question? Is there a way the PaymentSheet could process this step and link straight into the MobilePay App?
I see what you were referring to now. No you can't if the MobilePay app didn't configure a deeplink for this use case
That's why a webview is opened here.
sullen pawn
Ok. I thought so. Just to confirm, there is no way to bypass this using the showed flow, right?
still chasm
AFAIK nope.
sullen pawn
Ok. Thanks a lot for your efforts to identify and confirming the issue. Helped a lot!
Feel free to close 😄
One second please.
still chasm
Yes sure, take your time!
sullen pawn
I have some additional information for you.
We reproduced the flow, u mentioned universal links are not supported. Would it be possible to integrate support for them?
The PaymentSheet opens the Webview referring to the following redirect link.
https://pm-redirects.stripe.com/authorize/acct_1PxSkq*********/pa_nonce_SDFj1****************
This generates the correct target link for mobilepay, which supports deep linking via universal links.
https://pay.mobilepay.dk/?token=eyJraWQiOiJqd3RrZX*****
As a recommendation you could use or create an internal api in the sdk which resolves the link programmatically, opening the resulting link afterwards. This would automatically open the MobilePay app.
Or any other App of your supported payment providers.
still chasm
I see the point, but Stripe couldn't authorize (do that redirect link) on behalf of the merchant. That's why it needed to be done on their device.
sullen pawn
Ok, I see. Thanks for confirming.
Not sure why, but you have deeper insights. Do you have a bit more detailed clarfication available?
silk galleon
I'd recommend writing into our team directly and we can take a deeper look ito this. Clearly there's some confusion here about what is expected, so we're gonna need some time to understand how this feature works, and whether there's a change you need to make to your code
We can work async with you on this
keen flaxBOT
Hello @sullen pawn, we have sent you a direct message, please check it at https://discord.com/channels/@me/1366371664199417938
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.