Hide a credit card in a screenshot

Sixteen digits do not hide under a polite smear. Neither does the name on the plastic, the expiry, or the CVC you folded into a wallet photo because the decline toast sat next to the card.

Support asked for the error, not a studio shot of the plastic. Crop to the modal first. If that modal still prints the full primary account number, cover the number. If you already photographed the card on a table, bar every digit string, then check Recents so the original with GPS is not the file you later attach.

What to cover in the chrome

A card screenshot is rarely just the embossed line. Wallet apps, banking apps, and checkout pages wrap the number in chrome that repeats it. Work the frame from the outside in.

• The full number, including spaces and the last four when the rest of the shot already identifies the account holder.
• Name line on the plastic or in the digital wallet chip.
• Expiry and CVC / CVV, front or back.
• Barcode or QR on the reverse of a physical card photo.
• Wallet app header: issuer name plus a truncated number that still matches the visible card art.
• Browser checkout chrome: autofill dropdowns, saved-card tiles, and the address bar if a payment path is in the URL.
• Notification shade: a bank banner with amount and last four that slid in while you captured the toast.

If you only needed the red error copy, crop until the card art is gone. Cropping is cheaper than a dozen bars. When the layout must stay so someone can see which button you tapped, keep the layout and paint rectangles over every digit run.

Black bar, not a soft blur

Digit strings are the case redaction research keeps returning to. A light blur, a mosaic with large tiles, or a yellow highlighter leaves enough shape that a later pass can recover the glyphs. A filled black rectangle does not. Use that for the PAN, the CVC, and any IBAN-shaped string that wandered into the same frame.

Do not stack Markup on a JPEG and then screenshot the result into a chat. Each recompress can ring the edges of a weak smear. Draw the bar on the original, export PNG, send the export. Keep the unbarred file off the ticket.

Why the bar wins for short secrets is spelled out in blur versus black bar. Bank-app balances, IBANs, and profile chips are a sibling problem in the banking screenshot guide.

What a support ticket actually needs

Agents need the message, the timestamp if the system shows one, and sometimes the merchant name. They do not need the plastic. If the processor already masks all but four digits, those four can still be too much when the screenshot also shows your legal name and a unique avatar. Prefer the masked UI the bank already drew. If the UI failed to mask, you mask it.

Never include an SMS or authenticator code in the same image. The code is a second secret. The card number is the first. One screenshot should not carry both.

Physical card photos

Overhead photos pick up more than digits. Reflections on the hologram, a signature strip, and a kitchen calendar in the background all travel with the file. Bar the number block as one rectangle rather than tracing each digit. Cover the signature. If the background shows a street number or a name on mail, crop it out.

Phone cameras write location into many stills. Redacting pixels does not strip EXIF. Export from an editor that gives you a clean PNG, or strip metadata in the share sheet before the file leaves the device.

FAQ: Can I leave the last four visible?

Only if the rest of the image does not identify the cardholder and the bank’s own UI already shows those four. If the shot includes a name, an email, a face, or a unique wallpaper, bar the four as well. Last four plus a name is enough for a lot of “confirm your card” scripts you should not help.

FAQ: Is a highlighter on the number enough?

No. Highlighter is a tint. Brightness and contrast bring the digits back. Mosaic with huge blocks can still show four-then-four grouping. Paint an opaque bar that fully covers the character boxes, including descenders and the space between groups.

FAQ: Should I photograph the card to prove I own it?

Not as a default. Ask what field they actually need. Many issuers want a statement date or a decline code from the app, not the plastic. If a process truly requires a card image, cover everything except the specific area they named, and send through the official upload, not a public ticket forum.

FAQ: What about virtual card numbers in a password manager?

Treat them like the real PAN. Bar the generated number, the merchant lock label if it includes an account, and any QR the manager shows. The chrome of a password app also shows other logins; crop to one row or bar the rest.

Paint a solid bar over the PAN in the tab — the file never has to leave your machine. Open BlurThis and export the PNG you will actually attach.