Magnetic Stripe, Barcode, or QR Code for Custom Gift Cards?

1. Home
2. Categories
3. Gift Cards
4. Magnetic Stripe, Barcode, Or QR Code For Custom Gift Cards?

A gift card does not hold a balance. It holds an identifier, and your POS or gift card platform looks that identifier up in a database to find out what the card is worth. Nearly every encoding mistake traces back to not understanding that one thing.

Once you see it that way, the question changes. It is not which encoding format is best. It is which format the system you already run expects, and in what format it expects the data. Get that answer first and the gift card printing decision becomes simple. Get it wrong and you own a thousand cards that will not scan.

Start With Your POS, Not With Your Card

Most first-time buyers work in the wrong order. They choose a design, approve a proof, order a run, and then find out at the register that the cards cannot be read.

The correct order of operations has three steps.

1. Identify your gift card platform. This is not always the same as your POS hardware brand. You may be running native gift cards from your POS provider, or a third-party gift card platform that integrates with it.
2. Get the encoding spec in writing. Format, symbology, track, number length, character set, and any prefixes you must avoid.
3. Then print.

The specifics below were confirmed against each platform’s published documentation in July 2026. Platform requirements change, so treat this as a starting point for the conversation with your provider rather than a substitute for it.

Magnetic Stripe Encoding

A magnetic stripe stores data in iron oxide particles that an encoder head magnetizes in patterns. Two international standards govern it: ISO/IEC 7811-2 for low coercivity stripes and ISO/IEC 7811-6 for high coercivity.

Magstripe is not obsolete. That misconception costs businesses money, because they specify a barcode for a system built to swipe.

HiCo vs. LoCo

Coercivity is the magnetic field strength required to write to the stripe. Low coercivity stripes are generally brown and are encoded at roughly 300 Oersted. High coercivity stripes are typically black, encoded at around 2750 Oersted, and the stronger field makes them more resistant to erasure, which is why they suit cards that get swiped often over a longer life.

For gift cards the practical read is this. A card that sits in a wallet for eight months next to a phone, a purse clasp, and another twenty cards should be HiCo. A promotional card with a ninety-day life can be LoCo and save you money.

Your platform may not care. Toast’s encoding documentation, last updated December 16, 2025, states that gift cards can be either HiCo or LoCo, and that the cards Toast produces are LoCo. Ask rather than assume.

Track Selection

A stripe has three tracks with different capacities. Track 1 is encoded at 210 bits per inch and holds up to 79 alphanumeric characters. Track 2 runs at 75 bits per inch and holds up to 40 numeric characters. Track 3 holds up to 107 numeric characters.

Two things matter here. Those character counts include the start sentinel, end sentinel, and check character, so usable data is a few characters shorter than the headline number. And Track 2 is numeric only, so if your platform issues card numbers containing letters, Track 2 cannot carry them.

Toast accepts either Track 1 or Track 2, and where both are present it reads Track 1 first. Get your track assignment in writing before artwork goes to production. Plastek encodes magnetic stripe gift cards to the track and coercivity your platform specifies.

Where Magstripe Is Still Standard

Legacy restaurant POS with an integrated swipe reader, casino and gaming operations, hospitality property management systems, and established salon and spa software all still run on swipe. Mindbody’s assignable gift cards, for instance, take an ID number that is typically an ID, barcode, or magnetic stripe on the physical card, entered with a swiper or a barcode reader.

There is a notable exception worth knowing. Clover’s developer documentation recommends that gift card developers use QR codes for physical cards, because the merchant-facing camera on Clover devices can read them.

Barcode Encoding

A printed barcode is the most common format on modern cloud POS systems, and it is the cheapest to produce because it is part of the print run rather than a separate encoding pass.

Symbology Is Not a Detail

“Put a barcode on it” is not a spec. Symbology is the encoding scheme, and the wrong one fails silently.

• Code 39 encodes digits, uppercase letters, and a few symbols. It is low density, so it takes more width per character, and it wraps data in start and stop characters that some systems expect stripped and others expect intact.
• Code 128 encodes the full ASCII set and is considerably denser. Its Code Set C encodes two digits per code point, which matters when you are fitting a sixteen-digit number into a narrow panel.
• UPC and EAN are fixed-length retail product identifiers built for GTINs. They are almost always the wrong choice for a gift card.

The silent failure is the problem. A scanner not configured to decode your symbology does nothing at all when you scan. No error, no beep, no clue. Or worse, it decodes and hands the POS a string with an extra check digit or a missing start character, and the platform reports an invalid card.

Verified platform requirements: Lightspeed’s X-Series documentation recommends Code 128 barcodes with unique, non-sequential alphanumeric codes of at least 8 characters, and notes that as of August 12, 2025 no new gift cards can be created with codes under 8 characters. Vagaro supports entering a physical card’s number manually or scanning its barcode with a barcode scanner or the device camera. And critically, Toast does not currently support traditional barcodes scanned into the POS for gift card purposes. A restaurant that prints barcode gift cards for a Toast register has bought coasters.

Quiet Zone, Print Size, and Contrast

These are production issues, and they are where a manufacturer earns the work.

Quiet zone. A barcode needs clear space on both sides with no text or artwork in it. For Code 128, the minimum is 10X on each side, where X is the width of the narrowest module, and it is mandatory. A common working rule is 10X or one eighth of an inch, whichever is greater, and inadequate quiet zones are a frequent cause of read failure. Designs that run a background pattern to the edge of the barcode panel are the usual culprit, and the damage is done in pre-press.

Print size. Below a symbology’s minimum X dimension, the narrow bars fall under the scanner’s optical resolution and decoding simply fails. A barcode shrunk to fit a design constraint is a barcode that will not read.

Contrast. ISO/IEC 15416 grades 1D barcodes from A to F across eight parameters, and the overall symbol grade is the lowest grade of any single parameter, so one bad measurement drags the whole symbol down. Symbol contrast minimums typically sit around 40 percent for retail applications. In practice this rules out barcodes printed on metallic or dark substrates, reversed out white-on-black, or buried under a high-gloss varnish that flares under a scanner’s light.

Getting the numbering right across a full run is a variable data printing problem, not a design problem.

QR Code Encoding

A QR code is a 2D symbol that holds far more data than a linear barcode and can be read by a camera rather than a laser scanner. That last part is what actually determines whether it belongs on your card.

Shopify’s documentation states that gift cards from its Hardware Store carry a QR code on the back that can be scanned with the POS device’s front-facing camera or a supported 2D barcode scanner, and that a 1D scanner will not work. Cards from a third-party provider need a unique code printed on them, from 8 to 20 digits, which staff enter manually in the POS app.

Toast’s approach is stricter. Toast uses a 2D QR code pointing to a unique URL it hosts for each card it generates, and QR codes pointing to URLs generated by other vendors will not work for scanning. You can still use an outside card manufacturer, but Toast has to generate the data block.

Be honest about the rest. For a standard retail gift program with a scanner at the counter, a QR code is often a barcode with extra steps. It earns its place in three situations: your POS reads through a tablet camera, you want the cardholder to check their balance by scanning with their own phone, or you are running a hybrid program where the same identifier lives on a card and in a mobile wallet.

Dual Encoding

One card can carry more than one format. A magnetic stripe on the back and a printed barcode beside it is a common combination, as is a barcode plus a QR code.

Readers rarely know this is an option, and it solves real problems. It covers a POS migration you can see coming. It handles mixed hardware across locations, where the flagship store has a 2D scanner and the second location still swipes. It lets you phase a rollout without reprinting inventory.

Two constraints. Both symbols must encode the same identifier, which makes the numbering file the single source of truth for the run. And the back of a card has finite space once you account for a stripe, a symbol with its quiet zone, terms and conditions, and a balance-check URL. Dual encoding adds a production step and some cost, but it is far cheaper than a second full run.

Encoding Formats at a Glance

The Pre-Print Checklist

Take this to your POS provider before you approve anything.

1. Encoding format and symbology. You need “Code 128,” not “a barcode.” If magstripe, you need the track and the coercivity.
2. Number format and length. Digits or alphanumeric, fixed or variable length, and any prefixes you must avoid. Toast, for example, asks that third-party card numbers not begin with 862, and recommends 21 digits or fewer, because numbers longer than that cannot be keyed in manually and can only be swiped.
3. Who generates the numbers. You, the platform, or your card manufacturer. If the platform generates them, ask for the file format they will deliver. Toast requests a full list of manufactured cards in CSV or XLS format.
4. Whether cards ship pre-activated. Most closed-loop programs activate at the point of sale, but confirm it rather than discovering it on launch day.
5. Whether the platform supports third-party cards at all. Some do so with conditions. Toast states plainly that its hardware can swipe some but not all physical gift cards, and offers no guarantee for cards from an unlisted third-party provider.
6. Whether you can validate a test card before the full run. This is the one that saves the money.

Order a Test Card Before You Order a Thousand

Every checklist item above resolves into a single physical object: one card, encoded to the spec you were given, in your hands.

Plastek produces sample gift cards encoded to your platform’s specification so you can swipe or scan one at your own register before committing to a production run. If it reads, run the job. If it does not, you have spent one card instead of a thousand, and you know exactly which line of the spec was wrong.

If you are ready to work through your platform’s requirements with a custom card manufacturer, request a quote on custom gift card printing or call the Plastek gift card production team.