Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents

Setup Checklist

...

Table of Contents

Setup Checklist

Insert excerpt
Set-up Checklist
Set-up Checklist
nopaneltrue

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

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

    • Update the store’s appsettings.json under the Ecommerce node.  The store application service must be restarted after changing any value in appsettings.json.

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

        Status
        colourRed
        titleREQUIRED

      Ensure that you are using a tokenized version of RTP|One with CardDog/TRI/First Data.
      • Update the Azure appsettings to 'AllowTransferofCC' from false to true and give it a test. 

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

      Status
      colourRed
      titleREQUIRED
      If

    • storing primary CC for resort charge and DTL, ensure resort charge Authorization and other configuration is complete. Testing should include verifying the RTP|One Credit Card Profile visually looks correct and that the data in the PaymentCardToken table looks good. 

      Status
      Optional
      colourBlueRed
      titleREQUIRED

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

      Status
      colour

    Green
    • Update the store’s appsettings.json under the Ecommerce node.  The store application service must be restarted after changing any value in appsettings.json.

      Update the Azure appsettings to 'AllowStorageofCC' from false to true and give it a test. 

      Red
      title

    detailed setup

    2. Infrastructure Tasks

    • REQUIRED

    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. Validate the credit-related settings in the UnityPeakProd rtp-config.json when that switch occurs

      Status
      colourRed
      title

    REQUIRED
    Required

  • 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
    Red
    colourBlue
    titleOptional

  • Status
    colourGreen
    title

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

    detailed setup

    4. Commerce Tasks

    • Set up GL report with your Aspenware Representative.

      Status
      colourRed
      titleREQUIRED
      Perform a 'charge to the card on file' in the POS and a return to verify those are working.
      required

    • Configure Aspenware Commerce Payment Gateway

      Status
      colourRed
      titleREQUIREDRequired

    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

    • Set up GL report with your Aspenware Representative.

      Status
      colourRed
      titlerequired

    • Configure Aspenware Commerce Payment Gateway

      Status
      colourRed
      titleRequired

    Status
    colourGreen
    titledetailed setup

    Key Terms

    ...

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

    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 :

    ...

    This screenshot displays the uncollapsed view of 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.

    ...

    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.

    ...

    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

    ...

    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

    • 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

    ...

    Follow Payeezy getting started guide: https://docs.google.com/document/d/1vgCMI3bYbUNYWVL4gtMcgLggubwelRp99o3qGaoKTHk/edit?usp=sharing

    ...

    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)

    ...

    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.

      Image Removed

    ...

    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.

    Info

    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 this Payeezy article for a general overview on AVS:

    See this article on AVS filters and how to set them up in Payeezy:

    See this article on how to test AVS filters in the sandbox. 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

    ...

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

    ...

    Click Save.

    ...

    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

    Insert excerpt
    Detailed Setup Guide Excerpt
    Detailed Setup Guide Excerpt
    nopaneltrue

    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

    • 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

    • Follow Payeezy getting started guide: https://docs.google.com/document/d/1vgCMI3bYbUNYWVL4gtMcgLggubwelRp99o3qGaoKTHk/edit?usp=sharing

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

        Image Added

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

    Info

    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 this Payeezy article for a general overview on AVS:

    See this article on AVS filters and how to set them up in Payeezy:

    See this article on how to test AVS filters in the sandbox. 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. 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.

    2. 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 Added
    • 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 Added
      3. Click Edit and change the setting value to TRUE to hide the tab.

      4. Click Update to save the setting change.

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

    ...

    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.

    ...