Configuration: Payment Gateway - Windcave
Setup Checklist
1. POS TASKS |
|
---|---|
Complete POS accounting tasks for products sold online. Required | Prerequisite |
2. PAYMENT PROVIDER TASKS | prerequisite |
|
|
3. COMMERCE TASKS |
|
Update Settings REQUIRED
| prerequisite |
| Detailed Setup |
NOTE: At this time Aspenware does not support Windcave in a multi-store environment. We plan to add that feature as part of future development.
Prerequisite Tasks
POS Tasks
IMPORTANT: Syncing Windcave tokens to the POS to use for refunds or resort charge is not possible. This is due to POS technical limitations with storing Windcave tokens that would require the POS to engage in development activities to support.
Complete POS accounting tasks for products sold online.
Payment Provider Tasks
Obtain a Windcave Merchant account. If you don't already have one, you can sign up here: Windcave.
IMPORTANT: To activate your production environment you will need to obtain an API key and API username from Windcave. Make a note of these for use later in this guide.
Determine if you will use the 3DSecure feature within Windcave. This is an additional layer of security that Visa cardholders can opt into. To configure 3DSecure from the Windcave dashboard, click on the Payment Page tab and then scroll to the bottom for the 3DSecure fields. Your Windcave representative can assist you if needed.
Windcave Dashboard - Payment Page Tab Selected
Validation for Cards Not Accepted (Optional): Windcave can be configured to fail to validate any card number that is not a VISA, Mastercard or AmEx in the Card Number Field in the checkout. Error messaging is provided to the customer. This can be applied by contacting Windcave Tech Support.
Commerce Tasks
Update the following settings in Commerce Admin.
Go to Configuration > Settings > All settings (advanced)
Search for ecommercesettings.allowtransferofcc
Click Edit.
Set the Value to TRUE and click Update.
Search for ecommercesettings.allowstorageofcc
Click Edit.
Set the Value as to TRUE.
Click Update.
Detailed Setup Guide
Set Up GL Reporting
Determine Communication Requirements
Ensure CSS File is Sent to Windcave
Configure Payment Gateway
Activate Windcave Payment Provider Widget
Initiate Test Transactions
1. Set Up GL Reporting
Work with your Aspenware Representative to set up the GL Report so you can reconcile GL reporting in the POS and payment gateway.
2. Determine Communication Requirements
Windcave is an international payment gateway, meaning consideration must be given to the communication requirements for the individual countries in which your resort conducts business. Some countries have specific requirements for communication to customers on order confirmation emails, cancelation policies, etc. Verify any country-specific requirements with your Windcave Service Representative. Talk with your Aspenware representative about customizing the email template if necessary.
3. Specify Currency
Windcave has universal capabilities and, as such, accommodates many languages and currencies. To ensure that Aspenware is set to communicate with the gateway using the correct currency, the following configurations must be made.
Go to Configuration > Currencies in Admin.
Find the currency that you wish to choose and click Edit. If your currency is not listed, select Add new +
On either the Edit currency details or the Add a new currency page, complete the following fields:
1. Name: This should be the generally accepted name of the currency (e.g. Australian Dollar).
2. Currency code: This is the official code for the currency that us used in financial markets (e.g. AUD).
3. Rate: This will always be 1. The payment gateway handles all currency exchange rates
4. Published: This field should be checked.
All other fields are not used and may be left blank.
Click Save.
Once you’ve returned to the Currencies screen, find your currency and click the green Mark as primary exchange rate currency and the green Mark as primary store currency buttons. Blue checkmarks should appear to the left of each button. Please ensure that no other currency has a blue checkmark listed. Edit any other currency that is listed as Published to have that field unchecked (not shown in example).
4. Specify Language and Culture
Windcave has universal capabilities and, as such, accommodates many languages and currencies. To ensure that Aspenware is set to communicate with the gateway using the correct language and cultural references, the following configurations must be made.
Go to Configuration > Languages in Admin.
Find your chosen language and select Edit. If your language is not listed, select Add new +.
On either the Edit language or Add new language screen, complete the following fields:
Name: Enter the name of the language (e.g. English).
Language culture: Select appropriate language culture from the dropdown list.
Unique seo code: Choose a code (e.g. us)
Flag image file name: Select the appropriate flag.
Right-to-left: Check the box if the language reads right to left instead of left to right.
Default currency: Select the currency used.
Limited to Stores: Leave blank.
Published: Check this box.
Display order: Set as 1.
5. Ensure CSS File is Sent to Windcave
Each Windcave "account" (unique set of user name and API key) requires a custom CSS file to be configured and added. Work with your Aspenware Representative (support@aspenware.com) to ensure that the custom CSS file is sent to Windcave.
6. Configure Payment Gateway
Go to Configuration > Payment Methods in Admin.
Click Edit on the Windcave payment gateway.
Check Is active and save. Ensure that only the Windcave payment gateway 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 Windcave.
API Username: Obtain from Windcave.
Requires Billing Address: Check to supply postal code/zip for AVS. (You can edit which fields are captured under Settings/Customer Settings/Address Form Fields.
Credit Card Form Title: (Language String) This is a customizable title for the form the guest completes with credit card information. Default title is ‘Credit Card Information’.
3DS Successful Payment Title: (Language String) This is the first sentence of the customizable message a guest receives to proceed once they successfully pass 3DSecure (see screenshot below). Default message is ‘Payment information complete!’.
3DS Successful Payment Message: (Language String) This is the second sentence of the customizable message a guest receives to proceed once they successfully pass 3DSecure (see screenshot below). Default message is ‘Click the continue button to proceed.’
3DS Successful Payment Link Test: (Language String) This is the third sentence of the customizable message a guest receives to proceed once they successfully pass 3DSecure (see screenshot below). This language accompanies the link that takes a user back to the credit card entry screen to change their payment method. Default message is ‘change payment’
Click Save.
7. Activate Windcave Payment Provider Widget
Go to Configuration > Widgets. Select the Windcave Payment provider widget and click Edit.
Check the Is active checkbox to make the widget active. Leave Display order at 1. Click Update to save the settings.
8. Initiate Test Transactions
Windcave mandates 3DS is turned on for testing prior to a resort’s launch, so resorts need to test and decide to enable or disable this setting.
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 guide
Q: When a 3DSecure customer goes to enter their payment information, the screen is very small and there are scrollbars to see the whole window. Can we make this look better?
A: Unfortunately, this window is not configurable by Aspenware. We understand that it doesn’t conform to our UI standards. Fortunately, 3DSecure customers are savvy and have likely seen this screen many times will understand how to enter their credentials.
Q: I’m seeing the following screen. Why does it look like this?
A: The custom css file is needed. See Step 3 above in the Detailed Setup Guide.