Skip to main content
Go to como.com
Sign in

Releases

Search

Release Notes - 26.2.24

Como Sense Knowledge Team

Connectivity

Agent - Diagnostic Test Mode

We introduced a new diagnostics capability within the Agent interface to help identify environment, connectivity, and integration issues more efficiently.

This enhancement improves troubleshooting for Support and Delivery teams and provides better visibility into the Agent runtime environment across different POS integrations and hosting environments.

 

What’s included

A new Run Diagnostics option is now available within the Agent debug panel, enabling the system to analyze connectivity, environment configuration, and integration status.

Diagnostics are supported when the Agent is embedded in:

  • Web browsers

  • iOS WebView environments

  • Android WebView environments

  • iFrame integrations

 

Diagnostics reporting

At the end of the diagnostics process, a structured diagnostics report is generated that includes:

  • All executed checks

  • Pass or fail results

  • Actionable error descriptions when issues are detected

  • Full environment and platform context

Reports can be sent to the configured support email to assist with investigation and troubleshooting.

Screenshot 2026-02-25 at 11.16.44.png

 

Merge Transaction Flow

We added support for hybrid transactions, where the same purchase is handled across more than one touchpoint, for example POS plus Pay at Table or a payment terminal.

With mergeTransaction, Como can combine inputs from both sources into one complete purchase, so the transaction stays consistent from start to finish.

 

What this Improves

  • More accurate member identification, redemption, and payment tracking when multiple devices are involved.
  • Fewer duplicate or partial transactions in logs and reporting.
  • A single, consistent purchase record for analysis and customer history.

 

How it Works

  1. The POS opens an order and creates the transaction reference.
  2. The customer completes part of the flow on a second device (Pay at Table or payment terminal), which sends its purchase details linked to the same POS order.
  3. The POS later finalizes the order and sends the closing purchase details.
  4. Como merges the information from both sources into one final transaction record and processes it as a single purchase.

 

Where it's Relevant

  • Pay at Table (PAT).
  • In store payment terminals.
  • Any flow where the POS opens the order and another device participates in checkout.

 

Asset Tags Returned in getBenefits API Responses

We improved consistency in how asset tags are returned across benefit-related APIs.
Asset tags are now returned for all benefit types, enabling better mapping between Como promotions and external systems such as POS platforms and reporting tools.

 

What's included

  • Promo Code tags are now returned in API responses.

  • Asset tags are now consistently returned for:

    • Promo Codes
    • Deals
    • Gifts

 

Why it Matters

  • More reliable promotion mapping between Como and external systems.
  • Cleaner reporting and easier reconciliation across platforms.

 

Payment API Enhancement

A new property has been added to payment responses when using mode=query.

 

What’s Included

The response now includes paymentMethod, which can be either:

  1. "meanOfPayment" 
  2. "meanOfPaymentOrDiscount"
  3. "discount".

This allows integrated partners to identify the payment method before executing the final payment action.

 

Bug Fixes

  • Fixed an issue where API key-level wallet overrides incorrectly took precedence over the business-level payment configuration.

 

Customer-Facing Tools

Bug Fixes

 

Hub

  • Fixed an issue where Upload Promo Codes rules could not be saved due to a validation error after uploading a CSV file.

  • Fixed an issue where Franchisee (Access Group) Hub users could view campaign analytics created by HQ users.

 

Customer Portal

  • Fixed an issue where an error message was not displayed on the Purchase Scanner page.

  • Fixed an issue where the App Client ID was not regenerating, causing the same code to appear each time identification was requested.

  • Fixed an issue where Allow Card Linking was not saved correctly when members registered through the Customer Portal or Quick Registration forms.

 

App

Versions

  • Android: 3.0.37 (minimum supported: Android 7)

  • iOS: 3.0.37 (minimum supported: iOS 14)

  • Phoenix: 3.1.19

Improvements

  • We prevented temporary tokens from being generated when the app launches for users who are not logged in.
    • Configuration: Under Custom Params, set skipTokenForGuest to true.
    • Behavior: When this parameter is enabled, the app skips generating a temporary token if the user is not logged in.

Bug Fixes

  • Fixed an issue where the coupon code input field was not visible on Android devices due to keyboard and layout positioning.

     

Related articles