Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. for subscriptions where the status is active, the admin can change the next payment date only if it’s a date in the future.

  2. for subscriptions where the status is frozen or canceled, the admin can set the next payment date to a future date, even if the next payment date is in the past. After the admin changes the next payment date to a future date, the admin must then also change the enrollment status to Active.

Billing Address

...

Collection now supported

...

with Square

...

payments (2.13.3)

Previously, if Square was configured as a payment provider, a full address beyond zip code could not be collected or synced for resorts using Square payments, it was not possible to collect a full billing address on the payment step, or to save that address information to the POS. Our Aspenware’s integration of the Square payment API does not have address verification beyond zipcode, and our integration still does not have address verification beyond zipcode, however, if desired, Billing Address can be collected on the payment step and synced to the POS. The downside of enabling this is that zip code will be asked for twiceto Square payments offers address verification for PostalCode/Zipcode only.

However, with this enhancement, it’s now possible to collect Billing Address on the payment step, and that address will be sent to the POS (either Siriusware or RTP|ONE) and saved to that guest’s address in the POS. *IMPORTANT: When this feature is enabled, the guest must enter the postal code twice, because the postal code collected for Square uses hosted fields. The full billing address fields, which save to the POS customer’s record, cannot use that same hosted PostalCode field. This feature can be enabled in Payment Method configuration in Aspenware Commerce Administration.

...

Resolved Issues

Private Lesson Comments Longer than 255 characters caused order failures

...