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 |
Key Terms
While Aspenware does not provide Payeezy terminal configuration support to its Payeezy resorts, the following key terms and screenshots are shown so that resorts can see how the information Aspenware sends to Payeezy is used and displayed in Payeezy, and which transaction type displays the AVS results.
Auth Only
Payeezy can enable or disable terminals to allow $0 auth only transactions. All merchants using Payeezy with Aspenware must have the $0 auth only transaction type enabled. This setting is requested when the merchant is onboarded with Payeezy. Aspenware’s integration to Payeezy uses the $0 Auth Only request to send AVS details to Payeezy, and it is on this transaction type that the merchant can see the AVS results for an authorization request. This transaction type is not used for payment plan scheduled payments.
Pre-Authorization
Payeezy has a transaction type for pre-authorizations, which checks the cardholder’s credit limit first to ensure the cardholder has adequate funds for the amount in the request. This transaction type is not used for payment plan scheduled payments.
Tagged Completion
Payeezy’s transaction type for charges which succeed is Tagged Completion. This Transaction type is not used for payment plan scheduled payments.
Purchase
This transaction type is used for Payment Plan Scheduled payments.
This screenshot displays the Auth Only, Pre-Auth, and Tagged Completion transaction types in the Payeezy sandbox, and which transaction type displays the AVS results:
This screenshot displays the uncollapsed view of the $0 Auth Only request for a transaction which is approved because it passes AVS using Payeezy’s AVS filter 1 (Cardholder name matches)
This screenshot displays the uncollapsed view of an authorization request which is rejected because the terminal configuration in Payeezy uses AVS filter N (No Address or ZIP Code match)
This screenshot shows the message displayed to the guest in Aspenware Commerce who does not pass AVS in Payeezy. Aspenware intentionally returns a general message ‘Credit Card Validation Address Not Verified’ message. The reason the general error is displayed, rather than a more specific error message such as ‘Street Address matches, ZIP code does not’ is because this reveals too much detail to a malicious user.
This screenshot shows the Purchase transaction type, which is used in payment plan scheduled payments:
Detailed Setup Guide
This section describes all required steps to set up the feature after prerequisite tasks have been completed.
POS Tasks
Decide if you are syncing credit cards to RTP|One. (Tokenized RTP|One DB required)
Complete POS accounting tasks for products sold online.
Ensure that you are using a tokenized version of RTP|One with CardDog/TRI/First Data.
Infrastructure Tasks
If RTP|One version is 2016 or later AND RTP|One is tokenized, work with your Aspenware Representative to validate the following credit-related settings in the Unity rtp-config.json:
UsePaymentCardTokenTable = TRUE
EncryptPaymentCardTokenValue = FALSE
These settings DO NOT apply if you are running pre-2016 RTP and it is not tokenized.
If running a version of Aspenware Commerce earlier than 2.27, your representative will also need to validate these settings in the Azure appsettings.json file:
AllowStorageOfCC = TRUE
AllowTransferOfCC = TRUE if RTP 2016+ AND RTP is tokenized, FALSE if RTP is pre-2016 AND RTP is not tokenized
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
Follow Payeezy Getting Started Guide.
Set up a merchant account on the Payeezy site to get a Merchant ID.
Contact Aspenware Representative to set up an API dev account.
Add Merchant to Aspenware dev account by emailing Payeezy. Email payeezyboarding@firstdata.com to request having the client added as a merchant on our dev account. Include:
Customer’s Merchant ID
DBA name
Developer account email address: Rt.clark@aspenware.com
Payeezy will confirm the request and follow up with an email (May take a few days)
Then, Submit PaymentJS integration request following these steps under Step 4 in this guide exactly
When integration request complete, Email Payeezy to Confirm Values Match Merchant account values. (only required if issues with payment)
Once done Aspenware will get API key, API Secret, JS Key, and Token from the Payeezy developer account.
Obtain TaToken from Payeezy and make note of this for future Commerce configuration.
The transarmor token (tatoken) can be located in customer’s existing Payeezy account by logging in at https://globalgatewaye4.firstdata.com/terminal and clicking on the terminal to view the details. The TA token will be a 4 character code.
If using CVV2 verification (recommended)
Complete the steps within Step 7 in this guide.
If enabling Velocity Controls in Payeezy (recommended)
From within your Payeezy Admin screen, go to Admin > Terminals > Velocity Controls.
Set the Maximum # of Transactions per Card/Check No. to ‘10’. Based on ‘All Transactions’ within the duration of ‘1 Day’. Set the action to ‘Decline’.
Set the Maximum # of Transactions per IP to ‘10’. Based on ‘All Transactions’ within the duration of ‘1 Day’. Set the action to ‘Decline’. And Save.
Configure AVS filters for the merchant’s terminal in Payeezy. Aspenware sends all consumer-entered billing address information to Payeezy on the authorization request, which occurs prior to the cardholder being charged. This enables Payeezy to use that consumer-entered address information to either reject or allow the authorization request.
NOTE: The decision about which AVS filters are selected in Payeezy’s terminal configuration is entirely up to each resort administrator and accounting team. Aspenware will not dictate or recommend the use of any specific Payeezy AVS filters. This decision is solely up to each resort, working with Payeezy support.
See the following articles from Payeezy regarding AVS.
NOTE: All Aspenware resorts use the Aspenware Commerce demo account in the sandbox, so please contact your client service representative to view sandbox test results.
Change Payeezy from test to live when ready: To process live transactions, your APIs will need to be configured as follows:
Log into https://developer.payeezy.com
Navigate to the “APIs” page
Select your API and then
“Edit <API>”
Make sure that ‘Live’ is checked.
Commerce Tasks
1. Update Settings
If you are on version 2.27 or later, update the following settings in Commerce Admin.
Go to Configuration > Settings > All settings (advanced)
Search for ecommercesettings.allowtransferofcc
Click Edit.
If you are running RTP|One 2016+ AND RTP|One is tokenized, set the Value to TRUE.
If you are running an earlier version of RTP|One and it is non-tokenized, set the Value to FALSE.
Click Update.
Search for ecommercesettings.allowstorageofcc
Click Edit.
Set the Value to TRUE.
Click Update.
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 the Configuration > Payment > Payment Methods page.
Click Edit on the Payeezy payment gateway.
Check Is active on the desired payment method and click Save. Ensure that only the desired payment method is set to ‘is active.’
Select ‘Configure’ on the desired payment method.
Complete the following fields:
Use Sandbox: - Should be checked for ‘test’ and unchecked for ‘prod’
API Key: Obtain from Aspenware Payeezy developer Account
API Secret: Obtain from Aspenware Payeezy developer Account under the API tab
JS Key: Obtain from Aspenware Payeezy developer Account under the API tab
TaToken: Obtained in previous step above or get from Resort’s Payeezy account
Token: Obtain from Aspenware Payeezy developer Account under the Merchants tab
Requires Billing Address: This is likely required, so check to make sure it is collected for checkout.
Requires Phone Number: Check if phone number is required at checkout.
Click Save.
3. Disable Update Credit Card Feature
Disable the “Update Credit Card” feature in My Account (this feature is not supported by Payeezy). 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.
4. Test Payment Method
Test a live credit card for each type of accepted credit card (Visa, Amex, Discover, Mastercard) to ensure the gateway is processing payments properly once setup is completed.
Common Troubleshooting
Q; I set up address verification settings in my Payeezy portal and it’s not enforcing AVS for online orders.
A: We support CVV2 in all versions. (Set up guide within Step 7). We support AVS in version 2.16 or later. We strongly encourage customers upgrading to 2.16 who use Payeezy as a payment gateway. For more details on AVS, check out this article.
Q: Why is it required to close the store every time Aspenware does a deployment because I am on Payeezy?
A: As part of Aspenware’s push certification process a live credit check and confirmation is required before we “flip” the new version live. Typically Aspenware will run these tests in a staging environment prior to flipping the code live, however, because Payeezy has added security measures that require that the domain a payment is made from match the prod domain (i.e. shop.yourresort.com) this check cannot be made in staging. Our process for this check for Payeezy customers is to flip the new code live, close the store, run the transaction. As soon as the resort accounting contact confirms that they see the transaction in the Payeezy gateway, we open the store back up.
Q: We have been hearing from guests that they can not use Discover cards to buy products online.
Looks like you need to set the config to accept Discover cards:
See Step 8c in this reference resource.
Uncheck the S code on cvv2 filters if you want to accept Discover (in Payeezy):
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|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: Why can’t I sign up to move to Payeezy as Payment Gateway any longer?
A: Unfortunately, Payeezy announced that they are not taking any additional customers as of Jan 2021. If you were already migrated to use Payeezy as a payment provider, your functionality is not impacted, but new customers cannot choose this payment gateway, unfortunately.
Q: What functionality is and isn’t available to me because of having Payeezy as a Payment Provider?
A: Good news is that using Payeezy allows you to enable a number of advanced features, most notably Payment Plans and Subscriptions. Because Payeezy is the tokenization provider for RTP|One, if RTP|One is your POS, resorts that use Payeezy can offer guests resort charge, direct to lift, and capturing tokens for refunds in the POS. Note that the “Update Credit Card” feature on My Account is NOT supported with Payeezy. Apple Pay, Google Pay, Pay Pal, and Storing CC for future purchases are NOT currently supported with Payeezy.
Q: I’m moving to tokenization in RTP|One, what’s the process for syncing the tokens from the e-commerce store to RTP|One for resort charge and returns?
A: Follow the three steps below to sync tokens.
Step 1: Resort needs to tokenize their RTP|One database.
Step 2: Once that is done, you will need to update the 'ecommerce.allowtransferofCC' setting from false to true. Aspenware needs to validate the credit-related settings in the UnityPeakProd rtp-config.json when that switch occurs.
Step 3: Test it. Testing should include verifying the RTP|One Credit Card Profile visually looks correct and that the data in the PaymentCardToken table looks good. A 'charge to the card on file' and a return should also be performed in RTP|One to verify those are working (and maybe an auto-charge too if Copper does this but the card on file test may be sufficient).