✨ 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 Cashfree for WooCommerce: orders & payment metadata as tables

The Cashfree gateway writes its order, payment, and refund IDs as WooCommerce order meta. SleekView pivots those keys into named columns, HPOS-aware, with gateway-scoped filters so settlement reconciliation lives in the orders view.

♾️ Lifetime License available

SleekView table view for Cashfree Payment Gateway for WooCommerce

Cashfree IDs as real columns

Cashfree Payment Gateway for WooCommerce stores its Cashfree-side identifiers as order metadata. cf_order_id, cf_payment_id, cf_refund_id, and the chosen payment mode (UPI, netbanking, card, wallet) all live on wp_wc_orders_meta on HPOS stores or wp_postmeta on legacy. The default WooCommerce orders list shows core fields only, so none of those identifiers are visible without opening each order.

SleekView reads the right storage automatically and pivots the cf_* meta keys into named columns. A payment-method filter scopes the view to Cashfree-only orders, and the chosen payment mode becomes its own column for UPI-vs-card cohort analysis. Settlement IDs land alongside payment IDs so reconciliation against the Cashfree merchant dashboard happens row by row instead of tab by tab.

Edits stay in the WooCommerce CRUD layer; refunds still go through Cashfree's API via the gateway's admin action. SleekView never re-authenticates against Cashfree and never proxies its endpoints; it only surfaces the data the gateway already writes into the order record.

Workflow

From buried meta keys to gateway-scoped tables

1

Detect storage mode

SleekView checks HPOS vs legacy and reads wc_orders_meta or postmeta accordingly. Same path the Cashfree plugin uses, so storage detection stays consistent across both layers.
2

Pivot Cashfree keys

Move cf_order_id, cf_payment_id, cf_payment_mode, and settlement IDs from meta into named columns. The agent UI lists every cf_* key on the install.
3

Save views per role

Save "Cashfree finance", "UPI cohort", or "Failed payments" views and scope each to finance, analytics, or support via WordPress capabilities.
4

Edit inline or bulk-update

Inline-edit reconciliation flags and internal notes; bulk-update statuses for cohorts (e.g. mark all settled Cashfree orders for a date range) through the WooCommerce CRUD layer.

Sample columns

A typical Cashfree orders view

SleekView filters WooCommerce orders by Cashfree and pivots Cashfree-specific meta keys into columns.
Source: wp_wc_orders_meta + wp_postmeta (cf_* keys)
Order # Status Total CF payment ID Mode Date
#33102 Completed ₹2,499.00 cf_pay_8821... UPI May 14
#33101 Pending ₹899.00 cf_pay_8820... Netbanking May 14
#33100 Completed ₹540.00 cf_pay_8819... Card May 13
#33099 Failed ₹1,250.00 cf_pay_8818... Wallet May 13

Comparison

Default Cashfree Payment Gateway for WooCommerce admin vs SleekView

Default Cashfree for WooCommerce admin

  • cf_payment_id and cf_order_id hidden in order meta, invisible at list level
  • Payment mode (UPI, card, netbanking, wallet) not exposed as a column
  • No filter to isolate Cashfree-paid orders from other gateways
  • Settlement IDs require opening each order's meta panel
  • Failed payments grouped with successful ones, no failure-reason column

SleekView

  • Pivot cf_payment_id and cf_order_id into named columns
  • Filter by gateway to scope the view to Cashfree-paid orders
  • Surface cf_payment_mode as a column for UPI-vs-card cohort review
  • HPOS-aware: reads wc_orders_meta on modern stores, postmeta on legacy
  • Add failure-reason as a column for support triage

Features

What SleekView gives you for Cashfree Payment Gateway for WooCommerce

HPOS-aware reads

Cashfree uses the WooCommerce meta API and SleekView mirrors that, reading wc_orders_meta on HPOS and postmeta on legacy. The same view config works on WooCommerce 8.2+ and older installs.

Mode-scoped filters

Filter by cf_payment_mode to see UPI versus card versus netbanking cohorts. Pair with date range for AOV comparisons across modes inside one orders view.

Settlement reconciliation

Surface settlement IDs alongside payment IDs so finance can match Cashfree payouts to WooCommerce orders without switching tabs. The export honors active filters.

Audience

Who uses SleekView for Cashfree for WooCommerce

Finance teams

Reconcile Cashfree settlement files against WooCommerce orders by filtering on payment method and date, with cf_payment_id and settlement ID inline. Settlement matching turns into one saved view.

Conversion analysts

Segment AOV and success rates by cf_payment_mode (UPI, card, netbanking, wallet). The data is already in WooCommerce; surfacing it does not require a separate analytics warehouse.

Customer support

Search by Cashfree payment ID or order number, see status, mode, and failure reason inline. Support tickets that ask "why did my payment fail" answer in one screen.

The bigger picture

Cashfree metadata is data the orders screen ignores

WooCommerce's orders list is built around core order fields, not gateway-specific metadata. That works for simple stores but breaks for Indian merchants running Cashfree across UPI, netbanking, card, and wallets in parallel. Finance teams reconciling Cashfree settlement files need cf_payment_id and settlement ID as columns to match payout lines, not as buried meta entries.

Conversion analysts comparing UPI versus card need cf_payment_mode as a filter chip and a column. Support triaging failed payments needs the failure reason inline. The default workflow forces custom reports, custom code, or a tab-flip between the Cashfree merchant dashboard and WooCommerce admin.

SleekView pivots cf_* meta into proper columns and detects HPOS automatically, which collapses each workflow into one saved view. The gateway still owns the API operations, refunds still go through Cashfree, but the data Cashfree writes into your orders finally becomes queryable as plain WooCommerce data.

Questions

Common questions about SleekView for Cashfree Payment Gateway for WooCommerce

Cashfree does not add its own primary tables. All payment data lives as WooCommerce order metadata. SleekView reads wc_orders_meta on HPOS or postmeta on legacy automatically, so the same view config works regardless of storage.

 

cf_order_id, cf_payment_id, cf_refund_id, cf_payment_mode, settlement IDs, and any other cf_* key your install writes. The agent UI lists every present key so you do not have to dig through the plugin source.

 

No. Refunds go through the Cashfree API via the WooCommerce admin's refund flow. SleekView surfaces refund IDs and status but never proxies the gateway API. Inline edits affect only local meta and notes.

 

Yes. SleekView detects which storage the site uses and reads accordingly, same as the Cashfree gateway plugin itself. WooCommerce 8.2+ defaults to HPOS, older installs on postmeta still work without view-config changes.

 

Yes. Filter by _payment_method = cashfree or by presence of cf_payment_id to scope the view to Cashfree-paid orders. Useful for finance teams handling multiple gateways that reconcile each independently.

 

Pivot cf_payment_mode into a filter chip and a column. Compare conversion and AOV between UPI, card, netbanking, and wallet cohorts inside the orders view, without a separate analytics integration on top.

 

Yes. Cashfree writes failure reasons to order meta on declined transactions. SleekView surfaces that as a column so support can triage expired-card waves, insufficient-funds clusters, or wallet timeouts. A saved view of failed orders sorted by reason is a typical support pattern.

 

Yes. Filter to Cashfree orders by date range, surface the GST columns recorded as line-item meta, and export to CSV. The same saved view runs each month so finance does not rebuild the report.

 

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