Welcome to the release notes for Zuora Billing Release 264 (R264), December 2019. This release includes new Zuora Billing features, enhancements, and resolved issues.
For more information about the release notes of other Zuora products, see Zuora Release Notes.
Subscribe to Release Notifications in Zuora Community to receive notifications about Zuora Billing releases.
See API Changelog for a summary of REST API updates and documentation updates in the Zuora API Reference.
Orders and Subscriptions
Resolved: InitialTerm and InitialTermPeriodType fields not updated through T&Cs
The migration to full Orders is in Limited Availability. We are actively soliciting feedback from a small set of early adopters before releasing as generally available.
Previously in Orders, if the
lastTerm nested field was set through a Terms and Conditions (T&Cs) order action before a subscription was renewed, the
InitialTermPeriodType fields of the subscription were not updated. This issue has now been resolved:
InitialTermPeriod are updated as expected.
Previously in Subscribe and Amend, after a subscription is renewed, changing the term type from
EVERGREEN through a T&Cs amendment updated the
InitialTermPeriodType fields of the subscription. This issue has now been resolved:
InitialTermPeriodType are not updated.
Security enhancements for Payment Pages 2.0
Zuora has enhanced the security for Payment Pages 2.0 for all payment methods.
The following rate limiting settings are now available by navigating to Payments Settings > Setup Hosted Pages:
- Enable Rate Limiting
- IP Whitelist
- Submission Limit Per Minute
- Submission Limit Per Hour
You can customize the configuration based on your business use cases and security tolerance. See Configure Payment Pages 2.0 for more information.
To complement the security enhancements, the default values for the following page-level settings have been updated for newly created Payment Pages:
- Enable Captcha: This checkbox is now selected by default. Previously, it was deselected by default.
- Limit the number of submission before CAPTCHA Challenge: 0. Previously, the default value was 15.
- Limit the number of submission before blocking Submission: 3. Previously, the default value was 30.
For more information, see Configure Advanced Security Checks for Payment Pages 2.0.