Choosing a Google Wallet business card is easier when you separate three user goals: save contact details, open a website, or share a QR that contains contact data. QREasy supports each workflow, but through different interfaces. The same contact information can therefore be presented as a Contact Wallet card, a static vCard QR code, or a vCard button inside a hosted website without making them equivalent.
The practical question is what the recipient should do after scanning or activating a link. If the answer is “Add to Google Wallet and review my details,” use the Contact Wallet card. If it is “open the company website,” use a website-linked Wallet card. If the goal is a simple, camera-based contact exchange, use the separate vCard QR generator instead.
Key takeaways
Contact Wallet cards and website-linked Wallet cards create different recipient journeys and must not be described as the same type of 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.
A static vCard QR embeds contact data, so changing any embedded detail requires generating a replacement code
A website Save Contact button opens or downloads a vCard from its saved section; visitors do not need to scan another QR
A static URL QR can point to changing content at the same address, while a dynamic redirect is used when the destination itself may move within plan limits
Choose the Wallet journey: contact or website
QREasy’s digital business card creator supports both Contact Wallet cards and website-linked Wallet cards for Google Wallet and Apple Wallet. The distinction is the recipient’s next action: review and save contact details, or open a QREasy-hosted website. The formats can use similar contact information, but their QR destinations and supported journeys are different.
Choose a Contact Wallet card when the QR should share contact data. Choose a website-linked Wallet card when the QR should encode the site address. In the latter case, scanning opens the website in the phone’s browser, not inside Google Wallet. Google Wallet also offers a Visit Page link on the card. There is no mandatory card-review step before the website opens.
Contact Wallet card: free to use; shares contact data through a review-and-save journey.
Website-linked Wallet card: requires Lite SME or Business; its QR opens the website in a browser.
Only a website-linked Wallet card QR opens a website directly; a Contact Wallet card QR shares contact data instead.
Prepare and share a Contact Wallet card
Create the card in QREasy and review the displayed details before sharing its QR. For a contact card, the code shares contact data and takes the recipient into a compatible Wallet app, where the details can be reviewed and saved. Saving still depends on the recipient’s confirmation.
Wallet generation processes data on servers. Users should therefore apply their own approval and data-handling procedures before publishing a card, especially when the same details are used elsewhere. The stated functionality does not include automatic contact saving, NFC tap exchange, CRM synchronization, or identification of a particular contact.
Check every contact detail displayed in the card before distribution.
Test the intended recipient path on the devices your audience is likely to use.
Label the QR as a contact card and avoid promising automatic or one-step saving.
Keep a separate non-Wallet contact option for recipients who cannot use the Wallet journey.
Scan this code with your phone camera to open the QREasy digital business card page.
Use a static vCard QR for camera-based saving
The separate vCard QR generator is not a Wallet card. Its basic contact QR is generated in the browser and embeds the contact details directly in the code. A compatible phone camera or QR reader can present those details for review, after which the recipient chooses whether to save the contact. This data-embedded code does not open a QREasy website.
Because the details are embedded, editing them does not alter an existing QR. Generate a replacement whenever any embedded contact detail changes, then update the printed or digital placement. Do not rely on a website edit to update a static vCard that has already been shared.
Use this format when the main goal is a direct contact exchange without requiring a Wallet card.
Add visible wording that tells visitors to scan, review, and save the contact.
Retire old printed codes after publishing a replacement.
Add Save Contact to a hosted website
QREasy hosts editable small websites built from templates and supported sections for text, images, services, contact details, and links. Start with the website templates, publish the site, and use its Save Contact section as a separate contact-delivery interface.
When a visitor activates Save Contact, the browser downloads or opens a vCard file using the details saved in that section. The visitor does not scan the page with the camera. Device and browser handling, plus the visitor’s confirmation, determine whether the contact is saved. Editing and saving the section updates the file served by the button without requiring a replacement static contact QR.
The button, standalone contact-QR generator, and Wallet card should therefore be described separately. The button acts on the website; the generator creates an embedded static code; the Wallet card creates a Wallet journey. Website access requires an internet connection, while the saved contact file is handled by the visitor’s device.
Treat the website section as the source for the button’s vCard details.
Test the download and open behavior in the browsers used by your audience.
Describe the action as saving a contact rather than opening a Wallet card.
Keep static URL and dynamic redirects distinct
QREasy’s QR code generators support different destinations, and a static URL QR should not be confused with a static vCard QR. A static URL QR contains a fixed address. The webpage or PDF served at that same address can be replaced without changing or reprinting the code. Only changing the encoded URL requires a new static QR.
A dynamic QR uses a managed redirect, so its destination can change without reprinting, subject to plan limits. A hosted website does not need a dynamic QR merely because its content was edited: the existing address can show the update. Neither static nor dynamic coding guarantees scanning on every device, so test with the intended audience and keep the destination clear.
Static URL: keep the code fixed while replacing the content at the same address.
Dynamic redirect: keep the code fixed while moving its destination within plan limits.
Static vCard: keep the contact data embedded in the code and replace it after edits.
Match the plan and update method
Review the QREasy plans and pricing before publishing. Free includes one website with up to one page, one dynamic QR code, unlimited static QR codes, seven days of analytics history, and Contact Wallet cards. It costs EUR 0.00 monthly or annually. Website-linked Wallet cards require Lite SME or Business.
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, at EUR 2.99 monthly or EUR 28.70 annually. Business includes 33 websites with up to ten pages each, 357 dynamic QR codes, unlimited static QR codes, and 90 days of analytics history, at EUR 9.99 monthly or EUR 95.90 annually. Both include website-linked Wallet cards.
Match the workflow to the number of sites and redirect destinations you need. Then document the update path: static vCard data requires a new code, the website button follows its saved section, hosted content can change at the same URL, and a dynamic redirect can move within plan limits. Test the exact path you publish; do not promise automatic saving, a fixed number of taps, or a guaranteed time to complete an introduction.
Free supports a Contact Wallet card and a one-page website.
Lite SME and Business are required for website-linked Wallet cards.
Compare dynamic-code limits whenever destinations may need to move.
Frequently asked questions
No. A Contact Wallet card QR shares contact data. A website-linked Wallet card QR encodes the website URL and opens it in the phone browser; Google Wallet also provides the Visit Page link on the card.
No. A static vCard QR embeds the contact details, so any embedded change requires a replacement code. This differs from the website Save Contact button, which uses the details saved in its website section.
No. It is a button that downloads or opens a vCard file using the saved section details. The visitor does not scan the page, and device or browser handling plus the visitor’s confirmation determine whether the contact is saved.
No. A static URL QR can keep the same code while content at its fixed address is replaced. Use a dynamic redirect when the destination itself must change under the same code, subject to plan limits.
Get started
Create a contact QR
Open the free vCard QR generator, review the embedded contact details, test the code on a compatible phone, and publish a new code whenever those details change.
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.