Zuora Billing Release 285, September 2020

Changes to on-demand usage rating

Zuora now introduces a behavior change to on-demand usage rating for usage-based charges. If the charge through date of a usage charge is later than the target date of a bill run, the charge is not picked up for rating and billing in the bill run.

Support for more company codes in Avalara integration and third-party tax connectors

Currently, you can use at most 40 company codes defined for integration between Zuora and Avalara and for integration with a third-party tax engine via tax connector apps. Previously, the limit was 20 on the maximum number of company codes.

Refreshing changes to the payment run details page

Zuora now introduces a behavior change to the payment run details page. If a payment run is in Completed status, a refreshing icon is now displayed in the Payment Run Summary area for you to reload summary information.

First Data Payeezy supports stored credentials transactions of American Express

The First Data Payeezy gateway integration has been enhanced to support the Stored Credential Transaction framework of American Express. For more information, see First Data Payeezy Gateway and Support for stored credential transactions overview.

Vantiv (Now Worldpay) now supports stored credential transactions for Credit Card Reference payment methods 

The Vantiv (Now Worldpay) gateway integration now supports the Stored Credential Transactions framework for Credit Card Reference (CCRef) payment methods.

With this feature, you can create new CCRef payment methods with Zuora’s Vantiv (Now Worldpay) gateway integration. A network transaction ID will be stored on the Second Token ID (SecondTokenId) field, which will be used for future payments. 

Note that the support for stored credential transactions is enabled as the default behavior for CCRef transactions. No additional configuration is required. 

Create custom object definition API can now filter out the system fields in the request schema

Previously, when you tried to use the response schema of the Get custom object definition operation as the request schema and made a Create custom object definition request, the call failed due to the presence of the system fields in the schema. These system fields will now be filtered out automatically and you can successfully create a custom object definition by using the Get custom object definition response schema as the request schema.

Filterable fields can now be changed through Update custom object definition API

Previously, you cannot change the filterable value of a custom field once the field is created. You can now change a filterable field to non-filterable and vice versa though Update custom object definition API.