Using Drop-In and Components together

[gazseatfrog]

Description

We have Drop In working in our app, and have a new requirement to also show a GooglePay (straight to google play flow) button alongside Drop In (cards or google pay flow, 3DS works fine for Drop In Google Pay).

I've followed this example quite closely

Everything works fine except for 3DS handling. Using the 3DS cards when testing google pay, after passing the challenge I get a redirectUrl that I think is caught by Drop In activity, and never returns user to the app.

Integration Information

1. Server-side integration: Sessions
2. Client-side integration: Drop-in/Components Both!
3. SDK version: 5.9.1

Additional Information

Previously had the same issue as this user - have cleaned up the intent filters in our manifest from previous implementation, so no longer see the app chooser but cannot get back into app after 3DS challenge.

I see from the demo app there are no intent filters declared in the manifest, so assume they are not needed if the GooglePayComponent is set up correctly?

[gazseatfrog]

Update: I also see from your docs that I do need to catch the redirect when using component. Adding in the application ID to the intent filter (as per docs)
<data android:host="YOUR_APPLICATION_ID" android:scheme="adyencheckout"/>
results in the same issue described here

My takeaway is that if I want to use components along with drop in, we need our BE to provide a different returnUrl when using Components?

[ozgur00]

Hi @gazseatfrog, thanks for reaching out.

You are correct, it is required to declare the intent filters as per docs. Sorry for the confusion caused by not including the necessary intent filters in our GooglePayComponent example, we will be adding it there in short time.

About your question regarding intent filters, drop-in has an intent filter defined already, and if you further want to use GooglePayComponent along with Drop-in and handle returns separately you can define a separate intent filter with the android:path parameter (see initial code example), and your BE would provide this returnUrl for GooglePay.

At the bottom you can see an example of how you can form this returnUrl parameter, with the addition of the path.

            <!-- Use a different intent filter then the one used to handle the Drop-In result
            (if you have both Drop-In and standalone components in your app). If you don't do this
            the user will have to choose which Activity is used to handle the result, which is a
            confusing user experience. -->
            <intent-filter>
                <action android:name="android.intent.action.VIEW" />

                <category android:name="android.intent.category.DEFAULT" />
                <category android:name="android.intent.category.BROWSABLE" />

                <data
                    android:host="${applicationId}"
                    android:path="/googlepay"
                    android:scheme="adyencheckout" />
            </intent-filter>

val returnUrl = RedirectComponent.getReturnUrl(context) + "/googlepay"

Let me know if you need more information!