Extract Card Numbers, PINs & Balances from Any Gift Card Screenshot
Retyping a 16-digit code and an 8-digit PIN into a tracker takes about 2 minutes per card and nearly always introduces a typo — extraction reads the code straight off the screenshot in 5-10 seconds.
5-10s per screenshot · Up to 99% accuracy on printed text
The Four Fields That Make a Gift Card Screenshot Usable
A gift card screenshot isn't a document — it's a card graphic with a redeemable code buried inside. These four fields are what you actually need from it, and all four come from one image.
The card's identifying number — Amazon's 14-character alphanumeric claim code (A123-456789-ABCDEF), Nintendo eShop's 16 digits, or the 16-digit number on a Starbucks card.
The second part of a two-part code. Starbucks splits an 8-digit PIN from the card number across two lines; iTunes/App Store cards redeem with a 16-digit code that starts with X.
The remaining value, when the screenshot shows it — common on e-gift emails, digital card screens, and some physical-card receipts.
The last usable date, printed on some cards and e-gift emails — many issuers don't print one at all, and the field simply stays empty.
The Code Is There — You Just Can't Tell Which Text Is It
Every gift card screenshot carries two kinds of text: the redeemable code, and everything around it that isn't. The pain isn't reading the image — it's telling the two apart when every issuer formats the code differently.
"I took a picture of the code twice. Somehow, I can't get the camera to see the code. However it will pick up the other area of text on the card."
— AppleVis forum, "OCR apps that scan gift card codes", 2018 — a thread where users describe general OCR reading everything on a card except the code itself
General OCR Reads the Whole Card — Then Gives You a Wall of Text
A scanner that turns the image into text returns card art captions, terms, "gift from" lines, and the code all mixed together — with no way to tell which segment actually redeems. The AppleVis thread above is exactly that: the tool picked up "the other area of text" but not the code.
Every Issuer Formats the Code Differently
Amazon uses 14-character alphanumeric claim codes, Nintendo eShop 16 digits, iTunes/App Store 16 digits starting with X, and Starbucks splits a 16-digit number plus an 8-digit PIN across two visual lines. Template rules break the moment a new card arrives.
The Redeemable Part Isn't Labeled
Card art, terms, promotions, and the code sit in one visual blob. A person who knows the format still squints; a tool that only finds text has no way to discriminate between the code and the marketing around it.
Name the Columns — the AI Finds Each Value by Meaning
With Custom Column Extraction, you type "Card Number", "PIN / Redemption Code", "Balance", "Expiration Date" — and the AI locates each value on the image by understanding what it is, not where it sits on the card.
Format Becomes Irrelevant
The same four columns extract Amazon's alphanumeric claim code, eShop's 16 digits, iTunes' X-prefixed code, and Starbucks' card-number-plus-PIN pair — no per-issuer configuration, no rules to update when a new card design ships.
Marketing Text Is Read, Then Ignored
The AI sees the whole card — including the promo lines — but outputs only the segments that match the columns you defined. What comes back is the code, the PIN, and the balance, not a transcript of the card.
From Card Screenshot to a Ready-to-Redeem Log in Three Steps
If you're consolidating gift card balances — holiday cards, discounted cards from resale sites, or company incentives — the manual alternative is what one r/Costco user describes for Southwest cards: "every time you use it, you have to manually enter the card number until the card is depleted." Here's the loop that replaces that.
Screenshot the Card, Then Upload
The card back, the e-gift email, or the digital card screen in your wallet — whichever shows the code. A physical card photographs fine if the code area is clean and evenly lit. Upload Amazon, eShop, iTunes, and Starbucks screenshots into one batch; the AI reads each by meaning, no per-issuer sorting.
Name the Four Columns Once
Type Card Number, PIN / Redemption Code, Balance, Expiration Date. The same set for every issuer — the AI maps each screenshot into these columns, splitting Starbucks' two-line 16+8 pair into its own Card Number and PIN columns in the same pass.
Export the Log — Codes Ready to Paste
Processing averages 5-10 seconds per screenshot. The output is one XLSX or CSV where every card is a row: the code you can paste straight into any redemption field, the balance you can track, and the expiry that tells you which card to use first.
What a Code Screenshot Can Tell the AI — and What It Can't
When It Works Best
Full-resolution screenshots of the card back, e-gift email, or digital card screen. Machine-rendered codes extract at up to 99% accuracy.
Mixed issuers in one batch. Amazon claim codes, eShop digits, iTunes X-codes, and Starbucks card+PIN pairs process together with one column set.
Codes still intact on the image. Whatever digits are physically present and legible get extracted — the AI never fills in or guesses missing characters.
When to Be Cautious
The tool never redeems the code or checks its validity. It reads the image only — it can't confirm a code hasn't already been used, and it won't touch the card's balance or any issuer account.
A screenshot can't show what isn't there. If the code area was scratched off before the photo was taken, those digits don't exist in the image and can't be recovered by any tool.
Blurry or glare-covered photos. A photo of a physical card under bad lighting, or a heavily compressed forwarded image, lowers accuracy — screenshot the digital card or email instead.
Frequently Asked Questions
Can I extract the redemption code from a gift card screenshot without typing it by hand?
Yes. Create a Card Number or PIN / Redemption Code column and the AI reads the redeemable segment straight off the image. Amazon's 14-character claim code, iTunes' 16-digit X-prefixed code, and Starbucks' 8-digit PIN are all extracted as their own field, ready to paste into any redemption box — no transcription, no typos from re-typing 16 digits.
Amazon gift cards use a 14-character claim code — will the AI get the format right?
Yes. Amazon's claim code format — 14 characters like A123-456789-ABCDEF, dashes included — is read as the Card Number field. The AI understands that a string of letters and digits in that shape is the redeemable code, even when it sits next to card art, terms text, and promotional lines. The code is extracted exactly as printed.
Starbucks splits a 16-digit number and an 8-digit PIN across two lines — do they land in separate columns?
Yes. The 16-digit card number goes into the Card Number column and the 8-digit PIN into the PIN / Redemption Code column. The two-line layout is a common pattern across issuers, and the AI handles it by meaning rather than assuming a single code block.
Can the AI read the Balance shown on a card screenshot?
Yes, when the balance is actually visible in the image. E-gift emails, digital card screens, and some physical-card receipts print the remaining value, and a Balance column captures it as a number ready for spreadsheet math. If the screenshot doesn't show a balance — most physical card backs don't — the cell stays empty rather than guessing a value.
What if the code is scratched off or the photo is blurry?
Digits that are physically missing from the image can't be recovered — no extraction tool can read characters that were scratched away before the photo was taken. Blurry or glare-covered photos also reduce accuracy. Best practice: screenshot the digital card or e-gift email before the physical card gets worn, and capture codes while they're still intact.
Gift card codes are one node of the gaming and digital purchase screenshots overview — the same batch and column set also covers App Store receipts, Steam purchase confirmations, and console store receipts from PlayStation Store, Xbox, and Nintendo eShop.