formify-e-sign/formify-skills / plugins/formify-es-real-estate/skills/formify-es-real-estate
formify-es-real-estate
VerifiedES Real Estate Formify: the six documents a Spanish estate agency signs most (nota de encargo, KYC comprador y vendedor, oferta y reserva, contrato de arras, colaboración entre agencias, entrega de llaves), bilingual Spanish plus the client language, region-correct, signed through Formify. Use for a Spanish property sale or letting: encargo, mandato, reserva, arras, señal, KYC, blanqueo, llaves. Every run starts with scripts/start.py, which prints the welcome lines.
references/tink-attributes.md
View on GitHub<!-- generated from core/references/tink-attributes.md by build_vertical.py; edit the core file, not this copy -->
<!-- Mirrored from formify-e-sign/formify-skills shared/references/tink-attributes.md (commit d7cc486, 2026-09-10) by the segment factory. Never edit here: refresh from the developer's repository at each master release. -->
# `tink-*` field attributes — the complete catalogue
Open this file whenever a PDF needs a Formify feature inside a field: an ID scan, a company
lookup, a one-time code, an attachment upload, or an auto-filled value.
## How a Formify field is configured
A Formify widget is configured entirely through its AcroForm field name (`/T`). Everything
before the first `|` is the human-readable label. Each `|`-separated segment after it is a
`tink-*` attribute.
```
firstname|tink-scanned-id-mrz-firstname[1]
photo|tink-scan-id[1]|tink-scanned-id-portrait[1]
scan|tink-scan-id[1]|tink-scanned-id-allow-in-signature[1]
```
**The catalogue below is closed.** An attribute that is not in it is not rejected — it is
silently ignored, or it locks the field read-only and never fills it. There is no error
message anywhere. Inventing a plausible-sounding attribute produces a PDF that opens
perfectly and quietly does nothing.
Three attributes that people invent and that **do not exist**: `tink-format-date`,
`tink-scanned-id-mrz-gender`, `tink-verified-orgnumber-ceo`. A date field takes a plain
name and no attribute at all.
## The index in brackets
`tink-scan-id[1]` is correct. `tink-scan-id1` is not — without brackets the index is
ignored and the fields are never linked to each other.
The index groups everything belonging to **one person**. Three signers means `[1]`, `[2]`,
`[3]`, each with its own trigger and its own capture fields. The index is a property of the
person's position in the document, so inserting a second applicant above the first
renumbers everything below.
---
## Company verification
| Attribute | What it does |
|---|---|
| `tink-orgnumber-verification[index]` | Verifies the beneficial owner through Swedish BankID |
| `tink-orgnumber-verification-boardmember[index]` | Verifies a board member |
| `tink-orgnumber-verification-kyc[index]` | KYC variant; the result is stored for compliance |
**A trigger on its own is a dead button.** Each of the three must be combined, in the same
field name, with `tink-verified-orgnumber[index]` or
`tink-verified-orgnumber-companyname[index]`. Without that pairing the field never becomes
clickable.
Auto-filled company data, all indexed: `tink-verified-orgnumber`,
`tink-verified-orgnumber-companyname`, `tink-verified-orgnumber-addressline1`,
`tink-verified-orgnumber-zipCode` (note the capital `C`), `tink-verified-orgnumber-city`.
## ID document scanning
Four triggers, no others:
| Attribute | Document |
|---|---|
| `tink-scan-id[index]` | ID card, full validation |
| `tink-scan-id-basic[index]` | ID card, partial validation, less strict |
| `tink-scan-id-passport[index]` | Passport, full validation |
| `tink-scan-id-passport-basic[index]` | Passport, partial validation |
**There is no driving-licence trigger.** A driving licence is scanned with `tink-scan-id`.
**One trigger per person, ever.** Putting the scan trigger on each capture field produces
one scan button per field — a real document once shipped three buttons for one passport,
and the signer is asked to scan the same document again for each.
### What the trigger field itself becomes
| Combination | Result |
|---|---|
| Trigger alone | The field is **replaced by the front-side image** of the document. Draw it landscape, about 3:2, and generously sized. |
| Trigger + `tink-scanned-id-portrait[index]` | The portrait replaces the front-side image. Shape 3:4 upright. |
| Trigger + any `tink-scanned-id-mrz-*[index]` | **No image at all.** The field receives that value as text. |
| Trigger + `tink-scanned-id-allow-in-signature[index]` | The scan is reused for a Live ID signature — see below. |
The third row is the **data-minimisation pattern**, and it carries legal weight:
reproducing a copy of an identity document requires its own legal basis. When the user
needs the data but not the picture, combine the trigger with the MRZ attributes and no
image is stored.
### Text captured from the machine-readable zone
All `tink-scanned-id-mrz-<name>[index]`, all auto-filled:
`firstname` · `lastname` · `personalnumber` · `documentid` · `nationality` ·
`nationalitycode` · `birthdate` · `expirydate` · `issuedate` · `issuingstatecode` ·
`issuingstatename` · `placeofbirth` · `placeofissue`
There is no `gender`.
### Images captured from the document
| Attribute | Shape | Note |
|---|---|---|
| `tink-scanned-id-portrait[index]` | 3:4 upright | Strict — the scan **fails** if the portrait cannot be extracted |
| `tink-scanned-id-ghostportrait[index]` | 3:4 upright | Field is removed if absent |
| `tink-scanned-id-signature[index]` | 4:1 wide and low | Field is removed if absent |
| `tink-scanned-id-documentrear[index]` | 3:2 landscape | Field is removed if absent |
| `tink-scanned-id-barcode[index]` | 4:1 wide and low | Field is removed if absent |
**A captured image is stretched to fill the field rectangle exactly.** It is not fitted and
not letterboxed. A 3:4 portrait dropped into a full-width single-line box renders as a face
smeared across the page. Give every image field the shape in the table.
When several image attributes are combined on one field, the last one wins.
### Reusing a scan for the face check
`tink-scanned-id-allow-in-signature[index]` is a modifier. Combine it on the scan trigger
and a **fully successful** scan is carried into a Live ID signature: the signer goes
straight to the biometric face check without photographing their document a second time.
The face check itself always runs.
An incomplete scan is never reusable, even with the `-basic` triggers. The `[index]` here
is the scan group — it has no connection to any signature index.
## Attachments from the signer
`tink-upload-attachment[index]` opens the upload dialog. Pair it with
`tink-uploaded-attachmentname[index]`, usually carrying `tink-style-transparent`, or the
uploaded file's name appears nowhere in the document.
## One-time code verification
`tink-email-verification` and `tink-sms-verification`. **Neither takes an index.**
## Formatting and presentation
`tink-format-mobile` (Swedish mobile format) · `tink-format-email` ·
`tink-style-transparent` (draws no chrome). None take an index.
Do not put `tink-style-transparent` on a field that nothing fills. It draws nothing and
stays empty, which is a blank space no one can explain.
## Everything else
| Attribute | What it does |
|---|---|
| `tink-date-now` | Auto-fills the signing date, ISO 8601 |
| `tink-input-fullname` | The signer's full name |
| `tink-email-recipient` | The recipient's email |
| `tink-sign-and-pay-email[index]` | The only indexed attribute that is not part of a scan group |
| `tink-search-{label}` / `tink-search-firstname` / `tink-search-lastname` | Lookup field; `{label}` is the one customisable part of this entire catalogue |
| `tink-share-sms-phonenumber` / `tink-share-email-emailaddress` | Prefills a public-sharing recipient. **This does not send an invitation** — invitations are configured when the document is sent, not in a field. |
| `tink-access-document` | Document access action |
---
## Rules that produce a broken document silently
Each of these yields a PDF that opens correctly in every viewer and fails only in Formify,
or only when a signer reaches it.
1. **Brackets are mandatory.** `tink-scan-id1` is not an index; the fields never link.
2. **Two fields with the same name are one field to Formify.** Two boxes both named `Date`
fill from a single keystroke. Every field name must be unique across the document.
3. **Set the read-only flag on the widget itself** for every trigger and every captured
value. Sixteen attributes in this catalogue are marked as forbidding manual entry. A
scan trigger without the flag is an ordinary text box with a long name: the signer
clicks in and types, and what should have been a scan button never reads as a control.
4. **A signature is never a form field.** Formify's signing overlay is painted in that
zone; a widget or a printed line collides with it. Leave the space empty and let the
signing configuration place the signature.
5. **A radio option containing `/` corrupts the file.** The export value becomes a PDF name
object and `/` terminates it — a bilingual option like `Nej / No` once produced a file
no reader could parse. Use a dash in the stored value; the visible label can keep the
slash.
6. **What a signer types is limited to the WinAnsi character set.** `š ž å ä ö é` are fine;
`č ć đ ł ř` are not. Page text has no such limit — this applies to values typed into a
widget.
7. **A field cannot carry a pre-set value through an attribute.** There is no pre-fill
attribute in this catalogue. An agreed amount belongs in printed text; writing it into a
label renames the field for every downstream integration.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |