Zuora Billing Release 301, May 2021

Default Payment Method ID now available in the Account data source

When using the Account data source to export data, you can now choose the Default Payment Method ID field in the base Zuora object of Account.

Support for setting OAuth 2.0 scope in the configurable Tax app

The configurable Tax app now supports the "scope" parameter in OAuth 2.0 authentication. Some tax vendors require that you specify the scope parameter when authenticating via OAuth 2.0.

To configure the scope parameter, click the Engine Settings tab in the configurable Tax app, then edit your tax engine and click the System Configuration tab. You can specify Scope if Authentication Type is set to OAuth 2.0.

To determine the appropriate value of Scope, contact your tax vendor.

For more information about the configurable Tax app, see Configurable Tax app.

Support for reconciling refunds through Zuora REST API

You can now reconcile a refund through the Reconcile refund operation. If you specify reject for action through API, the gateway state on the transaction is set to FailedToSettle and the subsequent actions of handling the refund rejected events take place according to the option configured in the newly introduced Gateway Reconciliation Configuration setting. 

For more information about the options available for handling refund rejected events, see Configure how to handle refund rejected events.

For details about the Reconcile refund operation, see the API Reference.

Gateway reconciliation status information available for transactions

The following gateway reconciliation information is now available for payments and refunds in API responses, on the Detail pages in the Zuora UI, and in the data sources:

• Gateway Reconciliation Status
• Gateway Reconciliation Reason
• Payout Id

The following information is available for payment methods in the response body of the Get payment method operation and the data source:

• Mandate status
• Mandate reason

See API Changelog for detailed API updates.

Enhancement on processing CAPTCHA interaction in Payment Pages 2.0

To listen to the CAPTCHA interaction event and trigger an appropriate action, you can now set up the event handler through the Z.setEventHandler function when implementing your Payment Pages.

See Set up event handler for processing CAPTCHA interaction for details.

Stripe v2 supports downgrading Level 3 processing

The Stripe v2 gateway integration in Zuora now supports downgrading Level 3 processing to transactions without Level 3 data.

A setting called Downgrade failed L3 payment attempts is now available on the Stripe v2 gateway configuration page. With this setting and the Enable Level 2/Level 3 Processing setting enabled, an immediate payment attempt without Level 3 data will be made when the payment with Level 3 data fails to ensure collection against invoices.

See Stripe payment gateway for more information.

Support for Delayed Capture on CyberSource v2.0 

The CyberSource, Payment API v2.0 gateway integration now supports the Delayed Capture feature for credit cards. This feature allows you to authorize a payment amount prior to capturing the payment.

See the Create authorization API operation for more information.

Real-Time Reconciliation available on GoCardless gateway integration

The GoCardless gateway integration in Zuora now supports the Real-Time Reconciliation feature. With this feature enabled, the payment gateway can submit notifications to Zuora for various event types on gateway objects, and the corresponding records can be automatically updated in real time.

See GoCardless gateway for more information about this feature.