✨ 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

SleekView for PayKickstart Bridge: synced orders & subscriptions as tables

PayKickstart hosts the cart and affiliate tracking, and the bridge plugin syncs orders, rebills, and refunds into WordPress. SleekView reads those rows so funnel, affiliate, and dunning views land on one workspace.

♾️ Lifetime License available

SleekView table view for PayKickstart Bridge

PayKickstart's affiliate-heavy data, as tables

PayKickstart Bridge plugins receive webhooks from PayKickstart's hosted checkout and write each event into WordPress, usually as a pks_order custom post type with PayKickstart-specific metadata in wp_postmeta (pks_campaign_id, pks_product_id, pks_affiliate_id, pks_amount, pks_currency). Rebills, refunds, and subscription cancellations each arrive as separate events linked by the subscription id.

The default bridge admin is a stock WP list with a fixed column set. PayKickstart's strength (affiliate tracking and recurring campaigns) is the part that suffers in that flat view, because the affiliate id and campaign id are buried in postmeta and the rebill history requires opening each order. Affiliate performance audits, top-affiliate ranking by net revenue, and per-campaign dunning all need joined views that the bridge list does not provide.

SleekView pivots pks_* postmeta into proper columns, joins related events by subscription id, and groups by campaign or affiliate for the operational rankings ops teams actually run. Inline edits cover the internal fields the bridge exposes (tags, notes, fulfilment flags). Refunds and affiliate-commission adjustments stay in PayKickstart since those are hosted-side actions.

Workflow

PayKickstart events as a joined workspace

1

Map the bridge post type

Point SleekView at pks_order and expose the PayKickstart postmeta keys (pks_campaign_id, pks_affiliate_id, pks_product_id, pks_amount).
2

Group by affiliate or campaign

Per-affiliate ranking grouped on pks_affiliate_id, or per-campaign performance on pks_campaign_id. Aggregate columns compute paid count, refund count, and net revenue.
3

Save the dunning view

Filter to rebill-failed events grouped by subscription id, with customer email and last-failure timestamp visible. That is the dunning queue across the whole base.
4

Edit the writeable fields

Tags, notes, and custom flags are writeable inline. Refunds and affiliate-commission changes link out to PayKickstart so the hosted backend stays canonical.

Sample columns

A typical PayKickstart Bridge view

Pivots pks_* postmeta and joins related rebill events by subscription id.
Source: wp_posts (post_type=pks_order) + wp_postmeta
Order Status Customer Campaign Affiliate Amount Date
PK-58210 Paid alex@studio.co Pro Annual aff-204 $249 May 15
PK-58209 Pending ria@design.io Studio Monthly aff-118 $29 May 15
PK-58208 Paid tom@hello.dev Pro Annual none $249 May 14
PK-58207 Refunded mia@brew.coop Studio Monthly aff-204 $29 May 14

Comparison

Default PayKickstart Bridge admin vs SleekView

Default PayKickstart Bridge admin

  • Campaign and affiliate ids hide in postmeta, not in the list view
  • No top-affiliate ranking by net revenue
  • Per-campaign dunning across rebill events needs custom queries
  • Subscription rebill history requires opening each order
  • Refund cohorts by affiliate or campaign need CSV exports

SleekView

  • Pivot pks_campaign_id, pks_affiliate_id, pks_product_id into columns
  • Rank affiliates by net revenue and refund rate across the synced base
  • Per-campaign dunning filtered to rebill-failed events
  • Join rebill events by subscription id for full payment history per customer
  • Saved views: funnel performance, affiliate audit, dunning, customer LTV

Features

What SleekView gives you for PayKickstart Bridge

Affiliate performance

Group by pks_affiliate_id with paid count, refund count, and net revenue as aggregate columns. Rank affiliates inline without exporting from PayKickstart.

Per-campaign view

Pivot pks_campaign_id and surface paid, pending, and refund counts. Compare campaigns side by side before the next launch cycle.

Rebill triage

Filter to rebill-failed events grouped by subscription id. Dunning queue with customer email and last-failure timestamp for one-click outreach.

Audience

Who uses SleekView for PayKickstart Bridge

Affiliate manager

Top-affiliate ranking by net revenue and refund rate, filterable by campaign and date range. Identifies the affiliates worth keeping and the ones driving refunds.

Subscription ops

Rebill-failed view filtered by campaign with customer email and last-failure date. Resolves dunning before PayKickstart's next retry.

Support

Customer view with active subscription, rebill history, and affiliate attribution. Triage without opening the PayKickstart dashboard per ticket.

The bigger picture

Why affiliate-heavy funnels need a joined admin

PayKickstart's value proposition leans heavily on built-in affiliate tracking, recurring rebills, and one-click upsell flows on a hosted checkout. The data shape that produces (orders plus rebills plus refunds, each tagged with affiliate id and campaign id) is exactly what an ops team needs joined for affiliate audits, dunning, and campaign reviews. The bridge plugin lands every webhook event in WordPress, which is the right architectural choice, but the default admin shows a flat post list with affiliate id and campaign id hidden in postmeta.

That works for a single order lookup and fails for the ranking and cohort views that drive day-to-day decisions. SleekView pivots PayKickstart's postmeta into proper columns and gives each role the joined view it needs. Affiliate managers rank affiliates by net revenue and refund rate inline.

Subscription ops triage rebill-failed events grouped by subscription id before the next gateway retry. Support agents resolve a customer issue with full attribution and rebill history visible in one row. PayKickstart's dashboard remains the right place for affiliate-commission changes and refund processing.

SleekView fills the joined daily admin gap that the bridge list cannot.

Questions

Common questions about SleekView for PayKickstart Bridge

PayKickstart sends webhooks on every purchase, rebill, refund, and cancellation. The bridge plugin validates the signature and writes a pks_order post with PayKickstart-specific metadata in wp_postmeta. SleekView reads from the same tables.

 

Internal fields exposed by the bridge (tags, notes, fulfilment flags) are writeable. Refunds, affiliate-commission adjustments, and subscription changes stay in PayKickstart since those are hosted-side actions.

 

Each rebill arrives as its own row keyed by subscription id. SleekView joins related rebill events by subscription id for full payment history per customer, and aggregates net revenue per subscription for LTV ranking.

 

Yes. Group by pks_affiliate_id with paid count, refund count, and net revenue as aggregate columns. Filter by campaign and date range for the affiliate audit views PayKickstart users run constantly.

 

Course-platform bridges typically write the access-granted flag into postmeta on the order. SleekView surfaces that column so fulfilment teams confirm access alongside payment without opening the course platform.

 

Yes. PayKickstart's bump and upsell selections land in postmeta on the order row. Surface them as columns and filter to see take-rate per bump or per upsell step.

 

Coupon codes from PayKickstart's hosted checkout land in postmeta on the order. Group by coupon to see which codes drove revenue and which generated the most refunds.

 

pks_affiliate_id indexes well as a postmeta key, and SleekView caches the heavier aggregates (top-affiliate ranking, per-affiliate refund rate) so dashboards stay responsive even with hundreds of active affiliates and thousands of synced orders.

 

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