What to send us before a card-not-present review

Most card-not-present reviews fail before anyone draws a chart. They fail because the extract is “all settlements this year” with no acquirer merchant ID, no refund flag, and no note on whether the clock is Tbilisi time or UTC. We then spend the first days reconstructing what a finance export already knew.

Send the MID or MIDs in scope. Send the date range you actually care about, even if it is shorter than the extract. If refunds live in a second file, say so; mixing them silently makes a night-hour cluster look like sales. If you use a payment facilitator, tell us whether the rows are your sub-merchant or the facilitator’s umbrella.

Column headings in Georgian are fine. Unnamed columns are not. A one-line covering note — “pulled by Lela on 3 March, live account, not the sandbox” — saves a week of polite doubt. Do not send PAN data. Masked last four, if you already store them, are enough when they exist; many Georgian merchant files do not store them at all, and we will not ask you to recreate them.

If dual-control or a refund-approval rule existed during the window, attach the rule that was in force, not the rule you wish you had. A review that measures behaviour against a policy written afterwards is a different letter, and we will say so.