OwnPay is a self-hosted, open-source payment infrastructure designed to run entirely on your own server. Unlike standard payment processors or SaaS gateways, OwnPay provides complete control over your transaction ledger, isolated white-label store domains, sandboxed plugin gateways (supporting 123+ platforms including bKash, Nagad, Stripe, and PayPal), and native Android SMS parsing.
This repository contains the source code for the official OwnPay documentation portal hosted at learn.ownpay.org.
- Main Repository: own-pay/OwnPay
- Official Website: ownpay.org
To run the documentation portal locally, make sure you have Node.js v24.15.0 installed.
npm installnpm run devThe dev server will boot up locally (typically at http://localhost:5173/).
npm run buildGenerates statically compiled files in .vitepress/dist/ along with a dynamic sitemap.xml.
We welcome improvements and additions to the guides. Follow the instructions below to add or modify content.
- Find the target Markdown (
.md) file inside the workspace (e.g., insideuser-guide/ordeveloper/). - Implement your edits following the standard Markdown syntax.
- Verify your layout and formatting look correct on the local development server before staging.
- Create a new
.mdfile in the appropriate directory (e.g.,user-guide/new-section/guide-name.md). - Add standard Markdown headings (
#,##, etc.). Use a single<h1>title at the top of the file. - Open .vitepress/config.mjs and register your new guide inside the
sidebararray under the correct navigation block so that it appears in the sidebar menu.
To maintain premium quality, high readability, and technical accuracy, all documentation updates must adhere to the following rules:
- Use do-follow links: Ensure all links pointing to any
ownpay.orgdomain or subdomain are standard do-follow links (norel="nofollow"attributes). - Clear Headings: Use clean, structured headings to allow readers to scan pages easily.
- VitePress Features: Utilize built-in VitePress alerts (
::: info,::: warning,::: danger) to highlight important warnings.
- Do not use absolute paths for assets: Always link images and local assets using relative paths (e.g.,
../public/image.png) rather than local file URLs or hardcoded dev domains. - Do not add generic/SaaS placeholders: Do not add marketing pitches, waitlist forms, or SaaS fee calculations. The documentation is targeted at active self-hosters and developers.
- Do NOT bypass Ledger Integrity rules: Never write integration examples or guides that suggest bypassing the double-entry bookkeeping rules. Absolute precision is mandatory.
- Do NOT commit credentials: Never commit actual API keys, passwords, private keys, or SSH credentials. Use placeholders (e.g.,
op_live_...) in code examples.