card player, poker, masks, gambling, human, sharper, swindler, incognita, fraud, player, tramp, mask, gambler, rogue, ace, gain, victory, casino, stickman, fraud, fraud, fraud, fraud, fraud, gambler
Photo by Sunriseforever on Pixabay

Fraud Controls

Part of Payment authentication and fraud controls

Reviewing false declines alongside fraud losses

Fraud controls can appear successful when reported fraud falls, even if they also stop many legitimate buyers.

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Desk Payment Risk.

undefined

Fraud controls can appear successful when reported fraud falls, even if they also stop many legitimate buyers. Review both sides of the decision: orders that passed and later proved fraudulent, and good transactions that the risk setup rejected. The second group is harder to observe, so do not present a blocked payment as a confirmed fraud case.

Separate risk blocks, issuer declines and disputes

Split merchant risk blocks from issuer declines, authentication failures and customer abandonment. They have different causes and owners. A rule change may reduce merchant blocks but have no effect on an issuer declining cards. Record the provider's outcome and rule identifier where available, then compare only like-for-like traffic.

Pull the provider's transaction outcome, risk rule and issuer response code where available. Stripe documents that its outcome can identify a merchant risk block that was not sent to the issuer and can include decline information and response codes received from issuers (Stripe). For Australian context, Westpac QuickStream says successful card transactions generally have response code 00, “Approved or completed successfully”, or 08, “Honour with Identification”; authorisation does not confirm that the cardholder is legitimate (Westpac QuickStream).

Define the observation window for fraud outcomes. Disputes can arrive after an order is fulfilled, and not every dispute means fraud.

Reconcile provider or acquirer dispute records against fulfilled and captured orders, preserving each reason code. A chargeback reason code classifies why a transaction is disputed (Rivero); Stripe notes that some disputes use non-fraud reasons such as “product not received” and “product not acceptable” (Stripe).

Calculate counts and value, but also consider goods loss, operating effort and the customer value potentially lost through a false decline. Avoid combining these into one confident “fraud prevented” number if the counterfactual is unknown.

Use the same cohort and label each denominator. Estimated false-positive share, or false-decline estimate, equals control transactions the live profile would block and later assessment finds legitimate divided by control transactions the profile would block. Merchant acceptance rate equals paid attempts divided by all attempts in that cohort; issuer authorisation rate equals issuer-approved attempts divided by attempts sent to the issuer. Keep merchant risk blocks out of issuer-decline counts.

Add two loss measures: fraud-to-sales rate equals confirmed fraud loss value divided by captured sales value, and chargeback rate equals charged-back transactions divided by captured transactions. Show fraud-coded and other disputes separately, and report both counts and value; disputes are not all fraud, and fraud can also incur goods, operating and dispute costs (Stripe; Adyen).

Find and test evidence of good orders blocked

A customer contacting support after a blocked payment, a successful later attempt with another method, or a manual review can suggest a false positive. None proves that every similar blocked payment was good. Adyen documents a control-traffic approach that helps assess false positives and true positives within its system. Whether a merchant has comparable data depends on the provider and settings.

Adyen says a very small percentage of transactions is randomly selected for control traffic and settled regardless of risk evaluation. Review the risk rules triggered and later disputes: Adyen says this can identify false positives and confirm true positives, but the sample still contains some fraudulent transactions (Adyen).

Look for patterns by rule, payment method, customer tenure, product and geography, while handling personal data appropriately. If one new rule coincides with a rise in legitimate-customer complaints, review its matched transactions. Do not automatically allowlist a broad group or retry a rejected payment without checking the provider's process and the original reason.

Use a case sheet with one row per sampled blocked attempt: cohort, rule, amount, evidence for legitimacy, later payment outcome, dispute status and reason code. Mark cases unresolved when evidence is missing; a later attempt with another method does not prove that the original attempt was legitimate. Where no control or matched review data exists, report false declines as unmeasured rather than guessing.

Steps to Assess False Declines Without Bias

  • Review customer support contacts after blocked paymentsIndicates potential false decline
  • Check successful later attempts using alternative payment methodsSuggests original attempt may have been legitimate
  • Use control traffic sampling (Adyen) to assess risk rule outcomesRandomly selected transactions settled regardless of risk score
  • Audit patterns by rule, payment method, geography and customer tenureIdentifies high-risk rules affecting legitimate users
  • Maintain a case sheet with evidence per sampled blocked attemptIncludes amount, legitimacy evidence, dispute status

Make the decision reversible and report both sides

Agree on the acceptable loss and acceptance measures before changing a threshold. Review a small sample of cases with fraud, customer support and payments staff. Change one major rule at a time where possible, document its date and scope, and watch both early acceptance and later fraud signals. Some providers support backtesting or control datasets; those are tools to inform, not guarantees of future performance.

Give risk, payments, support and the acquirer the same cohort table, with the definitions and observation window. Separate observed fraud and chargeback losses from estimated false declines, and include reason-code mix in acquirer or scheme reporting when applicable; authorisation alone does not establish that a transaction was legitimate (Westpac QuickStream).

The useful review asks whether a control stopped the right transactions at a tolerable cost. A lower fraud count alone cannot answer that question.

Reversible Risk Control Evaluation Process

  1. Agree on acceptable loss and acceptance thresholdsBefore any rule change
  2. Review small sample with fraud, support and payments teamsCross-functional validation
  3. Change one major rule at a timeDocument date, scope and impact
  4. Monitor early acceptance and later fraud signalsTrack both short- and long-term outcomes
  5. Share cohort table across risk, payments, support and acquirerEnsure consistent definitions and observation window

More from Fraud Controls