Launched a marketplace section in the integrations area, allowing users to publish their own apps for future integrations.

Resolved the issue where duplicate cards were created when cloning a template from the head office to branches.

Fixed an error where a "share card" link appeared after a customer left a review, even when the referral program was disabled.

Added the ability for customers to update their phone number via their personal account under the "Information" tab in their profile.

In the template constructor, added an option to disable the "Install PWA Card" button on the card issuance form.

Corrected visit tracking on multipass cards. Previously, visits beyond the stamp limit were not counted. Now, the maximum number of active visits will be displayed as long as the available visits exceed the number of stamps shown on the card.

Added the ability to set up autopush notifications for inactive card templates.

Addressed an issue where membership tiers couldn't be deleted properly.

Fixed a bug where, during card restoration, if the customer changed their email, they would incorrectly receive a code request for restoration.

Implemented a series of visual improvements throughout the system for better user experience.

Previously, after redeeming a coupon and transforming it into another card, those cards were not counted in the coupon statistics. This issue has been resolved.

Fixed a bug where it was possible to reinstall a coupon if the previous one was redeemed with the status "not installed."

Now, the purchase amount of a guest customer is included in the revenue of the branch where the visit occurred.

Resolved an issue where the text below the barcode was not displayed for subaccounts.

It is now possible to navigate to the sub-account profile directly from the payments page in the "Agency" section (/agency/payments).

Resolved an issue where a card template would become unlinked from a branch when edited in the main (head) account.

Scheduled push notifications can now be deleted before their sending time. A delete button has been added above each scheduled notification in the push history section.

It's now possible to install cards in Telegram by creating your own chat bot. This bot can be connected as an external service for installing cards, sending push notifications, campaigns, and chatting with cardholders.

Added the ability to send notifications to sub-accounts through the GHL integration in the "Customize notifications" section.

The default logo, which previously appeared on cards in AW when a sub-account was created through prospecting and a snapshot was applied, has been removed.

The number of transactions that can be exported per card has been increased to 200,000. Previously, large export files would cause download errors. Additionally, a block has been added to prevent starting a new export while another report is still being downloaded.

When a company is deleted, its Stripe subscription is automatically canceled. Similarly, if a sub-account is deleted, the subscription is canceled. For agencies or franchise deletions, all associated subscriptions (for sub-accounts/branches) and plans are also canceled.

Reworked the connections between companies and customers to optimize the loading of statistics. Data now loads faster, even for companies with a large customer base.

Fixed an issue where membership subscriptions weren't renewing after reconnecting Stripe.

The "Terms of Use" for membership cards have been updated to comply with requirements and now include company data. For membership v.1, the text remains unchanged.

Fixed an issue where previously deleted customers were reissued old cards. Now, when a new card is issued to deleted customers, it installs correctly (both via general and individual links), and the old customers are not restored.

Adjusted the display of renewal and expiration dates on membership cards based on their type:

Cards without tiers but with periods (Membership v.1): Only the expiration date is displayed.

Cards with tiers and periods: Both the renewal date of limits and the expiration date are displayed.

Resolved the issue where network cards were duplicated in branches when cloning a card from the Head Office (HQ).

Fixed the problem where custom reward settings were not retained when cloning a card from the HQ to branches. Previously, cards copied to branches used default branch settings instead.

Added a "Purchase Amount" column to the export tables for transactions by template and by customer.

Corrected an error that occurred when a manager attempted to send a push message with editing access enabled.

The "Name" field on the background image of the membership card is now synchronized with the language selected in the template settings. Previously, it was always displayed in English.

A checkbox "Enable Membership v.1" has been added to the template constructor. This option appears when "Collect payments - NO" is selected. When enabled, tiers and limits are not displayed in the scanner or on the front side of cards, and visits are tracked but not deducted. User profiles on the dashboard will still show widgets with tiers and limits, including the reverse side of cards in Apple Wallet (AW) and Google Wallet (GW). This display issue will be addressed.

Added the ability to deduct visits directly through the dashboard.

Fixed the issue where the visit count in the "Limits" widget remained unchanged after visits were deducted.

Corrected the issue where the card name overlapped with the renewal date on the front side of the card.

On cards with an unlimited tier, the visit count now correctly displays as unlimited.

Implemented push notifications for subscription changes or renewals, ensuring that the card is updated with the latest limits.

Added the option to set an expiration date for cards without auto-renewal.

Made several visual enhancements in the template constructor for better usability.

Fixed a bug where, after deleting a template associated with a coupon, all information would disappear from the customer's profile upon coupon redemption. Additionally, the customer was removed from the coupon statistics.

Resolved an issue for AppSumo sub-accounts with white-label (WL) branding where the Boomerang logo would reappear after removing the custom branding logo.

Fixed an error where managers with granted permissions encountered access issues when navigating to the prospecting section.

Optimized the loading of the transaction table in the franchise branch profile, addressing a previous issue where the table failed to load.

Adjusted the customer search functionality in the franchise network scanner. Previously, customers from any branch could be found across the network. Now, only customers with network cards whose templates are available in the current branch can be located.

Refactored the synchronization process for customers during integrations to improve performance and reliability.

Added the display of transaction amounts (for ROI purposes) in the user profile page, enhancing the transparency and utility of transaction data.

Fixed an issue where custom fields in the card issuance form were empty when a user restored a card, despite being filled in during the initial issuance.

Resolved a bug where custom and exported snapshots were not being applied correctly.

Implemented measures to prevent the creation of duplicate customers across the network. If a customer already exists in one branch, they cannot be manually added or imported into another branch.

Added visibility of guest customers in the context of the network card. Guest customers are now included not only in the general list but also in client base statistics and transaction records.

Added information about the number of available visits and the membership tier in the get card method.

Updated the get template method to include details about all template types.

The aforementioned information has also been included in the webhooks for card issuance, installation, scanning, and balance updates.

Both the head office and branches can now see customers who have made transactions at a particular branch, even if the card was issued by another branch.

Adjustments to rewards or points can be made directly within the customer's profile, regardless of where the card was issued.

If a customer visits a different branch, push notifications can be sent from that branch using the customer’s profile.

When sending push notifications using a card template, recipients will include customers who have cards issued by other branches but have visited the current branch at least once.

When creating a network membership card with payment collection enabled, the Stripe settings will be copied to all branches.

Fixed an issue where limits were not updating when the subscription was renewed. Now, both the period and card limits are updated correctly upon renewal.

Subscription updates (both period and limits) now take effect from the start of the day.

If there are daily visit limits or branch-specific visit limits set in the template, these limits will also reset and update from the beginning of the next day.