7 gift card and store-credit bugs that quietly break checkout for your best customers

A new customer who hits a checkout bug usually just leaves. A loyal customer who hits a checkout bug, one holding a gift card or a store credit balance they've been saving for exactly this purchase, often fights for it. They email you. They call. They try again on their phone. And if the bug still doesn't resolve, you don't just lose a sale, you lose someone who had already decided to trust you twice: once with their money, and once with their patience. Gift card and store credit systems are small, rarely-touched corners of most storefronts, which is exactly why their bugs survive so long unnoticed.

Balance mismatches between systems

The most common failure is also the hardest to catch by just glancing at your admin: the balance shown to the customer doesn't match what the system will actually apply at checkout. This happens when gift card balances are cached on the product or cart page but recalculated at the payment step, or when a third-party loyalty app and your platform's native gift card ledger drift out of sync after a partial redemption.

A customer sees "$42.50 available," applies it, and checkout shows a different number, or rejects the code outright. On Shopify, this often traces back to apps that layer store credit on top of native gift cards without reconciling balances in real time. On WooCommerce, it's frequently a caching plugin serving a stale account page alongside a live cart total. The fix isn't exotic: audit how often your gift card balance is recalculated, and whether every touchpoint (product page, cart, checkout) reads from the same source.

Gift card balance not applying at all

A close cousin of the mismatch problem: gift card balance not applying is one of the most common checkout complaints. The code is valid, the balance is confirmed, and the customer clicks apply and nothing happens, or the discount field shows $0.00 deducted. This is often a JavaScript conflict between the gift card redemption script and another app running on the same checkout page, similar to the script collisions covered in cookie consent banners that block the buy button. It can also happen when a gift card was issued in a currency or region different from the one the customer is checking out in, and the platform silently refuses the mismatch instead of explaining it.

Because this failure produces no error message a merchant would see in analytics, it tends to go unreported until a customer escalates directly. If you rely on support tickets to surface this, you are almost certainly undercounting it.

Partial redemption and remaining balance errors

Gift cards are rarely spent in one transaction. A customer applies $30 of a $50 card to a $22 order, expects $8 left over, and finds the card shows $0 or an incorrect remainder on their next visit. This is a store credit checkout error pattern that specifically burns repeat customers, because they're the ones making multiple small purchases against a single balance over weeks or months.

The root cause is usually a rounding or sequencing bug: the system deducts the full card value instead of the order value, or a refund on part of that order fails to credit the gift card correctly. Test this deliberately. Issue a test gift card, make a partial purchase, check the remaining balance immediately and again 24 hours later, since some platforms update the visible balance on a delay even when the ledger is correct.

Currency conversion errors on multi-currency stores

If your store sells in multiple currencies, gift cards and store credit introduce a conversion problem that discount codes mostly avoid, because gift cards hold a fixed monetary value rather than a percentage. A $100 gift card issued in USD needs a defined, consistent conversion rate when redeemed against an order priced in EUR or GBP, and if that rate is calculated differently at checkout than it was at issuance, the customer either loses value or the store does.

This is a close relative of the pricing bugs described in wrong prices in the wrong currency. The safest pattern is to lock gift cards to a single currency at issuance and convert clearly at redemption, showing the customer the math rather than a silent deduction. If your platform doesn't support that natively, this is a configuration detail worth confirming with your app vendor rather than assuming it works.

Stacking conflicts with discount codes and promotions

Store credit and gift cards often share the same discount engine as promotional codes, and that shared plumbing is where stacking rules get tangled. A customer applies a 20% off code and then tries to add store credit, and one of three things happens: the second discount is silently rejected, the two combine in a way that wasn't intended, or the order total goes negative and checkout simply breaks.

The mechanics are similar to the coupon-stacking failures in stacking discount codes gone wrong, except here the cost isn't a free product, it's a frustrated loyal customer who can't complete a purchase at all. Define your stacking rules explicitly (can gift cards combine with sale pricing? With automatic discounts?) and test the combinations you actually allow, not just the ones you intend to allow.

Refunds that don't return credit correctly

When an order paid partly with store credit gets refunded, the credit portion should return to the customer's account, not vanish or get refunded as cash to a payment method they didn't use. This connects directly to the broader refund failure modes in return and refund workflows, but gift cards add a wrinkle: some platforms refund the non-credit portion correctly while quietly failing to re-issue the credit portion, leaving the customer short with no obvious error anywhere in your admin.

If your store processes any meaningful volume of store-credit purchases, periodically audit a sample of refunded orders against the customer's credit balance after the fact. It's tedious, but it's the only way to catch a slow leak that a fast-moving support team won't flag on its own.

Expired or orphaned codes from app migrations

The seventh failure mode shows up after a platform migration, a gift card app switch, or an uninstall. Old gift card codes stop validating, store credit balances disappear from customer accounts, or codes that should have expired keep working indefinitely because the expiration logic lived in an app that's no longer running. This is the same category of problem explored in orphaned app code: the storefront looks unchanged, but a dependency it relied on quietly stopped functioning.

Anytime you switch gift card or loyalty apps, export existing balances, confirm they import correctly into the new system, and test redemption with a real (small) balance before announcing anything to customers. Don't assume the migration tool's success message is the same as a working checkout.

Keep an eye on the parts customers rarely complain about

Gift card and store credit systems get less testing than almost any other part of a storefront because they get touched less often, not because they matter less. The customers affected are frequently your best ones: the people who came back, who trusted you with a prepaid balance, who expected the purchase to just work. Cassian™ monitors order flow, pricing, and overall store health continuously, feeding into the Cassian Score™, so that the quiet failures in corners like this surface before a loyal customer has to tell you about them.