June 2017 Release Notes

Knowledge Center > ZZ ARCHIVE > ARCHIVED Zuora Billing Release Notes > 2017 New Features > June 2017 Release Notes

June 2017 Release Notes

Welcome to the release notes for the Zuora June 2017 Release, R213. This release includes new Zuora features, enhancements, resolved issues, and improvements to the Knowledge Center.

For more information about the current product version, see Product Versions and Release Dates.

Release Schedule

The schedule for R213 deployment.


  • APISandbox Release Date: June 7, 2017
  • Production Release Date: June 14, 2017


  • APISandbox Release Date: June 20, 2017
  • Production Release Date: June 21, 2017


  • APISandbox Release Date: June 27, 2017
  • Production Release Date: June 28, 2017


  • Billing Setting for Inclusive Tax Calculation
  • Security Enhancements in Payment Pages 2.0

Billing and Payments

Billing Setting for Inclusive Tax Calculation

You can now set the tax rounding rule to calculate taxes for the inclusive tax mode. You can either round the net amount or the tax amount in the tax calculation. The tax amount might be different based on two different rounding rules.

To access this feature, click your username at the top right and navigate to Billing > Define Billing Rules > Zuora Tax rounding rule for inclusive tax calculation. By default, the Rounding Net Amount rule is used in the inclusive tax calculation. 

See Zuora Tax rounding rule for inclusive tax calculation for more information.

New Merge Fields for Invoices

The TaxSummary.AmountWithoutTax and TaxItem.AmountWithoutTax merge fields are now available on invoice templates. You can include these merge fields on invoices to display the subtotal of all charges without taxes in tax related tables. This enhancement gives you more flexibility in summarizing tax information on invoices.

See Merge Fields for Invoices for more information.


Security Enhancements in Payment Pages 2.0

For tighter security around Payment Pages 2.0, we added additional security checks.

Prevent Multiple Renderings with One Signature

Now you can render a Payment Page only once with one generated signature. You need to re-generate a signature if you want to re-render a Payment Page in callback code such as in the Inline Button Outside mode. If you attempt to re-render the page with a used signature, an error will be displayed on the Payment Page. 

Limit on Number of Payment Page Submissions

A new tenant level limit on the maximum number of Payment Page submissions is implemented. When an end user hits this threshold by repeatedly submitting incorrect information on the Payment Page, they will see the error message and will be blocked from further submission. When the submission limit is reached, you need to provide your end users a way to re-render the page, which requires a regeneration of a signature.

Contact Zuora Global Support if you want to increase the tenant level threshold for submitting Payment Pages.

Generate a New Signature for Each Direct POST Request

When the security checks are enabled in your tenant, you need to generate a new signature for each of Direct POST request that is sent to Zuora, or the security checks will block your requests.

Refer to Implement Payment Pages 2.0 via Direct POST for detail information about Payment Pages 2.0 via Direct Post.

Enable the New Security Checks

By default, the new security checks mentioned in this section are disabled. 

To enable the security checks, first go through the following checklist to set up the Payment Page, and contact Zuora Global Support to enable the setting or adjust the limits.

  1. Generate a signature for each Payment Page render.
  2. Generate a signature in your callback code before re-rendering a Payment Page when a previous submission fails.
  3. Generate a signature for each Direct POST request.
  4. Customize the error message for the Attempt_Exceed_Limitation error code. See Error Handling for Payment Pages 2.0 for the steps.
  5. Provide a way for end users to re-render the Payment Page when they hit the limits.

Support for WorldPay Gateway Reconciliation

This feature is in Limited Availability. If you wish to have access to the feature, submit a request at Zuora Global Support

Zuora now supports reconciling the electronic payment, refund, and chargeback events processed through the WorldPay gateway. To use this feature, configure WorldPay gateway reconciliation through the Zuora UI.

Additional Credit Card Types for Several Payment Gateways

Zuora now supports the following additional credit card types for several gateways.

Supported Credit Card Types Payment Gateways
  • JCB
  • Diners Club
  • BlueSnap
  • Braintree
  • SagePay
  • Stripe 
  • Adyen
  • China Union Pay
  • Adyen


A New Tenant Permission to Prevent Deleted Products Synced To Salesforce

When you sync product catalog from Zuora to Salesforce, by default, the deleted products in your Zuora product catalog are synchronized to Salesforce. Starting in this release, you have an option to skip deleted products in product catalog syncs.

Contact Zuora Global Support to enable the tenant permission not to synchronize deleted products to Salesforce.

Zuora for Salesforce Release (Q4 2016)

The following articles describe the latest features of Zuora CPQ:


The following articles describe the latest features of Zuora Reporting and the Zuora Insights add-on:


See API Changelog for a summary of REST API updates and documentation updates in the API Reference.


Current WSDL version: 85

See Zuora WSDL for information on how to check your version and download the latest version.

SOAP API Change History

See Zuora SOAP API Version History for a summary of updates made to the SOAP API in recent Zuora releases.

Knowledge Center

We have updated the following Knowledge Center articles based on your feedback:

Last modified


This page has no custom tags.


(not set)