Purpose
Explain the major PayPress systems and how they fit together.
Overview
PayPress is a WordPress plugin that uses Stripe Checkout for payment collection and WordPress for merchant-facing operations. Stripe remains the source of truth for payments, subscriptions, invoices, receipts, refunds, tax, promotion codes, and payment methods.
How It Works
PayPress stores plans in WordPress, launches Stripe Checkout through validated server-side flows, receives Stripe webhooks, validates installation ownership, and persists local orders and subscriptions. Admin pages then display the synchronized local records.
Important Components
- Plans.
- Checkout launchers.
- Checkout context.
- Webhooks.
- Orders.
- Subscriptions.
- Refunds.
- Donation and fundraising snapshots.
- Payment Forms.
- Analytics.
- Diagnostics.
- Admin design system.
Data Flow
Plan settings -> front-end shortcode -> launcher or donation route -> Stripe Checkout -> Stripe webhook -> ownership validation -> idempotent local persistence -> admin views, success page, exports, analytics, and diagnostics.
Security Considerations
Sensitive card data is handled by Stripe Checkout. PayPress validates webhook signatures and installation ownership before merchant-facing writes. Public REST endpoints expose only allowlisted state.
Known Limitations
PayPress is not a custom payment processor, tax engine, coupon manager, shipping-rate engine, analytics warehouse, or CRM. Some roadmap features such as partial refunds, conditional logic, reusable forms, and free trial configuration are deferred.