Billing Roadmap

- Observability
- No system can be improved without it being measured for its growth rate.
- Add dashboards, metrics to capture Payment success rate, churn reasons etc
- Capture them by Country, Payment modes, Payment Gateways, etc
- Better User Experience (UI/UX)
- Our payment experience pales in comparison to global standards.
- Show easy to understand failure messages and guide them with next steps.
- Smooth checkout flow with lesser clicks
- Improve Success Rate (> 85%)
- Currently the success rate for Stripe (recurring payment mode) is near about ~54%, which is very poor.
- Add smart retry mechanism based on payment failure reasons. e.g. retry immediately if payment failed due to network error, instead of letting the user feel stuck.
- Use different payment method and payment gateways as fallback mechanism. This is still there but user has to make the choice and do it manually. - Ideally the system should suggest and redirect automatically.
- More Recurring payment modes
- Currently Frappe Cloud only has Card as recurring payment mode and Stripe is very much tightly coupled with the system.
- With UPI, we have another recurring system (Thanks to Bowrna), but it is still available only for Indian users.
- Will add more global recurring payment methods like PayPal or JusPay.
- 30% of the FC users still pay via credits on a monthly basis instead of Card.
- Other enhancements
- Better refund process - Users need not have to raise tickets for refund every time.
- Reconciliation tool - We still lack any common report or tool to reconcile the payments across all our payment gateways.
- Dispute handling process - Common dispute handling process for all payment gateways. Currently we have our eyes only on Stripe dispute.
- Add support for hourly, quarterly and yearly payment mechanism.
- Discount model - Currently we only have partner and NPO discounts. But this is very limited.
- Better flow for Trial and Invoice due date extension process.
- Payout Mechanism - We do marketplace and Mpesa payouts manually out of the system but this will not be efficient over time and has to scale.
- Documentation

The issue does not identify files, tests, or an entry point. It describes a broad billing roadmap covering observability, payment flows, recurring methods, refunds, reconciliation, disputes, discounts, payouts, and documentation, so the scope and completion criteria must be defined before implementation can begin.

Written by the indexing model from the issue text.