About Ethereum QR Codes
An Ethereum QR code follows EIP-681, a format the Ethereum developer community defined specifically for payment requests, encoding your wallet address as an "ethereum:" link that can optionally include a specific amount, so a compatible wallet app pre-fills the transaction rather than requiring the sender to copy a long hexadecimal address character by character. As with Bitcoin, the underlying motivation is the same: manually retyping a wallet address is tedious and genuinely risky, since a single wrong character sends funds to an unrelated, unrecoverable destination with no way to claw them back afterward.
Where Ethereum meaningfully diverges from Bitcoin, and where this generator's simplicity can be a bit misleading, is that a single Ethereum address isn't tied to one single asset. The same address that holds ETH, the network's native currency, can also hold potentially hundreds of different tokens built on top of Ethereum's infrastructure - stablecoins, project-specific tokens, and more - all technically sent to that same address. A wallet app scanning this code will typically default to sending plain ETH unless told otherwise, so if you're actually expecting payment in a specific token rather than ETH itself, it's worth being explicit about that in any label or accompanying instructions, since the QR code and address alone don't communicate which asset you're expecting.
A second layer of complexity worth understanding: Ethereum's mainnet is no longer the only place transactions happen. A growing ecosystem of Layer-2 networks and sidechains exists specifically to offer faster, cheaper transactions than Ethereum's own mainnet, and a wallet address can, in some cases, be used across several of these different networks. An address alone doesn't specify which network a payment should travel across, so for anything beyond a simple, mainnet ETH transaction, it's worth confirming with the sender which network you're expecting the payment on, since sending an asset intended for one network to the wrong one can result in funds becoming difficult or impossible to recover.
Ethereum transactions also require a "gas fee" - a payment to the network itself for processing the transaction, separate from whatever amount is being sent - and that fee fluctuates with overall network demand, sometimes substantially. This is worth knowing if you're the one receiving payment: the amount that arrives is exactly what the sender specified, but the sender's total cost includes that variable gas fee on top, which is worth mentioning if a customer seems surprised their wallet is asking them to pay more than the sticker price.
A more recent, genuinely convenient feature worth knowing about is ENS - the Ethereum Name Service - which lets an address be represented by a short, human-readable name ending in ".eth" instead of a long hexadecimal string, similar in spirit to how a domain name stands in for a numeric IP address. If you've registered one, using it as the label alongside your QR code gives anyone double-checking the destination a much easier reference point than a string of forty-two random-looking characters.
It's used in similar contexts to a Bitcoin code: a freelance developer invoicing a client in ETH, a digital artist accepting payment directly to a wallet for a piece of work, an event booth collecting donations from a crypto-comfortable audience. A consultant working with web3-native clients might keep both a Bitcoin and an Ethereum code printed side by side on an invoice, letting the client pay in whichever currency they already hold rather than forcing a conversion neither party asked for.
As with any crypto payment, transactions are final once confirmed on the network - there's no dispute process, no chargeback, no customer service line to call if something goes wrong. Always double-check the address, network, and amount displayed inside the wallet app itself before confirming a transaction, rather than assuming a QR scan was necessarily read correctly, particularly for anything beyond a small, low-stakes amount.
A common and avoidable mistake worth flagging directly: sending a token built for a Layer-2 network or a different chain entirely to a plain Ethereum mainnet address without checking compatibility first. Not every wallet or token bridges cleanly between networks, and assuming an address works identically everywhere is one of the more frequent sources of lost funds in the broader Ethereum ecosystem - when in doubt, sending a small test amount before a larger transfer is a cheap, sensible precaution.
Where this type isn't the right choice: any recipient without an existing Ethereum-compatible wallet, or a transaction where the sender isn't already comfortable navigating gas fees and network selection. For a mainstream, non-technical customer base, a more familiar payment method is likely to convert meaningfully better than an Ethereum QR code that assumes crypto fluency the audience doesn't actually have.
It's worth labeling any printed code clearly with both the asset and the network you expect payment on - something as simple as "ETH on Ethereum mainnet only" printed alongside the code removes a substantial share of the confusion that otherwise falls entirely on the sender to figure out for themselves before confirming a transaction they can't later undo.