Configuration: Payment Gateway - Moneris

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

 

  • Complete POS accounting tasks for products sold online. required

Note that Moneris tokens and card info CANNOT be stored in RTP|One or Siriusware because of POS technical limitations.

Prerequisite

2. Infrastructure Tasks

 

  • If running a Commerce version earlier than 2.27, work with your Aspenware Commerce Representative to ensure the following credit-related settings are set in the Azure appsettings.json file:  required

    • AllowStorageOfCC = TRUE

    • AllowTransferOfCC = FALSE

prerequisite

3. Payment Provider Tasks

 

  • Set Up Moneris including additional Vault functionality. required

prerequisite

  • If running Aspenware Commerce 2.27 or later, update the following settings on Commerce Admin required

    • In Configuration > Settings > All Settings, configure the following:

      1. ecommercesettings.allowstorageofcc = TRUE

      2. ecommercesettings.allowtransferofcc = FALSE

 

4. Commerce Tasks

 

  • Work with your Aspenware Representative to set up GL Report. required

  • Configure Aspenware Commerce Payment Gateway required

  • Activate Moneris Payment Provider Widget required

  • Edit Email Template required

  • Configure Payment Card Logo Nop widget required

  • Test Credit in Live and Test Environments required

detailed setup

Prerequisite Tasks

This section describes all required prerequisite steps necessary to support feature setup.

POS Tasks

IMPORTANT: Syncing Moneris tokens to the POS to use for refunds or resort charge is not possible. This is due to POS technical limitations with storing Moneris tokens that would require the POS to engage in development activities to support.

  • Complete POS accounting tasks for products sold online.

Infrastructure Tasks

  • Work with your Aspenware Commerce Representative on the following tasks:

    • If running a Commerce version earlier than 2.27, update the store’s Azure appsettings.json with the following:

    • AllowStorageOfCC = TRUE

    • AllowTransferOfCC = FALSE

IMPORTANT: AllowStorageofCC must be set to TRUE for the GL Export function to work.

Payment Provider Tasks

IMPORTANT: The Aspenware integration with Moneris requires the purchase of Moneris' Vault functionality. Vault is not part of the base Moneris purchase and requires additional fees.

  • You will need a Moneris Merchant account. If you don't already have one, you can sign up here.

  • Once you have a merchant account, request the Aspenware product integration from Moneris using the following code, ‘ECNP-00578.’ This is mapped to  Aspenware Internet Solutions, Inc.

Commerce Tasks

If running Commerce version 2.27 or later, update the following settings in Commerce Admin.

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

    1. Search for ecommercesettings.allowtransferofcc

       

      1. Click Edit.

         

      2. Set the Value to FALSE and click Update.

         

    2. Search for ecommercesettings.allowstorageofcc

       

      1. Click Edit.

         

      2. Set the Value to TRUE.

      3. Click Update.

Detailed Setup Guide

This section describes all required steps to set up the feature after prerequisite tasks have been completed.

 

  • Work with your Aspenware Representative to set up the GL Report so you can reconcile GL reporting in the POS and payment gateway.

1. Configure Payment Gateway

  • Go to Configuration > Payment Methods in Admin.

  • Click Edit on the Moneris payment gateway.

  • Check Is active and 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. Store ID: From Moneris introductory email

    3. API Token: From Moneris during Account setup

    4. Store Profile ID: From Moneris, in Merchant Resource Center, Admin/Hosted Tokenization. Enter the URL of your store in the source domain field. Click CREATE PROFILE. Locate profile in the list - copy Profile ID and paste into the appropriate field in plugin.

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

    6. Card Number Label, Expiration Label, and CVD Label: Refer to the customizable labels that can be applied to the hosted fields in the checkout window.

    7. Card Number Invalid Title, Card Number Invalid Message, Expiration Title and Message, and CVD Title and Message: These fields are for customizing the display to a cardholder based on the response returned from Moneris.

  • Click Save.

2. Activate Moneris Payment Provider Widget

  • Go to Configuration> Widgets. Select the Moneris Payment provider Widget.

  • Click the edit button to be able to make the widget active. Update to Save the settings.

3. Edit Email Template

Moneris requires specific information to be included on your email confirmation, so Moneris customers will need to edit their email template to comply with this standard.

  • Go to Content Management > Message Templates and locate the template named: orderplaced.customernotification

  • Add the following token in a logical position: %Order.CustomValues%. Be sure to avoid placing in a code block beginning with “IF”, as the field will only display when the “IF” conditions are met. No label is required as the token includes labels for the data.

  • Click Save.

4. Configure Payment Card Logo Nop widget.

Moneris requires that each resort displays the payment network brand logos for the credit and debit cards accepted at your site. Logos include Mastercard, VISA, American Express, Discover, and Union/ChinaPay.

5. Test Credit in Live and Test Environments

  • Test using sandbox credit card values in test

  • Test a live credit card in the live store 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

Q: What functionality is and isn’t available to me because of having Moneris as a Payment Provider?

A: Moneris functionality includes preauthorization (vaulted token) capture, void (pre-batch), refund and partial refund (post-batch). Payment Plans will be added as an enhanced feature in 2022, for use for Season Pass Sales at the end of the 21/22 season.

Aspenware Subscriptions are not available.

Unfortunately, because some functionality is made possible by having a token stored in the POS, and neither RTP|ONE nor Siriusware support storing Moneris tokens, resort charge, direct to lift, and capturing tokens for refunds in the POS is not supported.

Also, ApplePay, GooglePay, PayPal, and storing credit cards for future purchases are not currently supported with Moneris.

Q: When I look at an order status in Aspenware Commerce Order Details, the status is set to pending rather than complete? What’s wrong with this order?

A:  The true indicator of whether a product made it to RTP|ONE 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.

This won't cause problems per se but is really only used for retail products that are shipped, so it shouldn't be checked.  Because Nopcommerce is often used as a retail platform, what processing means in Nop is similar to what Open means in RTP|One. The order is paid for, but the order has not been fulfilled, aka shipped. For ski, we send the order to RTP|One for fulfillment and don't do any fulfillment in NOP - we use the delivery plugin for shipping ski media and ignore Nopcommerce shipping, so it's not a problem. Uncheck shipping on these products and save, and you will start seeing these orders show as completed.

Q: I’m switching from another payment provider to Moneris, but the old payment provider UI continues to display on top of the new payment method on the Payment UI during checkout.  

A: You must uninstall the previous payment provider plugin and ensure that Moneris is the ONLY payment provider plugin that is enabled. Go to Configuration > Payment Methods in Admin to ensure that Moneris is the ONLY payment provider installed and enabled.

Q. How do I do a refund?

You will need to complete a two-step process for a refund or a partial refund. In your POS (RTP|One or Siriusware) you should follow the required procedures to cancel the entire order or the applicable portion.

In Aspenware Commerce, sign in as an Admin. Locate the order under Sales > Orders, and click Edit. Scroll down to locate Payment Status.

Clicking Refund will refund 100% of the transaction. The refund will be stored in the order table, with a PaymentStatusID of 40.

 

Clicking Partial Refund will open a dialog box that allows you to enter the dollar value of the refund. Partial Refunds are stored in the order table with a PaymentStatusID of 35.

The refunds are also reported in the transaction reports available through the Moneris Dashboard.

Q: Why am I getting an error message that says “null No such store number exists”?

A: If you are experiencing an error that indicates your store number does not exist, please check your configuration. All store numbers begin with a series of letters and must be typed in lowercase (e.g. “gwca”, not “GWCA”).

Q: Why am I getting an error message that says "Null Transaction not allowed", "Resolver/tmp" or a failure at the Add Token to Vault Stage?

A: Check with Moneris and confirm that Vault functionality has been enabled for your account. Moneris staff can advise you on activating this feature, which is required to use Aspenware Commerce and the Moneris Payment Gateway. This setting is managed by Moneris and requires their involvement.