[BUG][Android] PaymentSheet card number input not focusable when tapping middle/bottom of field

[OmarBadr94]

Describe the bug
On the card number field of the Stripe PaymentSheet, the text cursor only appears if the user taps at the very top of the input area. Taps in the middle or bottom of the field do not focus the input, so the user cannot start typing the card number unless they tap very precisely near the top edge.

Environment / Integration details
Integration type: Stripe Mobile SDK – Flutter
Flutter package: flutter_stripe version ^12.2.0
Native Android SDK: Stripe Android SDK 12.2.0 (via stripe_android plugin)
Platform: Android (PaymentSheet in a Flutter app)

File structure:
Payment logic: lib/layers/data/services/stripe_service.dart
Stripe initialization: main.dart (publishable key and merchant identifier)
PaymentSheet configuration

screen-capture.webm

dart
SetupPaymentSheetParameters(
paymentIntentClientSecret: clientSecret,
merchantDisplayName: merchantDisplayName,
allowsDelayedPaymentMethods: true,
applePay: PaymentSheetApplePay(
merchantCountryCode: countryCode,
),
googlePay: PaymentSheetGooglePay(
merchantCountryCode: countryCode,
currencyCode: currencyCode.toUpperCase(),
testEnv: isTestEnv,
),
)

PaymentSheet is initialized via: Stripe.instance.initPaymentSheet(...)
PaymentSheet is presented via: Stripe.instance.presentPaymentSheet()

Observed behaviour
The issue occurs specifically with the card number input field within the PaymentSheet on Android.
Other fields (expiry, CVC) appear to work correctly; the tap-to-focus problem is mainly on the card number field.
Users often need to tap multiple times or aim at the very top edge of the card number field to get the cursor and keyboard to appear.
This behaves like a UI / touch target issue inside the native Stripe PaymentSheet component on Android.

Expected behaviour
Tapping anywhere within the visible card number field should focus the input and show the cursor so the user can start typing.
The touch target for the card number field should cover the full height of the input, not only the top portion.

Steps to reproduce
Initialize PaymentSheet with a valid payment intent client secret.
Call Stripe.instance.presentPaymentSheet() on an Android device.
When the PaymentSheet appears, tap on the card number field in the middle or bottom area.
Observe that these taps do not focus the input and the cursor does not appear.
Tap again, this time near the very top of the card number field.
Observe that the input now receives focus and the cursor/keyboard appear as expected.

[realmeylisdev]

Related: Fixed by PR #2316

This issue is closely related to #2308 and both are fixed by the same PR: #2316

#2316

Root Cause

The limited touch target area (only top of field responds) is a symptom of the same focus management issue:

In PR #2291, descendantsAreFocusable: true was added to the Android Focus widget. This caused focus handling to be distributed to child widgets, resulting in:

• Fragmented focus management
• Constrained hit-test boundaries
• Only the top portion of the field responding reliably

The Fix

Removing descendantsAreFocusable: true from Android (keeping it only for iOS) centralizes focus at the wrapper level:

• Unified hit-test boundaries
• Full field height responsive to touch
• Clean focus routing through InputMethodManager

Verification

Tested locally:

• ✅ Tapping top of CardField → keyboard appears
• ✅ Tapping middle of CardField → keyboard appears
• ✅ Tapping bottom of CardField → keyboard appears
• ✅ Touch works uniformly across full field height

Both issues (#2307 and #2308) are fixed by the same change since they're symptoms of the same architectural problem.

@remonh87 - Ready for review!

[blaneyneil]

i can't even get this work again after downgrading to the following:

flutter pub deps --style=compact | grep stripe

• flutter_stripe 12.0.2 [flutter meta stripe_android stripe_ios stripe_platform_interface]
• flutter_stripe_web 7.0.0 [flutter flutter_web_plugins freezed_annotation stripe_platform_interface stripe_js web]
• stripe_android 12.0.1 [flutter]
• stripe_platform_interface 12.0.0 [flutter freezed_annotation json_annotation meta plugin_platform_interface]
• stripe_ios 12.1.0 [flutter]
• stripe_js 7.2.1 [freezed_annotation json_annotation meta web]

[realmeylisdev]

Clarification: This issue affects PaymentSheet, which is a native Stripe SDK component

@blaneyneil - Downgrading flutter_stripe won't resolve this issue. Here's why:

PaymentSheet vs CardField are different components:

Component	Implementation	flutter_stripe control
Stripe.instance.presentPaymentSheet()	100% native Stripe Android SDK	❌ None - just launches it
CardField / CardFormField widgets	Flutter PlatformView	✅ Full control

When you call presentPaymentSheet(), flutter_stripe simply invokes:

paymentSheet?.presentWithPaymentIntent(clientSecret, configuration)

The touch handling, input fields, and focus behavior are entirely inside com.stripe.android.paymentsheet.PaymentSheet from the native Stripe SDK. flutter_stripe cannot modify this behavior.

PR #2316 fixes CardField/CardFormField - not PaymentSheet. The symptoms are similar but the root causes are different.

Recommended next steps:

1. File this issue at https://github.com/stripe/stripe-android/issues - that's where the PaymentSheet code lives
2. Include your device model, Android version, and the native Stripe SDK version (check your android/build.gradle or run ./gradlew dependencies | grep stripe)
3. Check if removing custom appearance configuration affects the issue

[cedvdb]

@meylis1998 it seems like this has been fixed on android stripe sdk 22.7.0:

stripe/stripe-android#12245

[realmeylisdev]

@meylis1998 it seems like this has been fixed on android stripe sdk 22.7.0:

stripe/stripe-android#12245

I'm okay with closing this PR if you're too

[cedvdb]

@meylis1998 this package uses 22.2.0, doesn't it ? I'd suggest upgrading the android sdk version to version 22.7.0.

The react native library has made the upgrade, that version is supposed to have a fix for this.

[ahsanrahman0745]

any lead on the issue?

[remonh87]

Fixed in v12.3.0 which includes the sync to android 22.7.0