Setup Checklist
This section is a comprehensive and high level summary of all tasks and prerequisites required for this feature to function properly. This section is purposed for use after an administrator is familiar with configuring this feature as an “audit” checklist. For detailed set-up instructions, jump down to “Prerequisite Tasks” and “Detailed Setup Guide” and then follow up with this checklist to ensure all steps are completed.
1. POS Tasks | |
|---|---|
| DETAILED SETUP |
2. Infrastructure Tasks | |
| DETAILED SETUP |
3. Payment Provider Tasks |
|
| DETAILED SETUP |
4. Commerce Tasks | |
| DETAILED SETUP |
Detailed Setup Guide
This section describes all required steps to set up the feature after prerequisite tasks have been completed.
POS Tasks
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 UnityPeakProd 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
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.
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
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.
Add Silent Post URL
Log in to your Authorize.Net account.
In your account settings specify the Silent Post URL. (http://www.yourStore.com/Plugins/PaymentAuthorizeNet/IPNHandler) This is what it should be for each resort.
Ensure Merchant Service Provider is set up to accept Authorize.net payment.
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
Both settings should be set to TRUE. Click Edit to update settings as needed.
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:
Use Sandbox: Should be checked for test and unchecked for production
UseShippingAddressAsBilling: Unchecked
Transaction Mode Values: Set to ‘Authorize and Capture’
Transaction Key: Obtain from Authorize.net
Login ID: Obtain from Authorize.net
Additional Fee: Set to 0.00
Additional Fee Percentage: Uncheck
Requires Billing Address: Likely checked, but verify to be sure that it is required for checkout.
Requires Phone Number: Unchecked
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
Go to Configuration > Settings > All settings (Advanced).
Search for the setting customersettings.hideresortchargetab
Click Edit and change the setting value to TRUE to hide the tab.
Click Update to save the setting change.
Method Two
Go to Configuration > Customer Settings.
Scroll down to Additional Customer Settings.
Check the Hide Resort Charge Tab checkbox to hide the tab.
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.
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.
Like this page? Click the like button below. Don't like this page and/or want to give feedback about this page, leave a comment below and Aspenware will address to improve this article.