#uncle.t
1 messages · Page 1 of 1 (latest)
background, we uses Jetpack Compose
From the error message, the URL scheme that you defined in return URL can't be loaded
Can you double check if URL scheme is set up correctly?
we never configured the return URL before
the scheme of the URL cannot be opened, which is stripesdk
Can you share the Payment Intent (pi_xxx) with this error shown?
and stripesdk://payment_return_url is configured from the SDK itself
it is a setup intent
Hi @hard furnace stripesdk://payment_return_url/xxxx is the deeplink URL to return to your app.
Are you using the latest 20.34.4 ?https://github.com/stripe/stripe-android/blob/master/CHANGELOG.md#20344---2023-11-02
@visual reef yes, I understands that. We are looking for solution to ensure it can be correctly executed
yes, we are using 20.34.4
Is it happening in test mode or live mode?
test mode at this point
Can you decompress the apk file and open the Android.manifest file, check if stripesdk:// scheme is in the manifest file?
no, we don't have that scheme added to our app
or you mean the after manifest merging?
Yes, the final apk should have the stripesdk:// scheme added to the merged manifest.
If it's not there, try clean your project and buld again from scratch.
right, think this might be related to our deep link handling
when receive this fron Intent, do we need to handle it?
No you don't, the Stripe Android SDK will automatically handle it.
🤔
my concern is our AppsFlyer integration captured it
Not an AppsFlyer deep-link stripesdk://payment_return_url/au.com.aussiecommerce.luxuryescapes
which then tried to open it in web view
Ah, I see. You might want to check with AppsFlyer and see if there's a way to exclude stripesdk://
yeah, I've found a way to exclude it.
so I guess StripeSDK would handle this deeplink regardless the logic we have in MainActivity?
I don't have insights on what logic you have in MainActivity, as long as your app, or any 3rd-party depenencies you integrated in your app, doesn't intercept stripesdk:// and let Stripe SDK to handle it, your customer will be redirected back to your app upon completing 3DS authentication.
let Stripe SDK to handle it
yeah, this is the part I'd like to confirm.
Is there anyway I can check in our app that SetupIntent has been correctly handled?
"been correctly handled'" -> do you mean if a setupIntent is confirmed successfully?
ye
Ok, you can listen to setup_intent.succeeded webhook event