✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekPixel for WooCommerce Payments order receipts

WooCommerce Payments captures cards, Apple Pay, and BNPL through WordPress.com Payments infrastructure. SleekPixel hooks into each paid order, reads the totals and line items from wp_wc_orders, and renders a branded receipt card that ships with order emails and shareable order pages.

♾️ Lifetime License available

SleekPixel example output for WooCommerce Payments

From captured order to branded receipt card

WooCommerce Payments writes each order to the High Performance Order Storage tables, with payment status in wp_wc_orders, line items in wp_woocommerce_order_items, and the capture intent stored as _wcpay_intent_id postmeta. When a charge succeeds, the order moves to wc-processing and triggers the woocommerce_order_status_processing action. That hook is where SleekPixel listens.

The template reads order number, total, currency, and the first two or three line items, then renders a branded card with capture status, payment method last four, and the storefront's logo. The card is written to the uploads directory as a real PNG, attached to the order as a meta key _sleekpixel_receipt, and referenced from the customer-facing order page's og:image tag. When a customer shares the order URL in support chat or via the customer dashboard, the receipt card previews instead of the storefront's homepage OG image.

The integration handles refunds and partial captures the same way. When woocommerce_order_status_refunded fires, the card re-renders with a refunded badge and the new total. Each variant is a real file, so platforms cache it like any other image.

Workflow

From captured WooPayments charge to shareable card

1

Detect a WooPayments capture

SleekPixel listens for woocommerce_order_status_processing, then checks the _payment_method field for woocommerce_payments to confirm this is a WooPayments order.
2

Read the order via CRUD

Order totals, currency, line items, and the payment intent meta are read through wc_get_order() so SleekPixel works on both HPOS and legacy storage.
3

Render the receipt card

Order data is mapped into a branded card layout with the storefront logo, totals, capture status, and first line items, then exported as a 1200 by 630 PNG.
4

Attach to the order

The PNG is saved to uploads and linked via _sleekpixel_receipt meta, then referenced from the customer order page's og:image tag for sharing.

Output

Sample WooPayments order receipt card

Rendered from a real WooCommerce Payments order with capture status, line items, and totals pulled from the High Performance Order Storage tables.

Format: PNG, OG + Twitter card Dimensions: 1200 × 630
SleekPixel example output for WooCommerce Payments

Comparison

Default Woo order OG vs SleekPixel for WooCommerce Payments

Storefront logo on orders

  • Every WooPayments order page shares the same storefront logo as its OG image
  • Order totals, currency, and capture status never surface in link previews
  • Customer-facing order URLs look identical whether the order is paid or pending
  • Support chat receipts have no visual context about which order is referenced
  • Refunds and partial captures are invisible to anyone glancing at a shared link

SleekPixel

  • Hooks woocommerce_order_status_processing when WooPayments captures a charge
  • Reads totals and items from wp_wc_orders and order items table
  • Stores the receipt card as _sleekpixel_receipt attached to the order
  • Refund cards re-render on woocommerce_order_status_refunded automatically
  • Works with HPOS and legacy post-based order storage without configuration

Features

What SleekPixel gives you for WooCommerce Payments

Capture-aware receipts

Cards render with the actual WooPayments capture status, last four of the card or wallet, currency, and order total. Each receipt reflects the payment state at the moment the OG image was generated.

Refund and partial logic

When a refund fires, the receipt re-renders with the new balance and a refunded badge. Partial captures show captured versus authorized amounts so shared links stay accurate to the real order state.

HPOS-native CRUD reads

Reads order data through Woo's CRUD layer, so it works on the new High Performance Order Storage tables and legacy wp_posts orders without separate code paths or migrations.

Use cases

Where WooPayments stores get the biggest win

Customer order confirmations

Shared order URLs preview a branded receipt card in messengers and email clients, so customers see their actual order, not the storefront logo.

Support chat handoffs

When support agents paste an order link in chat, the preview shows order number, total, and capture status at a glance instead of a generic site image.

Internal order recaps

Slack and Teams channels that follow new sales get visual context per order, so finance and ops see card style and amounts without opening the dashboard.

The bigger picture

Order links should preview the order

WooCommerce Payments handles tens of thousands of stores running on the WordPress.com payments stack. Each order generates a customer-facing URL that gets shared in email, on chat with support, and sometimes in screenshots passed between finance and ops. That URL is also what gets sent into Slack channels watching new sales, into help desk tools that link back to the dashboard, and into automation that fires when an order is refunded.

In every one of those places, the default OG image is the storefront's homepage logo. So a $4,800 order looks identical to a $19 order in previews. A refunded order looks identical to a captured one.

SleekPixel changes that by treating each order as its own piece of content. The receipt card carries the order number, total, currency, capture status, and last four of the payment method, then ships as a real PNG attached to that order. When the order is shared anywhere, the preview reflects the order state at that moment, not the storefront's brand identity.

That single difference makes shared order links readable at a glance.

Questions

Common questions about SleekPixel for WooCommerce Payments

Yes. SleekPixel uses wc_get_order() to read order data, which is HPOS-aware. Whether your store is fully migrated to wp_wc_orders or still on the legacy wp_posts tables, the integration reads the same fields and renders the same card.

 

Order number, total, currency, capture status, payment method (card brand and last four or wallet name), and the first two or three line items by default. The template editor lets you swap any of these for other order fields such as customer name, ship-to city, or coupon codes.

 

Refunds hook into woocommerce_order_status_refunded and re-render the card with a refunded badge and updated total. Partial captures show the captured amount alongside the authorized amount so the card reflects the real balance, not the original order value.

 

Real files. Each card is rendered server-side when the order status changes and saved to the uploads directory. The order's og:image tag points to the static URL, so platforms cache it like any other image and there is no rendering cost per share.

 

No. The card shows only the card brand and last four digits, which is the same information WooPayments shows on the order confirmation email. Full card numbers, customer addresses, and personally identifiable data are never written into the image.

 

Yes. SleekPixel supports conditional templates based on order content. A digital product order can render a download-style card, while a physical product order can render a shipping-status card. The conditions read line item taxonomies and metadata directly from the order.

 

Yes. You can opt into rendering cards for on-hold, completed, cancelled, and refunded statuses. Each one can use its own template and badge so a cancelled order link looks visibly different from a paid one.

 

Existing orders stay untouched until you run the bulk regenerate command, which is a WP-CLI task that walks the orders table in batches and renders a card per order. The job runs in the background so the admin stays responsive while older orders catch up.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView