Look at four kinds of information separately
This page is about the support status of a gift card check. The “support status”, “verification progress”, “page content” and “client release” shown for each brand are four different kinds of information. They answer different questions and cannot replace each other.
- Support status says how far the code or entry has got, such as check entry available or integrated in development build. Target uses the same integrated status as the other US brands.
- Verification progress says what level of real evidence is on record, such as balance reads, request flow, offline development records or still to be verified.
- Page content says whether the website has documented the scope, workflow, FAQ and sources; it does not mean the feature works.
- Release says whether the code is in a client users can actually get, which is tracked on the download and release status page.
What “integrated in development build” shows
“Integrated in development build” means the current development code has records of the brand workflow or interface hand-off and can move on to real card verification. It does not mean a real balance was obtained, nor that the feature is packaged in an official release.
A brand menu existing, a page opening, an empty form loading, fields being fillable or offline simulation passing can all support a judgement about development progress, but none of them alone can be upgraded to a real card business result. You still need to check both the evidence on the brand page and the release record.
What counts as live-card verification evidence
Live-card verification needs a card you own or are clearly authorized to test, whose brand and region are confirmed, and an interpretable result returned by the brand’s actual business flow. The evidence record should at least distinguish card type, region, date, submission stage, whether an amount was obtained and the original business status.
An explicit amount and currency supports “balance read on record”; an explicit brand business message supports that business result. One result only shows the specific brand, card type, region and flow at that time; it does not automatically extend to other regions, all card types or every future check.
When recording evidence, do not publish full card numbers, passwords, verification codes, sign-in tokens or proxy credentials on a website, document or ticket. If full results need to be kept, store them somewhere the user controls.
What does not count as a successful balance
- A successful sign-in only means the account or session stage finished, not that the card check succeeded.
- HTTP 200 only means the request got a response, not that the response contains a real balance.
- An empty form, a page GET or a usable session cookie does not mean the balance submission ran.
- Offline simulation, synthetic data and test stubs can validate code paths, but are not official brand business results.
- HTTP 541, connection failures, session expiry, unfinished requests or unknown responses cannot show that a card is invalid, inactive or empty. The PRO pre-activation check uses the same rule for every brand: only an empty card status in the official pre-query marks the card as not activated or not enabled, and GiftVeri does not send the balance query.
How to read actual results and when to stop is covered in the results guide.
How to read Apple region progress
The Apple region directory shows “check entry available” and “entry not confirmed” separately from verification progress. Balance reads on record, request flow records only, and region verification records still missing are different levels; a region appearing in the directory does not mean the client supports it.
The US and UK pages also keep their own historical conclusions. Evidence for one region is never copied to another, and the same template or currency cannot replace independent regional verification.
How to read a connected brand
Target is connected for a single-card check in GiftVeri, the same as the other US brands, and its support status is integrated in the development build. Verification is still pending live-card results: a workflow exists, and that does not mean every card already has a real balance. A successful sign-in or an open page does not replace the amount read on this run.
Open the Target US page and check the 15-digit card number and access code. A Visa, Mastercard or other prepaid card bought at Target is not a Target GiftCard. Do not put it in this entry.
When status can be updated
Status can only be updated after new independent evidence is obtained. Editing text, adding a page, passing a build or completing a local browser check does not raise a brand’s or region’s verification progress.
- New evidence should state the brand, card type, region, date and flow stage it applies to.
- Content review dates and historical business verification dates are kept separately.
- A single failure should not mark a whole brand or region as verified unusable.
- A single success should not be extended to all regions, all card types or a guarantee of continued success.
Decide the next step from the status
- To confirm whether the current client includes a capability: check the download and release status.
- To see what evidence exists for a brand or region: open the brand pages and read the relevant page.
- To understand the amount, failure or unknown status of a check: read the results guide.
- If no brand, card type or region matches exactly: stop and re-check with the brand, card type and region guide.
Directory status is an information boundary, not a success rate, a service promise or a judgement of whether a card is genuine.