Loyalty & Promotions

[Beta] AI Filter Members (Currently Available Only for US, England & Australia)

The AI Free Text option within Filter Members allows you to search for members using natural language instead of manually selecting filters.

Simply describe the members you want to find, and AI will interpret your request, apply the appropriate filtering criteria, and return matching members.

This feature helps merchants create audiences more quickly and easily without needing to build complex filter combinations.

Results may take 20-60 seconds to generate, depending on the complexity of the request.

Understanding the results: 

• After a search is completed, AI displays a summary explaining how it interpreted your request (blue outline).
• Review the generated summary to confirm that the search criteria align with your intended audience before using the results.

👉 For more details, check out the Knowledge Article.

Credit Card Linking Consent Management

Introduced compliance-focused controls to securely handle payment-card tokenization consent across multiple onboarding channels, with all permission updates securely logged to the member audit history.

What's New

• Added an "Allow Card Linking" field selection under the Update Member Preferences rule action. This option is strictly restricted to the Joins the Program / External Event Submitted triggers and features a prominent, red legal sensitivity warning.

• Enabled automatic consent mapping through standard registration Terms & Conditions acceptance by default whenever tokenization flags are active.

• Merchants can now add a dedicated, optional "AllowCardLinking" checkbox directly to custom Registration Form layouts or capture consent via a new schema (optional) field in member import files.

• Whenever the field is deployed on the Mobile App or Customer Portal, it automatically displays a system-controlled, multi-language legal description ("I want my payment card to be linked to my account...") that cannot be edited or removed by the merchant.

"Remove Punch Card" Action

Added a new "Remove Punch Card" action for rule flows and one-time actions to automatically remove completed punch cards from a member's account immediately after a reward voucher is issued.

How it Works

When creating a One-Time or a Rule in the Campaign Center:

• Select Remove Benefit from the action dropdown menu.

• Set the type filter to Punch Card (or scroll down to the "Punch Cards" list) and select the specific punch card you wish to remove from the member's view.

Source-Specific Profile Update Triggers

To give merchants greater control over their omnichannel marketing and gamification campaigns, we have added new source-tracking conditions to the Campaign Center.
This update is perfect for businesses running campaigns through external apps or specific channels, such as rewarding points only when a member completes their profile details within a partner app, ensuring rewards are only issued for actions taken in the right place.

What's New

• Source Type & Name Conditions - You can now filter the "Update Membership Details" trigger in the Hub using Source Type (such as POS, API, or Customer Portal) and Source Name (identifying the specific external integration or app).

• Targeted Profile Gamification - Easily combine these source filters with existing profile-field conditions to reward members only when they update specific fields (like birthday or email) through your designated app.

• Intelligent Origin Matching - The Hub will only fire the rule when the profile update matches your configured source criteria, automatically ignoring updates that are missing source information or come from elsewhere.

• Backward Compatibility - All existing campaign rules using the profile update trigger continue to work exactly as they did before without any changes.

 

Export Event Throughput Configuration

Added a configurable throughput input (events per second) to the Export Event action settings, accepting only integer values.

On save, the Hub updates this rate and appends it as a throughput query parameter to the regenerated endpoint URL to regulate outgoing payload rates.

Bug Fixes

• Active recurrent campaigns were mistakenly hidden and grouped under the archived campaigns section, forcing merchants to manually unhide archives to view them.

• UI bug where an erroneous "image upload fail" text tag was mistakenly showing next to the Memoji on all member profile pages.

• Comilia AI text generator restricted SMS outputs to 50 characters instead of 160, while also expanding length constraints for Push and Email channels.

• One-Time Action with A/B testing failed to activate due to a name validation error.
  The failure occurred when the secondary push notification's button configuration was left blank.

• Member activity log displayed timestamps using the Hub user's local time instead of the business's local time.

• Filtering members by a minimum total purchase value incorrectly included members who did not meet the specified monetary threshold.

• Disabled the option to select past dates within the date picker component for existing recurring activities, preventing users from saving dates earlier than the current time or the activity's original start date.

Customer-Facing Tools

[Beta] Custom Brand Layout Support for Mobile Registration

Replaced the generic, plain white registration form on mobile with a fully branded experience that mirrors the merchant's brand identity.

Setup Workflow

• To activate this, enable the New Customer Portal Registration screen toggle (feature flag) under the Customer Portal's General Settings.

• Then, upload an image to the Login Screen Mobile Background slot.

• Once your background image is uploaded, the mobile sign-up page automatically shifts into a modern "frosted glass" look that supports both light and dark modes.

• Uploaded business logos automatically display centered above the sign-up form.
  If no logo is present, the layout auto-adjusts spacing to prevent empty gaps.

• If no mobile background image is uploaded, the page safely defaults to the original registration design layout.

• Changed the bottom text link from "Back to login screen" to "Already a member? Sign In".
  Desktop and tablet layouts remain completely unchanged.

Friend Referral Support for Existing Non-Registered Members (No-T&C Consent)

We have enhanced the friend-referral experience to bridge a critical gap for merchants using Como as a CRM.
Previously, when pre-existing, unregistered CRM profiles, such as customers imported from POS purchases or newsletter signups, tried using a friend’s referral link, they were blocked by "member already exists" errors or redirected without their referral credit.
This update resolves those friction points, enabling a smooth transition from a shadow CRM record to a fully registered, consenting loyalty member who can easily claim their reward.
To round out this experience, we have also migrated legacy email referral pages into the modern Customer Portal and added flexible campaign triggers in the Hub to help easily target and reward these specific signups.

What's New

• Referrals for Pre-Existing Profiles - Customers with unregistered "shadow" profiles can now seamlessly complete their registration using a friend's invite link, instantly unlocking referral benefits as they agree to the Terms & Conditions.

• Auto-Filled Referral Codes - Invite links will automatically pre-fill the referral code field on the CP registration form and profile update pages, saving users from manually copy-pasting codes.

  

• New Campaign Rule Triggers - Merchants can now target and reward members specifically when they transition into fully registered accounts using a referral code, thanks to a new "Used invite code" condition added to the profile update trigger in the Hub.

• Built-In Abuse Prevention - Added smart validation to ensure members can only claim a referral benefit once, protecting duplicate reward exploits.

• Modernized Email Links - Now all email invite links will redirect to the modern Customer Portal, instead of the legacy SSR URL, ensuring a faster, more secure, and consistent layout for users sharing codes.

Streamlined Global Country Code Management

Completely decoupled phone number country codes from portal language settings, allowing merchants to scale their international presence without forcing portal localization changes.

What's New

• Replaced the legacy single "Localization" card layout by splitting it into two visually distinct, independent configuration cards within the Customer Portal's General Settings page.
  • Languages & Display - Focuses entirely on interface localization preferences, retaining the unit of measure choice, currency symbol placement, a flat tag-based portal language selector, and a Default Language picker.
  • Supported Countries Code - Dedicated strictly to allowed dial codes.
    Merchants choose which prefixes are available for phone sign-ups using a searchable checkbox selection that collapses into removable country tags (with flags and dial codes) alongside a clear Default Country Code fallback field.

• The Customer Portal and Mobile app login/registration fields automatically change layout rules depending on selection volume:

  • 1 Country: Displays a fixed, static flag and prefix wrapper with no front-end country picker.

• 2+ Countries: Enables an end-user dropdown menu sorted by an administrative Default Country Code preference.

• All Countries: Unlocks an unrestricted international smart-phone input module.

  

  

• Saving changes in the Phone Number section automatically applies configuration rules across the login portal and registration forms instantly, removing the requirement to perform a second save step on the Hub Registration form page.

Point Shop Visual Enhancements

Improved the end-user visual presentation for point shop items and introduced safeguards to prevent empty catalog pages from being published.

• Optimized Item States - Redesigned item layouts across desktop and mobile to ensure full legibility in both light and dark modes. Enabled states, disabled states (when a member has insufficient points), and point progress bars now render with clean visual contrast.

• Hub-Side Inventory Validation - Added a system-level check on the Customer Portal Hub configuration page. An attempt to save portal changes while the point shop toggle is active but contains zero live items, will trigger a modal that blocks the action.
  The portal changes cannot be saved until items are added or the feature toggle is turned off.

• Customer-Facing Empty State - Implemented a new empty state screen on the portal and mobile app that displays a clear message when there are no active gifts available, replacing the previous blank page rendering.

Consolidated Tokenization Settings

Streamlined tokenization configuration within the Hub by grouping independent toggles under a centralized management section.

What's New

• Added an "Enable All Payment Token Features" master toggle under the API Keys tab.
  Activating it automatically enables all child sub-settings by default to simplify setup.

• Merchants can still independently manage individual payment token settings ("Allow Payment Token Collection", "Allow Payment Token Linking for Loyalty Identification", and "Show Card Link Status) after the master toggle is turned on.

• Removed the redundant tokenization setting from the Features & Add-ons → Data view.
  This backend data flag is now handled completely behind the scenes and automatically triggers whenever any individual token feature is activated under an API key.

Global Payments Theme

Added a Use Global Payment Colors switch under Features & Add-ons that instantly reskins the entire Hub user interface.
Once activated, it automatically updates all background colors, navigation states, borders, and typography to align with Global Payments corporate branding.

Bug Fixes

• Fixed a UI bug where fields mirrored each other's icons when the card activation option was enabled.

Multi-channel Communication

[Beta] WhatsApp Merchant-Owned Account Configuration 

We have expanded the Loyalty Server to support merchant-owned WhatsApp Business Accounts (WABA) for sending One-Time Password (OTP) verification codes.
The backend now integrates directly with Meta APIs to securely validate merchant credentials in real time and dynamically retrieve approved message templates.
This update transitions our WhatsApp authentication from a purely Como-managed service into a flexible infrastructure that allows the merchants to easily connect, verify, and run security codes through their brand's own WhatsApp account.

What's New

How to Configure

• Switch on WhatsApp OTP with a master toggle and choose between using Como’s Account (requiring zero setup) or My Own Account via mutually exclusive routing cards.

• When using the business own WABA, the setup cleanly separates credentials, template selection, and testing. Downstream configuration steps (Steps 2 & 3) remain locked and greyed out until the previous steps are validated to prevent setup errors.

• Input the business custom Access Token, Phone ID, and WABA ID into the required fields and click Connect to validate credentials.

• A green "Connected successfully" banner will display upon success.

  • This triggers a real-time call to the Loyalty Server to verify the business WhatsApp Access Token, Phone ID, and WABA ID.
    On-screen errors immediately guide you if any information is incorrect, and your Access Token is securely masked showing only the last 4 characters after entry.

• Select your template from the options automatically retrieved by the Loyalty Server from the Meta account via API, filtering only for approved templates that contain a Copy Code Button.

• After saving the template selection, Step 3 unlocks to let the user enter a mobile number and click Send Test OTP to verify message delivery safely before fully deploying the configuration to the customers.

Connectivity

Credit Card Linking Consent Management

• Flexible Consent Capture - Added support for credit card linking consent across multiple onboarding paths, setting Terms & Conditions acceptance as the default mechanism while allowing businesses to enable an optional explicit registration checkbox or provide consent states via member import files.

• Strict Rule-Based Consent Update - Introduced backend validation for the Allow Card Linking rule preference action, restricting its execution strictly to the Joins the Program trigger to prevent unauthorized consent changes from other event sources or direct API calls.

• Migration Paths & Auditing - Established a transition framework for existing businesses to either acknowledge consent for current members or require a new opt-in, with all consent changes, sources, and actions fully tracked in the member's audit history.

Member Update API Referral Code Support

• Referral Code Integration: Enhanced the v4/advanced/updateMember API to accept a referralCode field in the request payload, enabling seamless friend-referral flows for pre-existing, non-consented members who transition to fully registered profiles.

• Fraud Prevention Safeguards: Added server-side validation to check if the updating member has previously received a friend-referral benefit; if a prior benefit is detected, the profile updates normally but the system blocks the distribution of duplicate referral rewards.

• Referral Rule Execution: Ensures that eligible, first-time referral recipients trigger the corresponding program-joining campaigns and reward rules upon a successful profile update.

API Phone Number Normalization (Country Code Enhancement)

• Automated Input Sanitization - Implemented a server-side normalization layer that automatically strips special formatting, such as spaces, dashes, and parentheses, from phone number inputs before they reach the Loyalty API.
• Configurable Country Code Rules - Added API Key-level configurations to dynamically add or remove specific country codes based on integration requirements, ensuring consistent member matching and preventing duplicate profiles for multi-country businesses.

Quick Registration Additional Identifiers

Automated MemberID Generation

10DLC Support for Canada

Bug Fixes

• Quick registration API failed to validate identifier fields, allowing the creation of duplicate member profiles with empty or missing values instead of rejecting them with a validation error.

App

Versions

• Android: 3.0.40 (minimum supported: Android 7)

• iOS: 3.0.40 (minimum supported: iOS 14)

• Phoenix: 3.1.31

  • Minimum binary version android: 3.0.40
  • Minimum binary version android: 3.0.40
     

Improvements

Unified Mobile Country Code Selector

• Consistent Registration Experience - Implemented a unified country code selector across mobile platforms to establish complete visual and functional consistency with the customer portal.

• Multi-Country Support & Backward Compatibility - Ensures seamless login and registration flows for multi-country merchants without breaking any legacy mobile configurations.

Web View Navigation, Inbox Badges, & Deep-Link Domains

• Advanced Web View Control via Query Parameters - Introduced four new configuration parameters to customize the behavior of the in-app browser dynamically:

• useGlassNavigation - Relocates browser back/forward controls to the top header as circular buttons with a modern glass-effect background, replacing the legacy close/back button.

• showBottomNavBar - Determines whether to keep the app's global bottom navigation bar visible within the web view.

• allowGesture - Enables native iOS swipe-to-navigate gestures to flip forward and backward through browser history (Available on iOS only).

• comoIosSwipeEnabled - Allows users to swipe back to the native app from the web view when they reach the end of their browser history.

• Inbox Unread Counter Badge - Added a visual unread message badge to the inbox icon.
  The badge colors are mapped to the mobile app’s existing color scheme.

• Multiple Deep-Link Domains - Expanded deep-linking capabilities to support mapping and resolving multiple custom domains, allowing various promotional and regional domains to route users seamlessly into the app.

⚠️  Note: Requires App resubmission ⚠️

Data

Access Group Data Filtering

Integrated advanced access control logic across all Data Explorer explores to restrict data visibility based on user permissions.
When the Access Group feature is enabled, member data and analytical reports are dynamically filtered to match the exact access or location group tags assigned to the active user profile.

Promo Code Analytics in Data Explorer