Tamaro v2.16.x
This release strengthens security (optional HMAC signing and tighter Stripe/third-party checks), smooths moving subscriptions from Manager to Hub (keeps charge date), and fixes key issues—Stripe not loading, one-click payments not sending details and legacy methods not showing for recurring.
If you are using an earlier version of Tamaro, request an upgrade through RaiseNow support to get the new options outlined below. All Tamaro Versions 2.16 will automatically be upgraded to the latest version specified here. Hub forms will be updated automatically.
Tamaro v2.16.4
Fixed a regression introduced in v2.14.0 that caused legacy payment methods not to load when a recurring interval was selected and the allowedRecurringPaymentMethods option was used.
Tamaro v2.16.3
Fixed an issue where create_payment_source and create_supporter_fields was not sent to EPMS when the option oneClickPayment was enabled. The option to enable increased security for Stripe was introduced.
Tamaro v2.16.2
Fixed a regression introduced in v2.16.0, which caused Stripe JS SDK to not load/initialize.
Tamaro v2.16.1
We made some internal improvements to the code and introduced increased security measures.
Tamaro v2.16.0
This version brings several improvements like an improved subscription flow and enhanced security through HMAC as well as important fixes under the hood.
Improved subscription update flow for switching from RaiseNow Manager to RaiseNow Hub
When a supporter updates their subscription made in the legacy system (Manager) to the new system (Hub), the existing subscription's charge date and purpuse will be preserved.
General improvements and bugfixes
- We've added a security check for 3rd party libraries to automatically scan and detect vulnerabilities.
- Smoother Datatrans payments through secure field handling.
- Resolved a bug where the loading spinner would appear endlessly after cancelling a TWINT payment.
HMAC support for Tamaro
You can enable HMAC support for Tamaro transactions, making the payment process even more secure. Read more here