Skip to main content
Vindicia Knowledge Center

CashBox Release Notes 17.0.2

CashBox Release Notes 17.0.2

New Features and Enhancements

This release includes the following new features, enhancements or improvements.

CashBox AutoBill.makePayment() now allows customers to pay AutoBills in advance

CashBox has enhanced the ability for customers to pay directly for an invoiced subscription in advance of scheduled billing or invoice due date. This enhancement targets invoices whose status is: Open—which can now receive payments. Supported payment options include partial payment of the amount, multiple partial payments, full payment, and payments in excess of the amount of the subscription or invoice. In the case of over payment, any overage is carried on the AutoBill as a credit. If the invoice changes before settlement, the AutoBill credit is used to settle the invoice. Future invoices will also be paid from available AutoBill credit.

(CB-14692)

Push Event Class & Events: Accounts

CashBox adds a new Push Event Class: Accounts. The Accounts Event Class has the following Push Events:

  • Account Created
    • Trigger: an Account is created. Sent once per Account.
    • Content: A full ACCOUNT object (per the API account.fetchByVID using the existing merchant configuration governing API version for push messaging content—when unspecified, this defaults to latest SOAP API version). Also, includes standard push message details.
  • Account Shipping Address Changed
    • Trigger: the shipping address for an Account is changed.
    • Content: A full ACCOUNT object (per the API account.fetchByVID using the existing merchant configuration governing API version for push messaging content—when unspecified, this defaults to latest SOAP API version). A separate object contains the old/outgoing Shipping Address details. Also, includes standard push message details.

(CB-23081)

Push Event Class & Events: Payment Methods

CashBox adds a new Push Event Class: Payment Methods. The Payment Methods Event Class has the following Push Events:

  • Account Updater Change
    • Trigger: a payment method is updated due to Account Updater (AU) response.
    • Content: A full PAYMENT METHOD object (per the API paymentmethod.fetchByVID using the existing merchant configuration governing API version for push messaging content—when unspecified, this defaults to latest SOAP API version). Also, includes standard push message details.
  • Contact/Billing Address Updated
    • Trigger: a payment method is updated where the Account Holder Name or Billing Address is changed.
    • Content: A full PAYMENT METHOD object (per the API paymentmethod.fetchByVID using the existing merchant configuration governing API version for push messaging content—when unspecified, this defaults to the latest SOAP API version). A separate object contains the old/outgoing Billing Address details. Also, includes standard push message details.
  • Activated
    • Trigger: a payment method is added to an account (either directly or added to a one-time transaction or AutoBill owned by an Account.
    • Content: A full PAYMENT METHOD object (per the API paymentmethod.fetchByVID using the existing merchant configuration governing API version for push messaging content—when unspecified, this defaults to the latest SOAP API version). Also, includes standard push message details.
  • Deactivated
    • Trigger: A payment method is deactivated from an account (either directly removed (merchant sets active = false), or removed by a CashBox process.
    • Content: A full PAYMENT METHOD object (per the API paymentmethod.fetchByVID using the existing merchant configuration governing API version for push messaging content—when unspecified, this defaults to the latest SOAP API version). Also, includes standard push message details.

(CB-23084)

Ability for Merchant to specify Global Collect recurring transaction related values for one-time transactions

CashBox now supports the ability to pass the Global Collect-specific recurring transaction values OrderID, EffortID and AttemptID on the Transaction object as Name Value Pairs for one-time Transactions. These values would be forwarded to Payment processor as if the Transaction were a recurring transaction only when the payment processor is Global Collect.

(CB-23584)

Campaign Code Generation Improvements: Faster/Larger Code Generation and improved code file format

As part of ongoing enhancements to Campaign Management in CashBox, we have significantly increased the speed and scale of campaign code generation, and added identifying reference information in the code file returned. This significantly improves selfservice code management and lays the ground work for additional enhancements in this area in the coming releases, including the following:

  • Generate Coupon Codes (button in the CashBox Portal Manage > Campaigns > Campaign Detail (Coupons))—now generates a larger file (up to 1,000,000 codes) much faster. Requests towards the upper limit should still return in 2-5 minutes. For code sets larger than 1M individual codes, contact Vindicia Support.
    • Note that file generation and download will be very fast (2-5 minutes for up to 1M codes). However, the codes will not be mmediately usable (regardless of whether you specified “Activation Required Before Use”); after the file downloads, if you refresh the Portal webpage, or at any point revisit that campaigns detail page in the portal, you will see that a progress bar has replaced the Generate Coupon Codes button, which will indicate when the entire code set will be usable in CashBox. Generally this is within minutes of generation but can take up to several hours for large code sets or during peak hours.
  • The resulting code file now includes additional fields—expect a TAB-DELIMITED FILE download (.tsv) with no header row, whose columns are below (in the order they appear in the file):
    • Coupon Code Sequence—sequence ID within the code set; from 1 to the number of codes generated
    • Coupon Code—text string which is the “coupon code” of individual coupon—this is what customers/users enter to redeem the code
    • Campaign ID—merchant campaign identifier of the related Campaign
    •  Campaign VID—Vindicia ID of the related Campaign 
    •  Campaign Coupon Index Number—a sequence id used with upcoming functionality, expect 0 for current campaigns

(CB-24005)

Bug Fixes

The following bugs were fixed in 17.0.2.

Ticket No. Summary Description
CB-22179 One-time transactions are not marking coupon codes as used On one-time Transactions—auth() then capture(), orauth.capture()—CashBox was not decrementing the use count of limited use coupons, with the result that the coupons could be reused indefinitely. This has been fixed.CashBox now decrements limited use coupons by 1 for each one-time Transaction.

A limited use coupon can be used for a single or multiple TransactionItems on a single one-time Transaction and still count as a single use.

CB-23020 Refund.FetchByTransaction 500—should return a 404 when the transaction is not found

Refund.FetchByTransaction was returning a 500 error code when a Transaction was not found. This has been updated.Refund.fetchByTransaction() now returns a 404 error code with the error message Unable to load transaction tosearch by: No matches when the provided transaction is notfound.

CB-23114 Account.update() 500—should return a 400 when the parameter passed in is not an Account Account.update() was returning a 500 error code when the parameter passed in was not an account-only string. This has been updated. Account.update() now returns error code 400 when the parameter passed in is not an account, with the following error message: Required parameter account and Vindicia::Soap::Account type are specified, but the value is not an object.
CB-23120 Global Collect SEPA DD HML—Billing Statement Identifier not passed to GC When a BillingStatementIdentifier was set on a Transaction, Autobill, Product or Billing plan, it was not passed to the processor if the processor was Global Collect Hosted Merchant Link and the Payment Type was Direct Debit—it was instead overwritten by a hard coded value.

This has been changed. When a BillingStatementIdentifier is set on a Transaction, Autobill, Product or Billing plan, it is now correctly passed to the payment processor.

CB-23320 Enhanced status and billing state incorrect for AutoBills with catchup billing successfully applied after payment method was updated A number of AutoBills that had been canceled or gone into catchup billing and were revived (by, for example, adding a new payment method) had their enhanced status stuck at Expired, Billing Completed. This has been fixed. The status of these AutoBills is now reset to the correct value—for example, if the AutoBill's payments are current and there are no other issues, they would typically be set to Active, Good Standing.)
CB-23510 Internal Transaction ID being returned in failed AutoBill.finalizeCustomerActio()call When AutoBill.finalizeCustomerActioin() failed, it returned an error message containing an internal transaction ID. This has been fixed. Now, when AutoBill.finalizeCustomerAction() fails, it returns the 400 error code with a message containing the merchant_tx_identifier, and the Transaction VID.
CB-23873 Product Price with a zero (0) in the decimal place (such as $2.50), zero is not displayed in the Portal or returned via the API When a product with a price containing a trailing zero (0) in the decimal place was added using the Cashbox Portal (for example $2.50), the price was returned by the Portal and by the API as $2.5. This has been fixed. The CashBox Portal and the API now correctly display product prices.
CB-23859 Transaction Detail Report missing fields when selecting Transaction Status = Captured

When merchants selected the Transaction Status = Captured or Transaction Status = Cancelled radio button (instead of both), the Transaction Detail Report was missing the following columns in the output:

  • Billing Information|Billing Plan ID
  • Billing Information|AutoBill ID
  • Billing Information|AutoBill Cycle
  • Billing Information|Billing Plan Cycle
  • Billing Information|Retry Number
  • Billing Information|Original Billing Date

This has been fixed. All columns are now present when selecting the Transaction Status = Captured or Transaction Status = Cancelled radio buttons.

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