With pleasure, Aspenware presents Aspenware Commerce 2.5. We’re excited to be offering new features, such as discounts for date and time-based products. Additionally, we’ve addressed many login and failed order issues, among other requests that you have found important. See below for more specifics on what we’ve been up to.

Updates, Features, and Upgrades

Discounts by Product Date and Activity Time

RTP Payment Plan Support for Unity

Resolved Issues

• Login Issues

  • Previously some Siriusware and RTP customers were experiencing login issues in Aspenware Commerce after email or authentication profile updates in provider systems. Including some of the following:

    • RTP

      • updating username to an email does not allow updated user to login

      • find me by pass number does not update the RTP password if the RTP authentication ID is changed

      • when authentication profile and email profile are different, “find me” email results in frozen screen

      • the “forgot password” module loads an unhandled exception screen when a user enters an email that does not exist in the Aspenware Commerce database

    • Siriusware

      • password recovery doesn't work if an email was updated in Siriusware

• Saved resort charge credit card issues (RTP)

  • Previously, resort charge primary credit card profiles did not save or display correctly. This issue has been resolved.

• Pass media prefix not respected

  • Previously, some customers were able to reload media which did not have the required pass media prefix. Now, the process correctly respects the configured pass media prefixes during reload.

• Kount

  • Previously, issues in Kount were preventing orderId and success status from being updated after payments had processed. Now, orders are updating properly.

• Invalid address (RTP)

  • Previously, when a user entered an address with invalid characters (such as “/”), the customer would be unable to log back in after logging out. Now invalid characters are handled and customers can successfully log back in.

• Failed orders (RTP)

  • Previously, if customers did not have an email address in Aspenware Commerce, they could not complete their order (despite having a username and password). This was a result of a missing email profile required for order completion. Now, if there is a valid email profile in RTP, that address will also be assigned in Aspenware Commerce, allowing for order completion.

• Failed orders due to empty token (Siriusware)

  • Previously, when orders briefly failed before reprocessing successfully (due to empty token errors), customers would receive a “failed order” email. Now, brief empty token orders will not trigger failed order emails.

• Order queue issues causing multiple charges

  • Previously certain characters added to product attributes (such as “:”) would cause an input string error that signaling to customers that their order did not go through and resulting in customers creating multiple orders/charges. Now, special characters are handled in a way that does not cause input string errors or result in misleading messaging.

• My Account/Resort Charge waiver issues

  • Previously, if a user tried to add resort charge but cancelled out of the waiver prior to completing the form and selecting “Ok”, a credit card profile would still be created. Now, a user must complete the form and agree in order to receive a “success” message and have a credit card profile created.

• De-duplicated customers receiving failed orders (Siriusware)

  • Previously, if a customer had been de-duplicated in Siriusware, their orders would fail in Aspenware Commerce due to missing update profile information. Now, Siriusware Unity looks up de-duplicated guests and retrieves updated guest information resulting in successful order completion.

• Other resolved issues

  • Unwanted popups no longer appear when users switch between adding a new card or reloading in checkout.

  • Certain confirmation emails no longer show two extra zeroes at the end of the reservation price.

  • Edge users are now able to update their birthdates.

  • Email confirmations now showing AM and PM on Reservation Times

  • Prompt entries in Aspenware Commerce no longer throw errors when special characters are used in prompts.

Enhancements

• Authorize.NET Duplicate Window

  • Previously, a some transactions were charged successfully but would result in a timeout error in Aspenware Commerce. This would cause the customer to complete a second transaction resulting in a duplicate charge. Now if the customer tries a second time within a brief amount of time (about two minutes), this action will not result in a duplicate charge.

• Requires credit card for 0$ cart

  • Previously, requiring a credit card for a $0 cart was only available to certain products (e.g. for golf reservations with future payment). Now, a “requires credit card” product classification has been added in Aspenware Commerce that can be assigned to any product.

Things to Look Forward to

Payeezy V2 support

Siriusware Payment Plans

Resort Charge enhancements

Bulk payment processing (RTPOne/Braintree Payment Plans)

Subscriptions enhancements

Features

Discounts by product date and activity time added to Aspenware Commerce

Aspenware Commerce has extended the basic promotion feature to include products with a date and activity time (such as tee times). Now administrators can assign promotions to particular dates and particular times of day - such as before 9AM or after 4PM. Administrators can also add exclusion dates, such as holidays. Discounts can be in dollars or percentage off per player (e.g. $10 or 10%), or be a fixed price discount (e.g. $89). To configure this product see the Aspenware Commerce Discounts Documentation.

New functionality for RTP-Unity customers who do not use RTP|Connect

Previously RTP-Aspenware Commerce customers without RTP|Connect could not take advantage of some services. Now Aspenware Commerce customers can do the following with Unity only (without requiring RTP|Connect):

• Payment plan products for season passes

• Product prompts