Skip to main content

Moneris Hosted Paypage

The Moneris Hosted Paypage integration allows administrators to securely process parking and violation transactions through their Moneris merchant account via a hosted checkout page. Its primary purpose is to ensure secure communication and financial data transfer between the OPS-COM system and the external Moneris payment gateway. This article is intended for OPS-COM administrators and IT staff responsible for configuring financial integrations.

Setup and Configuration

Setting up this integration requires you to retrieve unique keys from your Moneris account, provide them to OPS-COM, and configure specific callback URLs within the Moneris portal.

  1. Log in to your Moneris account using the Development portal ([https://esqa.moneris.com/mpg/](https://esqa.moneris.com/mpg/)) or the Production portal ([https://www3.moneris.com/mpg](https://www3.moneris.com/mpg)).

  2. Hover over Admin and click Hosted Paypage Config.

  3. Copy the specific ps_store_id and hpp_key displayed at the top of the configuration page and provide them to your OPS-COM representative to connect the systems.

  4. Enter the required OPS-COM callback URL into the Approved URL and Declined URL fields on the main configuration page.

  5. Enter the required OPS-COM callback URL into the Async Response URL field within the Response/Receipt Data configuration section.

  6. Enter the required OPS-COM callback URL into the Response URL field within the Security Features configuration section.

  7. Modify the settings within the Paypage Appearance section to customize the visual design of the checkout page your customers will see. Use the preview button to verify your changes.

  8. Enable the desired options within the Email Receipts configuration section.

Environment URLs: The callback URL you must enter into the Moneris configuration fields depends entirely on the environment you are configuring.

Production/Live: Use [https://hostedpayments.parkadmin.com/hook/moneris/](https://hostedpayments.parkadmin.com/hook/moneris/)

Development/Testing: Use [https://hostedpayments.preview.parkadmin.com/hook/moneris/](https://hostedpayments.preview.parkadmin.com/hook/moneris/)

You will use this exact same URL for the Approved URL, Declined URL, Async Response URL, and Security Response URL fields.

Using this Feature

Because this is a backend payment gateway configuration, administrators do not manually interact with this feature on a daily basis. Once fully configured, the Moneris Hosted Paypage automatically handles electronic routing when users process transactions on the user portal.

During checkout, the user is securely redirected to the customized Moneris payment page to enter their card details. Once the payment succeeds or fails, Moneris automatically redirects the user back to the OPS-COM portal where an on-screen receipt is displayed and the transaction is logged in the user's account history.

Best Practices and Considerations

Simulating Payment Declines: When testing your integration in the development environment, Moneris provides a Penny Value Simulator chart in their developer documentation. Use specific penny amounts to force certain callback responses (such as an expired card or insufficient funds error) from the test gateway to ensure OPS-COM handles the declined payments properly.

  • Enable Email Receipts: It is highly recommended to enable email receipts within the Moneris portal. While OPS-COM displays a secure on-screen receipt and logs the payment to the user's history, OPS-COM does not currently send automated email receipts for this specific gateway integration.

  • Test Credit Cards: Always use the official Moneris test credit card numbers provided in their developer documentation when performing your initial penny testing in the development environment. Do not use real credit card data until you are fully configured in the live production portal.

Back to top