Creating a website-linked Wallet card is useful when a customer, client, or visitor should reach your business site from a phone. The goal is more than adding a QR code: the site, its destination, the Wallet pass, and the way you test the scan all need to fit together. This guide shows the practical sequence for a small business, service provider, or sales team.
QREasy provides digital business cards for Apple Wallet and Google Wallet, along with editable small websites and QR tools. Website-linked Wallet cards require Lite SME or Business, while contact Wallet cards and the first one-page website are free. The key distinction is that a website-linked QR opens your published website in the phone browser; it does not run the website inside Wallet.
Key takeaways
A website-linked Wallet card requires a Lite SME or Business plan
Publish the website before linking it to the Wallet card
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.
Content can change at the same URL without replacing a static QR code
The Save Contact button, contact QR, and website-linked Wallet card perform different jobs
Choose the card type and confirm your plan
Start by deciding whether the main goal is to share contact details or open your website. QREasy supports digital business cards for Apple Wallet and Google Wallet. A contact Wallet card is included with the free plan, but a website-linked Wallet card requires Lite SME or Business. Compare the current allowances on the QREasy plans before you begin.
Choose the website-linked option when a scan should take a recipient to the site you publish with QREasy. Do not treat a contact Wallet card as a substitute: its QR shares contact data rather than providing the direct website-opening journey. The plan requirement applies to the website-linked Wallet card, not to every Wallet or QR feature in QREasy.
Free: one website with up to one page and contact Wallet cards.
Lite SME: includes website-linked Wallet cards.
Business: also includes website-linked Wallet cards.
Check the current allowances on the pricing page.
Prepare and publish the website
Your Wallet card can point only to a working, published website. In QREasy, choose a website template, add and arrange supported sections with text, images, services, contact details, and links, then publish the site. Check the final address in a browser before using it in the Wallet workflow. Internet access is required for visitors to open it.
Review the page as a potential customer would: confirm the business name, services, links, contact details, and the action you want visitors to take next. If you later edit text or images but keep the same website address, visitors can still reach the updated content. If you change the address itself, the destination encoded in the Wallet QR will no longer match.
Publish the site and copy its final URL.
Test every service and contact link.
Keep the same URL for future content edits.
Decide whether the site also needs a Save Contact button.
Scan this code with your phone camera to open the QREasy website Wallet pass page.
Create the website-linked Wallet card
Open the website Wallet pass workflow described in this step-by-step guide. Start a website-linked card for the supported Apple Wallet or Google Wallet journey, select the published QREasy website, and verify the displayed address. Wallet generation processes the supplied data on QREasy servers, so check the URL and card details before distribution.
Create the pass using the same destination you tested on the website. A website-linked Wallet QR encodes that website URL; when scanned, it opens the site through the phone browser, not as a page running inside Wallet. Google Wallet also includes a Visit Page link. Keep both the pass and its QR together so recipients are not given a destination that differs from the one you approved.
Use a site that is already published.
Confirm the exact website address before creating the pass.
Retain the generated Wallet pass and QR for distribution.
Test the QR code on the intended phones
Test with a compatible phone camera or QR reader, using the devices and browsers your audience actually uses. For a website-linked card, the expected result is that the phone browser opens the published site. QREasy cannot guarantee that every device, camera app, or browser will handle every QR in the same way, so include a fallback link in your message when appropriate.
Google Wallet users can also select the Visit Page link to open the website. This gives them a direct route to the site, while the QR itself encodes the same web address. Do not describe the experience as a mandatory review step inside Wallet before the page opens, and do not suggest that the site is hosted inside the Wallet pass.
Open the destination in the phone browser.
Test Google Wallet’s Visit Page route.
Repeat on another phone or browser if possible.
Keep the three contact-sharing methods separate
A contact Wallet card, a static contact QR, and a website Save Contact button all involve contact details, but they are not the same interface. A static contact QR (the free contact-QR generator) embeds the contact details directly and is generated in the browser; a recipient uses a compatible camera or QR reader to review the details and choose whether to save them.
The website Save Contact section is different: it is a button that downloads or opens a vCard file using the details saved in that section. It does not require the visitor to scan the page with a camera. Device and browser handling plus the visitor’s confirmation determine whether the contact is saved. Updating the section changes what the button serves without requiring a replacement static contact QR.
QREasy’s separate QR code generators include the basic contact QR workflow, while the Wallet card is another interface. Contact Wallet cards are free and share contact data; they do not directly open the website in the same way as a website-linked Wallet card. These workflows do not promise automatic contact saving, NFC tap exchange, CRM matching, or identification of the visitor.
Static contact QR: contact data embedded in the QR.
Save Contact button: a vCard download or open action on the site.
Run the final publishing checklist
Before release, verify the entire journey rather than only the appearance of the pass. Use the same published site, check the QR destination, and test the route used by both Wallet and browser. If content changes later, keep the URL stable so the existing QR remains useful. A hosted website does not require a dynamic QR merely because its content may be edited.
Also decide which contact action belongs on the page. Use the website Save Contact button for a direct vCard download or open action, and use a contact QR only where visitors will scan it. If the encoded URL changes, create a new static QR. For a dynamic QR, a managed redirect can change its destination subject to plan limits, but that is optional rather than a requirement for an editable QREasy site.
Plan: Lite SME or Business is active.
Site: the destination is published and accurate.
Pass: the Wallet details match the business.
QR: a phone opens the intended URL.
Updates: the URL remains stable unless the destination changes.
Frequently asked questions
No. Website-linked Wallet cards require Lite SME or Business. The free plan includes contact Wallet cards and one website with up to one page, but not the website-linked Wallet journey.
For a website-linked Wallet card, the QR encodes the website URL and should open the published site in the phone browser, not inside Wallet. Google Wallet also offers a Visit Page link.
The Save Contact button downloads or opens a vCard from the website without asking for a camera scan. A static contact QR embeds the contact details, which a recipient reviews and chooses to save; changing embedded details requires a new QR.
Usually not if you edit content while keeping the same URL: the static QR still points to that address. A new QR is needed if the encoded URL changes. Dynamic redirects are optional and subject to plan limits.
Get started
Create your website Wallet card
Open the Wallet pass workflow and connect your published QREasy website.
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.