Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

Setup Checklist

Insert excerpt
AE:Set-up ChecklistAE:
Set-up Checklist
nopaneltrue

1. POS

TASKS POS Task 1

Tasks

  • Decide if you are syncing credit cards to RTP|One.

    Status
    colour

Red
  • Blue
    title

Required Expand
titleExample of POS Task
Products that need age ranges assigned are created in POS and have age ranges added to POS
  • OPTIONAL

  • Complete POS accounting tasks for products sold online needs to be completed

    Status
    colour

YellowInfrastructure Task 2 -
  • Red
    title

Prerequisite

2. INFRASTRUCTURE TASKS

  • REQUIRED

  • Ensure that you are using a non tokenized version of RTP|One (If RTP|One is tokenized, consider a tokenized credit provider)

    Status
    colourRed
    titlerequired

Required

Status
colour

expand

Green
title

Example of Infrastructure Task​Confirm that the Azure function app is setup and configured to the desired frequency. -

dETAILED SETUP

2. Infrastructure Tasks

  • Work with your Aspenware Representative to ensure that the Unity rtp-config.json file is setup properly. Ensure the following settings are set:

    Status
    colourRed
    titlerequired

Required

Status
colourYellow
titlePrerequisite

3. COMMERCE TASKS

Commerce Task 3 -
    • EncryptPaymentCardTokenValue = TRUE

    • UsePaymentCardTokenTable = TRUE

    • Validate the credit related settings in the Unity rtp-config.json when that switch occurs.  

  • If on a version earlier than 2.27, your Aspenware Representative will also need to set the following in the Azure appsettings.json file:

    • AllowStorageOfCC = TRUE

    • AllowTransferOfCC = TRUE

  • Testing should include verifying the RTP|One Credit Card Profile visually looks correct and that the data in the PaymentCardToken table looks good. 

    Status
    colourRed
    title

Required Expand
titleExample of Commerce Task
Confirm that the Aspenware Commerce products that will have inventory assigned to them are fully configured with the correct attributes -
  • required

  • Perform a 'charge to the card on file' and a return to verify those are working.

    Status
    colourRed
    title

Required
  • required

Status
colour

Yellow

Green
title

Prerequisite

Language String, Setting, HTML widget, etc. Task 4 -

Status
colourBlue
titleoptional

Expand
titleExample of Setting Task
​Ensure the setting ‘ecommercesettings.productinventory.cachetime’ is set to your desired cache time -

detailed setup

3. Payment Provider Tasks

  • Set Up Authorize.net

    Status
    colour

Blue
  • Red
    title

optional
  • required

Status
colour

Yellow

Green
title

Prerequisite

Configuration Task 5 -

Status
colourRed
titleRequired

Expand
titleExample of Configuration Task
Inventory is mapped to product or product variant in the Inventory Pool plugin

detailed setup

4. Commerce Tasks

  • If on a version 2.27 or later, set the following settings in Admin:

    Status
    colourRed
    title

Required

Code is entered

Status
colourRed
titleRequired

If using location in RTP, location code is entered
  • required

    • AllowStorageOfCC = TRUE

    • AllowTransferOfCC = TRUE

  • Set up GL Report.

    Status
    colourRed
    title

RequiredIf multi day product, number of days is defined
  • required

  • Configure Aspenware Commerce Payment Gateway

    Status
    colourRed
    titleRequired

If using non default lock time of 900 seconds, the desired lock time is configured.

Status
colour

Blue

Green
title

optional

Status
colourGreen
titleDetailed Setup

...

detailed setup

Detailed Setup Guide

Insert excerpt
AE:Prerequisites Tasks ExcerptAE:Prerequisites Tasks Detailed Setup Guide Excerpt
Detailed Setup Guide Excerpt
nopaneltrue

POS Tasks

  • POS Task that must be completed first

Infrastructure Tasks

  • Infrastructure Task that must be completed first. Remove section if not required

Commerce Tasks

  • AW Commerce task that must be completed first

Settings, Language Strings and/or HTML Widgets for this Feature

...

Settings

  • AW Commerce Settings that must first be completed

Language Strings

  • AW Commerce Language Strings that must first be completed

HTML Widgets

  • AW Commerce HTML Widgets that must first be completed

Detailed Setup Guide

  1. Step 1 Header

  2. Step 2 Header

1. Step 1 Header

  • First bullet should provide navigation instructions i.e. Catalog >Attributes >Product attributes

    1. Sub-bullet for step 1. Every step and click should be detailed so that someone could follow with little prior experience.

      1. Sub-bullet for step a. Include screenshots of the step and use skitch to mark up screenshots. It can be downloaded here: https://www.techspot.com/downloads/5705-skitch.html

Expand
titleExample of content within a section
  • From the Aspenware Commerce Plugins>Age Range page in Admin, click View Add Range Types in the upper right corner.

  • Click Add Age Range Type.

  • Enter a name and description for the age range type.

  • To set the date used to compare the customer’s age to the required age range, select:

    1. Calculate from Trip Start (this age range type is likely already configured), or 

    2. Calculate from Today’s Date (age range based on purchase date), or

    3. Specify the Calculation Start Date; the customer’s age on this date will be used to determine if they are eligible for the product based on the age ranges

  • Click Add.

  • Age Range Types can be edited and inactivated, but they cannot be hard deleted without contacting Aspenware. 

  • Age Range types that are set to Calculate from Trip Start or Today’s Date will never need to be edited, unless you would like to edit the name. Age Range Types that are calculated from a fixed date however, will need to be edited each year to adjust for the current year.

Image Removed

 

Hint: Age Range Types should also be adjusted year over year. If age ranges are calculated based on Trip Start, then they will not need to be updated.

Once completed for all required age range types move on to create Age Range.

Info

Note: When possible use notes, warnings, and hints within info panel macros. See https://aspenware.atlassian.net/wiki/pages/resumedraft.action?draftId=781156460 for more details on these.

2. Step 2 Header

  • First bullet should provide navigation instructions i.e. Catalog >Attributes >Product attributes

    1. Sub-bullet for step 1

      1. Sub-bullet for step a

...

DELETE CONTENT AFTER THIS LINE

go to the Glossary page and add the key terms Excerpt Include that you added for your configuration guide.

To add the feature terms to the Glossary, navigate to the glossary and add a header for your feature using an H2. Select the + and then select …view more. Search for Excerpt Include and in the Page Containing the Excerpt search for “Configuration: [FEATURE]” select to hide panel, preview and add.

How-to Guide of this page can be found here: [Internal] Configuration page Setup Guide

...

  • Determine whether or not your resort will be syncing credit cards to RTP|One.

  • Complete POS accounting tasks for products sold online needs to be completed.

  • Ensure that you are using a non-tokenized version of RTP|One. If RTP|One is tokenized, consider a different payment provider.

Infrastructure Tasks

  • Work with your Aspenware Representative to ensure that the Unity rtp-config.json appsettings.json file is set properly. Ensure the following settings are set accordingly:

    • EncryptPaymentCardTokenValue = TRUE

    • UsePaymentCardTokenTable = TRUE

    • Validate the credit-related settings in the Unity rtp-config.json when that switch occurs.  

  • If on a version earlier than 2.27, your Aspenware Representative will also need to set the following:

    • AllowStorageOfCC = TRUE

    • AllowTransferOfCC = TRUE

Note

IMPORTANT: AllowStorageofCC must be set to TRUE for the GL Export function to work.

  • Testing should include verifying the RTP|One Credit Card Profile visually looks correct and that the data in the PaymentCardToken table looks good. 

  • Perform a 'charge to the card on file' and a return to verify those are working.

Payment Provider Tasks

  • Create an Authorize.net account if you haven’t already done so.

  • Follow Authorize.net Getting Started Guide.

  • Send the following to Aspenware:

    • Your payment gateway ID

    • Transaction Key

    • Login

  • Within Authorize.net, on the system info tab check the "Active" check box to make the payment method active so you can accept payment using Credit Cards.

  • Set Authorize.net Fraud Detection Suite settings:

    • Hourly Velocity Filter - by default set to 100 transactions per hour

Note

IMPORTANT: It is recommended to disable the Hourly Velocity setting or set it to a larger number. This has caused production issues in the past.

Info

NOTE: Your MSP is the company that acts as your financial institution. The MSP deposits funds into your bank account and maintains your Merchant Account. They are also the company that charges you the percentage discount rate on your batch settlements. For more information on this subject, see the Support Article about MSP and their role in the payment process.

Commerce Tasks

1. Update Settings (for version 2.27 or later)

If you are running version 2.27 or later, you will need to update 2 credit card settings.

  • Go to Configuration > Settings > All settings

  • Search for “ofccC” to find AllowStorageOfCC and AllowTransferOfCC settings

    Image Added
  • Both settings should be set to TRUE. Click Edit to update settings as needed.

Note

IMPORTANT: AllowStorageofCC must be set to TRUE for the GL Export function to work.

2. Set Up GL Report

Work with your Aspenware Representative to set up the GL Report so you can reconcile GL reporting in the POS and payment gateway.

3. Configure Payment Method

  • Go to Configuration > Payment Methods in Admin.

  • Click Edit on the Authorize.net payment gateway.

  • Check Is active and Save.  Ensure that only Authorize.net is set to ‘Is active.’

  • Select Configure on the Authorize.net payment method. 

  • To change or set up payment account, fill in the following fields:

    1. Use Sandbox: Should be checked for test and unchecked for production

    2. UseShippingAddressAsBilling: Unchecked

    3. Transaction Mode Values: Set to ‘Authorize and Capture’

    4. Transaction Key: Obtain from Authorize.net

    5. Login ID: Obtain from Authorize.net

    6. Additional Fee: Set to 0.00

    7. Additional Fee Percentage: Uncheck

    8. Requires Billing Address: Likely checked, but verify to be sure that it is required for checkout.  

    9. Requires Phone Number: Unchecked

      Image Added
  • Click Save.

4. Disable Update Credit Card Feature

The functionality to update a credit card through the customer’s My Account page is not supported with Authorize.net. Therefore, the Resort Charge Tab on My Account needs to be disabled. This can be done in one of two ways:

  • Method One

    1. Go to Configuration > Settings > All settings (Advanced).

    2. Search for the setting customersettings.hideresortchargetab

      Image Added
    3. Click Edit and change the setting value to TRUE to hide the tab.

    4. Click Update to save the setting change.

      Image Added
  • Method Two

    1. Go to Configuration > Customer Settings.

    2. Scroll down to Additional Customer Settings.

    3. Check the Hide Resort Charge Tab checkbox to hide the tab.

      Image Added
    4. Click Save.

5. Test Payment Method

Test a live credit card for each type of accepted credit card (Visa, Amex, Discover, Mastercard) to ensure gateway is processing payments properly once setup is completed. 

Info

NOTE: Amex requires additional steps when configuring Authorize.net, so it is important not to skip testing Amex for live credit once configured. If Amex is declining but the other card types are working, reach out to Authorize.net support.

Common Troubleshooting

Q: What functionality is and isn’t available to me because of having Authorize.net as a Payment Provider?

A: Because Authorize.net encrypted credit cards can be stored in RTP|One as an alternate and primary credit card, functionality that is made possible by having a cc stored in RTP|One is supported. This functionality includes direct to lift product configurations and native RTP|One payment plans. Capturing cc for refunds in the POS is also supported. Unfortunately, because Authorize.net is not a tokenized provider, Aspenware has not and will not support a number of advanced features, most notably Aspenware Payment Plans and Subscriptions. Also, Apple Pay, Google Pay, Pay Pal, and storing CC for future e-commerce purchases is not currently supported with Authorize.net.

Q: When I look at an order status in Aspenware Commerce Order Details, the status is set to pending rather than complete? What’s wrong with this order?

A:  The true indicator of whether a product made it to RTP|One successfully is the order queue. If you see orders showing as Pending in the Sales>Orders area, check if any products in these orders have Shipping checked on the product editor


...


This won't cause problems per-say but is really only used for retail products that are shipped, so it shouldn't be checked.  Because nopCommerce is often used as a retail platform, what processing means in nopCommerce is similar to what Open means in RTP|One. The order is paid for, but the order has not been fulfilled, aka shipped. For ski, we send the order to RTP|One for fulfillment and don't do any fulfillment in nopCommerce - we use the delivery plugin for shipping ski media and ignore nopCommerce shipping, so it's not a problem, but my guess is that if you uncheck shipping on these products and save it, you will start seeing these orders show as completed.

Q: When a customer updates their credit card for resort charge from My Account, it isn’t working. What’s going on?

A: Unfortunately, Authorize.net doesn’t support this feature. See Step 3 above to hide the Resort Charge tab in My Account to avoid confusion.

Insert excerpt
Like this Page Excerpt
Like this Page Excerpt
nopaneltrue

...