Customization Overview
Minimum Version Requirement
This feature requires WhatsMarkSaaS v2.0.0 or higher. Ensure your installation meets this requirement before proceeding.
Legal Terms & Conditions
By creating, distributing, or using custom modules for WhatsMarkSaaS, you agree to the following terms:
Developer Responsibility. You are solely responsible for your module's implementation, testing, security, and maintenance. WhatsMarkSaaS provides the module system as-is. Do not request, advise, or expect changes to WhatsMarkSaaS core to accommodate your module.
Positive Use Only. Modules must be used for lawful, constructive purposes only. Modules that facilitate spam, abuse, fraud, harassment, or any activity that violates applicable laws or WhatsApp's terms of service are strictly prohibited.
Reverse Engineering Prohibited. Reverse engineering, decompiling, disassembling is strictly prohibited. Any attempt to bypass, circumvent, or tamper with the module system's security mechanisms, licensing, activation controls, or access restrictions will result in immediate license blocking, support termination, and your activity will be reported to relevant authorities.
Core Changes Without Notice. we aim to minimize changes that may impact the module ecosystem; however, we do not guarantee backward compatibility and may modify, refactor, or remove core functionality without prior notice. Module authors are responsible for ensuring compatibility with new releases.
Compatibility. Maintaining compatibility with WhatsMarkSaaS updates is your responsibility. Breaking changes in your module caused by core updates are not the responsibility of WhatsMarkSaaS.
Choose Your Development Path
WhatsMarkSaaS offers two distinct development paths for extending platform functionality:
Custom Module Development
Create general-purpose modules that extend WhatsMarkSaaS with new features, routes, controllers, models, views, and Livewire components.
Use cases:
- Custom integrations with third-party services
- Additional tenant features (CRM extensions, reporting tools)
- Workflow automation modules
- Administrative tools and utilities
- Data import/export modules
What you can build:
- Routes (web and API)
- Controllers and models
- Blade templates and Livewire components
- Database migrations and seeders
- Event hooks and filters
- Frontend assets (JavaScript, CSS)
- Multi-language translation support
Get Started with Custom Modules →
Payment Gateway Development
Integrate third-party payment processors into the WhatsMarkSaaS billing system for tenant subscription management.
Use cases:
- Regional payment gateway integrations
- Cryptocurrency payment processors
- Alternative payment methods (buy now, pay later)
- Banking integrations
- Invoice payment processors
What you must implement:
- Settings migration for gateway configuration
- Payment gateway interface implementation
- Webhook handling for payment confirmations
- Tenant billing integration
- Admin configuration UI
Get Started with Payment Gateways →
Prerequisites
Before developing either type of module, you must have working knowledge of:
| Technology | Purpose | Version |
|---|---|---|
| Laravel 12 | Framework foundation | 12.x |
| Livewire 3 | Dynamic UI components | 3.x |
| Tailwind CSS | Utility-first styling | 3.x |
| Alpine.js | Frontend interactivity | 3.x |
| Multi-tenant architecture | Data isolation patterns | N/A |
System Architecture
WhatsMarkSaaS modules are self-contained packages located in the Modules/ directory at the project root. Each module can be activated, deactivated, and removed independently without modifying core code.
Module capabilities:
- Extend application functionality without core modifications
- Integrate with WhatsMarkSaaS hook system (WordPress-style actions/filters)
- Register routes, views, translations, and configuration
- Execute database migrations and seeders automatically on activation
- Load frontend assets compiled with Vite
- Support multi-tenant data isolation
Development Workflow
Getting Help
Documentation Resources
Support Channels
- Documentation Issues: GitHub Issues
- Technical Support: Support Portal
- Feature Requests: Corbitaltech Canny
Next Steps
- Review Prerequisites: Ensure you have required framework knowledge
- Read Legal Terms: Understand your responsibilities as a module developer
- Choose Development Path: Custom Module or Payment Gateway
- Follow Getting Started Guide: Complete step-by-step tutorial for your chosen path
- Test Thoroughly: Validate functionality in sandbox environment before production