What Is UC Pay | UC Pay - Where the Kingdom Transacts.

1. What is UC Pay?

UC Pay is a network‑grade payment orchestration system for WordPress Multisite. It provides Stripe‑Connect‑class capabilities using NMI, WooCommerce, and Woo Subscriptions.

Key Promise: Payments route directly from buyer → merchant. No pooled funds. No float. No credential sharing.

One‑time payments (single & multi‑merchant)
Subscriptions (single‑merchant enforced)
Crowdfunding & donations
Fee recovery (optional, transparent)

2. System Architecture

Core Components

Component	Role	Activation
UC Pay Core	PayFac brain, vault resolution, idempotency	Network
UC Pay Gateway	WooCommerce payment gateway	Network
WPCF Recurring	Campaign subscription logic	Per‑site

Merchant Lock Rule (Non‑Negotiable)

A subscription is permanently locked to one merchant MID. Vault tokens are created under that MID. Renewals can never switch merchants.

This rule ensures:

PCI safety
NMI vault integrity
Accurate accounting

3. Supported Use Cases

One‑Time Payments

Single merchant checkout
Multi‑merchant marketplace checkout
Optional customer fee recovery

Subscriptions

Single merchant only (enforced)
Woo Subscriptions native lifecycle
Off‑session renewals via vault tokens

Crowdfunding / Give Hub

Monthly campaigns
Campaign‑level fee recovery
True subscriptions (not fake carts)

4. Network Admin Guide

Installation Order

1. Network‑activate UC Pay Core
2. Network‑activate UC Pay Gateway
3. Activate WooCommerce on subsites
4. Activate WPCF Recurring only where needed

Why Core Must Be Network‑Activated

Central vault resolution
Idempotent renewals
No credential crossover

Fee Recovery Setting

Each subsite controls fee recovery independently:

WooCommerce → Payments → UC Pay → 
✓ Allow customers to cover transaction fees

5. Merchant / Creator Guide

Connecting Your Payment Account

Enter your NMI credentials once
UC Pay stores them securely
Funds go directly to your account

Subscriptions

When someone subscribes:

Vault token is created under your MID
Subscription is locked to you
Renewals charge automatically

Fee Recovery

If enabled, customers may cover:

Processing fees
Gateway costs

Fees are transparent and shown at checkout.

6. Developer Guide

Transaction Routing

Order → UC Pay Gateway →
Vendor grouping →
UC Pay Core →
NMI

Idempotency

UC Pay Core prevents duplicate charges using:

Vendor ID
Order ID
Transaction type
Amount

Extending UC Pay

Custom fee logic
Risk checks
Reporting dashboards

UC Pay is intentionally designed as infrastructure — not just a plugin.

7. FAQ

Does UC Pay pool funds?

No. Funds always move directly from customer → merchant.

Can subscriptions be multi‑merchant?

No. This is intentionally blocked.

Is this PCI compliant?

Yes. Card data is vaulted via NMI. Tokens are merchant‑scoped.