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 10 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. REQUIRED

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

  • Ensure that you are using a tokenized version of RTP|One with CardDog/TRI/First Data. 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

  • Determing if ApplePay, GooglePay or PayPal will be used. REQUIRED

  • Configure GooglePay in Braintree OPTIONAL

  • Configure ApplePay in Braintree OPTIONAL

DETAILED SETUP

4. COMMERCE TASKS

  • Set up GL Report. REQUIRED

  • Configure Aspenware Commerce Payment Gateway REQUIRED

DETAILED SETUP

Detailed Setup Guide

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 tokenized version of RTP|One with CardDog/TRI/First Data.

INFRASTRUCTURE TASKS

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

  • 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

  • Determine which additional payment methods will be supported for your resort. Possibilities include:

    • PayPal

    • ApplePay

    • GooglePay

  • (Optional) Configure GooglePay in Braintree

    • Use debug merchant IDfor test: 01234567890123456789

    • In production Braintree go to Settings > Processing > Google Pay and enable Google Pay. 

    • In production, you'll also need to submit a support request with Google to register your domain and receive a merchant ID. - fill out this form: https://services.google.com/fb/forms/googlepaymentAPI/

    • Send Aspenware test site and production site to Google

    • Google approves submissions for APIs. They will need to ensure it adheres to their Acceptable Use Policy

    • Once approved, you’ll send Google an email address to be used for production access.

    • Once they approve you, you can sign up for a developer account payments.developers.google.com/signup 

    • Send Aspenware your merchant ID.

  • (Optional) Configure ApplePay in Braintree

    • Set up Apple Developer Account and Merchant and Certificate and upload your Certificate in Braintree.

    • Download the Certificate Signing Request https://www.braintreegateway.com/merchants/xgw9z8r4t7g55n5g/processing/apple_pay/csr 

    • Sign in to your Developer Center in Safari. (You may need an Apple Developer Account to do this.)

    • Create an Apple Pay Merchant ID - You'll first need a developer center account to do this I believe. They recommend using separate Apple Pay Merchant IDs for sandbox and production to ensure that your sandbox app cannot create production transactions.

    • Generate a new Apple Pay Certificate in Apple's developer portal - again you'll do this within your developer center.

    • Select Apple Pay Certificate and click Continue.

    • In the drop-down, choose the appropriate Apple Merchant ID for your Braintree environment (Sandbox or Production) and click Continue.

    • Under Payment Processing Certificate, click Create Certificate.

    • Upload the CSR that you downloaded from Braintree in the first step above. You must use the CSR we provide. Do not create a CSR file yourself.

    • Download the new Apple Pay Certificate and upload it when setting up Apple Pay in Braintree go to Settings > Processing > Apple Pay

    • Then host the domain association file from Apple on the shop.

ASPENWARE COMMERCE TASKS

  • Set up 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 Braintree payment gateway.

  • Check Is active the for Braintree and Save.  Ensure that only Braintree is set to Is active.

  • Select Configure on the Braintree payment method. 

  • To change or set up payment account, fill in the following fields:

    • Use Sandbox: Should be checked for test and unchecked for prod

    • Merchant ID: Obtain from Braintree

    • Private Key:  Obtain from Braintree

    • Public Key: Obtain from Braintree

    • Additional Fee: Set to 0.00

    • Additional fee. Use percentage: Unchecked

    • Requires Billing Address: Unchecked

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

Common Troubleshooting

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