Printing a payment QR code is useful when the destination is known in advance and the same code will appear on a counter, card, package, window, or other printed item. QREasy’s payment generator creates a static code containing a Bitcoin or Ethereum address, an optional amount, and an optional Bitcoin label—or other payment text you enter.
The important distinction is that the QR is a container for payment instructions, not a payment processor. QREasy does not receive or confirm money. After a customer scans the code, their own wallet app displays and handles the transaction, so the printed code must contain accurate information that the customer can review before paying.
Key takeaways
Choose a static code only when its payment details will remain fixed for that printed item
Verify the encoded address or text against the source before every print run
A practical guide to building a massage practice website with QREasy, choosing a template, separating plans, adding contact routes, and using QR codes and Wallet cards.
Organize the text, images, links and QR setup for a QREasy Business Card website, understand Free and premium sections, and prepare every customer contact route.
A practical guide to a three-page law firm website with QREasy, including consultation content, contact links, QR routes, Wallet journeys, and plan requirements.
A practical look at service provider website examples, the one-page QREasy Services template, free and premium sections, contact routes, publishing and QR access.
A practical guide to structuring a photographer website, separating template defaults from recommended content, and choosing free or premium sections without confusing contacts, bookings and QR codes.
Build a restaurant contact page and digital menu with QREasy, distinguish native website content from external contact actions, and update the same QR-linked page as your menu changes.
Make the asset, network context, and amount clear, then let the payer review them in their wallet
Test an actual-size print in the place and lighting where customers will scan it
Understand What the Payment QR Contains
A QREasy payment QR is a static container for payment instructions. It can hold a Bitcoin address, an Ethereum address, an optional amount, and a label when Bitcoin is selected. It can also hold other payment text that you enter. The QR itself does not act as a merchant account or a payment-processing button.
Each element has a distinct job. The address tells a compatible wallet where the user intends to send funds. The amount provides fixed amount data for the wallet to display. The Bitcoin label adds a short purpose or recipient note. Alternative text is plain text only, and how it appears depends on the scanning app.
Because the code is static, it cannot update itself when your address, price, or instructions change. It also cannot show whether a payment was made. Treat its contents as payment information that may be copied or photographed, and do not place secrets in it. QREasy also provides other QR code generators for non-payment uses. For the payment-specific route, the step-by-step payment link QR guide provides a useful companion to the checks below.
Bitcoin or Ethereum: the receiving address is the core payload.
Optional amount: the figure encoded with that address.
Bitcoin label: an optional note attached to a Bitcoin code.
Other payment text: a plain-text alternative when appropriate.
Create a Crypto Payment QR
Open the payment QR generator and choose the asset type (Bitcoin or Ethereum) before entering the receiving address. Copy the receiving address from its source, paste it into the generator, and then compare it with the source rather than trusting the paste blindly. Addresses are long, so review the first characters, the middle, and the final characters at minimum.
If you add an amount, decide whether it should be identical for every customer using that printed code. The embedded figure is fixed data, not a live invoice, and the payer’s wallet may still let them review or change the proposed amount. Any amount printed next to the QR must agree with the encoded amount.
For a second walkthrough of the setup, read How to Create a Payment Link QR Code with QREasy. After generation, scan the result with a QR reader or wallet and inspect the displayed destination and amount before making any physical version.
Use the exact address associated with the intended receiving wallet.
Check every character against a trusted source, not a screenshot of an earlier code.
Keep the asset and network context consistent between the code and surrounding material.
Regenerate the code if the address or amount changes.
Scan this code with your phone camera to open the QREasy payment link QR code page.
Add an Amount, Label, or Alternative Text
An embedded amount is convenient for a fixed-price item, but it ties the printed code to one figure. If the price changes, the old code does not change with it; generate a new code and replace the printed piece. If several values may be used, omit the amount and clearly show the customer what total to enter and verify in their wallet.
The Bitcoin label can identify the recipient or purpose, for example a short business name. Keep it recognizable and free of private information. The generator’s label option applies to Bitcoin only, not Ethereum, so add any Ethereum purpose in the surrounding printed information if customers need that context.
Other payment text is useful when the destination is a reference, instruction, or other plain message rather than a crypto address. It is not a universal payment button: a scanner might display it, copy it, or route it elsewhere. Keep the next action obvious and avoid assuming every wallet will understand the same text payload.
Fixed amount: suitable only while that value remains current.
Bitcoin label: short, visible, and non-sensitive.
Alternative text: useful for instructions, not a substitute for a wallet-supported destination.
Verify the Code Before Printing
Verification is the step that prevents a good-looking code from carrying bad data. Decode or scan the generated QR and compare its address or text with the source record character by character. Check the asset type, confirm that the amount beside the code matches the encoded amount, and make sure any network context shown on the printed item supports the intended payment.
Test with the wallet app customers are likely to use and, where possible, a second device or wallet. Inspect the destination, asset, amount, any network details, and any fee prompt shown by the app; do not approve a payment merely to test the code. If the scan produces an unexpected page, note, or destination, correct the input and regenerate it.
Keep one verified source record and a note of which printed batch uses it. When several products, locations, or versions share a design, give each code a clear internal filename and test a representative example from every batch. This matters most for static codes because each one continues carrying its original payload until it is replaced.
Decode the QR and compare every character.
Match the visible amount with the encoded amount.
Review the asset and network context in the payer’s app.
Test on more than one common scanning setup without completing a payment.
Track which physical batch contains which code.
Prepare the Print and Explain Its Limits
Use the image downloaded from the generator at full quality when placing it in your design, and do not rescale or compress it. Print a test copy at the actual size you plan to use, then examine it under the lighting and viewing distance of the payment point. Increase the size if a camera struggles. Keep a clean margin, strong contrast, and a matte or glare-free surface around the code.
Place the code where a customer can scan without rushing or blocking other people. A counter, card, package, or window is suitable if the code stays visible and unobstructed. Protect a reusable code from dirt and scratches, and replace temporary material whenever the address, amount, or instructions change.
Static codes have no live status: they cannot show that an amount is current, notify you that someone paid, identify an order, or refresh automatically. QREasy does not process, receive, or confirm payments; the payer’s wallet handles the transaction. The plan overview lists unlimited static QR codes, but that allowance does not turn a static payment code into a live tracker.
Print at final size and test in real conditions.
Preserve clarity; do not stretch the code.
Leave enough room around the square for reliable scanning.
Replace printed material when fixed details change.
Use the wallet confirmation, not the QR scan alone, as payment evidence.
Frequently asked questions
No. QREasy creates the static QR, but it does not process, receive, or confirm payments. The payer scans the code with their own wallet app, which displays the payment information and lets them approve the transaction. A scan or wallet confirmation is not a merchant receipt from QREasy.
Not automatically. The amount is fixed in a static payment QR. If the requested amount changes, generate a new code and replace the printed material. Leaving the amount out gives customers flexibility, but they must confirm the correct value in their wallet before paying.
It can help with verification, provided the printed address exactly matches the one in the QR code. Display the asset clearly too, especially when Bitcoin or Ethereum is intended. Customers should still review the destination and transaction details in their wallet rather than relying on the printed copy alone.
No. QREasy’s payment QR generator creates static codes only. Dynamic payment QR codes can serve different live data in other systems, but they are not part of this QREasy feature. The payer’s wallet app remains responsible for handling the payment after the scan.
Get started
Create Your Static Payment QR
Open QREasy’s payment QR code generator, enter a Bitcoin or Ethereum address with an optional amount, then test the result before printing.
A practical, section-by-section checklist for reviewing a four-page QREasy beauty salon website, including services, images, external enquiries, navigation, QR codes and Wallet connections.