A Wallet pass can give customers a digital business card that leads to contact details or to a small business website. The distinction matters: a contact pass is built around a vCard, while a website-linked pass uses the URL of a site created with QREasy. Choosing the right journey stops you from checking a QR against the wrong criteria.
This guide explains how to create a website Wallet pass for Apple Wallet or Google Wallet, publish the destination site and test the experience. It also shows what changes after publication, how a contact-saving button fits into the site and which plans include the feature.
Key takeaways
Choose by destination: contact details or a published website
A contact Wallet QR does not open a site; a website-linked Wallet QR does
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.
Website-linked Wallet passes require Lite SME or Business; contact Wallet cards are available on Free
Content can change behind the same URL, so a site edit does not automatically require a new QR
1. Choose between a contact pass and a website-linked pass
Start with the action you want after a scan. A contact Wallet card is for contact details: a static vCard QR shares the embedded data, and a compatible phone camera or QR reader lets the recipient review it and choose whether to save it. The QR does not directly open a website.
A website-linked Wallet card is for a broader destination. Its QR encodes the address of a site created with QREasy, so scanning opens that site in the phone browser. The site can present services, images, links and contact information before the visitor chooses to get in touch.
Keep these interfaces separate. The free contact-QR workflow appears among QREasy’s QR code generators, but it is not the website-opening Wallet journey. Likewise, a website’s Save Contact button opens or downloads a vCard; it does not turn the page into a static vCard QR.
Contact Wallet card: contact details are the destination, and the option is included with the Free plan.
Website-linked Wallet card: a published QREasy website is the destination, so it requires Lite SME or Business.
Save Contact button: a separate website action for offering contact details; the visitor’s device, browser and confirmation determine the outcome.
2. Build and publish the QREasy website
Open the website builder and choose a starting point from the website templates. Add only the supported sections you need, such as text, images, services, contact details and links. Arrange them so a first-time visitor can understand the offer and find a contact route without searching.
Review the wording and images before publishing the site. QREasy hosts the editable site, and the published address can later display revised content. Visitors need an internet connection because the site is served online, so publish and open the final address before attaching it to a Wallet pass.
Keep the homepage focused on one clear offer and one obvious next action.
Use images that represent the actual services, products or work.
Check names, phone numbers, email addresses and links before publishing.
Open the published address in a browser and review the page as a first-time visitor.
Scan this code with your phone camera to open the QREasy website Wallet pass page.
3. Generate the website-linked Wallet pass
Open the Wallet pass workflow and choose the option that links to a website rather than the option that stores contact details. Use the walkthrough for creating a website Wallet pass as a companion reference, and follow its steps to select the published site URL and generate the pass for the relevant Wallet..
Generate the pass for Apple Wallet or Google Wallet and add it through the corresponding Wallet flow. Wallet generation processes data on QREasy servers. For a clearer implementation pattern, compare the steps in the broader practical guide to website Wallet pass generators, then test the final QR on the device you expect visitors to use.
The generated QR should encode the final published site address. Do not confuse it with the static vCard QR used for a contact pass, and do not expect the QR to display the full site inside Wallet. Scanning is intended to hand the visitor to the browser-based site.
Have the published URL open correctly before generating the Wallet pass.
Generate the correct Wallet format for Apple Wallet or Google Wallet.
Add the pass to the Apple Wallet or Google Wallet app, then test the QR code you generated on the device your visitors will use.
4. Verify what the QR opens
Scan the generated code with a compatible camera or QR reader. For a website-linked pass, the expected result is the QREasy-hosted website opening in the phone browser. It is not a webpage running inside the Wallet application. Google Wallet also includes a Visit Page link for reaching the site from the saved pass.
Check the whole path, not only whether a camera recognizes a square. The destination page should load, display the intended content and remain usable over an internet connection. No QR format guarantees scanning on every device, so test current phones and browsers when possible and avoid promising a fixed number of taps.
Test contact handling separately. If the site has a Save Contact section, tapping it downloads or opens a vCard using the saved section details. The visitor then reviews the file and confirms whether to save it. The device and browser determine how that file is handled, so never describe saving as automatic.
Website scan: confirm that the correct published page opens in the browser.
Wallet visit: check the Visit Page link when testing a Google Wallet pass.
Contact section: confirm that the button opens the vCard and asks the visitor to confirm saving.
5. Update the site and confirm the right plan
A static URL QR does not need to be replaced merely because the content behind the URL changed. Update the text, images, services or links in QREasy, republish, and the same published address can show the new version. If you change the encoded address itself, create a replacement QR and update any printed copies.
Dynamic QR codes are a separate managed-redirect option whose destination can change subject to plan limits. A hosted site does not require one just to edit content. Compare the current QREasy plans before choosing a dynamic-code workflow, a higher website limit or a website-linked Wallet pass.
If only the Save Contact details change, edit and save that section instead. The website button will serve the updated details and does not require a replacement static contact QR. Conversely, a static contact QR with embedded details does require a new code when those embedded details change.
Free, EUR 0.00 monthly or annually: one website with up to one page; contact Wallet cards are included, but website-linked Wallet cards are not.
Lite SME, EUR 2.99 monthly or EUR 28.70 annually: website-linked Wallet cards are included, with three websites and up to four pages each.
Business, EUR 9.99 monthly or EUR 95.90 annually: website-linked Wallet cards are included, with 33 websites and up to 10 pages each.
Frequently asked questions
No. A contact QR shares a static vCard for review and optional saving. A website-linked Wallet QR opens the published QREasy site in the phone browser. The website’s Save Contact button remains a separate vCard action.
Yes, if the site stays at the same address. Edit and republish the content, and the existing URL QR can continue to lead to it. Create a replacement only when the encoded URL changes; changing a page’s text or images does not alter the URL.
Use Lite SME or Business for a website-linked Wallet card. The Free plan includes contact Wallet cards but not the website-linked journey. Lite SME and Business include the website-linked option and offer different website and page limits.
No. A website QR opens the site in the browser. A Save Contact button then opens or downloads a vCard, and the visitor confirms whether to save it. Device and browser behavior determines how the file is presented, so saving cannot be promised as automatic.
Get started
Create your website Wallet pass
Publish a QREasy website, then use the Wallet pass tool to create the website-linked pass for Apple Wallet or Google Wallet. If you only need contact sharing, use the free contact-card route instead.
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.