Quarantine Payment

A quarantine payment is one a business or its provider holds back while someone looks at it. The money has been taken, or is ready to move, and a check has raised a flag, so the payment waits in a state of its own. It is not a decline and it is not an approval. It is a pause with a decision attached, and that decision is usually made by a person rather than by a rule, which is what separates it from an ordinary decline.

The idea takes its name from public health and its logic from risk work. Machine checks sort the clearly fine from the clearly bad well enough, and they are weaker in the middle, where a payment looks odd without being wrong. Turning down everything in that band loses real customers, and letting it all through invites losses and trouble with the rules. A holding state is the compromise, and it exists because the other option is picking one of those two outcomes every time.

What Puts A Payment In The Queue

Rules vary a good deal by business. The common triggers do not. A first payment from a new account, an amount outside the customer's pattern, a card country that does not match the delivery country, or a burst of tries that trips a velocity check will all do it. So will a name that partly matches a sanctions list. A risk engine scores the payment and holds anything between two thresholds, so the width of that band is a commercial choice as well as a risk one.

Sanctions Holds Are Not The Same Thing

Two sorts of hold share the name and behave in different ways. A commercial hold is the business guarding itself, and it can be released whenever it likes. A hold that arises from money laundering law is not in the same box, since letting it go early can itself be an offence. In the UK the rules on consent, the notice period and the moratorium sit in section 335 of the Proceeds of Crime Act 2002. Those periods are set in the law, they are revised, and other markets run their own, so the local position governs.

The Cost Of Holding The Wrong Payment

Every held payment has two prices. The obvious one is the fraud or the fine avoided when the hold was right. The quieter one is the good customer who waited, gave up and bought elsewhere, and that cost seldom lands in the same report as the first. A business counting only caught fraud will keep widening the band, because widening it looks free.

Who Reviews, And How Fast

A hold is only as good as the review behind it. That means a named queue, an agreed turnaround, and enough on screen for a reviewer to decide without opening four other systems. Order history, device signals, earlier fraud score values and prior holds all belong in one view. Where reviews are slow, the hold stops being a risk control and turns into a support problem. This piece on real-time transaction monitoring covers what a working setup looks like.

Silence Is The Costly Option

This is where most of the damage gets done. A customer whose money has gone but whose order has not shipped assumes the worst, and silence backs that up. Saying a payment is under review, giving a realistic window, and confirming the outcome either way costs almost nothing. What a business cannot do in every case is explain why. Money laundering rules limit what may be said in some cases, and the wording is worth agreeing with a compliance adviser before it goes into a template.

Releasing, Refunding Or Turning It Down

A held payment ends in one of three ways. The first is that it clears and behaves like any other sale. The second is that it is turned down before capture, where a void transaction frees the customer's funds quickly. The third is that it has been captured, so the money goes back as a card refund and takes days to appear. Stopping a payment before capture is kinder wherever it is open, since a refund makes the customer wait twice.

Where It Sits In The Wider Risk Setup

A quarantine state is one control among several, and it works best when the others are tuned. A customer whitelist keeps known-good repeat buyers out of the queue, and a negative file keeps known-bad ones from reaching it. A high risk merchant carries a wider band than a low risk one, and the body that sets the global standards here, the Financial Action Task Force, shapes much of what the rules ask for.

Holds That Nobody Closes

The failure worth designing against is the payment held and then forgotten. It happens when reviews go to whoever is free, when the queue has no age report, and when a busy week pushes older items down. Those payments become complaints, then chargebacks, then a pattern a regulator can see. An age report and someone to escalate to are dull and cheap, and they stop a small queue becoming visible.

Keeping Holds Short And Fair

Set the thresholds on purpose and write down why they sit there. Review the band each quarter against fraud caught and customers lost. Give the queue an owner and a turnaround anyone can quote. Put what a reviewer needs on one screen, and stop payments before capture where you can. Track the age of the oldest open item as a measure in its own right. And keep sanctions holds on a separate track with their own rules. Payment fraud detection is designed to help with the scoring side. This guide to fraud and risk management covers the wider picture.

‍