First find which stage the problem is in
Before troubleshooting a gift card check, stop clicking and note which of these stages the problem happens in. Handle only the current stage at a time; do not switch version, platform account, brand account, region and proxy all at once, or you will not know which change affected the result.
- The client version or feature entry does not exist.
- GiftVeri platform sign-in or authorization cannot be confirmed.
- The brand account, region, proxy or session is not ready.
- The card was entered, but you are not sure whether the check was sent.
- The request finished, but the amount, status or details are unclear.
- The result is fine, but copying, CSV or saving work progress failed.
Check the version when an entry is missing
When the menu has no platform sign-in or a brand you expected, check the program version you have. See the download page for the current stable release and release notes. Older versions do not gain platform sign-in, authorization refresh or new brand flows because the website added instructions.
First check the download and release status to confirm the program name, version and release scope. Download, ZIP integrity and update steps are in the download and update guide. If your version lacks an entry the documentation describes, note the version and stop; do not modify local files or relaunch repeatedly to look for hidden features.
Platform sign-in or authorization problems
Your GiftVeri platform account only manages software permissions and is separate from Apple or other brand accounts. After signing in, still confirm your current plan, its status and expiry date; batch and export need an active PRO plan, while FREE only checks one card.
If you are signed out, your plan has expired, refresh fails or the account is suspended, follow the platform sign-in and authorization guide. When authorization cannot be verified, the client should stop before the next restricted action; brand requests already sent cannot be recalled by signing out of the platform.
Brand, card type, region and session problems
First confirm the actual product with the brand, card type and region guide. The store where you bought the card, the card number length or the displayed currency cannot decide the page on their own. For Apple, also confirm the purchase region, selected region, account and proxy separately.
A completed brand sign-in or an opened page only means the preparation session may be usable, not that the card request succeeded. If you see a sign-in failure, a verification page, a region mismatch or an expired session, stop at that stage and redo the explicit initialization steps from the brand page.
After submitting, first judge whether the request may have been sent
If a timeout, frozen window, dropped connection or unknown message appears after clicking check, look at the task row, time and interface status to judge whether the request may have been sent. If you cannot be sure, keep the task as result unknown.
Never retry automatically a check that may already have been sent, and do not re-add that row through batch “continue”. Treat a task as pending only when you can clearly show it was not sent; if it needs to run again, check the card and current session yourself and start it explicitly.
The request finished without an explicit amount
A completed check, HTTP 200, a successful sign-in or an empty response is not a balance. Record a real balance only when the brand’s business response explicitly returns an amount and currency. Empty amounts, dashes, HTTP 541, rate limits, connection errors and unknown responses can never be rewritten as zero.
Use the results guide to tell business results, session problems and unknown status apart. Keep the original feedback and do not conclude from a single error that a card is invalid, inactive or used; errors are not the empty card status the pre-activation check reads from a brand pre-query. Every brand uses that same rule.
Batch stop or continue problems
During a batch, first confirm whether the current card was already sent. Stopping should wait for the current card to finish, then prevent the next one from starting; unsent rows stay pending. After re-initializing a region or switching sessions, old tasks do not continue automatically.
Check the selected rows, pending rows, duplicate marks and current region; the detailed rules are in the batch import, stop and export guide. No row with an unclear result should be resent automatically by “continue”.
Copy, CSV or work-progress problems
First separate the result itself from the save action. A failed copy or file write does not change a business result already returned, and loading work progress does not sign in or check again.
Confirm the save location is writable and the file is not locked by another program, then choose a local location you control. CSV files may contain full card numbers; keep them in a controlled location and never upload them to a public ticket or chat. The difference between sessions, results and work progress is explained in the data storage guide.
Write down a reproducible problem report
- Client version, brand, card type, selected region and time it happened.
- Whether the problem is at the entry, authorization, initialization, submission, result display or export stage.
- Whether the check may already have been sent, and the status the task row currently shows.
- The redacted error text, amount column and currency shown.
- Whether you switched platform account, brand account, region, proxy or session.
Never include full card numbers, PINs, passwords, verification codes, sign-in tokens, cookies, proxy credentials or screenshots containing them. If you need help, use this report to find the matching answer in the Features & Help.
Stop continuing in these cases
- You cannot confirm the brand, card type or region.
- Your version does not have the matching entry.
- Platform authorization or the brand session cannot be confirmed.
- The request may have been sent, but the result is still unclear.
- A page asks you to guess, pad or change card fields.
- Continuing could send the same check twice.
After stopping, keep the existing tasks and original messages, fix the current stage first, and then decide explicitly whether to continue.