I'd like to submit a feature request for a first-party payment service within the Firebase ecosystem — tentatively called Firebase Payments.

The Problem

Firebase does an excellent job abstracting away common backend concerns — authentication, real-time databases, cloud functions, push notifications, and hosting. However, one critical backend responsibility remains entirely unaddressed: payment processing and subscription management.

Today, developers who build on Firebase must wire together third-party providers (Stripe, Razorpay, Paddle, etc.) manually, manage webhooks, store transaction state in Firestore themselves, and handle currency normalization independently across regions. This introduces significant complexity, maintenance overhead, and security surface area — all of which run counter to Firebase's core promise of letting developers ship faster.

The Proposal: Firebase Payments SDK

I'd like to propose a Firebase Payments service with the following capabilities:

1. Unified Currency Management

   • Automatic multi-currency support with real-time exchange rate handling
   • Locale-aware price display (formatting, symbols, decimal conventions)
   • A single price definition in the Firebase Console that renders correctly in any region

2. Subscription Management

   • First-class APIs for creating, updating, pausing, resuming, and cancelling subscriptions
   • Built-in support for free trials, grace periods, and proration
   • Subscription state synced automatically to Firestore, accessible via standard Firebase SDKs

3. Platform Agnosticism

   • SDKs for Web (JS/TS), Android, iOS/macOS, and Flutter
   • No platform-specific payment logic — one unified API surface regardless of where the app runs
   • Compatibility with existing Firebase Auth (tie payments directly to Firebase user UIDs)

4. One-Time Payments & Invoicing

   • Support for single-charge transactions alongside subscriptions
   • Optional invoice generation and email delivery

5. Firebase Console Integration

   • A dedicated Payments dashboard showing revenue, churn, active subscribers, and failed payments
   • Webhook/event triggers via Cloud Functions (e.g., onPaymentSucceeded, onSubscriptionCancelled)
   • Firebase Extensions support for quick setup with popular processors (Stripe, PayPal, etc.)

6. Security & Compliance

   • PCI-DSS compliant by design, similar to how Firebase Auth handles credential security
   • Firestore Security Rules extensions to gate content access behind payment status
   • Built-in SCA (Strong Customer Authentication) support for EU/UK compliance

Why This Fits Firebase's Vision

Every major SaaS backend platform is moving toward monetization primitives — RevenueCat for mobile, Paddle for web, Lemon Squeezy for indie developers. Firebase is uniquely positioned to offer this natively, deeply integrated with Auth, Firestore, Cloud Functions, and Remote Config (for paywall experimentation). It would close the last major gap in Firebase's backend coverage and reduce the need for developers to leave the ecosystem.

Impact

This feature would directly benefit indie developers, startups, and enterprise teams building subscription-based apps, marketplaces, and SaaS products on Firebase. It would also strengthen Firebase's competitive positioning against Supabase, AWS Amplify, and Back4App, all of which are gaining ground on developer mindshare.

I'd be happy to elaborate further, provide use-case examples, or participate in any early feedback program or beta. Thank you for considering this suggestion — Firebase has been a core part of my development workflow, and this addition would make it indispensable.