Member Card Template

The Member Card Template allows you to predefine the configuration of membership and loyalty cards to be used on campaigns to help you create images and other user interface elements aligned with your brand. You will be able to customize the Member Card's appearance for both iOS and Android devices.


It consists of a single UI screen with an entry section to the left and a preview screen to its right that will render the Cards contents as you define each element of the template.


Because the template addresses both iOS and Android based devices, some of its elements are device specific, so keep this in mind as you configure the template.

These are the steps.

  1. Enter the Issuer Name. The Issuer Name will
    • identify the Template in the main templates section,
    • appear in the lock screen notification and on the top of the Google Pay Pass.

  2. Enter the Card Title Program Name. The CardTitle Program Name will
    • appear in the top of iOS backside and
    • appear as the Card title in Google Pay Pass

The image below identifies these two areas.


In Design is where you introduce the images related to your card, define the colors for the background, labels and their related values, and which Barcode to use if any. Follow the detailed instructions and recommendations detailed for each element.


Header is an iOS Specific element of the Card setup and it refers to the content that will appear in the top right corner of the iOS version of the card.


It has three variables that need to be defined.
• Type
• Label
• Value

The Type field can either be Generic or Unique.


A Generic type is one that has no expected value and can be whatever you choose, whereas a Unique type has values restricted to the platform defined Fields.

The Label field is what identifies an item in the Card.

The Value field is dependent on the Type selected for this entry. For the Generic Type case, the Value field can be used to establish a different card elements, something that describes the value proposition of the membership offering, but it has no restrictions as what can be entered.

For the Unique type case, the Value field, as we mentioned above, will be restricted to the options offered by the pull-down menu displaying the existing platform fields, this is, the fields that are used throughout the platform to customize other types of campaigns and broadcasts. (See the example below).


This method of introducing data onto the Card template is used throughout the other sections.

Through the Main Fields you can offer the details of the Card offering. It also addresses iOS and Google Pay Passes to best adapt to each card configuration. You have the option of configuring up to three Fields for the Card presentation to cover all the membership information.


For the case of iOS, the Main Fields will be located immediately under the Strip Image, and for the Google Pay Pass, because of its configuration, the Main Fields can be found by scrolling down on the phone screen to uncover them.

Configuring the Main Fields is done the same way as it was done for the iOS Header, having the same elements, characteristics and constraints. The Type can be Generic and Unique, Label identifies the Card items, Value shares the same properties as the case of iOS Header. Below is an example of a fully defined Main Fields section.


Notice that once a card field is defined you have the option to edit it or delete under Actions.

Backside Fields addresses the “reverse side” of the Card. As shown in the template configuration screen, you can configure up to 5 fields.


Again, the configuration of each Field uses the same approach that was used for the other fields above: Type, Label, and Value, with the added twist of ensuring that the data format of the contents of the Generic Type Value be restricted to the format option you select in the Format entry box, whereas before, the Generic Type Value was open to have any value.


The data entered in the Value box must conform to the Format selected from the options shown. These are strictly formatting options and are not to be confused with Subscriber platform Fields. A fully populated Backside Fields section is shown below.


Locations is an iOS-based feature that involves relevant locations for the application of the iOS Card. Define them by configuring the section. It allows you to interact with the cardholder based on his presence in predefined locations. In this section of the template, you can configure the locations of interest. When you expand the Locations sections, you can begin adding locations up to a total of 10.


A card can have up to ten relevant locations. Begin configuring them by selecting Add New Location. The following popup window will appear.


In it, you will be able to pinpoint the relevant location by either
• entering the complete address in the Address box. For example,
Lincoln Center Plaza, New York, NY 10023, United States
• by dragging the pin and searching in the map which can be expanded to full page view through the icon in the top right, or
• providing the coordinates, which requires you to check the Advanced Location Settings box and enter the coordinates in WGS 84 Web Mercator coordinates. For example, Latitude: 40.7725 Longitude: -73.9835.

You can repeat this process until you have reached the 10 locations, if needed.

iBeacons is an Apple’s technology standard, that allows Mobile Apps to listen for beacon signals and have the app react accordingly. It allows Mobile Apps to understand the user's position on a micro-local scale, and deliver content to them based on location using Bluetooth Low Energy technology.

At the very bottom of the of the Content FIelds section you can set up the iBeacons to be detected by your app. Up to 10 iBeacons can be include. For this you will need the UUID for the beacons you wish to detect and optionally, the Major and Minor values if you deemed them necessary, which is dependent on how the beacons are distributed in the area and how they are interrelated.


To start defining the iBeacons,

  • Select the UUID entry and enter the UUID value
  • If required, enter the Major and Minor values in their corresponding boxes
  • Enter the text content that identifies the beacon location in the corresponding box
  • Repeat this process for as many iBeacons you need for your campaign by selecting Add and entering the next corresponding UUIDs, Major, Minor, and Text parameters.

Enter the UUID(s) for the beacons you intend to detect, up to ten, with the corresponding Major and Minor values to ensure you address your iBeacon setup. Only the UUID and Text fields are strictly mandatory, while the Major and Minor values are available to follow the beacon configuration and afford more granularity in the iBeacon detection process given you beacon deployments.

The following figure shows a sample setup for two different beacon deployment strategies that address different beacon density scenarios. One addresses a metropolitan area deployment, on the top, and the other, an in-store scenario.


The entries of the table can be edited or deleted by using the Action icons at the end of each table entry.

To end the template creation Select Save.

You will be taken to the main Templates screen where the template will appear as the last entry in the Member Card Section of the Template matrix.