Skip to main content

Make - Enrol Member to Square POS

Automate customer creation in Square POS from a new loyalty card enrolment

Written by Paul Tomes

Introduction

You can use Make to automatically create a customer in Square whenever a new member enrols in your PassKit Membership or Loyalty program.

This allows you to keep customer records synchronised between PassKit and Square without manually entering customer information into both platforms.

By mapping the member's PassKit ID (pid) to the Reference ID field in Square, you can also identify customers when their PassKit loyalty card is scanned at checkout.

This integration does not require a Square Loyalty subscription.

Before You Start

Before setting up the integration, you will need:

  • A PassKit account with a Membership or Loyalty program.

  • A Square account

  • A Make account.

  • A PassKit enrolment form configured to collect the customer information you want to send to Square

We recommend testing the integration with a test member before making it available to customers.

How It Works

The automation runs whenever a new member is created in PassKit.

  1. A customer completes your PassKit enrolment form.

  2. PassKit creates the member and assigns them a unique PassKit ID (pid).

  3. Make detects the newly created member.

  4. Make sends the member's information to Square.

  5. Square creates a corresponding customer record.

  6. The PassKit ID is stored in the Square customer's Reference ID field.

For example:

PassKit

Square

PassKit ID: abc123456

Reference ID: abc123456

This provides a common identifier between the two platforms.

Step 1: Configure Your PassKit Enrolment Form

Open your Membership program in the PassKit Portal and configure the data collection form.

Include the customer information you want to store in Square.

For example:

  • First Name

  • Last Name

  • Email Address

  • Phone Number

These fields can be mapped to the corresponding customer fields in Square.

[Screenshot: PassKit data collection form showing customer information fields]

Prevent Duplicate Enrolments

To help prevent duplicate members in PassKit, configure External ID Autofill using a unique customer field, such as an email address or phone number.

For example, using Email Address as the External ID prevents another member from being created with the same External ID.

Note: Choose an identifier appropriate for your enrolment process. If you plan to use the separate Square discounts integration, additional External ID mapping is required, as explained below.

Step 2: Set Up the Make Scenario

You can use our preconfigured Make scenario to automatically create Square customers when new PassKit members enrol.

New PassKit Loyalty Card → Create Square Customer – Make Template

To get started:

  1. Open the Make template.

  2. Sign in to your Make account if required.

  3. Create a copy of the scenario in your Make account.

  4. Connect your PassKit account to the PassKit module.

  5. Connect your Square account to the Square module.

  6. Configure the PassKit trigger to watch for newly created members in your Membership or Loyalty program.

  7. Review the customer field mappings.

  8. Save the scenario.

Step 3: Map the Customer Information

In the Square customer creation module, map the information collected during PassKit enrolment to the corresponding Square customer fields.

For example:

PassKit Field

Square Customer Field

First Name

Given Name

Last Name

Family Name

Email Address

Email Address

Phone Number

Phone Number

PassKit ID (pid)

Reference ID

The most important mapping is:

PassKit ID (pid) → Square Customer Reference ID

This allows the customer's PassKit ID to be used as the common identifier between both systems.

Step 4: Test the Automation

Before enabling the scenario for all members, test it using a new PassKit member.

  1. Open your PassKit enrolment form.

  2. Enrol a new test member.

  3. Confirm that the member was created in PassKit.

  4. Run the Make scenario or check that it detects the new member.

  5. Open Square Customer Directory.

  6. Confirm that the corresponding customer was created.

  7. Check that the customer's details were mapped correctly.

  8. Verify that the Square Reference ID matches the member's PassKit ID.

Once the test is successful, enable the scenario to process new enrolments automatically.

Handling Existing Square Customers

If a customer already exists in Square, you should avoid creating another customer record unnecessarily.

Depending on your requirements, you can extend the Make scenario to:

  1. Search Square for an existing customer using an appropriate identifier.

  2. Check whether a matching customer already exists.

  3. Update the existing customer where appropriate.

  4. Create a new customer only if no matching record exists.

This helps prevent duplicate customer records in Square.

Note: The shared scenario should be reviewed to confirm how it handles existing customers. Additional modules or filters may be required if you want to update existing records rather than create new ones.

Using This Integration with Square Discounts

If you also want to award PassKit loyalty points for Square purchases and allow customers to redeem rewards using Square discounts, you can extend the integration using our separate Make scenario.

Integration Square, PassKit – Make Scenario

For that workflow, two identifiers are important:

  • Square Reference ID: Stores the member's PassKit ID (pid) for barcode scanning.

  • PassKit External ID: Stores the corresponding Square Customer ID so Make can identify the correct member when processing Square transactions.

Because Square creates the Customer ID when the customer record is created, your automation must ensure that the Square Customer ID is subsequently stored against the correct PassKit member.

This additional mapping is required for the Square discounts workflow described in the separate article.

Important: Square Loyalty is not required to use PassKit loyalty points with Square discounts. However, the customer identifiers must be configured correctly for the purchase and redemption automations to work.

Troubleshooting

The Customer Isn't Created in Square

Check that:

  • The PassKit member was created successfully.

  • Make detected the new member.

  • Your PassKit and Square connections are active.

  • The Square customer creation module completed successfully.

Customer Information Is Missing in Square

Review the field mappings in the Square customer creation module.

Confirm that the corresponding information was collected during PassKit enrolment.

The Square Reference ID Is Incorrect

Confirm that you mapped the member's PassKit ID (pid), rather than their External ID, to the Square Reference ID field.

Duplicate Customers Are Created in Square

Check whether the customer already exists before creating another Square record.

You may need to add a customer lookup step to your Make scenario.

The Member Cannot Be Found When Processing Square Discounts

If you're using the separate Square discounts integration, confirm that the PassKit member's External ID contains the corresponding Square Customer ID.

This is separate from the PassKit ID stored in Square's Reference ID field.

Important Notes

  • Square Loyalty is not required for this integration.

  • Make automatically creates Square customers when new PassKit members enrol.

  • The PassKit ID should be mapped to the Square customer's Reference ID.

  • The Square Reference ID is used to identify customers when scanning their PassKit card.

  • If a customer already exists in Square, consider updating the existing record rather than creating a duplicate.

  • The Square discounts integration additionally requires the Square Customer ID to be stored as the PassKit External ID.

  • Test the automation before enabling it for all members.

Related Articles
Did this answer your question?