A website-linked Wallet card sends recipients to a business website, while a contact Wallet card is built around details they can review and save. They are separate products within QREasy, and neither is the same as a static vCard QR code or a website’s Save Contact button. This guide shows how to prepare a site, create the website-linked Wallet card, understand the scan journey, and update contact information without distributing the wrong code.
Key takeaways
A website-linked Wallet card uses a QR code that opens the published QREasy website in the phone browser
A contact Wallet card shares contact data; a static vCard QR embeds that data, while the website Save Contact button opens a vCard file
Many professionals struggle to choose between a microsite and a landing page. This guide explains the key differences and shows why a microsite is often the better fit for building a simple, professional, and always-on digital presence.
QREasy helps you reduce follow-up friction in two ways: let people save your contact instantly to their phone contacts with a vCard QR, or keep your micro page in Apple Wallet or Google Wallet so you can open it anytime and let people scan through to your fuller digital identity.
Prepare accurate property photos, descriptions, and viewing access steps for a QREasy real-estate microsite, separating confirmed details from items to verify at the viewing.
A microsite is a compact, focused digital presence built to explain who you are, what you offer, and what people should do next. This guide explains the definition, benefits, examples, and differences between micro pages, microsites, landing pages, and full websites.
A link in bio page is useful when you mainly need a simple hub for social links. A micro page or microsite is the better choice when you need a stronger branded presence that explains who you are, what you offer, and what people should do next.
Changes to hosted content do not require replacing a static URL QR when the URL stays the same, and changes to the website’s Save Contact details update the vCard file served by the button without touching any QR code
Contact Wallet cards and the first one-page website are free; website-linked Wallet cards require Lite SME or Business
Choose the right digital card format
Begin with the result you want. A contact Wallet card shares contact data and supports a review-and-save journey. A website-linked Wallet card encodes the website address, so its QR opens that site in the phone browser rather than running the site inside Wallet. Google Wallet also includes a Visit Page link. If you need a site, start by comparing the available website templates.
A static vCard QR code is a separate format: the contact details are embedded in the code, and a compatible camera or QR reader lets the recipient review them before deciding whether to save. The Save Contact section on a QREasy website is different again. It is a button that downloads or opens a vCard file using the details saved in that section; it does not ask the visitor to scan the page.
Use each interface for its own purpose: add a Wallet card through the supported Apple Wallet or Google Wallet journey, read a static vCard QR with a camera or reader, use the website’s Save Contact button to download or open a vCard file, and use a website-linked Wallet QR for a URL. Naming these options in your internal checklist prevents a contact-only code from being promoted as a direct website-opening code.
Prepare the website, QR code, and contact details
Create and publish the QREasy website before preparing the pass. Choose a template, add and arrange supported sections with text, images, services, contact details, and links, then publish it. Keep the resulting website address stable where possible. The site is hosted by QREasy, and visitors need internet access, so test the live address on a phone before linking it to a card.
Select the QR behavior that matches your purpose. A static URL QR contains a fixed URL, while content served at that same address can change without changing or reprinting the code. A dynamic QR uses a managed redirect whose destination can change under plan limits. Editing a hosted site does not automatically require a dynamic QR. For separate QR options, including the browser-generated basic contact QR, use the QREasy QR code generators.
Finalize the details before generating any static vCard QR because changes to embedded contact information require a new code. If the card represents the site, verify that the published URL is the one you want and that its visible contact details are current. Avoid placing the same essential information in several places until you know which one each visitor will actually use.
Scan this code with your phone camera to open the QREasy website Wallet pass page.
Create the website-linked Wallet card step by step
Open the Wallet pass tool, choose the website-linked card option, and select the published QREasy website that the pass should represent. Review the information presented in the workflow before confirming it. Wallet generation processes data on QREasy servers. Website-linked Wallet cards require Lite SME or Business, so confirm that the current account can create this type before starting the final steps.
Complete the corresponding flow for Apple Wallet or Google Wallet and save the pass to the device you are testing. Test each ecosystem you intend to distribute; do not assume that a card saved on one platform will appear on the other. The pass and its QR serve different functions: the pass is stored through a Wallet journey, while the website-linked QR acts as a route to the published URL.
Before broad distribution, verify three things: the scan reaches the correct website, the page is readable on a mobile screen, and the contact details visitors see are accurate. The walkthrough for creating a website Wallet pass provides a companion sequence for this workflow. Do not promise a mandatory review screen before the website opens, because that step is not part of the stated journey.
Understand what happens after scanning
For a website-linked Wallet card, the QR points to the website URL. A compatible reader recognizes the code and the phone opens that address through its browser. The visitor sees the normal hosted QREasy page, not a website embedded inside Wallet. The page can include services, images, text, contact details, and links, but it still depends on an internet connection.
A contact Wallet card leads to contact details that the recipient can review and choose to save. A static vCard QR behaves similarly because the details are embedded in the code. The website Save Contact button instead downloads or opens a vCard file, and the visitor’s device, browser, and confirmation determine the final result. None of these paths should be described as automatically saving a contact.
No QR workflow should be promised to scan on every device, so test with the phones and apps your audience actually uses. The number of taps and time required to save a contact depend on the visitor’s device and confirmation process, so allow enough time for them to review and confirm. Test the full journey on each ecosystem you distribute to, including the Visit Page link shown on Google Wallet cards.
Save contacts and update data correctly
Updates depend on where the information is stored. In a static vCard QR, the contact details are part of the code. If you change a name, phone number, email address, or another embedded field, generate a new QR and distribute it again. Updating a contact record elsewhere does not alter a code that somebody has already printed or saved.
The website Save Contact section works differently. Its saved section details supply the vCard file offered by the button, so editing and saving that section updates the file served by the website. The old static contact QR, if you also have one, remains unchanged. Device handling and the visitor’s confirmation still determine whether the contact is ultimately saved.
Changed embedded vCard details: create and redistribute a new static QR.
Changed Save Contact section details: save the section; no replacement contact QR is needed.
Changed page content at the same URL: keep the existing static URL QR.
Changed encoded destination: issue a new code or update the dynamic redirect within plan limits.
Check availability, plans, and common mistakes
Access depends on the format and account level. Contact Wallet cards are included with the free account, as is the first one-page QREasy website. A website-linked Wallet card requires Lite SME or Business. Review the current allowances on the QREasy plans page before choosing, especially if you manage multiple sites or need a managed redirect.
Common mistakes are mixing up the four interfaces, expecting a scan to save a contact automatically, editing a static vCard without replacing its QR, treating the website Save Contact button as a scannable code, or changing a destination without correcting the QR. Assign one owner to each asset, record which URL it encodes, and test the exact path before printing, publishing, or sharing it.
Free: 1 website, up to 1 page, 1 dynamic QR code, unlimited static QR codes, and 7 days of analytics history. Contact Wallet cards are included; website-linked Wallet cards are not.
Lite SME: 3 websites, up to 4 pages each, 50 dynamic QR codes, unlimited static QR codes, and 90 days of analytics history. Website-linked Wallet cards are included. Price: EUR 2.99 monthly or EUR 28.70 annually.
Business: 33 websites, up to 10 pages each, 357 dynamic QR codes, unlimited static QR codes, and 90 days of analytics history. Website-linked Wallet cards are included. Price: EUR 9.99 monthly or EUR 95.90 annually.
Frequently asked questions
The website-linked QR opens the site; it does not automatically save a contact. Visitors can use the site’s separate Save Contact button to download or open a vCard, then confirm saving if their device and browser support it. A contact Wallet card remains the route designed around contact details.
No, if the URL stays the same, because content at that address can change. A new QR is needed when the encoded URL changes. This differs from a static vCard QR: changing its embedded contact details requires generating and distributing a replacement code.
No. It is a button on the published website that downloads or opens a vCard using the saved section details; visitors do not scan the page. A static vCard QR is a separate asset with embedded contact data, and changing those details requires a new QR.
Website-linked Wallet cards require Lite SME or Business. The free account includes contact Wallet cards and the first one-page website, but it does not include the website-linked Wallet card option.
Get started
Create your website-linked Wallet card
Open the QREasy Wallet pass tool, choose the website-linked option, select your published site, and test the resulting pass before distribution.
A WiFi QR code lets guests connect to a wireless network by scanning a code instead of typing the network name and password. This guide explains how it works, what information it contains, how to use it safely, and how to create one with QREasy.
A micro page is a compact digital identity page that brings your most important links, contact details, social profiles, documents, maps, and QR codes into one easy-to-share place.
