System updates

🐛

🧮

The API endpoints for adding and subtracting a purchase amount on a card now accept decimal values instead of cutting them to whole numbers, and so do the matching AI Assistant tools. Amounts are rounded to two decimal places, with a minimum of 0.01.

📲

For cards added as a web app, the "card installed" webhook, automations and install statistics now fire only once the card is really installed. Before, they could fire too early and report the card as not installed. As a result, web-app install counts may look lower, because they now count only completed installs.

🎟️

Stamp cards set to earn per purchase or per amount can no longer be saved without a stamp count or threshold. That kind of setup made the scanner report success while giving no stamps. Saved cards with such settings were repaired, and location copies of a card now keep their full stamp settings.

🔄

After adding stamps to a stamp card through Spend or Visit, the Scanner app now shows the updated stamp count immediately. Before, the new stamps appeared only after a full page refresh, even though the customer's Wallet card was already updated.

📸

Applying a snapshot whose card templates include happy hours could report success while nothing was created in the sub-account. These snapshots now apply correctly. A snapshot that cannot be applied now returns an error instead of a false success.

🔑

When a sub-account of a white-label agency resets its password, the link in the e-mail now opens the agency's own dashboard domain instead of the default platform domain.

🧩

When creating or updating card templates through API v2, settings sent inside a "settings" block were silently ignored. They are now applied the same way as settings sent at the top level.