Open Source Payment Orchestrator

The Payment Infrastructure You Actually Own.

A fully self-hosted, multi-brand orchestrator. Process payments your way, eliminate third-party vendor lock-in, and scale with absolute sovereignty.

Access Dashboard Try Demo Checkout

POST /api/checkout/intents

curl -X POST https://your-app.pages.dev/api/checkout/intents \
  -H "Content-Type: application/json" \
  -d '{
    "payment_link_uuid": "abc-123",
    "gateway_slug": "stripe",
    "amount": "150.00",
    "customer_email": "user@example.com"
}'

Acme Corp

$150.00

Card Information

Developer-first Infrastructure

Everything you need to run a high-performance, sovereign payment gateway on Cloudflare Pages.

Admin Dashboard

Real-time KPIs, revenue charts, transaction lists, and customer management — all in one beautifully designed interface.

Multi-Brand Support

Manage multiple brands from one admin panel with per-brand gateways, themes, currencies, and customers.

Multiple Gateways

Stripe, SSLCommerz, bKash, NowPayments (crypto), and manual bank transfer — built-in adapters for global payments.

Double-Entry Ledger

Every transaction automatically books a balanced double-entry ledger record. Auditable, accounting-grade accuracy.

Frequently Asked Questions

What do I need to deploy this?

A Cloudflare account (free tier works), a Turso database (also has a free tier), and API keys for whichever payment gateways you want to use. The full setup takes about 15 minutes.

Is it really free to host?

Yes. Cloudflare Pages has a generous free tier (500 builds/month, unlimited requests). Turso's free tier gives you 9GB across 500 databases. Stripe, bKash, and others charge per-transaction fees but have no monthly minimum.

How is this different from the original OwnPay?

This is a JavaScript reimplementation that runs on Cloudflare's edge network instead of a PHP/MySQL server. The UI is cloned from OwnPay's design, and the schema mirrors OwnPay's database structure — but the backend is built on Hono + Turso for serverless deployment.

What about PCI compliance?

You never touch card data directly. Stripe handles card fields in their own iframe (Stripe Elements). Your server only sees a Payment Intent ID — keeping you on Stripe's PCI-SAQ-A path.