Paystack channel data lives on every order.

The official WooCommerce Paystack gateway plugin does not add custom database tables. It writes Paystack-side references (transaction reference, channel, authorization code, gateway response) into wc_orders_meta on each order. The default WooCommerce orders screen cannot filter on these, so the channel mix (card, bank transfer, USSD, QR, mobile money) that justifies Paystack in West Africa sits invisible at the list level.

SleekView reads those meta keys and promotes them to typed columns. _paystack_txn_ref becomes a searchable reference. _paystack_channel splits card, bank, USSD, QR, EFT and mobile money in one filter. Authorization codes (Paystack's reusable customer payment tokens) become groupable so saved-card cohorts surface as a real metric. Saved views like "bank transfer pending" or "mobile money declines this week" replace per-order audits.

Edits route through WooCommerce's CRUD layer so order notes and audit trails stay intact. Paystack-side references stay read-only because editing them locally would silently desync the order from the actual transaction. Per-role masking hides last4 and customer email from staff who do not need them.

Workflow

Make Paystack channel and reference data queryable

1

Pick the source

Point SleekView at wc_orders joined with wc_orders_meta. The grid auto-detects every Paystack-related key (_paystack_txn_ref, _paystack_channel, _paystack_authorization_code).

2

Compose columns

Promote channel (categorical), authorization code (string), transaction reference and gateway response to typed columns. The grid picks the right filter operators.

3

Save and scope per role

Save "bank transfer pending", "mobile money declines" and "finance reconciliation" views and scope to roles. Column-level masking handles email and last4.

4

Edit inline or bulk update

Edit notes and editable meta inline; SleekView routes through WooCommerce's CRUD layer to preserve hooks. Paystack-side references stay locked.

Sample columns

Paystack gateway order metadata

Each Paystack order writes its references into wc_orders_meta. The plugin maintains no custom tables of its own.

Source: wp_wc_orders_meta (HPOS) or wp_postmeta

Meta key	Description	Type	Filterable	Status
_paystack_txn_ref	Paystack transaction reference	string	Yes	Read
_paystack_channel	card, bank, USSD, QR, mobile_money	string	Yes	Read
_paystack_authorization_code	Reusable customer auth token	string	Yes	Read
_paystack_gateway_response	Verbose gateway response	string	Yes	Audit

Comparison

Default WooCommerce Paystack admin vs SleekView

Default WooCommerce Paystack admin

Paystack channel hidden at the orders list level
No way to filter card vs bank vs USSD vs mobile money
_paystack_txn_ref not searchable from the orders screen
Authorization codes (saved cards) cannot be grouped across orders
Bank transfer pending status scattered across order notes

SleekView

Promote channel to a filterable column from wc_orders_meta
Search by _paystack_txn_ref directly in the list
Group by _paystack_authorization_code for saved-card cohorts
Bank transfer chase view for slow clearances
Export Paystack-funded slices for finance reconciliation

Features

What SleekView gives you for WooCommerce Paystack

Channel split

Paystack covers card, bank, USSD, QR, EFT and mobile money under one gateway. One filter on _paystack_channel splits the channels into distinct reporting views.

Saved-card cohorts

Group by _paystack_authorization_code to see each saved-card customer's full purchase history. Repeat-buyer rate becomes a real metric, not a CRM lookup.

Bank transfer watch

Bank transfers in Nigeria and Ghana can sit pending until reconciliation. SleekView surfaces channel plus time-since-creation as a saved view so finance can chase slow clearances.

Audience

Who uses SleekView for WooCommerce Paystack

Finance reconciliation

Pair _paystack_txn_ref with capture date and channel, then export by batch to reconcile against the Paystack settlement report without manual pivots.

Customer support

When a customer references their Paystack receipt, support searches the transaction reference directly in the order list. The whole order context loads in one click.

Channel analytics

Compare card, USSD, mobile money and bank transfer success rates over time. Catch when a specific channel's performance drifts and prioritise the fix.

The bigger picture

African payments are channel-diverse. The default admin treats them as one.

Paystack's biggest pitch in Nigeria, Ghana, South Africa and Kenya is channel breadth: card, USSD, QR, bank transfer, EFT and mobile money all on one gateway. That breadth becomes a problem on the default WooCommerce orders screen because every transaction shows up as "Paystack" with no way to split channels at the list level. A USSD payment that takes 90 seconds, a bank transfer that clears in 4 hours, a mobile money push that fails on the first OTP and a card payment that authorises instantly all look identical.

Finance reconciles by exporting and pivoting. Support triages OTP failures and bank-side declines one order at a time. Channel analytics need an external BI tool because the WooCommerce admin cannot answer "what was USSD's success rate yesterday".

Promoting Paystack's meta keys to typed columns turns those bottlenecks into normal saved views. For African stores running real Paystack volume across channels, the setup pays back in the first support shift and keeps paying back every reconciliation cycle.

Questions

Common questions about SleekView for WooCommerce Paystack

No. The official WooCommerce Paystack gateway writes all Paystack-side references (transaction ref, channel, authorization code, gateway response) into wc_orders_meta on HPOS or wp_postmeta on legacy storage. SleekView reads those meta keys as columns; no extra plugin schema.

Yes. _paystack_channel carries Paystack's canonical channel codes (card, bank, USSD, QR, mobile_money, EFT, bank_transfer). One filter splits them into separate reporting views for marketing, finance and ops.

Yes. SleekView reads from wc_orders and wc_orders_meta on High-Performance Order Storage. Sites on legacy CPT storage are also supported; the grid detects the active layer. Saved views and column promotions carry over.

_paystack_authorization_code is Paystack's reusable customer token. SleekView promotes it as a groupable column, so grouping by authorization code assembles each saved-card customer's order history. Filtering to a specific code pulls just that customer's orders.

No. _paystack_txn_ref is immutable on Paystack's side; SleekView marks it read-only. Editing it locally would silently desync the order from the real transaction. Notes and editable meta keys can still be inline-edited and route through WooCommerce's CRUD layer.

No. SleekView reads only what the gateway already wrote to your database. Refunds and re-captures still run through the Paystack gateway's existing order actions because they need to update Paystack-side state, which keeps both systems consistent.

Paystack's reusable authorization codes power both subscription billing and merchant-initiated charges. SleekView groups orders by authorization code so the full charge history for a subscriber surfaces in one view. Failed renewals become a saved filter.

Yes. Filter to whatever finance or ops asked for, then export the visible slice as CSV. Column-level masking applies, so PII fields like email and last4 hide for users without the right capability. Common exports are daily channel splits and monthly Paystack settlement reconciliations.

Other plugins SleekView pairs well with

SleekView for WooCommerce Shipping EasyPost

SleekView reads the EasyPost shipment, carrier, service and rate meta the plugin writes on each order and renders order, carrier, service...

SleekView for WooCommerce Allegro.pl: offers, EAN and orders as tables

Read Allegro offer meta from wp_postmeta, marketplace config from wp_options, and synced Allegro orders from

SleekView for Paystack: gateway transactions as tables

Paystack for WooCommerce stores the transaction reference, payment channel, and gateway response against each order's meta. SleekView rea...

SleekView for Coinbase Commerce for WooCommerce: charges & crypto orders as tables

Coinbase Commerce for WooCommerce writes each transaction's charge code, coin, and confirmation state into WooCommerce order meta. SleekV...

Klarna Payments order data for WooCommerce

Pay in 3, Pay Later and direct payments live as separate columns you can filter, sort and reconcile. SleekView turns Klarna order metadat...

Ecwid local data and order references in WordPress

Surface the local Ecwid references and embed metadata stored on your WordPress side as one filterable, exportable table. Audit which post...

Pricing

Q: Can I split channels in the list?

Yes. _paystack_channel carries Paystack's canonical channel codes (card, bank, USSD, QR, mobile_money, EFT, bank_transfer). One filter splits them into separate reporting views for marketing, finance and ops.

Q: Does it work with HPOS?

Yes. SleekView reads from wc_orders and wc_orders_meta on High-Performance Order Storage. Sites on legacy CPT storage are also supported; the grid detects the active layer. Saved views and column promotions carry over.

Q: How are saved cards (authorization codes) exposed?

_paystack_authorization_code is Paystack's reusable customer token. SleekView promotes it as a groupable column, so grouping by authorization code assembles each saved-card customer's order history. Filtering to a specific code pulls just that customer's orders.

Q: Can I edit the Paystack transaction reference?

No. _paystack_txn_ref is immutable on Paystack's side; SleekView marks it read-only. Editing it locally would silently desync the order from the real transaction. Notes and editable meta keys can still be inline-edited and route through WooCommerce's CRUD layer.

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

Get started

3 websites
1 year of updates
1 year of support

Pro

€149

EUR

per year

Get started

Unlimited websites
1 year of updates
1 year of support

Lifetime ♾️

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

€749

Continue to checkout

Browse more

Ecommerce

Email

Security

Membership

SleekView for WooCommerce Paystack: charges and channels as tables

Paystack channel data lives on every order.