Skip to main content
Go to como.com
Sign in

Releases

Search

Release Notes - Version 26.5.19

Como Sense Knowledge Team

Loyalty & Promotions
Customer-Facing Tools
Multi-Channel Communication
Connectivity
App

 

Loyalty & Promotions

Hub Improvements - Campaigns Table Optimization

Increased the overall width of the main 'Campaigns' table to improve column visibility and prevent text truncation for values.

 

Bug Fixes

  • Fixed an issue where updating the feedback email ("To Mail") saved in Hub 1 but failed to sync to the backend, causing feedback to continue routing to the old address.

  • Configuration screen incorrectly displayed a Login Screen Mobile Background option in the Customer Portal. This unsupported upload field has been hidden from the UI.

 

Customer-Facing Tools

Customer Portal - Support Custom Fonts

We have introduced the ability for merchants to apply their own brand fonts to the Customer Portal, replacing the platform's default font. This allows merchants to maintain visual consistency and align the portal completely with their brand identity.

 

What’s Included

  • Nested Custom Fonts option is now available directly within the Branding settings in the Hub.

  • Dual Font Sources - Searchable Google Fonts library for license-free implementation, or custom file uploads supporting .woff2, .otf, and .ttf formats.

  • Font upload actions are strictly reserved for merchant accounts;
    Como Employee roles are prevented from performing file uploads.

  • Mandatory legal license confirmation checkbox required for all custom file uploads, automatically appending an immutable tracking record to Hub audit logs.

 

How it Works

  • Separate configurations for Heading and Body fonts, allowing independent use of either the Google Fonts library or localized directory file uploads.

  • Selected library fonts automatically pin to the top of the search list for immediate visibility and quick reference.

    Note: Active library font selections must be cleared via the "x Clear" button before the manual file upload option becomes active.

 

Bug Fixes

  • Registration and login accepted malformed email formats (e.g., John.@como.com).
    The email field now strictly validates input inline per RFC 5322 standards before proceeding to OTP.

  • Fixed an issue where logout behaviors varied across different user setups by unifying the logout flow across all platform environments.

 

Multi-channel Communication

[Beta] WhatsApp OTP Support

Overview

We have introduced WhatsApp as a secure One-Time Password (OTP) authentication channel across our mobile apps and Customer Portal registration interfaces. Driven by the Hub 2.0 registration form configuration, this allows merchants to prioritize WhatsApp for verification while keeping SMS and Email as secondary fallbacks.

The service is strictly limited to OTP authentication messages sent via Como's official WhatsApp account.
Future Phases will introduce business-owned WhatsApp accounts, custom templates, and marketing communications.

What’s Included

  • New WhatsApp tab under Hub Communication settings to enable the feature globally.

  • Dedicated config row under Hub Registration settings to set WhatsApp, SMS, or Email as the default login option.

  • Optimized login screen that emphasizes the chosen primary channel while neatly listing alternative methods below it.

  • 30-second "Resend code" throttle on the OTP verification screen, paired with "Didn't receive the code? Try another way" helper to prevent authentication dead-ends.



    Communication Tab - Feature Enablement

     

    Primary Login Channel



    Sign In Options

Verification Code Screen

 

Connectivity

Webhook Throughput Optimization

Set default throughput on the Export Event entity and added a throughput query parameter to webhook URLs to optimize data delivery.
Note: Currently supported on the server-side only via Postman configuration.

RejectPurchase API Parameter

Added an API key parameter returning HTTP 200 OK instead of HTTP 400 for rejected purchases, preventing POS infinite retry loops. (rejectPurchaseResponse200Ok)
Note: Currently configured via Postman; any subsequent changes made within Hub settings will override this Postman configuration.

API Key-Level Wallet Routing

Added support for configuring individual API key wallet properties for granular integration routing control. (payWithBudgetType / UsedByPayment)
Note: Currently configured via Postman; any subsequent changes made within Hub settings will override this Postman configuration.

 

Bug Fixes

  • Fixed an issue where a Sub-Location ID could not be completely removed or cleared once added to a location configuration in the Hub.

 

App

Release Date: 19.05.26

Android Version: 3.0.38 - (minimum Android version supported - 7)

iOS Version: 3.0.38 - (minimum iOS version supported - 14)

Phoenix Version: 3.1.27

  • Minimum binary version Android: 3.0.38

 

New Features

WhatsApp Login & Registration

Introduced a new V2 registration flow allowing users to choose between WhatsApp, SMS, or Email verification, with priority managed via the Hub. Features a 30-second resend throttle and an alternative fallback verification channel.
(More information above)

 

Performance

33% Faster App Launch - Optimized cold start times by loading login, home screen, and launch-time data in parallel, while deferring non-critical background tasks.

 

Bug Fixes

Denying location permissions caused the store locator screen to hang on an infinite loading state. Locations now render immediately regardless of permission status.

Related articles