Payment engineering
Payment webhooks in WooCommerce: design for the second delivery
A practical guide to verified payment events, duplicate deliveries and safe recovery, with a checklist for testing a WooCommerce gateway.
WideDock by Wideview Entertainment
Your software. One place to dock.
Thoughtfully built software, from the people who develop it. Meet VivaGo, our first WooCommerce payment plugin in development, and explore the engineering behind it.
VivaGo is not available for purchase yet. Features and supported versions will be published with the tested release.
Our first product
All products
VivaGo In development
Viva.com and Stripe payments for WooCommerce, currently in development.
- Category
- Payments
- Platform
- WordPress, WooCommerce
- Target markets
- Greece & international
Know what you have. Find what you need.
We are building one place for product information, licences, releases and support. Usage, updates and support will have clear, separate conditions, published before sales begin.
Read our journalClear decisions, before the first release.
Start with the store
Payment software sits inside a real business. Customers need to know whether their payment succeeded. Store owners need a consistent order history and a recovery path when something is delayed. We start with those situations when defining a product, then work through the interface and the server behaviour together. A payment button is only one part of that experience.
Make the important boundaries visible
We are building WideDock as the common home for product information, licences and releases. Each product has its own development and compatibility work. That separation helps us describe what is available, what is planned and which conditions belong to updates or support. It also keeps the merchant’s own payment flow separate from the software-distribution platform.
Publish what can be explained
Our journal shares concrete engineering questions and checklists: repeated payment events, checkout and storage compatibility, and the meaning of a plugin licence. Each article links to relevant primary documentation and is available in English, Greek and German. We aim to make technical decisions understandable without turning an unreleased feature into a promise.
From the journal
Explore the journalWooCommerce compatibility
HPOS and Checkout Blocks: what payment plugin compatibility really means
How to assess a WooCommerce payment plugin across order storage, checkout experience and real store conditions, without relying on one compatibility badge.
Product principles
Plugin licences, updates and keeping a store running
Separate usage, updates, downloads and support when evaluating a plugin licence. Our design principles for licensing outside the payment path.