Skip to main content
Common questions and answers about OwnPay.

​
General

OwnPay is a self-hosted payment orchestrator. It allows a single platform owner to manage multiple white-labeled merchant stores (brands) under one installation, with double-entry ledger bookkeeping, 100+ payment gateways, and Android SMS verification.
No. OwnPay is infrastructure you deploy and own. You control the server, database, credentials, and data. No third-party has access to your transactions.
Stripe and PayPal are payment processors - they process payments for your business. OwnPay is a payment orchestrator - it connects to multiple gateways (including Stripe and PayPal) and gives you a unified interface to manage all payment methods across multiple brands.
Yes. OwnPay is designed for platform operators who want to host payment processing for multiple businesses, agencies that white-label checkout for clients, or enterprises with multiple divisions needing independent payment processing.

​
Installation

  • PHP 8.3 or higher
  • MySQL 5.7+ or MariaDB 10.3+
  • 512MB RAM minimum (2GB+ recommended)
  • 1GB disk space minimum
  • SSL certificate for production
See System Requirements for full details.
Yes. OwnPay works with cPanel, DirectAdmin, and Plesk hosting. You need PHP 8.3 support and MySQL. See the Shared Hosting installation guide.
No. OwnPay includes a web-based installer. Upload the files, create a database, and visit your domain to complete setup through the browser.

​
Payment Processing

OwnPay supports 100+ payment methods through its plugin system, including Stripe, PayPal, Square, bKash, Nagad, GCash, bank transfers, and more. See the Gateway documentation for the full list.
No. OwnPay uses tokenization - credit card data is processed by the payment gateway and never stored in your database. This ensures PCI compliance without the complexity of storing card data.
Yes. Each brand can accept multiple currencies. OwnPay handles automatic currency conversion at checkout using exchange rates you configure.
OwnPay sends HTTP POST requests to your server when payment events occur (payment completed, refunded, etc.). You configure a webhook URL in the admin panel, and OwnPay delivers events with HMAC-SHA256 signatures for verification. See Webhooks for details.

​
Multi-Brand

There’s no limit. You can create as many brands as your server can handle. Each brand is completely isolated with its own customers, gateways, staff, and settings.
Yes. Each brand can have one or more custom domains for checkout pages. Customers never see the master OwnPay domain. See Custom Domains.
Yes. Each brand configures its own gateway credentials independently. Brand A can use Stripe while Brand B uses PayPal.

​
Technical

Yes. OwnPay is open source and available on GitHub. You can view the source code, report issues, and contribute.
Yes. OwnPay supports theme plugins for full checkout customization. Each brand can also set custom colors, logos, CSS, and JavaScript. See Theme Plugins.
Yes. OwnPay provides a REST API for payments, transactions, customers, and more. See the API Reference for details.
Yes. OwnPay has a WordPress-style plugin system. You can build custom gateways, themes, and addons. See Plugin Development.
Last modified on July 15, 2026

Related topics

Developer Quickstart - Build Your First Payment IntegrationOwnPay API Overview - REST API for Multi-Brand PaymentsNode.js SDK - TypeScript-First Payment IntegrationRetrieve Payment DetailsTroubleshooting - Fix Common Installation and Payment Errors