GiftVeri reads gift card balances here. The brands are Apple, Target, Walmart, Starbucks, Sephora, Best Buy, Nike, Nordstrom, Ulta, Lowe's, lululemon, Foot Locker and Vanilla. The sections below separate the balance, the failed check and the unknown result for these gift cards.
Separate the amount from the operation status
“The check finished” and “a balance was read” are not the same thing. A request can return a business message without an amount, or fail at the sign-in or network stage. When reading a result, look at the amount, currency, status and details together.
Treat an amount as a balance only when the brand's business response explicitly returns it. If you see "-", an empty amount or no result, do not fill in zero yourself. Even a zero amount does not, on its own, tell you what happened to the gift card before.
The PRO pre-activation check uses one rule for every brand: GiftVeri sends a pre-query to that brand official API. An empty card status in the response bytes means the card is not activated or not enabled, and GiftVeri does not send the balance query. A non-empty status continues the balance query. This rule reads only that pre-query status, not the sign-in, connection, rate-limit or unknown results described below. The check is read-only and does not affect later reloading of the card.
Explicit business messages and unknown results
Conclusions such as wrong card number format, region mismatch or already redeemed should be based on explicit business information returned by the brand and on the client’s details. Some older versions used combined status wording; read it together with the specific feedback rather than treating every result without an amount as “used”.
When there is not enough business information, keep “unknown” or the failure reason. The brand, card type and region guide explains how to confirm where a card belongs.
Sign-in, connection and rate-limit errors
Session expiry, sign-in failures, connection errors, rate limits or HTTP 541 cannot, on their own, show that a card is invalid, inactive or empty, and they are not the empty card status the pre-activation check reads from a brand pre-query. They mean the current flow did not obtain enough business information about the card.
Stop the current operation first, then check the selected brand, region and session. If you need to initialize again, do it explicitly as the interface shows; do not keep clicking retry to infer the card’s status.
When a request was sent but the result is unclear
If the request may already have been sent but the interface shows no clear result, keep that uncertain status. Do not put the same card back into the pending queue automatically, and do not use “continue” as a substitute for checking the uncertain task.
Completed rows and pending rows in a batch list are handled separately. Resuming after a stop should only process tasks that were clearly not sent; if a row needs to run again, check it yourself and start it explicitly.
What to keep when troubleshooting
- Client version, brand, selected country and the time it happened.
- The status and error text shown in the interface, with card codes and account details removed before sharing.
- Whether the failure happened during initialization, submission or result display.
- Whether you switched region, account or proxy, and whether any tasks were not yet sent.
This information helps tell flow problems apart from business results. Full card numbers, passwords, verification codes and sign-in tokens should never appear in public problem reports. To locate a problem by version, authorization, session, submission and export stage, see the troubleshooting guide; to keep full business results, save them somewhere you control, as described in the data storage guide.
After a balance has already been read
A missing amount, a sign-in failure and an unknown result stay above. A balance that was shown and later spent somewhere else, a sleeve number that does not match the card, a receipt that disagrees with the issuer, a store and a brand blaming each other, or money already in an Apple account that still will not pay, are not client failures. The cases are in the hour after the Sephora gift card scratch-off, the Apple and Best Buy gift card sleeve, the Apple and Starbucks gift card receipt, who can see where a Nordstrom, Target, Nike or Apple gift card was spent, reading the gift card out, an Apple account disabled months later and Apple gift card money that will not pay.
A gift card that already says redeemed, an error whose second half differs, a website and a phone line that disagree, an intact film with an invalid phone message, money gone before you opened the card, a GameStop email for a Razer gift card whose number is not the PIN, unspent value on a company's books, an Amazon gift card priced above face value, a ruling that Google need not refund a gift card, a Hulu gift card with no balance page, Steam, Xbox, Walmart and Starbucks gift cards that made the news, and gift cards taken from inboxes, are in an Apple gift card already redeemed, the rest of an Apple gift card invalid-code sentence, the GiftCardMall gift card website and the phone, the GameStop and Michaels gift card film still on, Marco's, Food Lion, Visa and Verizon gift cards with the money already gone, the 14 digits on a Razer gift card, the Starbucks gift card on the company books, an Amazon gift card listed at eighty, Google need not refund this gift card, a Hulu gift card with no balance page, what happened with Steam, Xbox, Walmart and Starbucks gift cards and gift cards taken from inboxes.