Table of Contents |
---|
...
1. POS Tasks | |||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| ||||||||||||||||||||||||||||||
2. Infrastructure Tasks | |||||||||||||||||||||||||||||||
|
| ||||||||||||||||||||||||||||||
3. Payment Provider Tasks | |||||||||||||||||||||||||||||||
|
| ||||||||||||||||||||||||||||||
4. Commerce 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
Validate the 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 colour Red title REQUIRED EncryptPaymentCardTokenValue = FALSE
UsePaymentCardTokenTable = TRUE
Validate the credit related settings in the
Unity rtp-config.json 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:
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.
...
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)
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.
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:
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.
...
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
...
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 excerpt
...