Payment support asked for the decline toast. What they often receive is a studio shot of the plastic: primary account number, CVV, expiry, and sometimes the SMS code that arrived while the camera was open. Soft blur over those digits is theatre. Sixteen characters still leave enough shape for a later pass to recover the glyphs.
This guide owns opaque cover for card secrets only: a solid black bar over the full PAN, CVV or CVC, expiry when it sits next to the number, and any one-time code that wandered into the same frame. Prefer crop when the card art is not needed. Prefer Black bar when the layout must stay so someone can see which button you tapped. If a full number already leaked, rotate the card with the issuer instead of hoping a re-upload will fix the past.
Open larger image in a new tabWhat 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 before you paint the centre.
Open larger image in a new tab- The full PAN, 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.
- Any SMS or authenticator OTP in the same image. The code is a second secret. One screenshot should not carry both the card number and a live login code.
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, keep the layout and paint opaque rectangles over every digit run.
Black bar, never soft blur on digits
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 brightness, contrast, or a trained guess can recover the glyphs. A filled black rectangle does not. Use that for the PAN, the CVC, any IBAN-shaped string, and any OTP that appears in the same frame.
Do not stack a weak smear on a JPEG and then screenshot the result into a chat. Each recompress can ring the edges of a light filter. 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 follow the same rule. The general stills walkthrough (without repeating card rules) is how to blur a screenshot.
How to hide a credit card number on a screenshot
Prefer Black bar for the full PAN, CVV, expiry, and any OTP banner. Soft blur and highlighter tints are the wrong tools for digits. Device Markup and Paint steps live on the linked guides, not on this page.
In BlurThis
Open the screenshot blur tool. These steps are card-specific:
- Drop or paste the screenshot. Editing stays in this tab.
- Select Black bar and Box. Drag one opaque rectangle over the full PAN, including spaces between digit groups.
- Add separate bars for CVV / CVC, expiry if visible, and the name line when it sits next to the number.
- Check the notification shade and any SMS or authenticator OTP in the same frame. Bar those banners too. Do not leave a live code beside a card number.
- Zoom to full size. If any digit silhouette remains, widen the bar. Tap Download PNG and send that file.
Banking app screenshots: what to cover
A banking screenshot for support or a forum should keep the error and lose everything else. Crop to the error first, then work the chrome:
- Name and avatar in the header.
- Balances and available credit, including home-screen widgets.
- IBAN, routing, account, and card numbers, full or last four.
- Payee names and saved-bill nicknames.
- Transaction lists that show other people's names.
- QR deposit or barcode pay screens.
- Notification banners with an amount plus last four.
Cover the full IBAN including spaces and country code. Light blur keeps digit silhouettes. The app's “eye” icon that hides balances is a start, but widgets, lock-screen notifications, and watch complications usually ignore it, so check the screenshot afterwards. If the bank asks for a selfie with the card, prefer its official in-app flow, show only what was asked for, and never post that still publicly. Never include an SMS or authenticator OTP in the same image as an account number, the same rule as WhatsApp login codes.
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. IBANs, member IDs, and routing numbers in banking screenshots need the same opaque bar as card PANs.
Ask what field they actually need before you photograph the card. Many issuers want a statement date or a decline code from the app, not a full-face shot of the embossing. When 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.
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. See screenshot EXIF and GPS privacy for the metadata side of the same problem.
If the number already leaked
Covering a new screenshot does not undo a file that already sat in a public ticket, a Discord channel, or a group chat. If a full PAN, CVV, or both left your control, contact the issuer and rotate the card. Treat the leaked image as compromised even if you later upload a barred version. Close the loop on the original message if you can delete or replace it, then assume someone already saved a copy.
The same urgency applies to an OTP that appeared next to the card. That code may already be spent or expired, but the habit of pairing codes with account numbers is what attackers want you to keep. Change the pattern for the next ticket: crop, bar, then send.
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. 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 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.
Editing in BlurThis stays in your browser tab. Prefer Download PNG so the opaque bar stays a flat fill in the file you attach. Closing the tab drops the working copy from this page; it is not a forensic wipe of your device, cloud backups, or the chat where an older copy may still live. Open BlurThis when you are ready to bar the digits, or start from the screenshot blur tool. For the wider cover map, see the how to blur hub. Prefer to stay in a phone or desktop editor? Use a filled opaque shape over the PAN and CVV, then save a new file. Walkthroughs: iPhone, Android, Windows, Mac. Local processing habits: blur a screenshot online without uploading.
Receipts, wallets, and the second page of the PDF
Card digits show up on more than the plastic. Wallet apps, banking receipts, and “order confirmed” emails reprint the last four next to a full address. Bar the PAN and CVV first, then check the address block and the QR code. A QR that encodes a payment link can still be scanned from a soft blur. Prefer a solid bar or a crop that removes the code.
PDFs of invoices often hide a second page with banking details. If you screenshot page one only, fine. If you flatten the whole PDF to images, walk every page. A black box sitting on a live text layer in Acrobat is not redaction. Rasterize, then bar. Details: PDF black box vs PNG.
Marketplace sellers who photograph a card “for verification” should stop. No buyer needs the CVV in a chat. If a platform demands a photo of the card, cover everything except the digits they named in writing, and assume the upload is retained. Prefer official in-app verification flows over sending card photos to strangers.
