Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/stripe_android/android/src/main/AndroidManifest.xml`:
- Around line 29-33: Update the FileProvider authority to a library-specific
namespaced value to avoid collisions: change the manifest provider entry for
android:name="com.reactnativestripesdk.StripeFileProvider" to use an authority
like "${applicationId}.com.reactnativestripesdk.fileprovider" and then update
the corresponding call to FileProvider.getUriForFile(...) in StripeSdkModule.kt
to use the exact same namespaced authority string; ensure both locations
reference the same new authority constant or literal so manifest merges and
runtime URI resolution remain consistent.
- Around line 21-25: The library manifest currently hardcodes the deep-link
scheme via the <data android:scheme="stripe-connect"/> intent-filter which
causes every host app to claim the same scheme; replace this with a manifest
placeholder and require the host app to supply an app-specific scheme (e.g.
generated from its applicationId or passed as a configuration parameter) so the
intent-filter uses that placeholder instead, and ensure the SDK exposes a
configuration entry (or constructor parameter) used when launching the Stripe
Connect auth flow so the host passes the same app-specific redirect URL; update
references to the intent-filter/data android:scheme and any Connect auth
entry-point code to read the provided scheme rather than the hardcoded
"stripe-connect".

In
`@packages/stripe_android/android/src/main/kotlin/com/reactnativestripesdk/customersheet/CustomerSheetManager.kt`:
- Around line 67-68: The code currently defaults the optional input to false by
using arguments.getBooleanOr("opensCardScannerAutomatically", false) and then
always applying it, which loses the distinction between unset and explicit
false; change the local variable opensCardScannerAutomatically to be nullable
(Boolean?) and populate it by checking for the presence of the key (e.g., if
arguments.hasKey("opensCardScannerAutomatically") then
arguments.getBoolean("opensCardScannerAutomatically") else null), and then only
call the builder/setter (the code on Line 88 that always sets the value) when
opensCardScannerAutomatically != null so the unset case is preserved.

In
`@packages/stripe_android/android/src/main/kotlin/com/reactnativestripesdk/StripeConnectDeepLinkInterceptorActivity.kt`:
- Around line 57-61: The current use of Intent.FLAG_ACTIVITY_REORDER_TO_FRONT /
FLAG_ACTIVITY_SINGLE_TOP on launchIntent in
StripeConnectDeepLinkInterceptorActivity won't bring the main app task to the
foreground because REORDER_TO_FRONT only works within the same task; replace
those flags with cross-task-safe flags by adding Intent.FLAG_ACTIVITY_NEW_TASK |
Intent.FLAG_ACTIVITY_CLEAR_TOP on the launchIntent (so the system will route to
the existing app task/root and deliver onNewIntent), and remove the
REORDER_TO_FRONT usage; update the code that sets flags on launchIntent to use
NEW_TASK and CLEAR_TOP instead.

In
`@packages/stripe_android/android/src/main/kotlin/com/reactnativestripesdk/StripeSdkModule.kt`:
- Around line 263-270: The current reuse of PaymentSheetManager in
StripeSdkModule (the if/else around paymentSheetManager and the call to
configure()) leaves native PaymentSheet/FlowController instances created in
PaymentSheetManager.onCreate() stale; always recreate the manager when
configuring or re-initializing (e.g., in initPaymentSheet) so native state is
rebuilt. Replace the reuse path so you instantiate a new
PaymentSheetManager(reactApplicationContext, params, promise) each time and call
registerStripeUIManager(newInstance); if PaymentSheetManager holds native
resources add/Call a dispose/destroy method on the old paymentSheetManager (or
implement one) before replacing it to avoid leaks; ensure configure() is only
used for in-place updates and not relied on for full re-init logic involving
customFlow or intentConfiguration.
- Around line 1576-1583: storeStripeConnectDeepLink currently appends URLs to
the instance-level pendingStripeConnectUrls, but
pollAndClearPendingStripeConnectUrls drains only the companion-level queue via
retrieveAndClearPendingUrls, so URLs never reach the poller; fix by adding the
incoming url into the companion queue used by retrieveAndClearPendingUrls (or
modify retrieveAndClearPendingUrls to also drain the instance queue), e.g. move
the add into the companion's pendingStripeConnectUrls while synchronizing on the
companion's lock (or call a companion method to enqueue), referencing
storeStripeConnectDeepLink, pollAndClearPendingStripeConnectUrls,
retrieveAndClearPendingUrls, pendingStripeConnectUrls and pendingUrlsLock so the
poller reads the same queue the bridge writes to.
- Around line 1696-1714: The flag isRecreatingReactActivity must be reset
whenever a ReactActivity recreation is detected (activity is ReactActivity &&
bundle != null), not only when shouldFinish is true; change the logic so after
you set isRecreatingReactActivity = true you always schedule a reset
(Handler(Looper.getMainLooper()).post { isRecreatingReactActivity = false })
tied to that recreation lifecycle, leaving the existing shouldFinish check for
activity.finish() unchanged; reference isRecreatingReactActivity,
isAuthWebViewActive, shouldFinish, activity (ReactActivity), and the
Handler/Looper post call to locate and update the code.
- Around line 1541-1544: The current Handler.postDelayed({ file.delete() },
3000) deletes the shared cache file after a fixed 3s delay which can race the
receiving app; remove that fixed-timer deletion and instead leave the exported
file in cache, and implement opportunistic cleanup (e.g., a housekeeping method
run on module init or app startup that scans the cache/export directory and
deletes files older than a retention threshold, or use Android Job/WorkManager
to periodically purge aged files). Locate the Handler.postDelayed block (the
file.delete() call) in StripeSdkModule.kt, remove it and add a cleanup routine
that deletes files by age or on startup rather than using a fixed short delay.

In `@packages/stripe_ios/ios/stripe_ios/Sources/stripe_ios/Stripe`
Sdk/Mappers.swift:
- Around line 1290-1299: The intValue(_:) helper currently accepts any NSNumber
(including booleans and floats) which lets invalid KYC dates slip through;
modify intValue(_ value: Any?) so it returns nil for NSNumbers that are actually
booleans or that have a fractional component: explicitly reject value as Bool
(or detect CFBoolean via CFGetTypeID) and for numeric NSNumbers verify that
number.doubleValue.truncatingRemainder(dividingBy: 1) == 0 before returning
number.intValue; otherwise return nil so the caller (e.g.,
DateOfBirth/dateOfBirth parsing) will trigger invalidField("dateOfBirth").

In `@packages/stripe_ios/ios/stripe_ios/Sources/stripe_ios/Stripe`
Sdk/StripeSdkImpl.swift:
- Around line 1947-1956: The dataTask completion handler currently ignores the
URLResponse and may treat HTTP 4xx/5xx responses as successful; update the
URLSession.shared.dataTask(with: url) { [weak self] data, response, error in ...
} closures to cast response to HTTPURLResponse and check response.statusCode is
in 200...299 before writing the file—if the status is outside that range, call
resolve with a meaningful error (e.g., "HTTPError" and the statusCode and/or
server body message) and do not save or present the share sheet; apply the same
fix to the other identical dataTask block around the referenced 1966-1989
region.
- Around line 1991-2022: presentShareSheet currently grabs
RCTKeyWindow()?.rootViewController and calls present(...) which can fail if the
root is already presenting; instead obtain a presenter via
findViewControllerPresenter(...) and present the UIActivityViewController on
that presenter. Update presentShareSheet to: use findViewControllerPresenter()
to get a presenting UIViewController (fall back to cleaning up file and calling
completion(false) if nil), set popover.sourceView and sourceRect to the
presenter's view when popoverPresentationController exists, and call
presenter.present(activityVC, animated: true). Also ensure the cleanup of the
temp file and calling completion(completed) remain in
activityVC.completionWithItemsHandler.

In `@packages/stripe_platform_interface/lib/src/models/customer_sheet.dart`:
- Around line 74-80: The deprecated factory includes the bool?
opensCardScannerAutomatically field but the .adapter and .session factories are
missing it; update both factory signatures (.adapter and .session) to accept a
bool? opensCardScannerAutomatically parameter and forward that value into the
created instance (the private constructor / underlying type used by those
factories, e.g., _CustomerSheetInitParamsDeprecated or the internal
_CustomerSheetInitParams) so the field is set consistently across all factories.
Ensure the parameter name and nullable type match the deprecated factory and
that it's passed through to wherever other similar params
(allowsRemovalOfLastSavedPaymentMethod, preferredNetworks, cardBrandAcceptance)
are forwarded.

In `@packages/stripe_platform_interface/lib/src/models/payment_sheet.dart`:
- Around line 139-145: The docstring for the field termsDisplay describes a
per-payment-method map but the field is declared as a single TermsDisplay?;
change the field to Map<String, TermsDisplay>? to match the intended map-based
design (and the Android PaymentElementConfig.kt/PaymentSheet.TermsDisplay
usage), update the doc comment to match snake_case keys, and adjust any
constructors/serialization/deserialization and equality/copy logic that
reference termsDisplay so they handle a nullable Map<String, TermsDisplay>
instead of a single enum value; ensure any platform/channel conversion code uses
PaymentMethod.Type keys mapped to the same snake_case strings.

In
`@packages/stripe_platform_interface/lib/src/models/payment_sheet.freezed.dart`:
- Around line 92-98: The generated model exposes termsDisplay as a single
TermsDisplay? but it must be a per-payment-method map; update the source model's
termsDisplay declaration (the field named termsDisplay and its type in the
PaymentSheet model) to use Map<String, TermsDisplay>? (or the appropriate
nullable map type) so serialization emits {"card":"automatic"} style objects,
then regenerate the freezed model (the generated payment_sheet.freezed.dart will
update) and verify the native bridge consumers (TermsDisplay enum and
termsDisplay field) receive a map; if a global enum was intended instead, align
docs/native code accordingly.

---

Nitpick comments:
In `@packages/stripe_android/android/build.gradle`:
- Line 69: The build hard-pins OkHttp to 'com.squareup.okhttp3:okhttp:5.3.2'
which conflicts with the repository's floating-version strategy used by
stripe-android and can cause resolution mismatches; update the dependency
declaration in the Android Gradle build (the implementation line for
com.squareup.okhttp3:okhttp) to use a floating range such as '5.3.+' (or align
with the transitive version used by stripe-android) and verify compatibility
with StripeSdkModule.kt usage so dependency resolution is consistent across
stripe-android and this module.