Dunkin Donuts Credit Card Swipe Device Machine Chip Reader, 9/2016, pics by Mike Mozart of TheToyChannel and JeepersMedia on YouTube #Dunkin #Donuts #Credit #Card #Swipe #Reader #Chip
Photo by Mike Mozart from Funny YouTube, USA on Wikimedia Commons · CC BY 2.0

Fraud Controls

Payment authentication and fraud controls

Payment authentication and fraud controls solve related but different problems.

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

Payment authentication and fraud controls address related but separate problems. Authentication checks whether a shopper can satisfy an identity challenge in a payment flow. Fraud rules decide whether to allow, review, challenge or block an order using risk signals. A store needs both to protect payments without turning legitimate buyers away unnecessarily.

The RBA describes an industry-led Card-Not-Present (CNP) Framework to reduce fraud on Australian cards used at Australian merchants in online channels. It also identifies the IAC Code Set and says overseas merchants and acquirers fall outside its regulatory reach and cannot be sanctioned by AusPayNet for breaching fraud thresholds (RBA).

Follow the payment authentication path

At checkout, the payment provider collects a payment attempt and may assess risk before authorisation. For card payments using EMV 3-D Secure, information can be sent to the card issuer for authentication. Stripe describes 3D Secure 2 (3DS2) as a protocol that authenticates online card transactions and often operates silently in the background through device fingerprinting and behavioural data (Stripe).

The issuer may approve a frictionless flow or request a challenge such as a one-time code or banking-app confirmation. An authentication result is then returned. The exact sequence and interface depend on the provider, issuer, card and integration.

A successful challenge does not guarantee payment. Authorisation can still fail after authentication, and a payment with no visible challenge has not necessarily skipped security checks. Wait for the provider's final payment status before marking an order paid or starting fulfilment. Test completed, failed, abandoned and timed-out authentication paths, not just the happy path.

Choose proportionate Australian controls

Fraud controls can request authentication, place an order in review or block it. A blanket rule such as “reject every order from a particular broad region” may stop some fraud but also deny legitimate buyers.

Risk-based controls can use transaction context and provider signals to reserve stronger checks for higher-risk cases. Examples include Address Verification Service (AVS), Card Identification (CID) and velocity risk checks, which Adyen recommends alongside business rules (Adyen). The issuer may independently require a challenge; a merchant's preference does not guarantee a frictionless flow.

Adyen says digital wallets such as Apple Pay and Google Pay, and major card schemes, use network tokens to create effortless and secure online payment experiences (Adyen).

Write each rule's purpose and expected action. What evidence supports the condition? Can an employee review it? What happens to a customer whose legitimate payment is blocked?

Separate merchant-selected rules from named Australian obligations. The Privacy Act 1988 sets out the Australian Privacy Principles (APPs); section 15 says APP entities must comply with them, and Part IIIC covers notification of eligible data breaches, including section 26WL, Entity must notify eligible data breach (Privacy Act 1988). Check whether the business is an APP entity and which provisions apply before deciding how to handle personal information in risk records.

PCI DSS is a card-data security standard. The RBA notes that PCI SSC requirements and guidance are international in nature and developed specifically for card payment systems (RBA).

Configure rules deliberately

Some payment platforms let a business label fraud rules by their basis. Adyen labels include Business for business-specific rules, Legal for rules based on laws or regulations, Fraud for specific fraud risks, and Block list or Trust list for list-based controls. Visible distinctions help staff understand why a control exists and avoid treating every rule as the same decision.

Adyen custom rules can run before or after authorisation, with conditions combined using AND or OR. Available actions depend on the rule setup and can include Allow, Block, Review or Check for 3DS. Adyen says custom rules require Protect premium, an online payments integration and risk management enabled; changing risk settings also requires an appropriate Customer Area role.

Before adding a rule, confirm who is authorised to change it and whether it belongs to the merchant's fraud policy or a legal or regulatory basis. For example, where the platform exposes these fields and actions, send an AVS or CID mismatch to Review, select Check for 3DS when a velocity condition matches, and Block a match on a business block list (Adyen). These are merchant policy examples, not universal Australian requirements; record and validate each condition.

Use provider risk information carefully

Risk products may combine signals a merchant cannot see at checkout. Stripe says its Radar adaptive AI models assess payments in real time using hundreds of risk factors and network data, and incorporate feedback when businesses mark payments as fraudulent. These model assessments differ from some Stripe risk settings and controls, which use specialised models.

Stripe reports risk outcomes including High risk, Elevated risk, Normal risk, Not evaluated and Unknown risk. A business can inspect payment risk information in the Dashboard or through the Charge object's Outcome attribute, and may also receive information about a decline from a financial institution. Use these provider-specific details as payment operations inputs, not as a substitute for checking the final payment status.

Measure fraud-control outcomes

A lower block threshold may catch more fraudulent attempts and reject more good customers. A higher threshold may improve acceptance while increasing fraud exposure. Review blocked and reviewed payments, issuer declines, completed orders and later fraud disputes by comparable cohorts. Distinguish a payment blocked by the merchant's rule from one declined by the issuer; remedies differ.

Stripe says card-not-present fraud represented 90% of total card fraud in Australia in 2023 (Stripe). The ABS reports that 10% of Australians aged 15 years and over experienced card fraud in 2024-25 (ABS). Neither population-level figure is a store-specific fraud rate or a rule threshold.

A false decline is a good transaction rejected by the risk setup, but a blocked transaction's true status is often not directly observable. Use customer contacts, manual investigation, provider control data where available and subsequent outcomes cautiously.

Adyen's control traffic supports assessing false positives and true positives; that is one provider's method, not a universal merchant dataset (Adyen). Stripe says the Australian chargeback process puts the burden of proof on the business, and winning a dispute takes time and administrative effort (Stripe). A dispute is a delayed signal, and not every dispute is fraud.

Test authentication and fraud rules

Use a payment provider's test environment to verify integration behaviour: authentication required and completed, challenge failed or abandoned, risk rule triggered, issuer decline and retry. Stripe's test cards can simulate successful payments, card errors due to declines, fraud or invalid data, disputes, and authentication with 3D Secure and PINs (Stripe). These tests confirm technical handling; they do not establish a production fraud rate or prove a new rule will improve revenue.

For a proposed new rule, backtest on historical traffic where the provider supports it, inspect a sample of matches, then deploy to a limited segment or review mode if the platform allows. Watch acceptance, review workload and fraud outcomes over a meaningful period before widening it. Have an owner and rollback condition in advance.

The operating goal is a checkout that reaches a clear final status for each attempt and a risk policy that can be explained and adjusted. Neither maximum friction nor maximum approval is a complete strategy.

In this guide

  1. Understanding the steps in a payment authentication flowA payment authentication flow may happen quietly or ask the shopper to take an extra step.
  2. Comparing risk-based checks with blanket restrictionsA blanket payment restriction applies the same block or challenge to a broad group.
  3. Reviewing false declines alongside fraud lossesFraud controls can appear successful when reported fraud falls, even if they also stop many legitimate buyers.
  4. Testing fraud rules before applying them to every orderTesting fraud rules before applying them to every order: practical criteria and a clear evaluation process for marketing teams.

More from Fraud Controls

Fraud Controls

Checkout security and access

Map who can change checkout, review staff and app access, keep payment data out of logs and prepare to investigate unexpected changes.