Features

Everything that ships for hub and stores.

Registry, PayPal, masked catalog, status bridge, fees, and licensed seats — built for WooCommerce and custom platforms.

Capability map

Four pillars of the processor

Each pillar solves a real multi-store problem — without forcing every shop onto WordPress.

Hub registry

Mint stores, rotate credentials, disable without downtime.

PayPal layer

Orders v2 on the hub — sandbox and live credential sets.

Masked catalog

Processor-facing titles and images — real prices stay accurate.

Status bridge

HMAC REST for Woo, signed webhooks for custom — with retries.

Multi-store hub

One registry. Many store identities.

The payment site holds credentials, platform labels, webhook URLs, and attribution — so each bridged order knows where it came from.

  • Disable, regenerate, or disconnect without taking the hub offline
  • Platform labels for Woo and custom stacks
  • Seat claims tied to your LicensePress plan
How minting works →

PayPal layer

Checkout lives on the hub — not on every shop.

PayPal Orders v2 with hosted fields and optional buttons. Sandbox and live credential sets stay central.

  • Hosted card fields on the payment domain
  • Apple Pay / Google Pay where your PayPal setup allows
  • One merchant configuration shared across stores

Delivery modes

Redirect or iframe — same money path.

Choose how the customer reaches hub checkout per session. postMessage is for UI hints only; paid status still comes from verified notify.

  • Redirect: open checkout_url in the browser
  • Iframe: embed with CSP allowlist for your origin
  • Never mark paid from a front-end message alone

Catalog masking

What PayPal sees is not what your storefront shows.

Push mask title, description, and image for processor-facing receipts. Real prices stay on the line; placeholders cover unsynced SKUs.

  • Per-product mask fields on the hub catalog
  • Cleaner receipts without exposing raw storefront names
  • Global placeholders when a SKU is not synced yet
See sync in the workflow →

Fees

Hub-side fee rules, store-side estimates.

Processing fees resolve on the Payment Hub per store. Stores can call fee/info before checkout so customers see accurate totals.

  • Configure fee logic once on the hub
  • Per-store resolution at session create
  • Optional estimates via fee/info

Security & seats

HMAC envelopes and licensed store slots.

Signed requests, replay windows, rate limits, and LicensePress seat claims — no inventing credentials offline.

  • HMAC-SHA256 over timestamp, request id, site id, action, payload
  • Redirect or iframe delivery per session
  • Hub-side fee rules with fee/info estimates for stores
  • HPOS-compatible Woo patterns on hub and Store-role shops
Custom platforms guide →

See it in sequence

Walk the full path from hub install to paid status — or pick a plan.