Skip to main content

12/25 – Platform Update – Week 51 ’25

Release Date: December 2025
About this update

All improvements listed below are automatically available to all users.

Resolved slow payment processing during peak periods

An issue was identified that could lead to delayed reporting of successful payments via webhooks and within RaiseNow Hub. The mechanism responsible for reporting the successful completion of the payment could become congested during peak load.

To resolve this, improved scaling was introduced for specific parts of the infrastructure. In addition, new metrics were added to the monitoring system to provide better visibility into similar situations in the future.

Increased likelihood of Strong Customer Authentication (SCA) for card payments during carding attacks

RaiseNow donation processes are usually streamlined to minimize friction during the payment flow. As an additional measure to protect both our clients and RaiseNow against carding attacks, a new mechanism has been introduced to increase the likelihood of requiring Strong Customer Authentication (e.g. 3D Secure) when an attack is detected.

Once the attack subsides, the system automatically switches back to a frictionless payment flow.

Backend support for direct debit mandate PDFs

The backend now supports generating direct debit mandate PDFs for Swiss direct debit variants (LSV+, PostFinance Debit Direct) in payment agreements. In this first iteration, template support is limited to customers migrating from RaiseNow Manager. Future iterations will extend support to a wider customer base.

Further bugs & improvements

  • Fixed an issue that resulted in the creation of pending payments for QR bill payment agreements.
  • Fixed an issue where the payment source was not stored for PayPal payments when the option “Save the payment method for future use” was enabled in Tamaro.
  • Corrected an incorrect field name in the API documentation for the Subscription GET endpoint related to subscription status.
  • Improved the targeting of firewall rules related to carding attacks.
  • Fixed an issue where payments originating from subscriptions migrated from RaiseNow Manager to RaiseNow Hub were missing the brand_code property.