Fix Base44 + Capacitor Mobile App Payment Issue

We need a developer to fix a payment integration issue in an existing Base44 + Capacitor mobile app. The app is already built and should not require a full rebuild. The work includes identifying the root cause of the payment flow problem, resolving the issue, and ensuring payments work correctly in the current app setup. Please apply only if you have experience with Base44, Capacitor, and mobile payment integrations, and can complete this task efficiently without rebuilding the app from scratch. I have a mobile app built on Base44 (a no-code AI app builder), wrapped with Capacitor for native iOS/Android. The app is not yet live. The problem: I need to integrate RevenueCat for native in-app subscriptions (App Store + Google Play). Base44 handles authentication and token management fully internally with no external API access, so RevenueCat can't be wired in cleanly alongside Base44's built-in login flow. Currently, OAuth login opens in an in-app browser, and after the user logs in, the app just navigates back to the splash screen instead of completing the flow. What I do NOT want: A full rebuild of the app on a different platform A full custom backend replacing everything Base44 does Losing the existing UI/UX that's already built What I'm looking for: A developer who can assess whether this can be fixed with a smaller, more surgical solution — for example: A custom auth layer that runs alongside Base44 (not replacing it) just to unblock native login + RevenueCat entitlement checks Or the minimum viable backend swap needed — ONLY if a partial fix genuinely isn't possible Someone who's dealt with Base44, Capacitor, or similar no-code-to-native handoffs before and can tell me honestly what's actually required, not just default to "rebuild everything" To apply, please answer: Have you worked with Base44, or similar no-code builders (Bubble, FlutterFlow, Adalo) wrapped in Capacitor/native shells? Based on the description above, what do you think the realistic fix is — a lightweight auth layer, or does this genuinely need a backend swap? (I want your honest technical read, not just what gets you the job.)