Turnstile Order Decisions

Before an order goes through

Decide

The queue, order by order: what fired, what it scores, what may go through.

Factors

Your own risk policy, as rows with points on them. Nobody else's model.

Ratios

Month by month, against each network's line. On the denominator each one uses.

Exposure

Orders that went through anyway, and the months already over a line.

After one comes back

Disputes

Each one against the order it came from, and what fired on it that day.

Programmes

The count and ratio lines you entered, and which month each is measured on.

What fired, after

Every factor, measured on the orders that came back. Your table, graded.

These Records

Where they are kept, and how to take them with you.

Decide×

An order may go through when its score is under the line you set, nothing you marked refuse on its own fired, and there is a sales row for its month so the ratio can be read. Turnstile never sees a card number, a name or an address — it records which of your own checks fired, and scores them against your table. It is not in the authorisation path and it does not take the money.

Batch

Factors×

Your risk policy, written down. Each row is something one of your own checks can report, what it is worth in points, and whether it refuses an order on its own. Turnstile does not invent a model and cannot see what your checks see — it holds the policy and applies it the same way every time, which is the part a person stops doing on a busy Friday.

These points are yours, not ours

The table ships with a starting set so the program opens with something to argue with. The weights are a guess at a business nobody here runs. Change every one of them, and the line, before the first real order.

Refuse at or above points. The highest-scoring order in the queue right now is —.

Ratios×

A dispute ratio is a fraction, and the networks do not agree on the bottom of it. One counts this month's disputes against this month's sales; another counts them against last month's. The same month can be under one line and over the other, so Turnstile computes each programme on the denominator that programme uses and never averages them into one number.

The month that is running now

Disputes×

Each dispute against the order it came from, and — the whole point — what fired on that order on the day it was let through. A dispute with no order behind it is recorded as that, loudly: it means something was charged that this program never saw.

Turnstile counts a dispute. It does not fight one — the evidence, the deadline and the representment belong to a different desk, and bolting them on here would make this program the place where both jobs get half done.

Programmes×

These rows are what you entered, not the rules

The card networks publish their monitoring thresholds and change them. Each row below says where the figure came from and when it was recorded. Check every one against your acquirer's current notice — your acquirer may also hold you to a tighter line than the network does, and that line belongs here too.

Exposure×

Orders that went through carrying something that would refuse them now, and months already over a line. Recorded rather than hidden: an order that has settled cannot be un-settled by a program that was never in the authorisation path, and pretending otherwise is how a ratio surprises somebody in a letter.

What fired, after×

Your factor table, graded by what actually came back. For every factor: how many orders it fired on, how many of those were disputed, and the rate — set beside the rate across orders it did not fire on. A factor that fires on everything and predicts nothing is costing you sales, and a factor worth two points that triples the dispute rate is worth more than two.