# Card-Present Fraud
Source: https://paymentsandrisk.com/docs/fraud/card-present-fraud

Last updated 4 November 2026.

TL;DR

-   A chip or tap failed? Check the payment's status first
-   Staff keyed it? Keep the entry method and receipt together
-   Went offline? Find the result before collecting again
-   The tip changed? Separate an unsettled payment from a dispute
-   A dispute arrived? Start with its claim and response date
-   No incident right now? Go to [preventing fraud at the counter](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#preventing-card-present-fraud): terminal checks, a keyed-entry policy and per-employee reports

You've got a customer waiting. The reader can't finish the sale. Check the payment's status before trying again. Keep its message, entry method and receipt together. Then use the steps for your system below. This workflow's for your shop, restaurant or mobile counter.

## The card failed at the counter

**Square with pending offline payments?** [Protect the queue first](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#square-offline). Keep the same device, app, mode and location until upload. Then check the payment's result before troubleshooting.

Save the screen message and the transaction reference. Check whether the payment went through. If you're unsure, ask your processor:

> "For transaction \[reference\], what's the current payment status? Was it approved, declined or queued? Which supported step should we take before trying again?"

Use the branch that matches what happened:

-   [The customer is still here](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#chip-or-tap-failed)
-   [Staff typed the card number](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#card-was-keyed)
-   [A payment was taken offline](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#offline-payment-declined)
-   [The tip changed](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#tip-changed)
-   [A dispute arrived later](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#dispute-after-sale)

### The chip or tap failed, and the customer's still here

Check the existing attempt before starting another. Follow your reader's supported recovery instructions. Keep manual entry out of the automatic fallback.

Say this while you check:

> "We haven't confirmed the payment yet. I'll check the record before we try again."

No second card and no cash? Take over as owner, or call your shift manager. For a retail sale, ask whether to pause the handover. For a meal or service already delivered, have the manager discuss the unpaid bill and an agreed next step. A saved card isn't permission for a later charge.

Ask support:

> "There's no other payment method available right now. What's supported on our reader and account? How will that method appear in the transaction record?"

**Using Stripe Terminal?** Standalone mode can back up a disconnected POS when the reader still has internet. It can't take offline payments. It's a public-preview feature for supported smart readers. In Stripe Dashboard, open **Terminal > Locations**, select the location, then **Local configurations > Edit**. Enable standalone mode and save with **Update**. Use Stripe's registration steps for your device. VENDOR [Stripe standalone mode](https://support.stripe.com/questions/standalone-mode-for-terminal).

Tap to Pay on Android doesn't support offline mode. Stripe lists support by reader and payment method. Check your exact combination before relying on it. VENDOR [Stripe offline support](https://docs.stripe.com/terminal/features/operate-offline/overview?reader-type=internet).

### Staff keyed the card number after the reader failed

Keep the receipt and original screen message together. Record why staff used that route. Ask for the processor's recorded entry method, rather than filling it in from memory.

> "For transaction \[reference\], how was the payment classified? Which entry-method and authorization records can you provide? There's a dispute attached. What claim does it make?"

Keep the recorded entry method with the case. Handle an actual case through [the dispute branch below](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#dispute-after-sale). The entry method alone won't tell you the outcome.

### The reader went offline, and a payment declined later

Find the payment's current result before collecting again. Use the steps for your system. A pending record isn't a second sale.

#### Square US

**Still got pending offline payments?** Keep the app installed and signed in. Keep the same device, mode and location until upload. Don't factory-reset before the queue uploads. Signing out, deleting the app, switching modes or locations, and factory resets can permanently lose those payments. Square permits a restart, but it doesn't remove the need to upload before expiry. VENDOR [Square queue protection](https://squareup.com/help/us/en/article/8551-view-offline-payments).

In a supported Square POS app, open **Transactions**, or **More > Transactions**, and select the payment. Pending offline records are visible in the app. After upload, open **Orders > All orders** and select the payment; a red notice identifies a declined offline payment. These steps apply to the apps and modes named in Square's guide. VENDOR [Square offline-payment status](https://squareup.com/help/us/en/article/8551-view-offline-payments).

Reconnect as Square directs and inspect the results. Square puts the loss from expired, declined or disputed offline payments on the seller. VENDOR [Square offline payments](https://squareup.com/help/us/en/article/7777-process-card-payments-with-offline-mode).

#### Shopify POS

Open **Orders** and inspect the order's badge. An offline card payment starts as **Payment pending**. After processing, it can show **Paid** or **Card declined**. Shopify processes saved offline payments after reconnection. Its guide lets you contact the customer using the order's collected phone number or email if payment declines. VENDOR [Shopify offline payments](https://help.shopify.com/en/manual/sell-in-person/shopify-pos/selling-offline/offline-payments).

Check your reader and payment method against that guide. Canadian Interac and Australian eftpos payments aren't supported offline. Neither are manual card entry or Tap to Pay on phones. VENDOR [Shopify offline requirements](https://help.shopify.com/en/manual/sell-in-person/shopify-pos/selling-offline/offline-payments).

#### Toast

Once you're back online, open **Toast Web > Reports > Payments > Payments**. Look for **Denied** in **Status**. If that column's hidden, enable it through **Show/Hide columns**. Toast says a declined offline payment can't be rerun. Contact the guest for a new form of payment. VENDOR [Toast offline recovery](https://support.toasttab.com/en/article/Prepare-to-Operate-in-Offline-Mode-During-Service-Disruptions-or-Outages).

#### PayPal Point of Sale or another integration

PayPal's offline feature is limited to third-party apps using selected SDK partners. Your POS provider handles onboarding. A PayPal Reader alone won't establish your app's support. VENDOR [PayPal offline payments](https://www.paypal.com/us/cshelp/article/what-are-offline-payments--help1311).

For PayPal POS, Clover or another setup, ask your POS provider:

> "Which payments are still queued, and which have declined? Show me where their final status appears. What should we avoid changing before they've uploaded?"

#### Decide what staff should do during the next outage

Make the decision before the shift starts. Will you accept the documented offline risk, or stop taking cards during an outage? Write down who's allowed to decide. Staff need that choice before they're at the register.

**Square US:** In the POS app, open **More > Settings > Checkout > Offline payments**. Its settings distinguish cash-only operation from accepting offline cards for each disruption type. Check the supported app, mode and device first. VENDOR [Square offline settings](https://squareup.com/help/us/en/article/7777-process-card-payments-with-offline-mode).

**Toast:** While you're online, open **Toast Web > Finance > Related > Settings > Payment options**. Under **Credit**, find **Card authorization during payment disruptions**. Review the choice with your manager. For Australia, Canada, Ireland and the UK, Toast directs changes through Customer Care. VENDOR [Toast outage preparation](https://support.toasttab.com/en/article/Prepare-to-Operate-in-Offline-Mode-During-Service-Disruptions-or-Outages).

**Shopify POS:** Setup starts in **Shopify admin > Sales channels > Point of Sale > Edit for POS app > Checkout > Allow offline payments**. Staff also need the offline-payment permission. Use Shopify's setup guide to configure limits and permissions before relying on the feature. VENDOR [Shopify offline setup](https://help.shopify.com/en/manual/sell-in-person/shopify-pos/selling-offline/offline-payments).

### The tip changed after the first amount

Put the original approval, tip and final total together. Keep each receipt if the customer split the bill. Then check which state you're dealing with.

-   **Still unsettled:** Use the POS provider's tip-settlement instructions. VENDOR Square's [tip guide](https://squareup.com/help/us/en/article/8375-settle-payments-and-manage-tips) separates its supported modes and requires settlement permission. Use [the appointment-fees tip branch](https://paymentsandrisk.com/docs/payments/appointment-fees/#the-tip-wont-settle) for the supported Square steps. Match your mode and permission first. That workflow isn't approval for every larger tip.
-   **Already settled, with no dispute:** Ask the provider which supported adjustment applies. A second keyed payment isn't a fix for mismatched totals
-   **A dispute's already open:** Use its stated claim and response date. Go to [the dispute branch](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#dispute-after-sale)

Ask your POS provider:

> "For check \[reference\], the original approval was \[amount\]. The tip was \[amount\], and the final total was \[amount\]. Settlement shows \[state\]. Which supported adjustment applies to this transaction?"

### A dispute arrived after the sale

Save the notice, case ID and the evidence request. Start with the claim and the provider's response date. A signature alone isn't your evidence plan.

**On Square US,** open **Dashboard > Orders & payments > Disputes**, then select the case. Its information request shows the reason, requested documents, status and deadline. Use that case's request to choose your records. VENDOR [Square dispute workflow](https://squareup.com/help/us/en/article/3882-payment-disputes-walkthrough).

For another processor, ask:

> "My case is \[ID\]. What's the exact claim and response deadline? Which documents does this case request? Where do I submit them?"

Use [Reading a Chargeback Notification](https://paymentsandrisk.com/docs/chargebacks/reading-a-chargeback-notification/) to identify the fields, then [the claim chooser](https://paymentsandrisk.com/docs/reference/reason-codes/#what-is-the-customer-claiming) for the code actually supplied. The customer's story alone won't identify the right code.

Still no reason or decision record? Keep the request and support reply. Ask where a supervisor can review that request. Keep working to the response date shown while you ask.

**Already lost?** Keep the outcome notice and what you submitted. Ask for the decision record:

> "What evidence reached the decision-maker? Can you provide the reason and outcome record? Is any further response available for this case?"

Square says a bank's final decision ends Square's ability to keep challenging that card dispute. An appeal isn't promised. VENDOR [Square dispute outcomes](https://squareup.com/help/us/en/article/3882-payment-disputes-walkthrough). Use [After a Lost Dispute](https://paymentsandrisk.com/docs/chargebacks/after-a-lost-dispute/) to check who decided and what remains. Ask your provider what remains available for your actual case.

### One counter card for the next shift

Keep this on a phone or beside the reader. Use references, not copied card details.

1.  **Check the attempt.** Save its message and reference.
2.  **Square offline queue?** Stay signed in. Keep the app, device, mode and location until upload. Skip app removal and factory reset. [Protect the queue](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#square-offline).
3.  **Find its status.** Pending isn't declined. Check the result before collecting again.
4.  **Keep its records.** Entry method, receipt and order reference. Add original amount, tip and final total.
5.  **Pick its branch.** [Failed read](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#chip-or-tap-failed), [keyed](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#card-was-keyed), [offline](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#offline-payment-declined), [tip](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#tip-changed) or [dispute](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#dispute-after-sale).
6.  **Name who takes over.** Owner or shift manager. Keep any case ID and response date together.

If the screen and processor disagree, ask before collecting again.

Running More Than One Counter

For one counter, assign a manager and a backup. If you're mobile, keep the provider's recovery instructions with the reader. Across several registers, use the same card and name the escalation owner for each shift. Test the actual devices your staff use.

These Steps Are Product-Specific

These paths belong to the named products and markets. A similar-looking screen on another system isn't enough. Match the help guide to your reader, app and permissions. A finished service, unsettled tip, declined offline attempt and filed dispute need separate decisions. This card isn't permission for a later charge.

Train It Before You Need It

Use training records, not a live customer charge. Give staff a failed read with unclear status, a keyed payment, a declined offline payment, an unsettled tip and a dispute notice. Ask them to find each record and choose its next step. Include a restaurant guest with no alternative payment and a retail sale awaiting handover. Pass when staff can show the status, preserve the queue, find the right provider instructions and name who takes over.

Where to go next

-   [The queue has uploaded. I need equipment help](https://paymentsandrisk.com/docs/operations/terminal-operations/)
-   [The service happened, but the tip won't settle](https://paymentsandrisk.com/docs/payments/appointment-fees/#the-tip-wont-settle)
-   [I've already lost the dispute](https://paymentsandrisk.com/docs/chargebacks/after-a-lost-dispute/)

## Preventing Fraud at the Counter

If you take payments in person, somebody has told you that's the safe channel. It isn't safe. The [fraud](https://paymentsandrisk.com/docs/fraud/) losses that can land on you there, from keyed entries, swiped chip cards and your own staff, are yours to keep.

[EMV](https://paymentsandrisk.com/docs/fraud/reference/emv-liability/) rules can move counterfeit liability to the issuer, when the chip is processed and the network's tests are met. A keyed sale has no chip read to rely on, swiping a chip card outside proper fallback can leave a counterfeit claim with your acquirer (the bank behind your processor) and then you, and losses from employee schemes and tampered hardware can stay on your side of the line.

You may not need a fraud vendor for any of this. Start with a two-minute terminal check, a written keyed-entry policy, and a per-employee report. Ask your provider whether its reports include terminal, employee and entry method, and what they cost. See [fraud metrics](https://paymentsandrisk.com/docs/fraud/metrics/) to size your exposure before you spend anything.

## What Matters

1.  **EMV [liability shift](https://paymentsandrisk.com/docs/fraud/reference/emv-liability/) turns on more than the swipe.** On an eligible counterfeit [fraud](https://paymentsandrisk.com/docs/fraud/) claim, check the network's card, terminal, region and transaction-data tests. A correctly processed chip payment and a qualifying technical fallback are two ways the claim can fail.
2.  **Skimming didn't go away.** Attackers still overlay devices on your [terminals](https://paymentsandrisk.com/docs/operations/terminal-operations/) to harvest card data.
3.  **Employee fraud shows up in your own reports, so check it first.** [Refund schemes](https://paymentsandrisk.com/docs/fraud/types/refund-fraud/), keyed abuse, card data walking out the door.
4.  **Set a policy for keyed transactions.** Keep the entry method and the reason, and compare their fraud losses with other entry methods on comparable orders. Include keyed attempts in the velocity rules your provider supports ([how they work](https://paymentsandrisk.com/docs/fraud/detection/velocity-rules/)).
5.  **Physical security is fraud prevention.** Terminals in view, tamper checks, access control. See PCI DSS [Requirement 9](https://paymentsandrisk.com/docs/compliance/pci-dss/).

* * *

## Skimming Detection

A skimmer sits between the customer's card and your terminal and copies the data on the way through. Tell your staff exactly what to look for ([PCI SSC's Guide to Safe Payments](https://www.pcisecuritystandards.org/wp-content/uploads/2022/05/Small_Merchant_Guide_to_Safe_Payments.pdf), copyright 2024, p. 15).

### Types of Skimmers

| Type | How It Works | Detection |
| --- | --- | --- |
| **Overlay skimmer** | Fits over existing card slot | Wiggle test, visual inspection |
| **Deep insert skimmer** | Inside the card slot | Harder to detect visually |
| **Bluetooth skimmer** | Transmits data wirelessly | RF detection, Bluetooth scan |
| **Shimmer** | Thin device reads chip data | Very hard to detect |

### Daily Terminal Check

Two minutes, done by whoever opens. A skimmer left on for a week has had a week of your customers' cards:

-   [ ]  Card slot sits flush, doesn't wiggle
-   [ ]  No overlay on PIN pad
-   [ ]  Terminal casing is intact, no gaps
-   [ ]  Cables are secure, no additions
-   [ ]  Tamper stickers/seals unbroken
-   [ ]  Terminal serial number matches inventory

### Weekly Deep Check

-   [ ]  Compare terminal to photo of known-good state
-   [ ]  Check for unusual Bluetooth devices nearby
-   [ ]  Verify firmware version matches expected
-   [ ]  Review transaction patterns for anomalies

Take the photos now, while you know the terminals are clean. You can't do a known-good comparison later if you've got nothing to compare against.

* * *

## Terminal Tampering

Skimmers aren't the only way a terminal gets compromised. Somebody can open the housing, swap a component, or hand it back looking untouched.

### Tamper Indicators

| Sign | What It Means |
| --- | --- |
| Broken or missing tamper seal | Terminal may have been opened |
| Loose screws or panels | Internal access attempted |
| Different colored parts | Replacement components |
| Unusual weight | Internal additions |
| Strange behavior | Slow transactions, unexpected prompts |

### What to Do If Tampering Suspected

1.  **Stop using the terminal immediately**: see [terminal operations](https://paymentsandrisk.com/docs/operations/terminal-operations/)
2.  **Don't run another transaction on it**
3.  **Preserve it as evidence.** Don't open it, don't clean it, don't try to fix it
4.  **Call your [processor's](https://paymentsandrisk.com/docs/operations/processor-management/) security team**
5.  **Pull 30 days of transactions from that terminal**: check [metrics](https://paymentsandrisk.com/docs/operations/metrics/)
6.  **File a police report if it's confirmed**: and document the whole thing for [PCI](https://paymentsandrisk.com/docs/compliance/pci-dss/) incident response

### Physical Security Basics

-   Terminals in view of staff at all times
-   Cable/lock terminals to counter
-   Limit who can access back of terminal
-   Lock terminals in safe overnight (high-risk locations)
-   Visitor/vendor check-in for anyone who touches terminals

* * *

## Employee Fraud Schemes

Your staff hold the keys to your terminal, your refunds and your reports. That's why insider [fraud](https://paymentsandrisk.com/docs/fraud/) hurts. When an insider runs the scheme, it's [first-party fraud](https://paymentsandrisk.com/docs/fraud/types/first-party/) with your own credentials behind it.

Don't read that as distrust your team. Read it as build controls that clear the honest ones fast. A per-employee refund report does that. It also makes the dishonest ones obvious.

### Common Schemes

#### Refund Fraud

**Pattern:** Employee refunds to their own card, or a friend's, with no sale behind it. ([Refund fraud](https://paymentsandrisk.com/docs/fraud/types/refund-fraud/) is the customer-side version. Different scheme, different controls.)

**Signals:**

-   High refund count for specific employee
-   Refunds without corresponding sales
-   Refunds to same card repeatedly
-   Refunds processed after hours or at close

**Prevention:**

-   Manager approval above an amount you choose from refund values and staffing; test it for legitimate returns and attempts just below the line
-   Match refunds to original transactions
-   Review refund reports by employee weekly
-   Dual control for cash refunds

**Then watch your own threshold.** Set approval at $50 and you've described a $49 scheme. You're not looking for one big refund. You're looking for a cluster just under your own line. Read the distribution, not the outliers.

#### Overstated Refunds

**Pattern:** The sale is real. The refund is real. The amount is wrong.

A customer returns a $40 item. The employee puts through $140. The extra $100 goes to cash, or to another card.

This walks straight past the control above. "Match refunds to original transactions" passes here, because there **is** an original transaction. Compare the amounts, not just that a sale existed.

**Signals:**

-   Any refund larger than the sale behind it
-   Refund value per employee climbing while refund count stays flat
-   Refunds that land on round numbers

**Prevention:**

-   Cap refunds at the original amount in the POS, not in the policy document
-   Flag every refund that exceeds its original, by any amount
-   Track refund value and refund count separately by employee

#### Skimming by Staff

**Pattern:** Employee uses a hidden reader to copy card data, then sells it or spends it.

**Signals:**

-   Employee handles cards out of customer view
-   Transactions take unusually long
-   Multiple fraud reports traced to your location

**Prevention:**

-   Customer-facing terminals only
-   Cards never leave the customer's hand
-   Clear sightlines to all terminals
-   Background checks for new hires

#### Keyed Transaction Abuse

**Pattern:** Employee types in card numbers from memory, a photo, or a note, and buys things.

**Signals:**

-   High keyed ratio for specific employee
-   Keyed transactions to same card
-   Keyed transactions after hours

**Prevention:**

-   Monitor keyed ratio by employee
-   Manager approval for keyed transactions
-   Review keyed transactions daily
-   Turn keyed entry off entirely on terminals that don't need it

#### Void/Cancel Manipulation

**Pattern:** Employee rings the sale, takes the cash, then voids the transaction.

**Signals:**

-   High void rate for specific employee
-   Voids at end of shift
-   Voids without customer present

**Prevention:**

-   Customer signature on voids
-   Manager approval for voids
-   Receipt required for all voids
-   Camera coverage of the register area

### Monitoring by Employee

Track these per person. Set alert ranges from comparable shifts, duties and transaction counts. These are prompts to investigate, not proof an employee stole.

| Metric | When to investigate |
| --- | --- |
| Refund count | Outside the range for comparable shifts and duties |
| Refund value | Climbing without a matching change in sales or return reasons |
| Keyed transaction % | Entry without the approval and documented reason your policy requires |
| Void rate | Unexplained change against comparable tills and shifts |
| After-hours transactions | Outside authorized operating hours |
| Same-card refunds | Repeats not explained by the linked original orders |

### The check that needs no suspect

Everything above needs you watching a particular person. This one doesn't. Run it first.

Track **refunds as a share of gross sales**, monthly, across the business. A refund scheme moves that ratio. It moves whether or not you know who's running it. Sales flat and refunds climbing is the shape. Ask your provider whether its reports give you refunds and gross sales. If they do, work it out on one consistent definition.

Two things move it that aren't fraud. Seasonality, so compare to the same month last year. And a real product or fulfillment problem, which you want to find anyway. **The ratio tells you to look. It doesn't tell you what you'll find.**

If you want the scale of this

The ACFE publishes [Occupational Fraud: A Report to the Nations](https://www.acfe.com/fraud-resources/report-to-the-nations) as a free PDF. It's a survey of completed cases reported by investigators, about staff stealing from their own employer. It breaks out by organization size, by scheme, and by how each case got caught. It isn't payments-specific, and it can't tell you how common this is in general.

Ask Your Dev

"Can we pull reports showing refund and void rates by employee? What about keyed transaction percentage?"

* * *

## MOTO/Keyed Transaction Risk

Every keyed transaction is a bet you're placing with your own money.

### When Keyed Entry Is Acceptable

| Scenario | Risk Level | Notes |
| --- | --- | --- |
| Established B2B customer, phone order | Lower | Known relationship, verify identity |
| Card present but chip failed once | Medium | One retry, then request different card |
| Delivery driver collecting payment | Medium | Consider mobile terminal instead |

### When Keyed Entry Is a Red Flag

| Scenario | Risk Level | Notes |
| --- | --- | --- |
| Walk-in says chip "doesn't work" | High | Can be a fraud tactic. A chip can also really fail |
| Customer reads card number from phone | High | Can be stolen card data. Investigate |
| Rush to complete before closing | High | Can be a pressure tactic |
| High-ticket item, new customer | High | A pattern to check, not proof |
| Employee keying without customer present | Critical | Potential internal fraud |

### Liability Shift Loss

These are starting points for an eligible counterfeit claim, not the test. Apply the actual network, code, region and authorization and clearing data. The rules allocate between the issuer and your acquirer. What reaches you depends on your acceptance agreement.

| Transaction Type | Where an eligible counterfeit claim can land |
| --- | --- |
| Chip dip (EMV), required data sent | Stays with the issuer |
| Contactless (NFC) | Check the code's contactless conditions |
| Swiped chip card, outside proper fallback | Your acquirer, then your agreement |
| Swiped card with no chip | Outside that chip code. That doesn't allocate every fraud loss |
| Keyed, phone or mail order (MOTO) | No chip read to rely on. Check your provider's terms |
| Keyed in person as proper technical fallback | Can be excluded from Mastercard 4870, when it's identified in both authorization and first presentment ([Mastercard's guide](https://www.mastercard.com/content/dam/public/mastercardcom/na/global-site/documents/chargeback-guide.pdf), 13 May 2025, pp. 495-504) |

Visa has its own regional eligibility, full-chip-data and fallback conditions ([Visa rules](https://usa.visa.com/content/dam/VCOM/download/about-visa/visa-rules-public.pdf), 24 October 2026, sections 4.1.17.45, 4.1.17.47 and 11.8.2).

**If you key a fraudulent transaction, don't count on the liability shift to protect you.** Your provider's own terms decide the rest, including [offline payments](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#offline-payment-declined).

Keyed entry can cost you twice. Check what your plan charges for a keyed payment against a read one. A provider's keyed charge isn't proof that interchange changed, because interchange depends on the card and how the payment qualifies ([how interchange works](https://paymentsandrisk.com/docs/reference/glossary/interchange-fee/)).

### Keyed Transaction Policy

1.  Chip must be attempted first
2.  If chip fails, tap must be attempted
3.  If both fail, request a different card
4.  Keyed entry requires manager approval
5.  Document the reason for every keyed transaction
6.  Never key a number read off a phone or a scrap of paper

Write those six lines on a card and tape it next to the register. A policy that lives in a binder isn't a policy.

* * *

## EMV Liability Shift Mechanics

The liability shift helps decide which bank carries an eligible counterfeit claim. That can be the difference between a chargeback you never see and one you have to answer.

### How Liability Shift Works

**Before the US shift (October 2015, ordinary point of sale):** the issuer usually ate counterfeit fraud.

**After:** responsibility can follow whoever didn't support the chip, under each network's code. The tests cover the card, terminal, region, required data and exclusions: see [Mastercard 4870](https://paymentsandrisk.com/docs/reference/reason-codes/mastercard/chip-liability/) and [Visa 10.1](https://paymentsandrisk.com/docs/reference/reason-codes/visa/10-1-emv-counterfeit/).

That's for counterfeit cards only. Lost or stolen cards, keyed entry and [offline payments](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#offline-payment-declined) follow other rules, and your provider's terms can put those losses on you.

### What "Chip Terminal" Means

-   Terminal must be EMV-capable
-   EMV must be enabled and active
-   Transaction must be processed as chip (not fallback)
-   The required chip data must reach authorization and clearing

All of them, not most of them. If your terminal has a chip reader and your staff swipe anyway, you may have lost the protection, and you won't find out until the chargeback lands.

### Fallback Transactions

When the chip fails and the terminal drops to swipe, that's a fallback. Whether it's protected turns on the network's read attempt, approval, acceptance and data conditions, not on how many times it's happened ([Mastercard's guide](https://www.mastercard.com/content/dam/public/mastercardcom/na/global-site/documents/chargeback-guide.pdf), pp. 498-504; [Visa rules](https://usa.visa.com/content/dam/VCOM/download/about-visa/visa-rules-public.pdf), section 4.1.17.47, p. 255, and Table 11-11, p. 694).

If one terminal keeps falling back, investigate it. Some things to check:

-   Dirty chip reader
-   Worn chip slot
-   Firmware issue
-   Someone testing you

* * *

## A Two-Week Security Audit

**Week 1: Assessment**

-   Inspect all terminals for tampering signs
-   Pull keyed transaction report by employee
-   Review refund patterns for past 90 days
-   Verify terminal firmware is current
-   Check physical security (locks, sightlines, access)

**Week 2: Remediation**

-   Address any tampering concerns
-   Investigate high keyed ratios
-   Stand up employee monitoring dashboards
-   Update terminal check procedures
-   Train staff on fraud indicators

**Success criteria:** All terminals checked against their known-good state. Keyed entries have approval and a documented reason. Unexplained keyed or fallback patterns investigated, with monitoring in place.

If week 1 turns up nothing, that's a real result. Write down the date, keep the terminal photos, and run it again next quarter.

* * *

## What to Focus On by Volume

| Volume | Focus |
| --- | --- |
| **Under $100k/mo CP** | Daily terminal checks. Manager approval for keyed entries. Basic employee monitoring. |
| **$100k-$1M/mo CP** | Automated employee metrics. Weekly refund review. Tamper detection procedures. |
| **Over $1M/mo CP** | Dedicated loss prevention. Camera integration. Real-time anomaly detection. Regular security audits. |

* * *

## Where Prevention Gets Harder

1.  **High-turnover retail.** New faces every month means training never sticks. Don't fight that with a longer manual. Shorten the procedure until a new hire can do it on day one, and automate the monitoring.

2.  **Mobile and delivery.** A terminal you can't see is a terminal you can't inspect. Use cellular units you can track, and turn keyed entry off on them.

3.  **Multi-location franchises.** You won't get consistency by asking for it. Centralized reporting and a real audit schedule, or you're guessing.


* * *

## Analyst Layer: Metrics to Track

| Metric | What It Tells You | How to judge it |
| --- | --- | --- |
| **Keyed transaction %** | Manual entries / All transactions | Match entries to approved use cases; investigate unexplained changes |
| **Refund rate by employee** | Refunds against comparable sales | Compare shifts, duties, product mix and return reasons |
| **Void rate by employee** | Voids / Transactions handled | Investigate unexplained changes against comparable shifts |
| **Fallback transaction %** | Fallbacks / Chip-card transaction attempts | Compare each terminal with its own history and provider guidance |
| **CP fraud and disputes** | Confirmed fraud and disputes, reported separately. Ratios need their denominators stated | Use [Fraud Metrics](https://paymentsandrisk.com/docs/fraud/metrics/) and the applicable written dispute limit |
| **After-hours transaction %** | Transactions outside authorized hours / All transactions | Investigate unauthorized activity |

### Location-Level Comparison

Running more than one site? Compare keyed %, refund share and chargeback ratios across comparable sites and periods. An unexplained outlier tells you where to look: a bad terminal, a bad hire, or a local fraud pattern that hasn't reached your other stores yet.

### Trend Analysis

Week-over-week movement beats any single snapshot:

-   Keyed ratio climbing = investigate
-   Refunds climbing at one location = investigate
-   Voids spiking right before somebody resigns = investigate

### CP Anomaly Monitoring

Build alerts from your own terminal use. Choose each amount, count and time window from comparable shifts, then check the workload and false alarms before relying on it. Multiple cards per hour is ordinary for a busy checkout; counts alone don't identify abuse.

| Anomaly | Detection Logic | Alert Threshold |
| --- | --- | --- |
| **Keyed entry spike** | Keyed % > baseline + 2 std dev | Real-time alert |
| **Off-hours transactions** | Transactions outside business hours | Any occurrence |
| **Refund without sale** | Refund not matched to prior sale | Any occurrence |
| **High-value void** | Void > $X (set threshold) | Each occurrence |
| **Multiple cards, same device** | Card count outside the range for that terminal and shift | Investigate with declines and other signals |
| **Repeated decline then success** | Pattern outside normal retries, using your chosen window | Flag for review |

**Anomaly Investigation Workflow:**

1.  **Alert fires** → Identify employee, terminal, transaction details
2.  **Verify legitimate?** → Check with manager, review camera
3.  **If suspicious** → Escalate to loss prevention
4.  **If false positive** → Tune threshold
5.  **Document outcome** → Train detection model

### Employee Risk Scoring

Score on these factors:

| Factor | Weight | Signal |
| --- | --- | --- |
| Keyed % vs peers | High | Above-average = risk |
| Refund % vs peers | High | Above-average = risk |
| After-hours transactions | Medium | Any = flag |
| Void pattern | Medium | Clustered voids = risk |
| Tenure | Low | New employees = higher monitoring |

**Score monthly and review the unexplained outliers.** Limit the batch to what you can investigate, then expand it if you find a pattern. Don't assume an outlier is fraud. It might be your best closer, or the person who handles the complicated orders because nobody else will. You're looking for the one who can't explain the pattern.

* * *

## Next Steps

**Preventing skimming and tampering?**

1.  [Train daily terminal checks](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#daily-terminal-check): Staff inspection routine
2.  [Perform weekly deep checks](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#weekly-deep-check): Compare to known-good state
3.  [Handle suspected tampering](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#what-to-do-if-tampering-suspected): Response protocol

**Addressing employee fraud?**

1.  [Know common schemes](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#common-schemes): Refund, skimming, keyed abuse
2.  [Monitor by employee](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#monitoring-by-employee): Per-employee metrics
3.  [Put prevention controls in place](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#common-schemes): Manager approvals

**Managing keyed transactions?**

1.  [Identify acceptable scenarios](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#when-keyed-entry-is-acceptable): Low-risk cases
2.  [Recognize red flags](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#when-keyed-entry-is-a-red-flag): High-risk signals
3.  [Enforce keyed policy](https://paymentsandrisk.com/docs/fraud/card-present-fraud/#keyed-transaction-policy): Chip first, approval required

**Background reading for this page**

-   [Terminal operations](https://paymentsandrisk.com/docs/operations/terminal-operations/) and fleet management
-   [PCI DSS](https://paymentsandrisk.com/docs/compliance/pci-dss/) requirements for physical security
-   [Fraud types](https://paymentsandrisk.com/docs/fraud/types/) and how card-present differs from [card-not-present fraud](https://paymentsandrisk.com/docs/fraud/types/third-party/)
-   [EMV liability shift](https://paymentsandrisk.com/docs/fraud/reference/emv-liability/) rules

* * *

## Related Pages

-   [Card-Present Terminal Decisions](https://paymentsandrisk.com/docs/payments/card-present-terminal-decisions/): Terminal selection
-   [Terminal Operations](https://paymentsandrisk.com/docs/operations/terminal-operations/): Day-to-day management
-   [Fraud Prevention](https://paymentsandrisk.com/docs/fraud/prevention/): Prevention strategies
-   [Velocity Rules](https://paymentsandrisk.com/docs/fraud/detection/velocity-rules/): Pattern detection
-   [EMV & Contactless](https://paymentsandrisk.com/docs/fraud/prevention/emv-contactless/): Chip security
-   [PCI DSS](https://paymentsandrisk.com/docs/compliance/pci-dss/): Physical security requirements
-   [Refund Fraud](https://paymentsandrisk.com/docs/fraud/types/refund-fraud/): The customer-side version
-   [First-Party Fraud](https://paymentsandrisk.com/docs/fraud/types/first-party/): Customer abuse
-   [Chargeback Prevention](https://paymentsandrisk.com/docs/chargebacks/prevention/): Dispute reduction
-   [Fraud Metrics](https://paymentsandrisk.com/docs/fraud/metrics/): Measuring CP fraud

## Sources

| Source | Supports | Opened |
| --- | --- | --- |
| [Square offline-payment status](https://squareup.com/help/us/en/article/8551-view-offline-payments) | US POS status screens, pending queue protection and restart distinction | 21 October 2026 |
| [Square offline payments](https://squareup.com/help/us/en/article/7777-process-card-payments-with-offline-mode) | US supported apps, offline settings and seller risk | 21 October 2026 |
| [Shopify offline payments](https://help.shopify.com/en/manual/sell-in-person/shopify-pos/selling-offline/offline-payments) | POS badges, reconnection, contact after decline, setup, permissions and method exclusions | 21 October 2026 |
| [Toast outage preparation](https://support.toasttab.com/en/article/Prepare-to-Operate-in-Offline-Mode-During-Service-Disruptions-or-Outages) | Online setup, regional Customer Care handoff, Denied status and new-payment recovery | 21 October 2026 |
| [PayPal US offline payments](https://www.paypal.com/us/cshelp/article/what-are-offline-payments--help1311) | Selected third-party SDK integrations and POS-provider onboarding | 21 October 2026 |
| [Stripe standalone mode](https://support.stripe.com/questions/standalone-mode-for-terminal) | Public-preview smart-reader backup, internet requirement and configuration | 21 October 2026 |
| [Stripe offline support](https://docs.stripe.com/terminal/features/operate-offline/overview?reader-type=internet) | Reader and payment-method matrix; Android Tap to Pay offline exclusion | 21 October 2026 |
| [Square tip settlement](https://squareup.com/help/us/en/article/8375-settle-payments-and-manage-tips) | Supported modes, unsettled payments and settlement permission | 21 October 2026 |
| [Square payment disputes](https://squareup.com/help/us/en/article/3882-payment-disputes-walkthrough) | Case path, information request and final bank decision | 21 October 2026 |
| [ACFE Report to the Nations](https://www.acfe.com/fraud-resources/report-to-the-nations) | Occupational-fraud research by size and scheme; background reading | 21 October 2026 |
