The unified payment multiplexer

One account.
Many products.

Unyplex multiplexes payments for multiple websites and products through a single account — checkout, webhooks, provisioning, and branded email — without wiring a payment integration into every project.

Payment gateway
  │ metadata: product=<id>, plan=<id>
  ▼
Unyplex ── resolves the product in its registry
  │ signed callback → your product provisions what the purchase grants
  ▼
Your product ── mints the entitlement (a key, a bucket, a tier)
  │ ↩ returns the email body
  ▼
Unyplex ── sends it, branded per product
How it works

Register once. Bill forever.

01

Register a product

Name, logo, plans, and a signed provision callback. One registration — never a code branch in the hub.

02

Take the payment

Checkout carries product + plan. Unyplex verifies the webhook and routes it to the right product.

03

Provision & deliver

Your product mints what the purchase grants and hands back the email. Unyplex sends it, branded.

Why Unyplex

The gateway is swappable. Your products never change.

One integration, N products

Stop re-wiring payments into every project. Register and go.

Provider-agnostic

Stripe today. The hub isolates the gateway, so a cheaper one slots in later — products don't re-integrate.

Branded per product

Each product keeps its own name, logo, and sender. Customers only ever see their brand.

Powering  CelDrive Powering  Pentasor