How to Create a Cash App QR Code: The Complete 2026 Guide

Your $cashtag is the username that starts with a dollar sign — $janesbakery, $mikethebarber. It maps directly to a web address: https://cash.app/$janesbakery. That address is what you encode.

Get it in under a minute. Open Cash App, tap your profile image in the top corner, and your $cashtag shows under your name. Tap to copy, or use the share option to copy the full cash.app/$cashtag link. Paste that URL into the generator.

Confirm it works before you print. Open https://cash.app/$yourcashtag in a browser on a phone not signed into your account. If the page loads, names you, and shows a pay prompt, the QR will too.

A few format rules keep the QR clean:

• Encode the full HTTPS link: https://cash.app/$yourcashtag. The https:// and the $ both matter.
• Don't encode a screenshot of the in-app QR — that's an image, not a link, and it won't survive a print run.
• Don't run the link through a shortener like bit.ly. It adds a redirect hop, lowers trust, and some networks block shorteners. The raw cash.app URL is short enough to keep the QR low-density.
• For payment tracking, encode an EZQR dynamic redirect that points at your cash.app/$cashtag URL instead.

The $cashtag URL is stable for the life of the username, which is why a printed Cash App QR can run for years.

Both point at the same $cashtag and both move money through Cash App. The difference is who's scanning and on what. Use this to decide which one goes on the sign.

Be clear on the split, because it changes what you should expect. EZQR is a QR code generator. It takes your cash.app/$cashtag URL and turns it into a scannable code you can print — that's the whole job. EZQR never touches a payment, never holds funds, and never charges a transaction fee, because no money flows through it.

Cash App is the payment processor. When someone scans your QR and pays, the money moves between their Cash App balance or card and your account. Any fee, limit, hold, or dispute lives inside Cash App. EZQR can't see that a payment happened and can't notify you about it.

That last point matters: a QR generator cannot send you payment alerts. If a generator claims to ping you when a payment lands, it's misrepresenting what it does or routing your money through its own processor. Your payment notifications come from the Cash App app, not the QR. EZQR's dynamic codes log scans — how many, when, and roughly where — but a scan is not a payment. Treat scan counts as interest, not revenue.

The fee question isn't about the QR. It's about which Cash App account the $cashtag belongs to. Decide that first, then generate the QR for whichever profile you settle on.

Personal Cash App is generally free for standard transfers — payments between friends, splitting a check, sending a gift. There's no per-transaction fee on a standard send or receive. The trade-off: a personal account is meant for personal use, not a storefront. Accepting steady business payments through a personal $cashtag can run against Cash App's terms, and personal accounts don't get merchant features.

Cash App for Business is the account type for accepting payments for goods and services. It charges a fee on payments you receive — commonly around 2.75%, though verify current pricing, since rates change. In exchange you get a business profile built for customer payments and the record-keeping that comes with it.

One separate cost applies to both: instant deposits. Standard bank deposits are free but take one to three business days. To get the money immediately, Cash App charges an instant-deposit fee. Verify the current rate in-app.

Run the math on your volume.

A static QR has the URL baked into the pattern — no server in the middle. The phone reads cash.app/$yourcashtag straight off the code. It can't be changed after printing, it never expires, and it keeps working whether or not you pay for anything.

For most Cash App users, static is correct. Your $cashtag doesn't change, so the QR can be permanent too — print one on your tip jar and it works for years at zero ongoing cost. EZQR's free plan gives unlimited static codes as PNG, no watermark, no signup wall.

A dynamic QR points at a short EZQR redirect that forwards to your cash.app/$cashtag URL. The pattern never changes, but you can change where it forwards. Three reasons that's worth it:

• You might switch `$cashtag` or accounts. Repoint the same printed QR instead of reprinting every sign.
• You want scan data. Dynamic codes log scan counts, timing, and rough location — useful for seeing which flyer or stall draws interest. A scan isn't a payment.
• You run rotating links. Point the QR at a preset-amount Cash App request today, swap it next week, same printed code.

The trade-off: a dynamic QR depends on an active EZQR subscription for the redirect to resolve. Static codes survive cancellation; dynamic codes need the lights on. EZQR plans: Free gives 3 dynamic plus unlimited static (PNG); Lite at $5/mo gives 25 dynamic plus SVG and PDF; Pro at $10/mo gives 100 plus analytics; Max at $20/mo is unlimited plus API. See the pricing page and the static vs dynamic guide.

The contrarian take: most small operators are sold dynamic QRs they don't need. If your $cashtag is stable and you don't care about scan analytics, a free static QR is the right answer and the upsell is noise. The permanent QR guide shows how to confirm a downloaded static code keeps working after you walk away from the generator.

The cash.app/$cashtag QR pays off where someone wants to pay you fast and typing a username is friction. A few that work in practice.

Tips for service workers. Baristas, bartenders, hairstylists, buskers, valets, delivery drivers. Print the URL QR on a small card by the register or on the tip jar. A scanner who carries less cash than they used to still leaves a tip in ten seconds. Add your $cashtag in plain text so it doubles as a payable label.

Market stalls, pop-ups, and small retail. Farmers' market booths, craft fairs, flea markets, food carts, countertop signs. A laminated sign with the QR and your $cashtag lets buyers pay without you fumbling a card reader, and a counter QR sits next to the terminal as a no-hardware backup. If you're charging for goods, use a Cash App for Business account. The retail QR guide covers store placement and signage.

Freelancers and small services. Put the QR on an invoice, a quote, or the last slide of a pitch. Where the amount varies, the plain cash.app/$cashtag QR lets the payer enter the amount — no need to preset anything.

Donations and creators. Nonprofits, mutual-aid drives, church collections, fundraisers, stream overlays, zines, merch tables. A QR on a donation box or flyer turns a glance into a gift — pair it with the amount-free flow so donors choose what they give.

Across all of these the print rules are the same: high contrast, a quiet margin, big enough for the scan distance, and your $cashtag in readable text beside it. The best-practices guide and the size guide cover the specifics.

Any payment QR left in public has one real, documented attack: someone prints their own $cashtag QR and sticks it over yours. Customers scan, pay, and the money lands in the thief's account. It's happened on parking meters, restaurant tables, and charity boxes — and a Cash App QR is a direct target because the money moves the instant someone taps pay.

The attack is cheap and silent. The scammer needs a sticker and thirty seconds. You don't find out until takings come up short or a customer says they paid and you never saw it. Cash App's notification is your tripwire — if a customer pays and your app shows nothing, check the sign.

Reduce the risk:

• Print the QR into the sign, don't tape on a loose sticker. A laminated or fixed-sign QR is harder to cover cleanly than a peel-off label.
• Put your `$cashtag` in plain text beside the QR. A scanner can confirm the destination name matches your business before tapping pay. A mismatched name is the giveaway.
• Inspect public-facing codes daily. Test-scan unattended signs with your own phone to confirm they still resolve to your $cashtag. If not, peel the overlay and report it.

A dynamic QR doesn't stop overlay fraud — the attacker covers the whole code regardless — but you control the redirect, so a legitimately printed code can't be silently repointed at the URL level. The physical defense is still the sign itself. The best-practices guide covers placement and verification habits for every payment QR you put outdoors.