Welcome to the release notes for Zuora Release 2023.04.R1. This article is a consolidated page of all release notes for the following Zuora products:
For the latest release notes of Zuora Revenue, see Zuora Revenue release notes.
We welcome and appreciate your feedback on this release notes article. Please use the Feedback button to let us know what you think about the new release notes.
For release schedule details, see this release notification.
For the planned schedule of upcoming Zuora releases, see Zuora Release Management in Zuora Community.
Join Release Notifications in Zuora Community to receive timely notifications about Zuora Billing, Collect, and Central Platform.
New UI experience now opt-out by default (Sandbox only)
The new Zuora UI experience was introduced in early 2022 and has been continuously improved based on feedback. We are pleased to make the new UI experience opt-out by default for all customers on all Sandbox environments in April.
With the default setting, the following UI enhancements are generally available:
- All reinvented list views
- Reinvented invoice details page
- Reinvented subscription details page
- Reinvented payment details page (with Invoice Settlement supported)
If you are an existing customer and have previously disabled the new UI experience, we will also enable the new UI experience for you. However, you can switch back to the old UI using the Enable New Zuora Experience user profile setting as necessary.
Orders and Subscriptions
UI enhancements to Orders Harmonization
Previously, if your amendments and subscriptions were created in the Subscribe and Amend tenant, and if the Orders UI is enabled after being migrated from the Subscribe and Amend tenant to the Orders Harmonization tenant, you cannot perform the following tasks for draft subscriptions, draft amendments, and pending amendments.
You can now perform the following tasks after being migrated to the Orders Harmonization tenant:
- Activate pending amendments
- Manage draft amendments including:
- Enter the Contract Effective date
- Edit the draft amendments
- Preview the draft amendments
- Delete the draft amendments
- Manage draft subscriptions including:
- Modify the draft subscription details page
- Add, update, and remove products on the draft subscriptions
- Save the draft subscriptions again
- Activate the draft subscriptions
- Delete or preview the draft subscriptions
Support for creating draft invoices through Orders API
You can now create draft invoices through the
generateDraftInvoice field in the "Create an order" operation. Previously, you can only generate draft invoices through the "Generate billing documents by account ID" operation. The default value of the
generateDraftInvoice field is
false. If you set the field as
true, draft invoices are generated.
Support for some Subscribe and Amend APIs in Orders tenants
Invoicing and Tax
New REST API operation to retrieve Contact Snapshot object
A new REST API operation called "Retrieve a contact snapshot" is now available. You can use this operation to retrieve information about Bill To Contact Snapshot or Sold To Contact Snapshot objects.
soldToContact field available at subscription level through REST API
The Flexible Billing feature now provides you the capability to have different sold-to contacts for subscriptions through the REST API. Therefore, you can sell products and services with different tax addresses for different subscriptions in the same order.
ChargeNumber and SubscriptionNumber fields available on more objects in exports and Data Query
SubscriptionNumber fields are now available on the Invoice Item, Credit Memo Item and Debit Memo Item objects through data source exports and Data Query.
PurchaseOrderNumber field is available on the Invoice Item object through data source exports.
New bill run edit page valuable in Sandbox
The newly redesigned bill run edit page with improved and consistent usability is now available through the Zuora UI.
We will release the new bill run edit page only in Sandbox environments, and it will not be deployed to Production environments until further notice.
Settings for enabling payment gateway integrations available
The settings for enabling the supported payment gateway integrations are now available on the configuration page for payment gateways. After a payment gateway integration is enabled, you can set up and configure an instance of the payment gateway for your tenant.
Previously, you had to submit requests at Zuora Global Support to enable payment gateway integrations.
For more information, see the following articles:
Support for processing MOTO payments on Stripe v2
We have enhanced our Stripe v2 gateway integration to support processing Mail Order Telephone Order (MOTO) payment transactions with credit card payment methods. When creating a payment through the UI or API operation, you can now define the transaction source with MOTO. The MOTO transaction indicator will be included in the request to the gateway and a recurring stored credential profile will be created for the payment method used to process the payment. The network transaction ID (NTI) will be returned in the authorization response.
For more information, see Overview of Stripe payment gateway integration.
Support for using MOTO transactions to create stored credential profiles for credit card transactions on Stripe v2
For credit card transactions through the Stripe v2 gateway integration, you can now enable the following settings on the CIT/MIT configuration page and use MOTO transactions to create stored credential profiles while creating payment methods or processing recurring payment transactions:
- Always use MOTO transaction to create stored credential profiles when payment methods are created from Zuora UI
With this setting enabled and the End user consent agreement received checkbox selected when creating a credit card payment method through the UI, the MOTO transaction indicator will be included in the payment method validation request to the gateway and a recurring stored credential profile will be created for the card. The NTI will be returned in the authorization response.
- Allow using MOTO transaction as grandfathering transaction to create stored credential profiles
With this setting and the support for Stored Credential Transactions for the card brand enabled on the CIT/MIT configuration page, the MOTO transaction indicator will be included in the recurring payment request to the gateway and a recurring stored credential profile will be created for the card used to process the payment. The NTI will be returned in the authorization response.
For more information, see the following articles:
Enhancement in migrating existing Apple Pay Visa payment methods on Chase Paymentech Orbital for stored credential transactions
For Apple Pay Visa payment methods on the Chase Paymentech Orbital integration, if the Visa card brand is enabled in the CIT/MIT Configuration setting, stored credential profiles will be created for all existing Apple Pay Visa payment methods when processing payment transactions.
For more information, see Migrate payment methods for stored credential transactions.
WePay payment gateway integrations support ACH payment methods
WePay gateway integrations in Zuora now support ACH payment methods to perform payments and refunds. You can create ACH payment methods on WePay through any of the following methods:
- Zuora UI
- Payment Pages
- API operations for creating payment methods
For more information, see Overview of WePay payment gateway integration.
Support for generating tenant-specific Google reCAPTCHA Enterprise site keys
If you want to enable Google reCAPTCHA Enterprise on your hosted payment pages but you do not want to use your own Google Cloud Enterprise account, you can use Zuora’s Google Cloud Enterprise account. For tenants that are already using or will use Zuora’s Google Cloud Enterprise account, we now generate a Google reCAPTCHA site key dedicated to each tenant. Previously, a shared site key was applied to all tenants that use Zuora’s account.
For more information about configuring Google Cloud account for reCAPTCHA service in Zuora, see Security measures for Payment Pages 2.0.
Updates on payment method types supported by GMO, SB, and Sony
To align with the gateway providers’ service and security policies, we no longer support Credit Card payment methods on the following payment gateway integrations:
For more information about the preceding gateway integrations, see the following articles:
- Overview of GMO payment gateway integration
- Overview of SB Payment Service gateway integration
- Overview of Sony Payment Services gateway integration
Zuora Central Platform
Zuora Central Platform has only internal enhancements and resolved issues in this release.
For the detailed API documentation, see API Reference.
For a summary of REST API updates and documentation updates in the Zuora API Reference, see 2023 API Changelog.
From 2022.09.R1, the Quickstart API is available to you if you have the Orders (or Order Harmonization) and Invoice Settlement features enabled in your tenant. The QuickstartAPI allows new integrators to swiftly integrate with Zuora, and it supports essential business use cases.
For the detailed Quickstart API documentation, see Quickstart API Reference.
For a summary of REST API updates and documentation updates in the Quickstart API Reference, see Quickstart API Changelog.
Current WSDL version: 132
For information about how to check your version and download the latest version. see Zuora WSDL.
SOAP API change history
For a summary of updates made to the SOAP API in recent Zuora releases, see Zuora SOAP API Version History.