Pingverablog ← Blog
Home › Blog › Gift Card Fraud Prevention for Online Stores: A Checklist Before Black Friday

Gift Card Fraud Prevention for Online Stores: A Checklist Before Black Friday

November 6, 2026 · 12 min read

Gift Card Fraud Prevention for Online Stores: A Checklist Before Black Friday

To prevent gift card fraud, treat every place a code can be checked or spent as a payment endpoint. Rate-limit the balance checker and the code field at checkout. Hold digital gift card delivery on orders your fraud tools rate as risky. Restrict who can see full codes, and know how to deactivate a card on your platform before you need to. Then watch three numbers through the peak: gift card share of orders, failed payments on gift card products, and requests to the balance endpoint.

Fraudsters favour gift cards because a digital card arrives by email within minutes and can be resold without shipping anything. Black Friday falls on 27 November 2026, and the weeks around it are when most gift cards are bought and activated. If you start this week, you have time to change settings and test them before the code freeze.

At a glance

  • OWASP lists gift card enumeration as automated threat OAT-002, Token Cracking: bots guess codes until they find ones with a balance.
  • F5 reports that gift card cracking increases in the holiday season, when most cards are purchased and activated.
  • The other common losses are digital gift cards bought with stolen payment cards and hijacked customer accounts holding a stored gift card balance.
  • On Shopify (as of November 2026), gift cards in medium or high risk orders are not fulfilled automatically, and orders paid in full with a gift card get no fraud recommendation.
  • WooCommerce Gift Cards lets store owners deactivate a code and shows store managers only its last four characters.
  • Write the response plan now: who deactivates codes, who contacts the payment provider, what customers are told.

Why gift card fraud matters this month

The OWASP Automated Threats project defines Token Cracking (OAT-002) as the "mass enumeration of coupon numbers, voucher codes, discount tokens", and lists "voucher, gift card and discount enumeration" among its other names. In practice, bots send thousands of guessed codes to a balance checker or a checkout field and record which ones return a value. F5 describes the next step: once attackers find cards with a positive balance, they use or sell them "before the legitimate customer has had a chance to use it." F5 also notes that attackers narrow their guesses with number patterns and the feedback they get from error messages.

The attack needs live balances to find. F5 states it has "observed an increase in gift card cracking during the holiday season, as that's when the majority of gift cards are purchased and activated." A store that sells many cards between late November and the end of December has more value sitting in active codes in that window than at any other time of year.

There is a second pressure from the buyer side. The US Federal Trade Commission tells consumers that "only scammers will tell you to buy a gift card" and give them the numbers off the back. Some gift card purchases on your store will come from people being coached by a scammer. You cannot stop every such purchase, but a short warning on the product page costs nothing.

Platform behaviour you should know before planning, as of November 2026:

  • Shopify: a gift card can't be used to buy another gift card. If an order is rated medium or high risk, gift cards in that order aren't automatically fulfilled. Orders paid in full with a gift card receive no fraud recommendation. Deactivating a gift card is permanent; Shopify's guidance is to issue a new card instead. Merchants see only the last four characters of a code, and the standard CSV export includes only the last four as well.
  • WooCommerce Gift Cards: codes use a 19-character format (XXXX-XXXX-XXXX-XXXX). From a code's edit page, store owners can activate or deactivate it. Customers can redeem a code into their account balance for later use. Store managers see only the last four characters; administrators see the full code.

If you run Magento or a custom platform, check the same points in your own gift card module: code length and randomness, whether the balance check is public, whether a card can pay for a card, and how deactivation works.

Four ways stores lose money on gift cards

Balance cracking is the bot-driven guessing described above. The store sees a burst of requests to a balance page or repeated invalid code attempts at checkout, often from many IP addresses.

Stolen payment cards buy digital gift cards. A fraudster pays with a stolen card, receives the gift card code by email, and resells or spends it before the chargeback arrives. The store loses the merchandise bought with the card and pays the chargeback. This overlaps with card testing; see our guide to a card testing attack on your online store.

Account takeover drains stored balances. Where customers redeem gift cards into an account balance, as WooCommerce Gift Cards allows, a stolen password gives access to the money. Our account takeover protection map covers login controls.

Scam victims buy cards under instruction. The store is paid, but the customer may later ask for a refund.

Step-by-step checklist for this week

  1. List every endpoint that accepts a gift card code: the public balance checker, the cart or checkout code field, the customer account "redeem" form, any storefront or headless API, and in-person POS if you have one. Agencies should record this per client site.
  2. Put rate limits on each endpoint, keyed by IP address and by session or account. A real customer checks a balance a handful of times; hundreds of attempts per hour from one source is automation.
  3. Add a bot challenge (CAPTCHA or your CDN's bot protection) to the public balance checker. If you get little legitimate use from it, consider replacing it with balance display inside the gift card email or the customer account.
  4. Return the same error message for "invalid code" and "code with zero balance". Distinct messages tell an attacker which guesses are close.
  5. Confirm risky orders are held. On Shopify, check that you have not overridden the default hold on gift cards in medium and high risk orders. On WooCommerce, decide whether first-time buyers of high-value digital cards should wait for manual review before the code is sent.
  6. Set limits: a maximum gift card value per order and per customer per day. Shopify caps gift card product denominations at USD 10,000 or equivalent; most stores need a far lower internal limit.
  7. Review who can see full codes and who receives copies of issued codes. Remove former staff and agency accounts that no longer need administrator rights.
  8. Practise deactivation on a test card. Know whether it is reversible on your platform (on Shopify it is not) and how you will reissue value to a legitimate holder.
  9. Add a scam warning to the gift card product page and confirmation email, in your own words, based on the FTC wording that no real business or government agency asks to be paid in gift cards.
  10. Set baselines now for gift card share of orders, failed payment rate on gift card products, and daily balance-check requests, so you can recognise a spike in late November.

Controls table

Risk Owner Check Frequency
Balance cracking via public checker Developer or agency Request rate per IP to balance endpoint; challenge in place Daily from mid-November to January
Code guessing at checkout Developer Invalid code attempts per session; uniform error message Weekly, daily during peak
Stolen-card gift card orders Store operator Gift card share of orders and failed payments on gift card products vs baseline Hourly alerts during peak, daily review
Account balance draining Store operator Unusual balance redemptions from new devices or after password resets Daily
Over-broad access to full codes Store owner Admin user list; who sees full codes or code copies Before peak, then monthly
Slow response to a compromised batch Store owner and agency Deactivation tested; runbook owner named Once before peak

Copyable artefact: gift card incident runbook

GIFT CARD INCIDENT RUNBOOK  (store: ____________  owner: ____________)

Trigger (any one):
[ ] Balance-check requests > __ x normal in 1 hour
[ ] Gift card share of orders > __% (normal: __%)
[ ] Failed payments on gift card products > __ in 1 hour
[ ] Customer reports a card drained before first use

First 30 minutes
[ ] Turn on or tighten bot challenge on balance checker and code field
[ ] Temporarily hide digital gift card products if stolen-card orders are suspected
[ ] Pause automatic delivery of new gift card codes; switch to manual review
[ ] Export the list of codes used or checked during the spike (last 4 chars + IDs)

First 24 hours
[ ] Contact payment provider about suspected stolen-card orders
[ ] Deactivate confirmed compromised codes; record ID, balance, time, who did it
[ ] Reissue value to verified legitimate holders (new code, not reactivation)
[ ] Reset passwords on accounts where balances were redeemed unexpectedly
[ ] Note the incident on the shared timeline with deploys and config changes

Before closing
[ ] Rate limits and challenge reviewed; thresholds adjusted
[ ] Customer replies sent using an agreed template
[ ] Short write-up: trigger, impact (illustrative or measured), fix, follow-up

Worked scenario (illustrative)

The numbers in this scenario are invented for illustration. A WooCommerce store sells clothing and digital gift cards. On a normal November day, gift cards make up about 4% of orders. On the Saturday before Black Friday, the operator's hourly order alert shows gift cards at 30% of orders over two hours, most of them at the maximum denomination, from new customers, with several failed payment attempts before each success.

The operator follows the runbook. They hide the gift card product, pause automatic code delivery, and send the order list to the payment provider. Because WooCommerce lets them deactivate individual codes, they deactivate the codes from those orders that have not yet been redeemed. Two orders turn out to be genuine customers buying presents, and the operator emails them new codes after a quick verification. The next week, the agency adds a per-customer daily gift card limit and a challenge on the balance page before relisting the product.

Common mistakes

  • Treating the balance checker as a marketing page. It accepts code guesses and needs the same protection as a login form.
  • Showing different errors for invalid and empty codes, which helps attackers narrow their guesses.
  • Turning off fraud holds during peak to speed up delivery. A delay of an hour is cheaper than a chargeback on a card that was spent in minutes.
  • Assuming gift card payments are covered by your fraud tool. On Shopify, orders paid in full with a gift card get no fraud recommendation, so drained cards spent on merchandise need your own checks.
  • Deactivating a code on Shopify to "pause" it. The action is permanent.
  • Sharing full code lists by email or spreadsheet with staff and contractors.

Limitations: rate limits and challenges slow attackers and raise their cost; determined groups rotate IP addresses and solve challenges, so these measures reduce losses without removing them. Platform behaviour described here is as of November 2026 and may change; check your platform's current documentation. Consumer protection and gift card expiry rules vary by country and region, so confirm refund and reissue terms with your own adviser. This article is operational guidance, not legal advice.

FAQ

What is gift card cracking?

It is a brute-force attack where bots try large numbers of possible gift card codes against a balance checker or checkout to find cards that hold value. OWASP classifies it as OAT-002, Token Cracking.

Should I remove the public gift card balance checker?

If few real customers use it, removing it or moving balance display into the customer account and the gift card email reduces exposure. If you keep it, add rate limits, a bot challenge and uniform error messages.

Can I reverse a gift card I deactivated by mistake?

That depends on the platform. On Shopify, deactivation is permanent and the guidance is to issue a new card. WooCommerce Gift Cards provides an activate/deactivate control on the code's edit page. For other platforms, test on a dummy card before peak.

Sources

  • OWASP Automated Threats to Web Applications, OAT-002 Token Cracking: https://owasp.org/www-project-automated-threats-to-web-applications/assets/oats/EN/OAT-002_Token_Cracking.html
  • F5, Gift card cracking: https://www.f5.com/solutions/gift-card-cracking
  • US Federal Trade Commission, Avoiding and reporting gift card scams: https://consumer.ftc.gov/articles/avoiding-and-reporting-gift-card-scams
  • Shopify Help Center, Gift cards overview: https://help.shopify.com/en/manual/products/gift-card-products/overview
  • Shopify Help Center, Managing purchased gift cards: https://help.shopify.com/en/manual/products/gift-card-products/manage-purchased-gift-cards
  • Shopify Help Center, Modifying gift card settings: https://help.shopify.com/en/manual/products/gift-card-products/modify-gift-card-settings
  • Shopify Help Center, Redeeming gift cards: https://help.shopify.com/en/manual/products/gift-card-products/redeem-gift-card
  • Shopify Help Center, Reviewing orders with fraud analysis: https://help.shopify.com/en/manual/fulfillment/managing-orders/protecting-orders/fraud-analysis
  • WooCommerce, Gift Cards store owner's guide: https://woocommerce.com/document/gift-cards/store-owners-guide/

Last reviewed: 2026-11-06


Step 10 asks you to watch order flow, including failed payments. For WooCommerce stores, Pingvera receives order.created and order.failed events in real time through its WordPress connector and places them on one timeline with deploys and incidents, so a burst of failed payments sits next to the configuration change that came before it. Its anomaly detector compares orders with an hourly baseline and alerts when the site is up but orders stop. Pingvera does not block bots or inspect gift card codes. For a deeper look at order-flow alerts, read catching a WooCommerce store that stopped selling.

Know about problems before your customers do

Pingvera watches whether an online business actually works — uptime, checkout, orders, domain, SSL and server — and alerts you in Telegram, email or a webhook before a customer has to tell you.

Start free

Read next: Holiday Return Policy for Online Stores: 2026 Setup Guide · Fraud Controls vs Ecommerce Conversion · Magento Security Patch Oct 2026: BlockStrap Fix Checklist · 5 Best Client Reporting Tools for Web Agencies (2026) · Run a free site check.

Read next: Holiday Return Policy for Online Stores: 2026 Setup Guide · Is Cloudflare Down? An Outage Plan for Online Stores · Fraud Controls vs Ecommerce Conversion · Magento Security Patch Oct 2026: BlockStrap Fix Checklist · Run a free site check.

← All articles · Privacy policy · pingvera.com