Roadmap

This roadmap outlines our planned features and improvements for QZPay. Priorities may shift based on community feedback and real-world usage patterns.

Current Focus

v1.1 - Quality & Polish

In Progress

Improvements to the current stable release:

Enhanced error messages with actionable guidance
Performance optimizations for large datasets
Additional React component variants
Improved TypeScript inference
Extended test coverage

v1.2 - Developer Experience

Planned

Better debugging tools
Development mode with detailed logging
Schema visualization tools
Provider emulators for local development

Upcoming Features

New Payment Providers

PayPal Adapter

Planned

Full PayPal integration including:

PayPal Checkout
PayPal Subscriptions
Webhook handling
Multi-currency support

Braintree Adapter

Planned

Braintree integration for:

Credit card processing
PayPal through Braintree
Venmo payments
Apple Pay / Google Pay

Other Providers (Under Consideration)

Square
Paddle
LemonSqueezy
Razorpay (India)
Adyen

New Storage Adapters

Prisma Adapter

Planned

Official Prisma support:

Schema generation
Migration integration
Transaction support
Type-safe queries

TypeORM Adapter

Under Consideration

For projects using TypeORM.

Framework Integrations

Express Integration

Planned

Dedicated Express.js package:

Pre-built middleware
Route handlers
Error handling integration

Fastify Integration

Planned

Fastify plugin with:

Route registration
Schema validation
Hooks integration

Vue.js Package

Under Consideration

Vue composition API hooks and components similar to the React package.

Svelte Package

Under Consideration

Svelte stores and components for billing UI.

Feature Requests

Analytics & Reporting

Under Consideration

Revenue analytics dashboard
Churn analysis
MRR/ARR tracking
Cohort analysis
Export to analytics platforms

Advanced Billing Features

Under Consideration

Metered billing with complex pricing models
Volume discounts
Tiered pricing
Hybrid pricing (base + usage)
Custom billing cycles

Multi-Tenancy

Under Consideration

Support for multi-tenant SaaS applications:

Organization/team billing
Per-seat pricing
Usage allocation per tenant

Dunning Management

Planned

Improved handling of failed payments:

Configurable retry schedules
Customer notification emails
Graceful degradation of features
Recovery analytics

Self-Service Portal

Under Consideration

Embeddable customer portal:

Subscription management
Payment method updates
Invoice history
Usage dashboard

Infrastructure

Admin Dashboard

Planned

Web-based admin interface for:

Customer management
Subscription overview
Revenue metrics
Event logs
Configuration

API Versioning

Planned

Stable API versioning strategy:

Versioned endpoints
Deprecation notices
Migration helpers

Community Contributions

We welcome community contributions! Areas where you can help:

Payment Adapters

Create adapters for payment providers in your region

Storage Adapters

Add support for your preferred ORM or database

Framework Integrations

Build integrations for other frameworks

Documentation

Improve docs, add examples, translate content

See the Contributing Guide to get started.

Request a Feature

Have an idea for QZPay? We’d love to hear it!

Check existing requests - Search GitHub Issues for similar requests
Open a discussion - Start a GitHub Discussion to gather feedback
Submit an issue - Create a feature request issue with details

When requesting a feature, include:

Use case - What problem does this solve?
Proposed solution - How should it work?
Alternatives considered - What other approaches did you consider?
Priority - How important is this for your project?

Release Schedule

We aim to release updates regularly:

Patch releases (1.0.x) - As needed for bug fixes
Minor releases (1.x.0) - Every 4-8 weeks with new features
Major releases (x.0.0) - As needed for breaking changes (we try to minimize these)