Billing

billing = "external" (the default)

You handle billing entirely on your own infrastructure — your own Stripe/ Razorpay, your own invoicing. Prebit does nothing beyond tracking that the installation exists. Most apps use this.

billing = "prebit"

Declared in your manifest:

billing = "prebit"
price   = 299

What actually happens:

1. Your AppRelease's manifest declares a flat monthly price.
2. The merchant sees an "Active App Subscriptions" list on their own dashboard and clicks Subscribe — this is a merchant-initiated action on a Prebit-owned page, not something your app's backend calls.
3. Prebit charges the merchant through Prebit's own master Razorpay account (not your own, not the merchant's sub-merchant account) and records an immutable ledger entry splitting the charge between you and Prebit.
4. If payment fails, there's a grace period before the installation is automatically uninstalled — shorter than Prebit's own SaaS billing grace, since a third party's revenue (yours) is at stake.

What you get today

• Charging works and is tested.
• An immutable per-charge ledger recording your share (developerShareMinor) of every successful charge.

What doesn't exist yet

• Developer payouts. The ledger knows what you're owed; nothing turns that number into an actual bank transfer yet. This is blocked on a real business step (enabling Razorpay Route on Prebit's own account, which requires Razorpay's approval) and per-developer KYC — not something more code alone can finish.
• Multi-tier or usage-based pricing — one flat price per manifest today, no plan list.
• Trials.