# Digital business card and QR

> A QR digital business card for every user — public page, link or offline vCard QR, printable card, e-mail signature, Apple Wallet and Google Wallet, a prospect company or fair lead from the 'Leave your details' form, statistics; scanning other people's QR codes on mobile.

Every user has a **digital business card**. Your customer scans the QR code with their phone camera and your card opens: one tap adds you to their contacts, calls you, writes an e-mail or leaves their own details. Those details land in the CRM as a prospect company (a fair lead during a trade fair) and a task is opened for you.

The card is on **every plan**. On the web: **Settings → My card** (Personal section; the *Business card* row on the Profile page opens it too). In the mobile app (3.7): **Menu → My card** or Profile.

## Publishing and what the card shows {#publish}

Your card is ready, but **nobody can see it until you publish it**. Press **Publish** under **Status**; the status changes to *Published*. **Unpublish** closes the card at once: the link says *This business card is not available*.

The **Details** section:

| Field | Source | Limit |
|---|---|---|
| Full name, e-mail, phone | Taken from **Settings → Profile**; change them there | — |
| Photo | Your profile photo | — |
| Company | Your workspace's name | — |
| Title · Department | Typed on the card | 120 · 80 characters |
| Mobile | Typed on the card | 40 characters |
| Website | Typed on the card; empty = your company's website | 200 characters |
| Address | Typed on the card | 250 characters |
| About | A short introduction | 280 characters |

With the **Show on card** boxes you choose what is visible: photo, title, department, e-mail, phone, mobile, website, address, about. Name and company are always shown; **the address is hidden by default**. A hidden field never reaches the public page, the vCard, the QR code or the Wallet pass.

**Preview** shows the QR code, your name and the card's address (**Copy**, and **Open** when published).

### Public page {#page}

The card's address looks like `https://ornek.solk.app/k/Ab3dEf9hQk`. The page shows:

- photo (initials when there is none), name, title · department, company and its logo;
- **Call** · **Email** · **Add to contacts** (`.vcf` with photo) · **Website** buttons;
- mobile, phone, e-mail, website, address (opens in maps) and about;
- Wallet buttons and the **Leave your details** form (when on).

The page uses your colour palette and opens light or dark following the phone's theme. If the visitor's browser is not in Turkish, labels are in English. It is closed to search engines (`noindex`).

## QR types: link and offline {#qr}

| | Link QR (default) | Offline vCard QR |
|---|---|---|
| What it holds | The card's address | Contact details (vCard 3.0) |
| What the scanner sees | The public page | The *Add contact* screen directly |
| Internet | Needed | Not needed |
| Always current | Yes — changes show on the page at once | No — reprint when details change |
| Form and statistics | Yes | No |

The offline QR has no photo or *About*; an address longer than 80 characters is left out; without a website the card's address is added. The code is denser — print it a little larger.

On the web download it with **Download and share → Offline vCard QR**. On mobile switch with **Link · Offline** above the QR on the My card screen.

## Sharing and downloads {#share}

The **Download and share** section:

- **QR (SVG)** · **QR (PNG)** — the link QR for print and slides.
- **Offline vCard QR** — PNG.
- **vCard (.vcf)** — contact card.
- **Printable card (PDF)** — see below.
- **Apple Wallet** · **Google Wallet** — when Wallet is set up.

QR images and the vCard download only while the card is published; the printable card always.

On mobile: **Share** (the phone's share sheet, sends the card's link), **Add to Apple Wallet** (iPhone) / **Save to Google Wallet** (Android), **Contact card**, **Open page**, **Edit** (title, department, mobile, website, address, about and what the page shows), **Renew link**. The card is kept on the phone, so the screen opens without a connection too.

### Printable card {#print}

An 85 × 55 mm, two-page PDF:

- **Front:** name, title · department, company; mobile, phone, e-mail, website.
- **Back:** the link QR and the card's address.

Give this file to your printer. If you renew the link, the QR on printed cards stops opening.

### E-mail signature {#signature}

The **E-mail signature (HTML)** box holds a ready signature with your QR code: name, title, company, phones, e-mail and a *Digital business card* link. **Copy signature** → paste it as HTML into your e-mail program's signature setting. The QR image loads from your card's address.

### Apple Wallet and Google Wallet {#wallet}

Add your card to your phone's wallet; open it from Wallet and let the other person scan the QR. Visitors can also add your card to their own wallet with **Add to Apple Wallet** / **Add to Google Wallet** on the public page.

- **Contents:** name, title, company, mobile and phone; on the back e-mail, website, address (visible fields only) and the card's link. QR = the card's link. Apple Wallet also shows your photo (when visible).
- **Apple Wallet stays current:** when card details, your profile name, phone or photo change, or when you renew the link, the pass updates itself through an Apple notification. If you unpublish the card, the Wallet pass becomes void and its contact details are removed.
- **Google Wallet** keeps the details from the moment it was saved; it does not update on its own.

Wallet buttons appear only when Solk has set up the Wallet certificates (Solk Panel → App keys → *Apple Wallet and Google Wallet*). Without them no button is shown; the rest of the card works as usual.

## The 'Leave your details' form {#lead-form}

At the bottom of the public page: **Leave your details — *Name* will get back to you.** The visitor enters:

| Field | |
|---|---|
| Full name | required |
| Company | optional |
| Email · Phone | one of them required |
| Note | optional, up to 500 characters |
| KVKK consent box | required |

The consent text says the details are stored by your company only to contact them, and how to ask for deletion: your e-mail shown on the card, the company's e-mail address when yours is hidden, otherwise *the card owner*.

After **Send** the visitor sees a thank-you screen and an **Add to contacts** button. In the CRM:

1. **Company and contact:** a company with the same name or a contact with the same e-mail is reused (no duplicates); otherwise a **prospect company** is created — source *QR kartvizit*, owner the card owner. The contact is added with name, e-mail and phone.
2. **Note:** the visitor's details, note and consent record (date, time, network address) are written to the company.
3. **Task:** for the card owner, due today: **Kartvizitten iletişim: Name (Company)** ("Contact from business card") — type *Arama* (call) when a phone was left, otherwise *E-posta*.
4. **Notification:** *Name (Company) kartvizitinizden bilgi bıraktı* (left their details on your business card) — in the app and, depending on your settings, on your phone.

### During a trade fair {#fair}

If your plan includes [Fair leads](/objects/leads), the admin left **Fair lead during a fair** on and an active fair is running today, the details go to **that fair's lead list** instead of a prospect company: owner the card owner, interest `Ilık` (warm), visitor type `Potansiyel müşteri` (potential customer), next action `Ara` (call) today, note *QR kartvizitten bırakıldı* (left via QR business card). When several fairs run on the same day, the one that started last is used. You can [convert the lead](/objects/leads#convert) later.

### Abuse protection {#lead-limits}

The form carries a hidden trap field, a signed timestamp (at least 2 seconds, at most 2 hours) and a session token. At most 8 forms per hour are accepted from the same network address and at most 60 per card per day.

## Statistics and renewing the link {#stats}

The **Statistics** section shows three numbers — total and last 30 days:

- **Views** — the public page was opened.
- **Saved to contacts** — the `.vcf` was downloaded.
- **Details left** — a form was sent.

The same visitor counts once per 30 minutes for views and once per 10 minutes for saves. Looking at your own card while signed in is not counted. Counters are daily totals; the visitor's identity is not kept.

### Renewing the link {#rotate}

**Link → Renew link → Renew** (you are asked to confirm). A new address and a new QR are created. Old QR codes, printed cards and links in old signatures stop opening. The Apple Wallet pass renews itself. Use it when your card circulates where it shouldn't; then download and reprint the new QR.

## Scanning other people's QR codes (mobile) {#scan}

In mobile app 3.7 [business card reading](/guides/mobile-pro#card) also reads QR codes (**Advanced and Enterprise**):

- **In the photo:** **QR · Aztec · PDF417 · Data Matrix** codes in a business card photo are read on the phone together with the text.
- **Live:** **Menu → Scan business card** or **+ New → Business card** → **Scan QR code**. VisionKit on iPhone, the Google code scanner on Android (the app needs no camera permission).
- **Fair lead form:** **Scan QR** at the top right fills company, contact, title, phone and e-mail from a badge or business card; filled fields are not overwritten (*Filled from badge*).

The decoded text is parsed on the server: **vCard** (2.1 / 3.0 / 4.0), **MECARD**, **BIZCARD**, `tel:`, `mailto:` and **web addresses**. A Solk business card link is read directly (*This business card is not available* when it is unpublished). For another page the server tries the page's vCard link first, then the person data on the page (JSON-LD), then the page text; if it cannot read anything it says *enter the details by hand* and **Open** shows the page. With the live scanner the form opens with *Read from QR code*; matching existing contacts and companies works as for photos.

## Admin settings {#admin}

**Settings → My card → Workspace** (admins only):

| Switch | When off |
|---|---|
| **Digital business cards** | All public pages, QR codes and Wallet passes stop working; users cannot publish their cards and My card is hidden on mobile. |
| **'Leave your details' form** | No form on public pages. |
| **Fair lead during a fair** | Details create a prospect company even while a fair runs. |

All three are on by default. The section shows how many users have a published card. Changes are written to the audit log; the card of a deactivated user closes too.

## Privacy {#privacy}

- The card stays closed until the user publishes it; the user chooses the visible fields and can unpublish or renew the link at any time.
- The public page loads no external resources and has no tracking code or ads; only an essential session cookie is used for form security.
- Counters are daily numbers per card. To avoid counting the same visitor twice, the network address is held only temporarily in server memory and is not written to the database.
- Name, company, e-mail, phone and note from the form are stored in your workspace's CRM; the data controller is the company that owns the workspace. The consent date and network address are kept in the company's note.
- A phone that adds your card to Apple Wallet registers its wallet device identifier and notification token with the workspace so it can receive updates; the registration is deleted when the pass is removed from the wallet.
- The [export](/guides/export#contents) package includes `kartvizitler.csv` and `kartvizit_sayaclari.csv`.

Details: [Privacy policy](https://solk.app/en/privacy.html#business-card).

## API {#api}

Endpoints used by the mobile app: [`GET /card`](/rest-api/workspace/my-card) · [`POST /card`](/rest-api/workspace/my-card-save) · [`POST /card/rotate`](/rest-api/workspace/my-card-rotate). QR contents go to [`POST /cards/parse`](/rest-api/workspace/card-parse) as `qr`. `caps.card` in the `/me` response (business cards on in the workspace).

The public page and its files (`/k/<link>`, `.vcf`, `/qr.svg`, `/qr.png`, `.pkpass`, `/gwallet`, form submission) and the Apple Wallet web service (`/wallet/v1/…`) are not part of the REST API; they need no session and answer only for published cards.