Each PayTR transaction row links to the order via <code>siparis_no</code>: <code>islem_tutari</code> is the collection, <code>kesinti_tutari</code> the commission, <code>net_tutar</code> your transfer. S=sale, I=refund; TL normalises to TRY.
What do the report fields mean?
The PayTR transaction report (panel export or API) carries: siparis_no order reference, islem_tipi sale (S) or refund (I), islem_tutari gross collection, kesinti_tutari/kesinti_orani commission, net_tutar transfer, islem_tarihi date in dd.MM.yyyy format, and para_birimi usually TL. An installment column marks installment sales.
How does it match the Shopify side?
siparis_no is whatever reference your integration wrote to the Shopify order — usually the order number. Rows without a matching reference fall back to amount + date-window matching; collisions are flagged ambiguous.
What to watch for?
- Refund rows arrive separately — sale + refund must be netted under the same siparis_no.
- TL/TRY spelling differences break currency matching unless normalised.
- Installment sales carry different commission — a single-rate assumption produces false gaps.
StoreCheck Reconcile reads the PayTR report as exported from the panel (Turkish headers, CSV) or with API field names — both reach the same result.
FAQ
How do I get the PayTR file?
PayTR Merchant Panel → Transactions/Transaction Report, pick a date range and export; or pull it via the report API — the field dictionary is the same.
Does a refund row reconcile separately?
Yes — the refund is processed as a negative effect under the same order reference and stays traceable at row level.
Skip the manual matching: StoreCheck Reconcile parses your report in the browser and matches every row to order evidence. Start free · All guides
More guides: How to reconcile Shopify payouts with iyzicoiyzico commission rates and reading the settlement reportCash-on-delivery reconciliation — matching carrier collections to orders