Versions Compared

Key

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

...

REQUIREDfile is set up properly. (These two settings are not needed if you are running a version of RTP earlier than 2016 and RTP is not tokenized.) Ensure the following settings are set:

1. POS Tasks

  • Decide if you are syncing credit cards to RTP|One. (Tokenized RTP|One DB required)

    Status
    colourRed
    titlerequired

  • Complete POS accounting tasks for products sold online

    Status
    colourRed
    titleREQUIRED

  • Ensure that you are using a tokenized version of RTP|One with CardDog/TRI/First Data.

    Status
    colourRed
    titleREQUIRED

  • If storing primary CC for resort charge and DTL, ensure resort charge Authorization and other configuration is complete.

    Status
    colourBlue
    titleOptional

Status
colourGreen
titledetailed setup

2. Infrastructure Tasks

  • Validate the credit-related settings in the UnityPeakProd If you are on RTP 2016+ and RTP is tokenized then work with your Aspenware Representative to ensure that the Unity rtp-config.json when that switch occurs.  

Status
colourRed
title
Status
colourRed
titleREQUIRED

  • EncryptPaymentCardTokenValue = FALSE

  • UsePaymentCardTokenTable = TRUE

  • Validate the credit related settings in the Unity 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. 

    Status
    colourRed
    titleREQUIRED

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

    Status
    colourRed
    titleREQUIRED

  • Status
    colourGreen
    titledetailed setup

    3. Payment Provider Tasks

    • Set up Payeezy and Complete Configuration to allow your Aspenware Commerce test and prod stores to use your sandbox and production Payeezy.

      Status
      colourRed
      titleRequired

    • If using CVV verification (recommended), ensure that CVV filter settings are configured for the terminal according to instructions below.

      Status
      colourBlue
      titleOptional

    • If using CVV verification (recommended), ensure that Payeezy/FirstData have enabled $0 authorizations for the terminal used by the store.  

      Status
      colourBlue
      titleOptional

    Status
    colourGreen
    titledetailed setup

    4. Commerce Tasks

    • Update Settings

      • ecommercesettings.allowtransferofcc

      • ecommercesettings.allowstorageofcc

    • Set up GL report with your Aspenware Representative.

      Status
      colourRed
      titlerequired

    • Configure Aspenware Commerce Payment Gateway

      Status
      colourRed
      titleRequired

    Status
    colourGreen
    titledetailed setup

    ...

    • 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 you are on RTP 2016+ and RTP is tokenized then work with your Aspenware Representative to ensure that the Unity rtp-config.json file is set up properly. (These two settings are not needed if you are running a version of RTP earlier than 2016 and RTP is not tokenized.) Ensure the following settings are set:

      Status
      colourRed
      titleREQUIRED

      • EncryptPaymentCardTokenValue = FALSE

      • UsePaymentCardTokenTable = TRUE

      • Validate the credit related settings in the

      UnityPeakProd
      • Unity rtp-config.json

      when that switch occurs.  
      • when that switch occurs.  

    Info

    NOTE: These two settings are not needed if you are running a version of RTP earlier than 2016 and RTP is not tokenized.

    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.

    ...

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

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

    ...

    Commerce Tasks

    1. Update Settings

    Determine if you will be using Aspenware Payment Plans with your Payeezy implementation before updating If you are on version 2.27 or later, update the following settings in Commerce Admin.

    • Go to Configuration > Settings > All settings (advanced)

      1. Search for ecommercesettings.allowtransferofcc

        Image Modified

        1. Click Edit.

      Image Removed

      Set

        1. Image Added

        2. If you are running RTP|One 2016+ AND RTP|One is tokenized, set the Value to TRUE.

        3. If you are running an earlier version of RTP|One and it is non-tokenized, set the Value to FALSE

      and click
        1. .

        2. Click Update.

          Image Modified

      1. Search for ecommercesettings.allowstorageofcc

        Image Modified

        1. Click Edit.

          Image Modified

        2. Set the Value

      as follows:
      1. If Using Aspenware Payment Plans, set to FALSE

      2. If NOT using Aspenware Payment plans, set to TRUE

        Image Removed
      Click Update
        1. to TRUE.

          Image Added
        2. Click Update.

    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 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:

      1. Use Sandbox: - Should be checked for ‘test’ and unchecked for ‘prod’

      2. API Key: Obtain from Aspenware Payeezy developer Account

      3. API Secret: Obtain from Aspenware Payeezy developer Account under the API tab

      4. JS Key: Obtain from Aspenware Payeezy developer Account under the API tab

      5. TaToken: Obtained in previous step above or get from Resort’s Payeezy account

      6. Token: Obtain from Aspenware Payeezy developer Account under the Merchants tab

      7. Requires Billing Address: This is likely required, so check to make sure it is collected for checkout.  

      8. Requires Phone Number: Check if phone number is required at checkout.

        Image Modified
    • 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

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

      2. Search for the setting customersettings.hideresortchargetab

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

      4. Click Update to save the setting change.

        Image Modified
    • 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 Modified
      4. 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.

    ...

    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

    ...

    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, we you will need to update the Azure appsettings to 'AllowTransferofCC' 'ecommerce.allowtransferofCC' setting from false to true.  The Aspenware needs to validate the credit-related settings in the UnityPeakProd rtp-config.json should also be validated 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). Insert excerptLike this Page ExcerptLike this Page Excerptnopaneltrue

    ...