Knowledge Center

Knowledge Center > What's New > Previous Zuora Releases > 2009 New Features > July 2009 New Features

July 2009 New Features

Overview

We are pleased to provide you with a summary of our July, 2009 release.

Z-Billing

Bill Run Rearchitecture

Starting in this release, posting and canceling bill runs now operate asynchronously, meaning these operations will run in the background and you will be notified by email when the operation is complete. This allows you perform other tasks in Z-Billing while the operation is running, which is especially useful for large bill runs.

Faster Invoice Export

We optimized the Invoice Export, which now allows you to export invoices much more quickly.

Invoice Template Validation

Additional error checking is now performed on invoice templates upon upload to Z-Billing. Now, if you try to upload a template that contains an error, it will fail. This ensures that future bill runs do not produce invalid invoices.

Z-Payments

Ability to Retrieve Gateway Messages via API

Z-Payments now has expanded support for gateway error messages. You can query Z-Payments via the API and retrieve response codes to identify why a payment failed. The gateway response and gateway response codes (no typo, these are two different data fields) are already displayed when logged into Z-Payments after processing an ad-hoc payment or payment run. The Payment.GatewayResponse is a message that is returned by the gateway (e.g., The configuration with processor is invalid. Call Merchant Service Provider). The Payment.GatewayResponseCode is a numeric code which provides additional information. Both the Payment.GatewayResponse and the Payment.GatewayResponseCode will vary by your gateway. Using these two fields, you can deliver accurate messages to customers with problem cards and save business that might otherwise not realize there were problems with their cards.

Integration with the Cybersource Gateway

Z-Payments now supports payment processing through the Cybersource payment gateway, a leading gateway for enterprise-class customers.

Cybersource's Export Compliance Check

You can now perform an Export Compliance Check on all new electronic payment methods entered into the system as well as on all updates of electronic payment methods. This allows payers who are subject to the US Department of Commerce Export Control and Export Embargo lists as well as the US Department of Treasury Office of Foreign Asset Control list to be rejected in order to comply with these regulations. To use this feature you must have Export Compliance Check Service turned on within your Cybersource account. You will need to contact Cybersource for more information

CVV Code for Authorize.net

You may now verify credit cards using CVV code, which is passed securely and directly to Authorize.net for verification. This will help minimize fraud and may improve transaction rates you pay for transactions that include a CVV code. Please note that according to PCI compliance and merchant bank rules and regulations, the CVV code is never stored. The CVV code is accepted upon initial validation of the credit card. For recurring payments all of the initial validation information is used except the CVV code.

Recurring Flag for PayPal's Payflow Pro Gateway

You may now opt to process credit card reference transactions (a distinct payment method that is different from processing a credit card directly) through your gateway as "recurring". This flag turns off some validations on future transactions after the credit card’s initial validation. The benefits of doing this include potentially processing payments on credit cards that have expired (e.g., the credit card number has not changed but there is a new expiration date which you do not have) and also potentially lower transaction costs. Please note that to use this feature, your merchant bank (if you are not using PayPal as your merchant bank) must support the recurring flag option. Your Merchant Bank may have other restrictions, so you will want to check with them before using this feature.

User Administration

Creating new Users

Administrators can now create additional users by navigating to Z-Billing > Admin > Manage Users > Add Single User.

Starting with this release, you will no longer have to log a support ticket to create new users.

Manage Users

You can reset user passwords, update user contact information and view user login history by navigating to Z-Billing > Admin > Manage Users.

So that you can tune your security settings to meet your needs and policies, you can configure password expiration for a higher level of application security. User passwords can be set to "never expire" or to expire every 30, 60 or 90 days. When the user password expires, the user is prompted to reset password during login. Please note that password expiration does not apply to API logins so that your order processing is not unnecessarily interrupted.

Tip: Best practice is to have a single user login for API access (for example, api@companyname.com). User logins created using this nomenclature, api@companyname.com, will not expire.

Reset All Passwords for All Users

If you have a security concern and want to force all users to change their passwords, you can now do so by navigating to Z-Billing > Admin > Manage Users > Reset All User Passwords.

When resetting all passwords for all users (with exception of users with API logins), they will be required to change their passwords upon their next login.

Z-Commerce API

New RatePlanChargeTier Object Fields

For the RatePlanChargeTier object, the IsOveragePrice and PriceFormat fields are now exposed. The PriceFormat field specifies the charge model for a given tier (i.e., Per Unit, or Flat Fee). The IsOveragePrice field specifies if the tier is the pricing for overage, and should only be used for overage pricing models.

Overriding Price Tiers

You can now override price for individual tiers using the subscribe() and subscribeWithExistingAccount() calls. This is useful if you need to change override default pricing for volume and tiered based models when creating subscriptions. For example, if you have two tiers with pricing of 1-10 units at $5 each, and 11+ at $4 each, you can override the price of each of these tiers, such as 1-10 units at $4 each and 11+ at $4.50 each.

Z-Force 360

New Invoice Fields Synchronized

Z-Force 360 now synchronizes the following new Invoice fields from Z-Billing to Salesforce.com:

  • Generated On date (the date on which the Invoice was generated)
  • Posted On date (the date on which the Invoice was posted)
  • Total Amount (the total amount of the invoice)

In addition, the "Balance2" field has been renamed to "Balance", which will reflect the outstanding balance on the invoice.

Please note that if you have built custom reports in Salesforce.com using this field, you will need to change your reports to use "Balance" instead of "Balance2". 

All Posted Invoices now Synchronize

Z-Force 360 now synchronizes all posted invoices. This is a significant new feature as you will now be able to build a host of reports in Salesforce.com to manage your business. Aside from operating reports, this feature will help you determine the health of your customer base, target potential up-sell and renewal opportunities, and a host of other actions made possible by integrating Salesforce.com with Zuora.

Z-Force 360 Asynchronization

Z-Force 360 synchronizations now run in the background (just like billing and payment runs in Z-Billing and Z-Payments). You can now start a Z-Force 360 synchronization and move on to other tasks while the sync is performing. When the sync is finished, you will see an update in our user interface that shows a sync completion.

Last modified
16:32, 12 Feb 2015

Tags

Classifications

(not set)