Skip to main content
Vindicia Knowledge Center

CashBox Release Notes 11.0.0

CashBox Release Notes 11.0.0

Features and Enhancements

This release includes the following new features and enhancements.

Additional Information Displayed in the Transaction Detail Report

As of this release, three new data columns (AutoBill Cycle, Billing Plan Cycle, Retry Number) are added to the Transaction Detail Report.

  • AutoBill Cycle: The number of the billing cycle in the AutoBill service for which this transaction charges. As this index begins with 0 (for the initial billing cycle of an AutoBill) it can also be considered the “renewal count” (that is, 1 is the first renewal, 3 is the third renewal, and so on).
  • Billing Plan Cycle: The number of the billing cycle in the AutoBill service, since the last billing plan change, for which this transaction charges. If there has been no billing plan change for this AutoBill, this number will be the same as the AutoBill Cycle.
  • Retry Number: The number of the retry attempt represented by this transaction. For one-time transactions this value is null. This index begins with 0, for the initial attempt to charge for a particular billing. A value of 1 indicates the first retry, 3 indicates the third retry, and so on.

Ticket: CB-17249 

parentMerchantAccountId Data Member Added to Account Object

As of this release, if an Account has a Parent Account, the Account Object is populated with the MerchantAccountID (merchant_customer_identifier) of the parent account. If the account does not have a parent account, this is null.

Ticket: CB-18497 

Transaction Detail and Refund Reports Improved for Readability

Previously, the Transaction Detail and the Refund reports repeated Transaction records for every Event associated with a Transaction (for rated products including usage and license-based services.) As of this release, the related Event fields: the Rate Plan ID, Rate Plan Description, Rated Unit Total, and Rated Unit Name columns, have been removed from the Transaction Detail, Transaction Refund Detail, and Active AutoBills reports. This change ensures that a single record is presented for each Transaction or Refund on these reports.

Ticket: CB-18719 

Value Added Tax (VAT) ID Template Tag Available

As of this release, a new tag for email templates is available that contains the Account Tax Exemption Identifier (also known as Value Added Tax (VAT) ID. This tag can now be used with appropriate email templates—including the common practice of presenting the Account VAT ID on an Invoice or billing notice.

Ticket: CB-19241

Bug Fixes

The following Bugs were fixed in this release.

Ticket No. Summary Description

CB-15320

When a transaction that was processed through Global Collect has a Chargeback and then has a subsequent Refund request, the refund was getting stuck in Pending status.

The Global Collect process has been updated to prevent this issue. Refunds in these situations will now process properly.

CB-16075

Edits to an AutoBill using the CashBox Portal, in which an AutoBill Item with an “Update next billing period” setting was removed, were applying an erroneous credit to the next billing.

When the “Update next billing period” setting is used with the removal of an AutoBill Item from within the CashBox portal, there should be no proration and thus no credit issued. The change should take affect at the end of that period. Due to a bug, the erroneous credit was applied, leading to under-billing in select circumstances. This has been fixed so that portal changes take effect properly, and in line with how the API equivalents were already performing.

CB-16229

A Credit Activity search on Name/Value Pairs displayed extra columns.

Previously, when doing a Credit Activity search with only the Name/Value Pairs optional display selected, the search results included extra columns, such as AutoBill ID, Customer ID, and Amount. In the current release, a search on Name/Value pairs returns the expected results.

CB-16254

Unable to remove the last Product or Billing Plan when editing a campaign.

Previously, when editing a Campaign, CashBox Portal prevented removal of the last Product or Billing Plan in each respective list. This has been corrected in the current release.

CB-17821

The Account.grantCredit() API method returns 200 even though the credit parameter was not correctly populated.

 When an invalid Credit was specified in the Account.grantCredit API method, CashBox was erroneously returning a 200/OK response. This has been corrected to provide the proper error code.

CB-17868

When using the CashBox Portal to create a billing plan with billing periods using Seasonal Billing, CashBox did not recognize the selected Season Set.

The portal was preventing the creation of new Billing Plans that used Seasonal Billing when there was not a period with “indefinite” recurrence. This has been fixed. It is now possible, and valid, to create a fixed-length (non-infinite) billing plan using Seasonal Billing settings from within the CashBox Portal.

CB-19201

The Template Toolkit tag for tier_rate_price (rate plan tier pricing) was unnecessarily rounding the value returned to templates.

The tier_rate_price tag was rendering a rounded-to-two-decimals version of its true value on emails in which the tag was used. This has been fixed to show the true value stored in that field.

CB-19329

The Account.update API method calls that did not specify a valid Account Identifier were returning a 500 error response rather than 400.

Account.update API calls that did not specify a valid Account Identifier were returning 500 error responses. This is an error condition—you must specify the Account to be updated. But the error should be a 400, not a 500. The fix returns the proper 400 error, for all versions of the API.

CB-19497

AutoBill cancel notifications sometimes had an incorrect end date.

Due to a bug in the process that feeds Cancel events to the email notification process, a wrong AutoBill end date could get presented. This occurred when the end date was changed as part of the API-based cancel request—the template still showed the pre-call end date rather than the new end date. This has been fixed to show the final end date when the notification is generated.

CB-19612

The AutoBill.makePayment API method calls that did not specify a valid AutoBill Identifier were returning 500 error response rather than 400.

AutoBill.makePayment API calls that did not specify a valid AutoBill Identifier were returning 500 error responses. This is an error condition—you must specify the AutoBill to be updated. But the error should be a 400, not a 500. The fix will return the proper 400 error code (for all versions of the API.)

CB-19650

Prevent Account Updater from updating inactive payment methods.

The Account Updater card replacement logic was updating all payment methods using the updated card, even if that method was deactivated. This lead to creation of a new active version, with the new details. This has been corrected so that it replaces only active payment methods.

CB-19785

Projections Detail Report list (CashBox Portal) filters displayed HTML code on page.

After the report was run, the listing of Projections Detail reports in the Report List of the My Reports page had some HTML formatting code showing – this has been removed.

Note: This was a Known Issue reported in the release notes of the 9.0 CashBox release – fixed permanently in this release.

CB-19820

The Entitlement.fetchByAccount() API method sometimes returned incorrect additional entitlement records after an AutoBill modification.

Since the CashBox 10.0 release, when an AutoBill is modified using AutoBill.modify() (10.x.x versions) to add or remove an item with Next Bill effect, any subsequent Entitlement.fetchByAccount API with the showAll parameter set to true will return an extra inactive entitlement record for the outgoing or changing item, with an early end date (not showing the date of the next billing.) In the current release, this API call returns only the properly expected results—not the erroneous extra entitlement records.

CashBox for
Salesforce (Basic)

Learn More
CashBox for Salesforce (Basic)

StoreFront

Learn More
StoreFront

CashBox for
Salesforce (Premium)

Learn More
CashBox for Salesforce (Premium)
Back to Top