Quick Boost UPI Gateway
Deployment Documentation
This guide is designed to be readable offline after upload and is optimized for simple Hostinger deployment.
Recommended deployment: use a root domain or subdomain such as pay.example.com, not a subfolder like example.com/quickboost/.
Hostinger Deployment Steps
- Create a subdomain.
- Enable SSL.
- Upload the ZIP.
- Extract files directly in the web root.
- Create a MySQL database.
- Open
https://yourdomain.com/install.php.
- Enter DB details.
- Create or log in to the admin account.
- Test the checkout.
Expected Folder Structure
admin, auth, payment, config, migrations
should be directly inside public_html or the subdomain root.
Installer and Admin URLs
Installer URL:
https://yourdomain.com/install.php
Admin URL:
https://yourdomain.com/admin/login.php
Default Admin
Username: QuickBoost
Password: Payment#2026
Change the default admin password immediately after first login.
Manual Database Method
- Import
database.sql.
- Import
migrations/2026-06-08-quick-boost-upgrade.sql.
Preferred runtime config file: config/local.php
Fallback config file: config/quick_boost.php
Legacy fallback if still needed by older modules: pages/dbInfo.php
How to Test
- Admin login
- Dashboard page
- Transaction filters and CSV export
- Checkout QR page
- Payment status polling
- WooCommerce plugin flow
Important Payment Routes
/api/create-order/payment/instant-pay/{token}/payment/payment_status.php
WooCommerce Plugin Setup
Plugin ZIP location:
auth/cxrfiles/quick-boost-upi-gateway.zip
- Activate the plugin in WooCommerce.
- Set the Base URL.
- Set the API key.
- Configure webhook/callback URL if applicable.
- Test a digital product order.
Troubleshooting
- User not found: check the selected database and confirm
admin_users contains the expected admin row.
- Invalid password: confirm the password was stored with
password_hash() or reset it to the default during fresh deployment.
- Wrong database connected: review
config/local.php and confirm SELECT DATABASE() matches the intended DB.
- install.php blocked: check whether
config/install.lock already exists.
- ₹ symbol broken: confirm UTF-8 files and browser charset handling.
- QR not loading: confirm the payment page receives a valid UPI link and the QR container is rendering.
- Payment stuck pending: verify the connected collection method and the status polling endpoint.
- .htaccess rewrite not working: enable Apache rewrite support and keep the root and
payment/.htaccess files in place.
Security Checklist
- Let
install.lock block the installer after setup.
- Change the default admin password.
- Enable SSL.
- Protect config files.
- Keep
database.sql and migration SQL protected from public access.
- Do not expose debug mode publicly after deployment.
Final Deploy Checklist
- Upload and extract files into the root of the domain or subdomain.
- Create the MySQL database.
- Open
/install.php.
- Finish installer steps and log in at
/admin/login.php.
- Change the default admin password.
- Test checkout, status polling, and WooCommerce if needed.