Creating a static payment QR code is useful when a customer needs one reusable request for a Bitcoin address, an Ethereum address, or another payment instruction. The QR code carries data; it is not a checkout page, and QREasy is not the party handling the transaction.
Before generating one, decide exactly what the code will contain and which wallet should read it. The payer will review and authorize the payment in their own wallet app, while QREasy only creates the static code. That boundary prevents confusion about confirmation, receipts, and payment status.
Key takeaways
QREasy’s payment generator creates a static code from a Bitcoin or Ethereum address, an optional amount, an optional Bitcoin label, or other entered payment text
The code does not process, receive, or confirm money. The payer’s wallet handles those steps
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.
Check the network, address, amount, and wallet compatibility before publishing the code
Because the code is static, it does not update its amount or show payment status
Understand What the QR Code Contains
A payment QR code is a machine-readable way to carry a payment request. With QREasy, the request can contain a Bitcoin address, an Ethereum address, an optional amount, and a label for Bitcoin, or it can contain other payment text you enter. It is a static data carrier, not a hosted checkout session.
When a compatible wallet reads the code, it may present the address, amount, or text as a payment request. The customer then reviews and authorizes the transaction in that wallet. QREasy does not process, receive, or confirm the payment, and it does not display a live status for the code.
This makes the workflow straightforward for a counter, reception desk, event, or shared business message, but it also makes accuracy important. A QR code can make an incorrect address easy to scan repeatedly, so the source and destination should be checked before the code is put into use.
QREasy encodes the request; it does not execute it.
The payer reviews and authorizes the payment in their own wallet.
The code carries no live payment status from QREasy.
Choose the Payment Data Before Generating the Code
For Bitcoin or Ethereum, start in the wallet that controls the funds. Copy the receiving address from that wallet, confirm that it is the address for the intended network, and compare every character before entering it in QREasy. A Bitcoin address and an Ethereum address are not interchangeable.
An amount is optional. If included, it is encoded in the static code and remains the requested amount each time someone scans it; the code does not recalculate it for a new purchase. Bitcoin requests can also include a label, such as a product, service, or order reference.
You can instead enter other payment text, but wallet support varies. Test the exact payload in the wallet your customers use before publishing it. Never put a seed phrase, private key, password, or other secret into a payment request, because the resulting QR is intended to be shared.
Match the address to Bitcoin or Ethereum as intended.
Compare the full address character by character.
Add an amount only when a fixed request is suitable.
Use the Bitcoin label for a clear purpose when helpful.
Confirm that the intended wallet supports the chosen text.
Scan this code with your phone camera to open the QREasy payment link QR code page.
Create the Static Code in QREasy
Open QREasy’s QR code generators and choose the payment QR option. The dedicated tool is designed for a static payment request rather than a dynamic code whose contents or status change for each transaction.
Enter the Bitcoin or Ethereum address, or the other payment text you want to carry. Add an amount if the request should always show one. For Bitcoin, add the optional label only when it helps identify the purpose of the payment. Before creating the code, compare the entered data with the source wallet.
For a full walkthrough, see the payment link QR code guide; the step-by-step version covers the same creation flow in more detail. Both focus on preparing the static request; the wallet remains responsible for the payment.
Retrieve the receiving address from the source wallet.
Choose Bitcoin or Ethereum, or enter the required payment text.
Add the optional amount and, for Bitcoin, the optional label.
Create the static QR code.
Test it in the intended wallet before use.
Scan, Verify, and Pay in the Wallet
Test the generated code with the camera and wallet combination your customers are likely to use. The customer should see the expected payment details in their wallet and decide whether to approve. If the wallet offers a review screen, they must check the network, address, and amount there before confirming.
A successful scan only proves that data was read. It does not prove that money was sent, accepted, or received. After the customer confirms in their wallet, use the information supplied by that wallet or the relevant payment network to determine status; QREasy is not a payment confirmation service.
For a new payment setup, test on a real compatible device before printing or displaying the code. For a larger or repeated transaction, consider a small test payment first and compare the receiving address in the wallet with the address in the code carefully. These checks reduce the operational risk of copying or scanning the wrong destination.
Open the code with the expected camera and wallet setup.
Review the displayed address, network, and amount.
Approve only after the details are correct.
Use wallet or network information for payment status.
Know the Limits and Publish Responsibly
A static QR code does not change automatically. If you need a different amount, replace the source data and create a new code. The QREasy payment generator does not provide a dynamic payment QR code, so it cannot issue a changing payload, add a live status, or confirm a completed transaction through the QR itself.
Plan where the code will appear and who owns it. For example, a shop may display one reusable request at the counter, while a freelancer may include a code in a client message. If the receiving address or payment instructions change, update the published material instead of assuming the old code will follow the change.
Learn more about the service in the information about QREasy. For static requests, keep the original wallet details available as a fallback and review the code periodically. The goal is a clear handoff from QR code to wallet, without expecting QREasy to become the merchant, processor, or receipt system.
Expect the amount to remain fixed.
Do not expect automatic status or confirmation.
Replace the code when payment details change.
Keep the underlying wallet details available as a fallback.
Frequently asked questions
No. QREasy creates the static QR code. The payer’s own wallet app handles the payment, and QREasy does not process, receive, or confirm it.
Yes. The amount is optional. When included, it is encoded in the static code. For Bitcoin, you can also add a label. The code does not update the amount after a scan.
A static code contains fixed payment data and can be reused. A dynamic code can change its payload or status for each payment. QREasy’s payment generator creates static codes and does not provide a dynamic payment QR code.
Not necessarily. Wallet support for the selected address or text can vary. Test the exact code with your intended wallet before publishing it, and ask customers to verify the network and payment details before approval.
Get started
Create Your Static Payment QR Code
Create a static payment request with QREasy, then test the code in the wallet your customers use before publishing it.
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.