This is Zuora Fall 2017 product release notes. It includes new Zuora features and enhancements.
This feature is only available if you have the Order Metrics feature enabled. If you wish to have access to the feature, submit a request at Zuora Global Support. We will investigate your use cases and data before enabling this feature for you. If you have the Orders feature enabled, you already have the Order Metrics feature enabled.
Zuora provides the Revenue Metrics feature to auto-generate the orders when you create subscriptions and subscription amendments. An order represents an agreement between a merchant and a customer. You can view the metrics for orders to get additional metrics that are helpful for reporting and revenue recognition.
Order metrics capture the impact of every change across the whole subscription lifecycle. You can retrieve order metrics and measure billed and unbilled amounts by order from the REST API. You can also export order metrics from the orders data sources through Export ZOQL queries. These data sources provide you the detailed information about orders.
For more information, see Order Metrics.
Previously we only supported performing a verification on an existing customer’s payment method when modifying payment method details. Zuora now supports performing a standalone zero dollar verification or one dollar authorization for credit cards. It also supports a billing agreement status check on PayPal payment methods. To verify the payment methods, make a call using the REST Verify payment method operation.
This feature is only available if you have the Client-side HPM Parameter Validation feature enabled. If you wish to have access to the feature, submit a request at Zuora Global Support.
Zuora now supports the Client-side HPM Parameter Validation feature to better protect the client-side HPM parameters in the request for rendering or submitting Payment Pages 2.0. When receiving such a request, Zuora validates the client parameters in this request by comparing with the value specified in the digital signature.
For more information, see Validate Client-side HPM Parameters.
Zuora now supports reconciling the following events with the GoCardless payment gateway.
| Object | GoCardless Action | Zuora Event |
|---|---|---|
| Mandate | resubmission_requested | MandateReinstated |
| Payment | customer_approval_denied | TransactionRejected |
| Payment | late_failure_settled | TransactionReversed |
| Refund | paid | TransactionSettled |
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 Chase Paymentech Account Updater. This feature enables merchants to automatically incorporate changes made to a customer's Visa or MasterCard data into Zuora. The data includes the expiration date, new card number, account closure, and brand migration.
For more information, see Configure Chase Paymentech Account Updater.
This feature is only available if you have the Payment Tokenization feature enabled. If you wish to have access to the feature, submit a request at Zuora Global Support.
Zuora’s SlimPay integration now supports Card Aliases via the Credit Card Reference Transaction payment method. This will allow you to leverage the SlimPay’s card-alias API to create credit card payments against subscriptions.
The following table shows the API mapping between Zuora and SlimPay.
| Zuora REST API or SOAP API | SlimPay API |
|---|---|
| PaymentMethod.TokenId | Card-Alias: id |
| PaymentMethod.SecondTokenId | Card-Alias: reference |
When creating a payment method from the Zuora UI, REST API, or SOAP API, you need to populate the token generated from SlimPay only in the TokenId field on the payment method.
The new Account.Parent.Name merge field enables you to display the parent account name of a customer account in billing documents. You can add the Account.Parent.Name merge field in invoice templates, debit memo templates, and credit memo templates. It makes the account hierarchy clearer in billing documents.
See merge fields for Invoices, Debit Memos, and Credit Memos for more information.
Previously, you could only import tax rates as Windows Comma Separated CSV files using Microsoft Excel. Now, Zuora also supports the following CSV format variations for tax rate import:
See Tax Rates for more information.
Two thresholds are added to limit the maximum number of Payment Page submissions. Through the Zuora UI, you can configure these thresholds on the Payment Page configuration page.
See Configure Advanced Security Checks for Payment Pages 2.0 for more information.
OAuth is now enabled for all tenants in the Zuora Production environment and is the recommended authentication approach for REST API calls. See Authentication for information about using OAuth to authenticate with the REST API. OAuth continues to be enabled for all tenants in the Zuora API Sandbox environment.
Additionally, all users with the “Administrator” Platform role can now create OAuth clients for users. For an OAuth client to be able to write data using the REST API, the user that the OAuth client was created for must have a Platform role that includes the “API Write Access” permission.
With the opening of Zuora EU Data Center in July 2017, Zuora now operates two geographically separated data centers in US and Europe.
Zuora EU Data Center hosts a completely isolated instance of the Zuora services, hosted completely in the cloud. No customer data will be copied or replicated between US and EU.
See Zuora Data Centers for more information.
Customers using the following gateways and payment method updaters need to provide Zuora's new EU IP addresses for whitelisting directly with the gateway partners:
See Outbound IP Address Whitelisting for the IP addresses.
The following articles describe the latest features of Zuora for Salesforce:
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.
Vision