Personalisation

Personalisation

Additional properties personalise your passes. You define the fields that change for each holder, then use them anywhere on the pass as placeholders. When you create a pass, Passcreator asks for those values and fills the placeholders with the real data.

You do not have to show a property to the holder. You can also store data you need behind the scenes, for example a contact number from your CRM that you later search by.

Create an additional property

Open your template, go to the Personalization section, and add a field. Give it a name and a type. The name becomes the placeholder you use elsewhere on the template.

The Personalization section with custom fields added

Additional properties also drive email and SMS sendouts. Those fields hold the email address or phone number of each holder.

Use a property as a placeholder

Create a property named Name and you reference it anywhere with {Name}. Passcreator swaps in the real value when the pass is created.

Placeholder functions

Two helper functions extend what placeholders can do.

urlencode

Wrap a placeholder in {urlencode({yourPlaceholder})} to convert it into a form that is safe inside a URL.

For example, to put a first and last name into a link inside your QR code, use https://yourdomain.de/?name={urlencode({firstName} {lastName})}.

sign

Wrap a placeholder in {sign({yourPlaceholder})} to create a signature of the value. You use this to protect data from tampering.

How tamper protection works

Signing proves that a value came from you and that nobody changed it on the way.

When Passcreator signs the data, it creates a hash of the value with a cryptographic hash function. Even a tiny change to the value produces a different hash. Passcreator then encrypts that hash with a private key, which gives you the signature. The pass carries both the data and the signature.

On your side you verify it. You decrypt the signature with the matching public key to recover the original hash. You can fetch the public key through the API. You then hash the received data yourself with the same function. If your hash matches the decrypted hash, the data is authentic and untouched. If the two hashes differ, someone changed the data.

    • Related Articles

    • Additional Property as User Provided ID

      You can build the User Provided ID of a pass from your additional properties. You define a pattern, and Passcreator fills it with the values of those properties when it creates the pass. Define the pattern The pattern can mix plain text and ...
    • Create a digital business card using a Wallet pass

      You can build a digital business card as a Wallet pass. The card holds the person details, and a QR code shares them as a vCard that a phone reads into contacts. This guide walks through the template. Create the template Create a new template and ...
    • Display a field only if it matches a condition

      You can show or hide a field on a pass based on a condition. You write the condition with the syntax below, and Passcreator checks it when it creates or updates the pass. Where to add a condition Edit the field in the template editor and open ...
    • Welcome to Passcreator, core concepts

      Passcreator lets you create, distribute, manage and analyse digital Wallet passes for Apple Wallet, Google Wallet and Samsung Wallet, without writing any code. Before you build anything, learn the four words you'll see everywhere in the interface. ...
    • Differences between Google Wallet and Apple Wallet

      Apple Wallet and Google Wallet both hold passes, but they behave differently. Knowing the differences helps you design passes that work well on both. Adoption Apple Wallet is built into every iPhone. Google Wallet is not pre installed on most Android ...