iyzico Payment Gateway for WooCommerce does not add its own primary tables. Payment data lives as WooCommerce order metadata: iyzico_payment_id, iyzico_status, iyzico_installment, 3DS state, and card brand are written through the WooCommerce meta API to wp_wc_orders_meta on HPOS or wp_postmeta on legacy. The default WooCommerce orders list never shows them because the screen renders core fields only.

SleekView reads the right storage automatically and pivots the iyzico_* meta keys into named columns. A payment-method filter scopes the view to iyzico-paid orders. Taksit plan and card brand become inline columns, which means Turkish finance teams reconciling iyzico settlements and conversion analysts comparing taksit cohorts work from one screen.

Edits route through the WooCommerce CRUD layer for the columns the plugin marks editable. Refunds still flow through iyzico's admin action that calls its API; SleekView never re-authenticates against iyzico.

WooCommerce's orders list shows core fields and ignores gateway-specific meta. That works for one gateway and a simple flow. It fails for Turkish stores running iyzico across tek çekim and multiple taksit plans, where the conversion question "do longer taksit plans actually drive AOV" has a real answer in iyzico_installment that nobody can see without opening every order.

Finance teams reconciling iyzico settlements need iyzico_payment_id as a column to match payout lines. Risk reviewers auditing 3DS compliance need 3DS state inline. Conversion analysts need card brand and bank as filterable columns.

The default workflow forces a tab-flip between the iyzico merchant dashboard and WooCommerce admin. SleekView pivots iyzico_* 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 flow through iyzico, but the data iyzico writes into your orders finally becomes queryable as plain WooCommerce data.