Configuration: Payment Gateway - Authorize.net

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.

Prerequisite Tasks

This section describes all requirements that must be completed before you can begin setting up this feature. Once these tasks are complete continue to the next section.

POS Tasks

• POS Task that must be completed first

Infrastructure Tasks - STILL NEED TO EDIT

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

• 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 Aspenware your payment gateway ID.

• API Instructions:

  • Login to the application with Admin credentials.

  • Go to Administration section.

  • Go to Configuration -> Payment -> Payment Methods.

  • Click on the edit link on AuthorizeNet payment methods.

  • Click on the configuration tab. 

  • If you are going to use Sandbox (test) account the check ‘Use sandbox’ checkbox else leave it unchecked.

  • Select the transaction mode depending upon the requirement. If you want to just authorize the credit card the select ‘Authorize,' if you want to have actual payment instantly then go for ‘Authorize And Capture.’

  • Enter the Transaction key and Login ID which you get from Authorize.net account.

  • Click on save button

  • Send the following to Aspenware - It’s in an area on your account called “API” 

    • Transaction Key: 5t46R28dnBV3V8bk

    • Login: 8jC8FVH5u42

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

  • Once test is vetted, we will start testing in live and putting some real transactions through for .50 cents or so to make sure Authorize.net is hooked up correctly.

  • Authorize.net Fraud Detection Suite settings

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

    • May need to disable this setting or set it to a larger number if the customer expects this much traffic.

  • 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

    • The only other thing that could be causing all these transactions to decline with this response would be if there is something on your Merchant Service Provider (MSP)'s end that is causing this. 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, we have a great Support Article about your MSP and their role, vs our own, in the payment process. For your convenience, I have provided a link to this article below:

    • Please navigate to the next link: 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

    • I would recommend having the Merchant Service Provideron the line when you call. Please have them contact us at 877-447-3938. We are available 24 hours a day, 7 days a week (closed major holidays). Your Gateway ID is 2052951.

    • Please let them know they will need the last 4 of the bank on file, as well as the last 4 of the EIN (Tax ID) on file when they call to verify security. Please push option 5 to speak to someone.

  • You may also need to contact Merchant Service provider to help with accepting AMEX

    • After taking a look at your account, I can see that your gateway is set up to accept AMEX transactions. However, since these are receiving General Errors, it would seem that your Merchant Service Provider (MSP) has not yet enabled that card type on their end. 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.

  • Authorize.net Fraud Detection Suite settings

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

    • May need to disable this setting or set to a larger number if customer expects this much traffic.

Commerce Tasks

• AW Commerce task that must be completed first

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

This feature may require updates to the following settings, language strings and/or HTML Widgets. Learn more about how to update and create Settings, Language Strings, and HTML widgets follow the links to the respective section.

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

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

 

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.

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.

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

Real Example of this page can be found here: https://aspenware.atlassian.net/wiki/spaces/DB/pages/edit-v2/1037172926