The Themes manager controls the HTML and CSS template envelopes that render every customer-facing checkout page in OwnPay. Themes determine the layout, typography, animation style, and input field patterns that customers interact with when they visit aDocumentation 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.
/checkout/{token} or /pay/{slug} URL. OwnPay supports modular theme plugins, meaning the visual layer is fully swappable without touching gateway logic or brand configuration. A default theme — own-pay — is bundled with the platform and serves as the production-ready fallback.
The active theme identifier is stored in the
op_system_settings database table as active_theme. Visual assets such as logos, favicons, and brand colors configured under Branding Settings or per-brand contexts are injected into Twig templates at render time, regardless of which theme is active.Accessing the Themes Manager
Log in to the Admin Panel
Sign in to the OwnPay admin dashboard with your administrator credentials.
Theme Card Overview
Each installed theme is displayed as a card containing:Theme Name
The display title of the theme (e.g.
Own Pay Theme). The currently active theme is visually distinguished with an Active badge.Version & Author
The package version and developer credit string (e.g.
v2.0.0 – Own Pay).Description
A summary of the theme’s features, such as whether it supports responsive layouts, multi-gateway tabs, or custom animations.
Controls
Activate makes the theme the global active checkout template. Remove permanently deletes the theme files from the server.
Activating a Theme
Locate the Target Theme
Browse the theme cards on the Themes dashboard and find the theme you want to apply.
Installing a Custom Theme
Custom or third-party theme packages can be uploaded as.zip archives directly from the admin panel.
Select the Archive
Choose the
.zip theme package from your local machine. The archive must contain a valid manifest.json with "type": "theme" and a unique slug field.Upload
Submit the upload form. OwnPay extracts the files, validates the manifest, and adds the new theme to the Themes dashboard.
Best Practices
Test themes on mobile devices
Test themes on mobile devices
A large proportion of payment transactions occur on mobile devices. Test any new theme on both small-screen smartphones and tablets to ensure payment input fields, gateway selection tabs, and the submission button remain fully accessible and usable.
Keep the default theme as a fallback
Keep the default theme as a fallback
Always maintain the bundled
own-pay theme on the server. If a custom theme is removed or becomes corrupted, the system has no template to fall back to and checkout pages will break. The default theme is a reliable recovery baseline.Validate uploaded theme archives
Validate uploaded theme archives
Before uploading a theme
.zip, verify with the publisher that the manifest slug is unique and that the archive does not modify core platform files. The theme’s slug must match the folder name in the package.Related Pages
Branding Settings
Upload logos, favicons, and configure brand colors injected into all themes.
Landing Page
Configure the public marketing home page content separately from checkout themes.
Plugins
Install theme plugins via the central plugin manager.
Public Checkout
Understand the customer checkout experience rendered by the active theme.