FinPay

One payment hub.
Many stores.

Connect WooCommerce and custom storefronts to one Payment Hub. Customers pay once via PayPal — status returns to the store that started the order.

View plans See the workflow
WooCommerce store role
Custom Store API
PayPal Orders v2
HMAC status sync
HPOS ready
Licensed seats

Trusted by design

Secure. Verified. Built to scale.

FinPay is engineered for multi-store networks — signed traffic, licensed seats, and a hub that stays online when a single store changes.

HMAC signed

Requests and status webhooks are signed — stores and hub verify every payload.

Secure

Licensed seats

Connect and pay flows check LicensePress plan limits — no offline credential inventing.

Trusted

Multi-store scale

One hub, many stores — WooCommerce and custom — grow seats as your network grows.

Scalable

PayPal Orders v2

Checkout runs on the payment layer with sandbox and live credential sets.

Verified rail

Status retries

Backoff retries plus admin Order Sync keep origin orders in sync when the network blips.

Resilient

HPOS ready

Built for modern WooCommerce high-performance order storage on hub and stores.

Woo ready

Architecture

A live mesh between stores and money

Every connected storefront talks to one Payment Hub. The hub owns PayPal. Your stores keep catalog, cart, and customer email.

Store A WooCommerce Store B Custom API Store C Headless FinPay Payment Hub PayPal checkout
Session create Status return Hub owns money rail

Live workflow

Watch a payment move through the graph

From storefront session → FinPay hub → PayPal checkout → signed status back to the origin store.

Store A WooCommerce Store B Custom API Store C Headless FinPay Payment Hub PayPal checkout Status sync HMAC → origin order 01 CREATE SESSION 02 CHECKOUT 03 STATUS RETURN

Create session

Store creates a payment session on the hub — WooCommerce or Custom API.

PayPal checkout

Customer pays via PayPal on the Payment Hub — redirect or iframe.

Status return

Signed status finalizes the originating store order with HMAC sync.

Core systems

What ships in the plugin today

Hub registry, PayPal layer, masked catalog, order bridge, fees, and licensed seats — one processor for the whole network.

Multi-store hub

Mint stores, rotate credentials, disable without taking the hub offline.

PayPal Orders v2

Hosted fields and buttons on the hub — sandbox and live credential sets.

Product masking

Processor-facing titles and images — real prices stay on the line.

Status bridge

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

Redirect / iframe

Per-session delivery mode with CSP allowlist for connected origins.

Licensed seats

Store slots claim against your LicensePress plan — no offline inventing.

Explore all features →

Catalog engine

Mask what PayPal sees. Keep what your store sells.

Push products to the hub with masked title, description, and image for processor-facing receipts. Real prices stay accurate. Global placeholders cover unsynced SKUs.

  • Per-product mask fields
  • Hub-side catalog for checkout
  • Clean receipts without exposing raw storefront names
Product masking details
Raw store titles

Inconsistent · noisy

Masked catalog

Clean · checkout-ready

Mask & standardize

Remove storefront noise — normalize titles PayPal sees on receipts.

Per-product masks

Set masked title, description, and image per SKU on the hub catalog.

Hub catalog sync

Push the masked catalog so checkout and the processor stay in sync.

Cleaner receipts

Customers and PayPal see structured titles — your storefront names stay private.

Order bridge

Payment on the hub. Status on the origin store.

Store creates a bridged checkout session. After PayPal capture on the Payment Hub, status returns as HMAC REST (WooCommerce) or a signed webhook (custom) — with retries and admin Order Sync recovery.

  • Attributed bridged orders on the hub
  • Immediate notify + Action Scheduler / cron retry
  • Customer emails stay on the originating store
Full status workflow
PAYMENT HUB ORIGIN STORES 01 CREATE SESSION → 02 CAPTURE → 03 STATUS RETURN Checkout session Redirect / iframe Payment successful $129.00 · captured Store A · WooCommerce HMAC REST /orders/status PAID Store B · Custom API Signed webhook PAID Store C · Headless Signed webhook PAID { status: paid } HMAC → ORIGIN STORE Warm = create session · Lime = status return · Store remains system of record

Instant status sync

Hub notifies the originating store as soon as PayPal capture succeeds.

Signed & reliable

HMAC REST for Woo, signed webhooks for custom — plus retries and Order Sync.

Woo + custom stores

Same paid outcome whether the storefront is WordPress or a custom stack.

Pipeline

Four beats from install to live sessions

01

Install Payment Hub

WordPress + WooCommerce, Payment role, PayPal sandbox or live.

02

Mint & connect

Add Woo or custom stores. Copy credentials once — store them securely.

03

Sync masked catalog

Push products so the processor sees clean titles, not raw SKU noise.

04

Create sessions

Redirect or iframe checkout on the hub; status finalizes the origin order.

Open full workflow →

Broad solutions

WP stores and custom stores on the same hub

The Payment Hub is WordPress + WooCommerce. Connected storefronts are not limited to WordPress.

WooCommerce multi-store

Store role on each shop, Payment role on the hub. Catalog sync, checkout bridge, status back to Woo orders.

Custom platforms

Keep Laravel, Node, or headless. The hub handles payment; your app gets status when the customer pays.

Agencies

Per-store credentials, attribution, and hub-side registry — many client storefronts, one payment site.

Shared outcome

One PayPal destination, masked products, status on the originating store, emails owned by the store.

Read full solutions →

Custom platforms

Your stack. Our payment hub.

Keep building on Laravel, Node, or headless commerce. FinPay is the payment destination — not a forced rebuild in WordPress.

Your storefront

Laravel Node Headless

Payment Hub

FinPay WP + Woo hub

WordPress payment destination

How custom platforms connect →

Secure credentials

Per-store keys — rotate or disable without taking the hub offline.

Signed status sync

HMAC webhooks return paid status to your origin storefront.

Any stack

Laravel, Node, headless — connect without rebuilding in WordPress.

Scalable seats

Grow connected stores under your LicensePress plan limits.

Control plane

Credentials, fees, and seats under one roof

Store credentials

Regenerate keys, disable a store, or disconnect — without taking the payment hub offline.

Processing fees

Hub-side fee rules per store. Stores can fetch fee info for estimates before checkout.

Licensed seats

Connect and create-payment verify the hub license and store claim against your plan.

Upcoming

Stripe & multi-account failover

Quota rotation and admin notify are on the roadmap — same hub model, more rails.

See the roadmap →

Explore

Go deeper when you are ready

SolutionsAgencies, multi-store brands, and non-WP platforms. Full workflowHub setup, connect, sync, pay, notify, retries. Custom platformsConnect any stack to the WordPress payment hub. FeaturesPayPal layer, product masks, fees, seats, sync. PricingStarter, Growth, Scale — monthly/annual 70% off. Custom developmentOther gateways and platform-specific builds.

Insights

Notes from the field

Workflow

Why separate the payment domain

Hub checkout, store attribution, and status retries explained end-to-end.

 Platforms

Connecting a non-WP store

Why custom platforms stay easy — and where the technical guide lives after install.

 Roadmap

Stripe & multi-account failover

What is coming next for quota rotation and admin notify.

Ready for one payment destination?

Compare plans or see how custom platforms connect to the hub.

View plans Start Growth