Refunds and Chargebacks in Türkiye: The Merchant Evidence File

سفير تركيا · 2026-10-12T00:01:42+0300

Refunds and chargebacks: the merchant evidence file in Türkiye
Link customer rights, refund references and dispute evidence without returning the same amount twice

A customer’s refund request, a gateway refund and a card dispute are three separate events needing linked records. You may refund voluntarily to correct an error, owe a consumer remedy or face a dispute through the bank or provider. This guide helps Turkish merchants document sales, delivery, communication and refunds and prevent returning the same amount twice. No document package guarantees winning every dispute: evidence strength depends on reason, rules, deadline and actual facts. Example amounts and dates are hypothetical training material.

A refund needs a financial reference linked to the original payment.

⁦⁩ Distinguish goods returns, refunds and disputes

Returning goods is a logistics procedure that may precede or coincide with a refund depending on the case. A refund is a financial action by the merchant or authorized service returning all or part of an amount. A card dispute arrives through the bank, network and provider, with its own reason, deadline and response procedure. Combining everything as a ‘return’ causes errors: goods may arrive before the financial transaction is handled.

Maintain order, payment, return request, refund and dispute references where applicable. Warehouse staff must not assume receipt means finance refunded, and support must not assume an order-status change returned money. For a dispute concerning an already-refunded order, retain the refund reference and review it with the provider before another refund so the correct procedure handles the case.

Event	Primary reference	What it does not establish alone
Goods returned	Return request and receipt record	Successful financial refund
Provider refund	Payment and refund references	Immediate appearance in the bank
Card dispute	Dispute ID and reason	Automatic merchant fault
Order marked refunded	Platform record	Bank movement without verification

⁦⁩ Consumer rights differ from technical service windows

Turkish consumer distance-sales contracts have withdrawal rules and exceptions. The general fourteen-day right starts at delivery for goods and contract conclusion for services. Ministry guidance explains that the refund period starts differently by case: handover to the specified return carrier, receipt when another carrier is used, or withdrawal notification for undelivered goods and services. Do not write one oversimplified rule for every order.

A gateway’s technical refund window does not authorize delaying an already-due right for that long. Check the legal circumstances and current policy, then perform the appropriate financial action. Withdrawal requires an appropriate refund through the payment method without consumer cost or burden and cannot automatically be replaced with store credit. Defects or nonconformity also require treatment beyond withdrawal alone.

Warning: a gateway’s technical window or card-dispute response deadline does not replace consumer obligations.

⁦⁩ Full or partial refund

Before execution, identify what is being refunded: the full order, one item, a price difference or agreed compensation in an appropriate case. Link amount and currency to the original transaction and previous refunds. Some services process refunds at basket-item or transaction level; follow your integration’s method. Entering the order page’s displayed total is insufficient with multiple attempts or discounts.

After an earlier partial refund, calculate the remaining refundable amount. Review shipping, taxes and financial documents with the accountant under the appropriate legal procedure, without unsupported deductions. Record reason, approver and executor, then retain the result and refund ID. If the provider requires funding the refund balance, follow through to completion; submitting a request alone is not confirmed success.

⁦⁩ Cancellation, refund and the money’s appearance

A service may cancel transactions through one procedure and refund collected payments through another. iyzico documentation distinguishes cancellation from refund and permits full or partial refunds within the remaining amount. Verify transaction status and service rather than using the terms interchangeably. Some cases depend on bank-processing timing; check dashboard or integration capabilities for that transaction.

After success, send amount, reference, date and available bank-posting information without uncertain timing promises. Do not say ‘instantly back in your account’: request success alone does not determine the card statement update. If money is not visible, verify with the provider using the reference rather than issuing another refund after one message. Keep evidence of the financial movement beyond an order-status screenshot.

Order-fulfillment evidence supports a response to the specific dispute reason.

⁦⁩ Receive the dispute and identify its deadline

Immediately record dispute ID, reason, value, payment ID and response deadline. The provider’s practical deadline may be shorter than general expectations of network rules, so do not wait until the final day. Assign an evidence collector and reviewer checking relevance to the reason. Start with the cardholder’s allegation and facts supporting or rebutting it, rather than a long letter.

Request missing information through official channels. Do not approach the customer’s bank as a substitute for the provider route unless the approved process directs it, or pressure customers to abandon rights. Seek clear resolution while retaining communication and understanding how a voluntary refund during a dispute affects processing to avoid duplicate deductions or conflicting evidence.

⁦⁩ Build order evidence before a dispute

Keep the product information, price, size, delivery promise and terms displayed at sale, and evidence of ordering and appropriate information acceptance. Today’s page may differ, so it is insufficient alone. Combine order number, invoice, payment references and fulfillment data with the minimum necessary personal information. Dated records are more useful than ten undated images.

Do not manufacture retrospective evidence or rewrite old descriptions to fit a dispute. Where evidence is absent, state known facts and decide accordingly. For custom products, retain confirmed specifications and updates. For services, keep suitable output, access or performance evidence rather than an unrelated carrier receipt.

Evidence group	What to collect	Why it helps
Sale	Description, price and terms at ordering	Explain what was purchased
Payment	ID, amount and status	Link dispute and transaction
Fulfillment	Invoice, preparation and tracking	Sequence of order execution
Communication	Relevant dated messages	Explain requests and handling
Refund	Refund ID and amount	Prove what was actually returned

⁦⁩ Nonreceipt requires delivery evidence

For goods-not-received claims, start with order address, dispatch date, tracking and carrier delivery details. Carrier handover proves carriage began but not always consumer receipt. Review the person or location in delivery evidence and customer-requested address changes. A generic store ‘completed’ status cannot explain the facts.

For lost or returned shipments, provide the appropriate remedy rather than defending a delivery that never occurred. A separate contractual carrier claim may be needed but does not alone settle the customer relationship. Keep delay notices, offered solutions and relevant agreement. For multibox shipments, identify each parcel’s products so evidence for one parcel is not used for another disputed portion.

⁦⁩ Product mismatch and defects require different evidence

For not-as-described disputes, compare sale-time description, images and sizing with actual dispatch. Record preparation inspection and suitable photographs without overstating them as conclusive. Parcel delivery does not establish correct or undamaged contents. Collect the complaint, clarification requests, offered remedies and return or exchange evidence where applicable.

Do not classify every complaint as fraud because authentication succeeded or the parcel was accepted. Distinguish customer-selected size, wrong size dispatched, transport damage and incomplete descriptions. Each needs a different answer. Where error is established, resolve it and close financial and operational records. Organized evidence helps discover mistakes and learn as well as answer unsupported claims.

Dispute reason	Most relevant evidence	Insufficient alone
Nonreceipt	Delivery evidence linked to the address	Carrier handover
Nonconforming product	Sales description and fulfilled contents	Successful payment
Refund not received	Refund reference and result	An employee’s promise to refund
Unauthorized transaction	Permitted payment-flow data	Unrelated shipping receipt

The evidence file combines order, delivery, communication and financial movements.

⁦⁩ 3D Secure does not replace fulfillment evidence

Authentication helps reduce unauthorized card-use risk but prevents neither every fraud nor every dispute reason. Liability effects depend on rules, circumstances and payment flow. Do not tell customers or staff that all transactions authenticated this way cannot be disputed. Successful authentication proves neither delivery nor conformity.

Retain provider-available authentication evidence with the transaction reference, then add evidence relevant to the specific reason. If expected authentication did not occur, inspect risk settings and integration rather than falsifying a new status. Follow provider guidance on accepted documents, channel and deadline, avoiding security codes or full card data as supposed evidence.

⁦⁩ Hypothetical example preventing duplicate refunds

Assume an order of one thousand two hundred lira. The store approves and successfully refunds three hundred for an item, leaving nine hundred. A dispute then requests one thousand two hundred, saying money was not returned. Before any new refund, the owner submits the three-hundred reference and result and asks the provider to handle the dispute with that information. Silently adding a full refund would return one thousand five hundred.

These figures illustrate the issue; final action depends on facts and dispute procedure. The remainder may need handling, or a temporary dispute deduction may require reconciliation rather than a final conclusion. Record each movement separately with date and ID. Provider recovery through the dispute must not also be recorded as a voluntary refund. Settlement and bank reconciliation reveal the true effect and prevent closure before understanding the balance.

Hypothetical movement	Value in lira	What to check
Original payment	1,200	Transaction ID
Successful partial refund	300	Refund ID and result
Arithmetic remainder	900	1,200 − 300
Dispute received	1,200	Reason, deadline and earlier refund
Handling decision	Determined with the provider	Prevent duplicate refund of the same money

Result: document and reconcile prior refunds by reference; their existence does not automatically call for another refund.

⁦⁩ Give a concise response with understandable attachments

Begin with reason-relevant facts, then a timeline and named attachments. Every assertion should trace to a document: sale date, goods sold, delivery, communication and refunds. Do not send every customer message when three specific documents explain the facts. Check provider format and file-size limits.

Verify that names, amounts and references concern the same dispute. A similar order’s delivery photograph weakens the response and exposes unnecessary data. Record submission date, evidence-receipt confirmation, later decision and available further response rights. Uploading a file is not winning; monitor decision and money movements and keep settlement differences open until final treatment appears.

⁦⁩ Frequently asked questions and evidence checklist

Refund management requires separation of request intake, approval, execution and reconciliation according to store size. At minimum, review material-value transactions a second time and assign deadline cover for absences. Do not wait for disputes to collect descriptions or delivery proof; include these in daily records with suitable retention and access policies.

After closure, record the true cause, cost and practical lesson: incomplete description, carrier delay, fulfillment error, poor communication or evidence-supported fraud. Improve products, packing and support. The aim is clear fulfillment of customer rights and protection against duplicate money movements and decisions based on incomplete files, rather than preventing disputes.

Does marking an order refunded automatically return money?
It depends on platform, gateway and procedure. Check provider refund results and references rather than status alone.

Should I send a shipping receipt for every dispute?
Include it when relevant, but nonreceipt requires delivery evidence and mismatch requires sales descriptions and fulfillment contents.

Should I refund when a dispute arrives after an earlier refund?
First verify the earlier refund and dispute amount with the provider, following a process preventing duplicate deductions or refunds.

I linked order, payment, refund and dispute references.
I identified reason, deadline and response owner.
I collected relevant sale, fulfillment and communication evidence.
I checked earlier refunds before new movements.
I reconciled the final decision with settlement and bank records.