Small businesses often use the word “Wallet card” for several different tools that lead to different outcomes. A QREasy contact Wallet pass, a website-linked Wallet pass, a static vCard QR code, and a website Save Contact button can all support a follow-up, but they do not work in the same way. This guide explains what each option does, when a new QR code is needed, and where free access ends and a paid plan begins.
Key takeaways
A contact Wallet pass lets recipients review details and choose whether to save them; a website-linked pass opens a website URL
A static vCard QR embeds contact data, so changed embedded details require a new code
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.
The website Save Contact button opens or downloads a vCard; it is not a camera-scanned static QR and does not guarantee automatic saving
Website-linked Wallet cards require Lite SME or Business, while contact Wallet cards are included with free access
What a website Wallet pass can do online
QREasy provides digital business cards for Apple Wallet and Google Wallet, an editable small-website builder, and free QR tools. A website-linked Wallet pass is intended to take a recipient to a QREasy-hosted website, where supported sections can present text, images, services, contact details, and links. The published site is reached through its website address and needs an internet connection.
This is useful for a freelancer, shop, or one-person business that wants a compact page explaining its offer. Start by choosing from the website templates, arrange the supported sections, and publish. Keep the page focused on a clear next step; the website and Wallet pass are separate parts of the same customer journey.
Contact journey: review the details and choose whether to save them.
Website journey: open the associated website through its URL.
QREasy does not promise automatic saving, NFC tap exchange, CRM integration, or contact identification.
Contact and website-linked Wallet passes
A contact Wallet pass and a website-linked Wallet pass are related, but they serve different purposes. The contact pass centers on contact details: after opening it, the recipient can review the information and decide whether to save it. The website-linked pass centers on a URL. Its QR opens the associated website in the phone browser rather than running the website inside Wallet.
Choose the contact pass when the immediate goal is “add this person to my address book.” Choose the website-linked pass when the goal is “show me what this business offers, where it is, and how to get in touch.” Do not describe a contact pass as if its QR directly opens a website, because that mixes two separate journeys.
Contact Wallet cards are included with free access.
Website-linked Wallet cards require Lite SME or Business.
QREasy supports both Wallet journeys.
Scan this code with your phone camera to open the QREasy website Wallet pass page.
How the Wallet QR opens a website
To use a website-linked Wallet pass, publish the QREasy website first, verify its address, and use that URL for the pass. The QR encodes the website URL, so a compatible camera or QR reader opens the site through the phone browser. Google Wallet also provides a Visit Page link. QREasy does not claim that a card review is required before the website opens.
Scanning behavior can differ across phones, readers, browsers, and connections. The recipient still needs internet access, and the URL must be reachable. Wallet holds the pass; it does not host a replacement for the site. If the website’s copy, images, or service details change, the same address can serve the revised content while the URL stays unchanged.
For a step-by-step setup, see How to Create a Website Wallet Pass with QREasy. Use this practical sequence: create and publish the site, check the page on the intended connection, create the website-linked pass, and test the QR on devices you can access. Testing your own route is more useful than promising universal compatibility.
Why Save Contact differs from a static vCard QR
The Save Contact section on a QREasy website is a button that downloads or opens a vCard file using the saved section details. It does not ask the visitor to scan the page with a camera, and it is not a static QR code embedded with contact information. Device and browser handling, plus the visitor’s confirmation, determine whether the contact is saved.
A static vCard QR works differently. Contact details are embedded in the code, and a compatible phone camera or QR reader lets the recipient review them and choose to save the contact. If the embedded details change, generate a new code. Editing the website’s contact section instead updates the details served by its button; it does not require replacing a static QR.
These are separate interfaces: the website button, the free contact-QR generator, and the Wallet card. The basic contact QR is generated in the browser. For standalone vCard QR creation, use the QREasy QR code generators, but label printed material accurately so recipients know whether to scan a code or use a button.
When a new QR code is needed
Begin by identifying what the code contains. A static vCard QR contains fixed contact details, so changing an embedded field calls for a new code. A static URL QR contains a fixed URL instead. Content at that URL can change—a hosted page can be revised, or a PDF can be replaced at the same address—without changing or reprinting the QR.
A dynamic QR uses a managed redirect, so its destination can change without reprinting, subject to plan limits. A hosted website does not become dynamic merely because its text or images are editable. Only a change to the encoded URL requires a replacement static code. In short, update the destination when appropriate, but do not confuse redirect flexibility with embedded contact data.
New static vCard QR: embedded contact details changed.
No new static URL QR: only the content at the same URL changed.
New static URL QR: the encoded URL changed.
Managed destination change: use a dynamic QR within plan limits.
Neither static nor dynamic QR guarantees scanning on every device.
Free and paid options for websites and Wallet passes
QREasy’s free option includes one website with up to one page, one dynamic QR code, unlimited static QR codes, seven days of analytics history, and a contact Wallet card. Website-linked Wallet cards are not included in free access; they require Lite SME or Business. Review the current QREasy plans before building a workflow around the direct website-opening journey.
Lite SME includes three websites with up to four pages each, 50 dynamic QR codes, unlimited static QR codes, and 90 days of analytics history. It is listed at EUR 2.99 monthly or EUR 28.70 annually and includes website-linked Wallet cards. Business includes 33 websites with up to 10 pages each, 357 dynamic QR codes, unlimited static QR codes, and 90 days of analytics history. It is listed at EUR 9.99 monthly or EUR 95.90 annually and also includes website-linked Wallet cards.
Free access still supports several useful jobs: a contact Wallet card, a simple one-page website, and static QR creation within the stated limits. The direct website-linked Wallet journey is the paid trigger. Neither scanning nor saving is automatic on every device, so choose the interface around the recipient’s intended action and test the complete path before distribution.
Frequently asked questions
No. A contact Wallet pass supports review and saving contact details. A website-linked pass encodes the URL of a QREasy website and opens that site in the phone browser. Their purposes, QR behavior, and access requirements are different.
No. It downloads or opens a vCard file using the saved section details. Device and browser handling plus the visitor’s confirmation determine the outcome. It is not a static vCard QR and requires no camera scan of the page.
Generate a new static vCard QR when its embedded contact details change. A static URL QR can stay the same when content at that URL changes; replace it only if the encoded URL changes. A dynamic QR can redirect elsewhere within plan limits.
No. Device cameras, readers, browsers, and connections can behave differently. QREasy provides the tools, but visitors still need a compatible scanning route and internet access for hosted websites. Test the actual QR and destination before distribution.
Get started
Next step: build the website-linked pass
Create and publish the QREasy website first, verify its address, then open the Wallet pass tool and test the complete QR journey.
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.