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 and support for payment plans for Siriusware customers. We’ve also upgraded Payeezy customers to v2 just in time! We’ve also resolved login and failed order issues, among other requests that you have found important. See below for more specifics on what we’ve been up.

• Payeezy v2 - 2137, 3009, 3142

• RTP Login issues: 2738, 3053, 3211, 3018, 3031, 3079, 2726

• SW login issues - 3136, 2879, 3019,

• Golf discounts - 2490, 3023

• Siriusware payment plan support: 2904, 3007, 3008, 3025, 2684

• RTP payment plan support for unity - 3113

• 2921 - similar issue 3114

• 3084

• Kount- 3087, 3170, 3171 may want to check this entry

• 1536

• 2637

• 2643

• RTP Failed order issue: 2853, 3106

• SW failed order issues - 2783

• 2082

• 1569

• 3045

• 3047

• 2758

• 2859

• 3086

• 2879

Updates, Features, and Upgrades

Payeezy V2 (2137, 3009, 3142)

Discounts by Product Date and Activity Time (Tee Time)

Siriusware Payment Plan Support

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, saving a resort charge credit card as a primary credit card were saved incorrectly, causing them to display wihth .

• Pass media prefix not respected

  • Previously, some customers would be able to reoload their invalid media. Now, a prefix check will require those with invalid media to purchase new media and correct prefixes to reload.

• Kount

  • Previously, issues in Kount were preventing orderId and success status from being updated after payment had process. 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.

• Confirmation email showing extra zeroes

  • Resolved issue with certain confirmation emails showing two extra zeroes on the end of reservation price.

Enhancement

• Authorize.NET

  • 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 duplicate transactions within a brief amount of time (about two minutes) 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 reservations with future payment). Now, a “requires credit card” product classification has been added in Aspenware Commerice that can be assigned to any product.

Things to Look Forward to

Kount fraud protection with Authorize.net

Resort Charge (My Account page)

Bulk payment processing (Payment Plans)

Subscriptions

Features

Payeezy V2 (2137, 3009, 3142)

In preparation for the March 15th cutoff. Aspenware Commerce has upgraded all customers using Payeezy to payment.js version 2. Payment.js allows merchants working with Payeezy APIs and gateways “to tokenize payment credentials for later transactions without collecting, processing, or otherwise being able to view those payment credentials in their untokenized form, thus lowering their PCI compliance requirements.” For more information see: https://docs.paymentjs.firstdata.com/

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).

Payment Plan Support (Siriusware)

Aspenware Commerce now supports Payment Plans for Siriusware. Products may now be configured to pay a partial amount at purchase (start) date, and equal monthly installments thereafter (until an assigned end date). The number of payments and the amount of each payment is based on the Siriusware ‘end date’ of the SW Payment Plan Rule. See configuration document for more information.

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

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

• Payment plan products with accurate price allocations (including lesson + lift packages) and tax calculations