The System Settings panel is the master configuration board for your OwnPay platform. Every global runtime value — from the application name displayed in customer emails to the timezone used for financial reports — is managed here. Changes take effect immediately after saving, making it the first stop for any new deployment or platform migration.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/own-pay/OwnPay-Documentation/llms.txt
Use this file to discover all available pages before exploring further.
Runtime settings are persisted in the
op_system_settings database table under the runtime group. Always edit settings through this panel or the EnvironmentService wrappers. Writing raw SQL directly to the table can cause cache-mismatch errors.Accessing System Settings
Log in as Super-Administrator
Sign in to the OwnPay admin dashboard using your super-administrator credentials.
Application Settings
The Application Settings section controls the global identity and localization of your platform.App Name
The visual name of the platform (e.g.
Own Pay). This value is injected into admin headers, customer emails, and payment invoices.Base URL
The primary domain where OwnPay is hosted (e.g.
https://pay.example.com). Used to construct checkout route links. Do not include a trailing slash.Timezone
Dropdown to select the default system timezone (e.g.
Asia/Dhaka, Europe/London). This offset aligns financial reports, transaction timestamps, and audit logs.Support Email
The global support email displayed on checkout flows and payment error screens so customers can reach your team.
Footer Text
Custom copyright or company text shown at the bottom of the admin panel (e.g.
© 2026 Your Company).Field Reference
| Field | Type | Required | Example | Description |
|---|---|---|---|---|
| App Name | Text | Yes | Own Pay | Platform display name. |
| Base URL | Text | No | https://pay.example.com | Main server access URL (no trailing slash). |
| Timezone | Select | Yes | Asia/Dhaka | Localizes report timestamps and audit offsets. |
| Support Email | Text | Yes | support@example.com | Customer-facing contact address. |
| Footer Text | Text | No | © 2026 Your Company | Admin panel copyright footer. |
| Maintenance Mode | Toggle | No | Disabled | Blocks public checkout routes (returns HTTP 503). |
Updating the System Timezone
Maintenance Mode
When Maintenance Mode is toggled on, all customer-facing checkout screens and landing pages return an HTTP 503 Service Unavailable response. The administrative dashboard remains fully accessible to logged-in staff, allowing configuration work to continue uninterrupted.Verify
Open a private browser window and navigate to your public root URL. Confirm it returns a 503 page while your admin session still works.
Certain paths remain accessible during maintenance mode by design:
/admin, /login, /webhook, /cron, and /checkout routes are whitelisted so gateway callbacks continue processing and you can still sign in to the admin panel.Best Practices
Base URL configuration tips
Base URL configuration tips
Always set the Base URL to use the
https:// protocol matching your SSL certificate. Insecure http:// endpoints can cause API connection drops and mixed-content browser warnings. Never append a trailing slash — the platform constructs sub-paths automatically.When to use Maintenance Mode
When to use Maintenance Mode
Enable Maintenance Mode before uploading platform updates, running database migrations, or reconfiguring gateway credentials in bulk. This prevents customers from encountering partial states or broken checkout sessions during the operation window.
Related Pages
Branding Settings
Upload logos, favicons, and configure SEO metadata for your platform.
Landing Page
Manage the public-facing marketing home page content and hero text.
Custom Domains
Assign white-label custom domains to your brands.
System Update
Check for and apply core platform updates.