Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

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

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

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

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

DETAILED SETUP

2. Infrastructure Tasks

  • Update the Azure appsettings to 'AllowTransferofCC' from false to true and give it a test. REQUIRED

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

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

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

DETAILED SETUP

3. Payment Provider Tasks

  • Set Up Authorize.net REQUIRED

DETAILED SETUP

4. Commerce Tasks

  • Set up GL Report. REQUIRED

  • Configure Aspenware Commerce Payment Gateway REQUIRED

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 two Azure settings in appsettings.json are set as follows:

    1. AllowStorageOfCC set to TRUE

    2. AllowTransferOfCC set to TRUE

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

  • 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: https://support.aspenware.com/en/support/solutions/articles/42000064328-getting-started-with-authorize-net

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

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 in the article below: https://support.authorize.net/s/article/What-Is-the-Difference-Between-Authorize-Net-My-Reseller-Processor-and-Merchant-Service-Provider-MSP-Who-Do-I-Contact-with-Concerns-Regarding-My-Transactions

Commerce Tasks

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

  • 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

  • Click Save.

  • 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 Auth.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 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 Nop is similar to what Open means in RTP. The order is paid for, but the order has not been fulfilled, aka shipped. For ski, we send the order to RTP for fulfillment and don't do any fulfillment in NOP - 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.

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.


  • No labels