Skip to main content

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.

OwnPay is an open-source, enterprise-grade payment gateway orchestration platform that you install, run, and own entirely on your own infrastructure. Unlike SaaS payment products, no third party has access to your server, your database, or your transaction records. Every payment processed through OwnPay stays within the boundaries of your own deployment — giving operators, agencies, and fintech teams full sovereignty over their payment stack.

What Makes OwnPay Different

OwnPay is built around a small set of architectural decisions that distinguish it from typical hosted payment platforms.

Sovereign Single-Owner Model

One master administrator controls the entire installation. There is no self-registration — all brands, staff members, and API keys are created by the administrator.

Multi-Brand Scoping

Run multiple fully isolated merchant stores (brands) under one installation. Each brand has its own customers, gateways, staff, and checkout domain.

White-Labeling

Brands configure custom domains, logos, color schemes, and email templates — fully masking the master application domain from end customers.

Double-Entry Ledger

Every payment, fee, and transfer is recorded using double-entry bookkeeping to guarantee financial integrity and support full audit trails.

Mobile SMS Gateway

Connect local Android phones to automatically parse mobile-banking SMS alerts (bKash, Nagad, etc.) and automate manual payment verification flows.

Plugin Architecture

Extend OwnPay with gateway plugins, custom payment methods, and admin panel integrations through a structured plugin system.

OwnPay Is Not a SaaS

When you deploy OwnPay, you control the server, the database, the credentials, and all customer data. There is no OwnPay cloud, no transaction fees paid to OwnPay, and no vendor lock-in. You are running payment infrastructure the same way you would run any other self-hosted application.
OwnPay requires you to manage your own hosting environment, database, SSL certificate, and server maintenance. Review the System Requirements before proceeding with installation.

Who Should Use OwnPay

OwnPay is designed for operators and developers who need more control than SaaS payment tools provide.
RolePrimary Use Case
Platform OperatorsHost a centralized payment infrastructure for multiple businesses or clients under one installation
Agency OwnersDeliver white-labeled checkout flows for clients, each on their own custom domain with their own branding
Fintech DevelopersBuild and integrate custom payment flows, plugins, and automations via the full REST API
Finance TeamsAudit transaction records, reconcile ledger balances, and export financial reports

Quick Start Path

1

Check System Requirements

Verify your server meets the minimum PHP, MySQL, and extension requirements before downloading OwnPay. See System Requirements.
2

Install OwnPay

Download the latest release from GitHub, upload it to your server, and run the web-based installer at yourdomain.com/install. See Installation Guide.
3

Log In as Master Admin

After installation, log in at yourdomain.com/login with the administrator credentials you created during the installer wizard.
4

Create Your First Brand

Navigate to People → Brands and add a brand with a name, currency, and timezone. This is the merchant entity that will process payments.
5

Configure a Payment Gateway

Go to Gateways and connect your payment provider (Stripe, PayPal, bKash, or another supported gateway) to your brand.
6

Generate an API Key or Payment Link

Visit Developer Hub to generate API credentials for programmatic integration, or create a Payment Link to start accepting payments immediately without any code.

Next Steps

System Requirements

Review the server specs, PHP extensions, and hosting environment needed to run OwnPay.

Installation Guide

Step-by-step instructions for shared hosting, VPS, and Docker deployments.

Core Concepts

Understand the multi-brand model, payment lifecycle, and RBAC system before building.

Payment Flow

Trace a payment from API intent creation through gateway callback to webhook delivery.

Build docs developers (and LLMs) love