Two integrations, one API. Chapter I is a proof-of-concept on a mock Shopify storefront — because Shopify's checkout is gate-kept, we demonstrate rather than ship. Chapter II is a real WordPress plugin merchants install today — because WooCommerce is open, we ship what they'll actually use. The same dx-winkpg Stripe-shape API sits behind both.
A working demo end-to-end. Mock Shopify storefront & admin, a live WinkPG merchant, wired through dx-winkpg. Two customer flows: a B2B admin-driven pay-link, and a B2C QR takeover from the product page. Same API surface as production.
No gatekeeper, no mock. A WordPress plugin the merchant downloads, installs on their live WooCommerce store, and takes real payments through — card and ACH, at the checkout radio their customers already look at. Two modes: redirect and inline element.
Shopify's checkout is locked to certified providers — becoming one is a six-to-twelve-month approval process with Shopify's payments team, not an engineering task. So for Shopify, we demonstrate what a WinkPG integration looks like end-to-end using a mock merchant on our infrastructure, wired to a real WinkPG merchant record through our Stripe-shape API.
Your operations team creates a draft order in the mock admin, hits Send pay-link, and the buyer receives an SMS or email with a link. They pick card or ACH on the WinkPG page. The admin auto-updates to Paid when the webhook lands.
A desktop customer on the product page taps Pay with QR instead of entering the Shopify checkout. Their phone opens the WinkPG page, they pay with card or ACH, and the desktop advances to the order-confirmation page as soon as the payment lands.
The PoC is a mock storefront, a merchant admin, and a real WinkPG merchant record — glued to infrastructure that already runs in production.
qa.winkpg.ioLoopback processor for test transactions.dx-api.winkpg.comPayment intents, checkout sessions, mandates, refunds.Fixed scope, fixed cadence. Every milestone has a demoable artifact.
The Kestrel & Kite mock — nav, PDP, catalog, admin scaffold. Real product content wired to a local catalog.
Draft order → Send pay-link → SMS/email delivery. Payment Links endpoint wired.
PDP button, QR modal, desktop polling, redirect to thank-you.
Real merchant record, hosted-page template branded, notification subscription live. Then edge cases.
qa.winkpg.ioFull walk-through against the live PoC. Rehearsal + buffer for surprises.
WooCommerce is thirty-something percent of the world's e-commerce by count.
It's open-source, extended by plugins, and payment gateways are one such
extension: write a PHP class that inherits from
WC_Payment_Gateway,
register it, and it appears at the checkout alongside every other payment
method. No approval process. No revenue-share negotiation. So the artifact
for Chapter II isn't a mock — it's woo-winkpg.zip,
an actual plugin the merchant uploads through WordPress admin.
Both keep the merchant out of SAQ-D. Mode A puts them in the smallest tier of all; Mode B keeps the customer on-site through the whole checkout.
winkpg.com/pay/… → pays → redirects back to WooCommerce order-received.dx-api.winkpg.com; the merchant's page frames but doesn't touch the card.Standard WooCommerce plugin lifecycle — the same pattern every WordPress admin has done a hundred times.
woo-winkpg.zipFrom the dx-winkpg developer portal or via wp-admin → Plugins → Add New → search "WinkPG" (once we're on the WordPress.org directory).
WordPress Admin → Plugins → Add New → Upload Plugin → activate. Standard WooCommerce plugin lifecycle; nothing custom.
WooCommerce → Settings → Payments → WinkPG → paste sk_live_… and pk_live_…, choose Mode A or B, save. WinkPG appears as a payment method immediately.
A gateway plugin is a small, well-understood shape. Most of the work is testing edge cases; the wire is done in a couple of days.
Extends WC_Payment_Gateway. Settings page, API-key config, redirect-mode checkout, order write-back.
Iframe from dx-api.winkpg.com embedded in the checkout page. Uses the dx-winkpg client SDK.
Refund action from the WooCommerce order screen. WooCommerce Subscriptions extension compatibility. Partial payments, cancellations, expired sessions.
PHPUnit suite for the gateway class. Install-and-configure walkthrough. Optionally, submit to the WordPress.org plugin directory.
readme.txt for WordPress.orgwoo-winkpg.zip ready to installIn both integration models, the moment a card number or bank account is typed, the customer is on WinkPG's hosted page, inside their PCI-DSS certified boundary. The merchant's storefront, their admin, and their database never see sensitive data.
Card & bank entry live on winkpg.com,
served inside their PCI boundary. Annual self-attestation. No quarterly
scans, no on-site.
A card number touching a form or database you own — even briefly — expands scope: quarterly ASV scans, annual audit, formal change control, penetration testing. Thirty to eighty thousand a year for a mid-market merchant.