Moneris Go Portal - Appendix
This article covers supplementary information regarding ecommerce indicators, transaction channels, terminal IDs, the custom ID, and Visa installments, esp. as applicable to Moneris Go portal.
Written by Ray Aravind
Updated at May 10th, 2025
Table of Contents
Procedure
Product
Moneris Go portal - Channel indicator descriptions
Moneris Go portal - Channel indicator descriptions
The "Channel" is defined as the device, application, or ecommerce integration through which payment data were originally captured prior to being sent to the Moneris host for processing as a transaction. The table below describes the channel indicators supported in Moneris Go portal.
Where to locate the "Channel" indicator in Moneris Go portal
The "Channel" indicator displays as a standard header in the financial transaction report (see Moneris Go portal - Financial transactions report) and as line item on the "Transaction details" page of any transaction (see Moneris Go portal - Transaction details) and on the "Payment request details" page of a paid payment request (see Moneris Go portal - Payment request details).
| Channel indicator | Description |
| Cash | The approved/declined cash transaction (Purchase or Refund) was originally initiated via your Moneris Go portal store's virtual terminal (see Moneris Go portal - Purchase with cash; and see Moneris Go portal - Refund: manual entry), or the cash transaction was initiated via a POS device or application that is synchronized to your store. |
| E-commerce (Moneris Checkout) | The approved/declined transaction (debit, credit, or gift) was initiated via a Moneris Checkout integration with your Moneris Go portal store (see Moneris Go portal - Moneris Checkout - How to get started. |
| E-commerce API | The approved/declined transaction (debit, credit, or gift) was initiated via an ecommerce integration with your Moneris Go portal store using a third-party plug-in or cartridge (e.g., Shopify, SAP Digital Payments, or Salesforce B2C Commerce) to facilitate the integration. |
| Go Retail POS | The approved/declined transaction (debit, credit, or gift) was initiated via a POS device (Go terminal or Go Plus terminal) that is synchronized to your Moneris Go portal store, and this store is enabled for Go Retail POS. |
| Payment requests | The approved/declined Purchase (credit) was originally initiated via a customer paying a payment request that was issued from your Moneris Go portal store (see Moneris Go portal - Paying a payment request). |
| Tap to Pay | The approved/declined transaction (debit/credit) was initiated via the Moneris Go app on a mobile device, and the Moneris Go app is synchronized to your Moneris Go portal store. Any associated follow-on transaction will also show the "Tap to Pay" channel indicator. |
| Terminal | The approved/declined transaction (debit, credit, or gift) was originally initiated via a POS device (Go terminal or Go Plus terminal) that is synchronized to your Moneris Go portal store, and this store is not enabled for Go Retail POS. |
| Vault |
The approved/declined transaction was initiated using Moneris-tokenized card data that is stored (or in the process of being stored) in a Vault customer profile within your Moneris Go portal store: |
| Virtual terminal |
The approved/declined transaction (credit) was originally initiated from your Moneris Go portal store's virtual terminal:
|
| WIX payment | The approved/declined transaction was originally initiated via a WIX ecommerce integration with your Moneris Go portal store. |
Moneris Go portal - Ecommerce indicator descriptions
Moneris Go portal - Ecommerce indicator descriptions
The ecommerce indicator (ECI) specifies the level of security that was used to obtain the cardholder's payment data. The table below describes the electronic commerce indicators supported in Moneris Go portal.
Where to locate the ecommerce indicator in Moneris Go portal
The ecommerce indicator displays as a standard line item on the "Transaction details" page of any transaction (see Moneris Go portal - Transaction details) and on the "Payment request details" page of a paid payment request (see Moneris Go portal - Payment request details).
| ECI indicator | Description |
| M - Manually Keyed Card Present | |
| 0 - Not an electronic commerce transaction | |
| 1 - Mail/Telephone Order - Single | Cardholder provides credit card details via phone or on paper. Authorizes the use of the card for one payment. |
| 2 - Mail/Telephone Order - Recurring | Cardholder provides credit card details via phone or on paper. Authorizes the use of the card for multiple payments processed at predetermined intervals |
| 3 - Mail/Telephone Order - Instalment | Cardholder provides credit card details via phone or on paper. Authorizes the use of the card for a single payment of goods or services billed to the card in multiple segments over a period of time. |
| 4 - Mail/Telephone Order | Unknown classification: Cardholder provides credit card details via phone or on paper. Transaction type is unknown at time of authorization – may be one time or multiple payments. |
| 5 - Fully Authenticated - 3D Secure |
Applicable to ecommerce transactions whereby the cardholder provides their card data over the Internet on a secure site and authenticates their identity via 3-D Secure. |
| 6 - Authentication Attempted - 3D Secure | Applicable to ecommerce transactions whereby the cardholder provides their card data over the Internet on a secure site and attempts to authenticate their identity via 3-D Secure. |
| 7 - SSL Transaction (Not Authenticated) | Applicable to ecommerce transactions whereby the cardholder provides their card data over the Internet on a secure site. |
Moneris Go portal - Terminal ID descriptions
Moneris Go portal - Terminal ID descriptions
The terminal ID is an 8-digit identifier associated with one or more card types and/or the point-of-sale device or application through which a financial transaction was initiated. The terminal ID displays as a line item on the "Transaction details" page of every approved/declined transaction except for cash transactions (see Moneris Go portal - Transaction details).
A debit/credit terminal ID can be assigned to only one device/application at a time. Therefore, this ID can also denote the point-of-sale device or application through which the transaction was initiated as described in the table below. Conversely, a gift terminal ID is variable and may be assigned to multiple point-of sale devices/applications.
Note: The "Transaction details" page includes additional information about a transaction that can help you to identify the point-of-sale device or application through which the transaction was initiated.
| Prefix | Card type | Description |
| 66 | Debit/credit | If the prefix starts with "66" (e.g., 66012345), it indicates the debit/credit transaction was initiated via your store's virtual terminal, a payment request, an ecommerce integration (e.g., Moneris Checkout), or an API. |
| A1 | Debit/credit | If the prefix starts with "A1" (e.g., A1012345), it indicates the debit/credit transaction was initiated via a Moneris Go terminal that is synchronized to your store. |
| A2 | Debit/credit | If the prefix starts with "A2" (e.g., A2012345), it indicates the debit/credit transaction was initiated via a Moneris Go Plus terminal that is synchronized to your store. |
| AP | Debit/credit | If the prefix starts with "AP" (e.g., AP012345), it indicates the debit/credit transaction was initiated via the Moneris Go app (installed on a mobile device) that is synchronized to your store. |
| - | Gift | A gift terminal ID is variable and has no defined prefix. |
Moneris Go portal - Custom ID: list of transactions and reports
Moneris Go portal - Custom ID: list of transactions and reports
The custom transaction identifier (custom ID) field/header is configurable from your Moneris Go portal "Store settings" page (see Moneris Go portal - Custom ID: store settings). The custom ID may be featured in the following Moneris Go portal financial transactions, reports, and receipts as described below:
Virtual terminal transactions:
- If a custom ID is enabled, you will have the opportunity to enter/append a custom ID during these transactions:
- Purchase (see Moneris Go portal - Purchase with credit card: manual entry; see Moneris Go portal - Purchase with cash).
- Preauthorization (see Moneris Go portal - Preauthorization with credit card: manual entry).
- Independent Refund (see Moneris Go portal - Independent Refund with credit card: manual entry).
- Follow-on transactions (listed below) inherit the custom ID from their predecessor transaction:
- Void (see Moneris Go portal - Void: manual entry).
- Refund (see Moneris Go portal - Refund: manual entry).
- Completion (see Moneris Go portal - Completion with credit card: manual entry).
Payment requests:
- If a custom ID is enabled, you will have the opportunity to enter/append a custom ID to a new or draft payment request prior to sending it (see Moneris Go portal - Sending a payment request).
Reports/receipts:
- The custom ID appears as a header or line-item in reports, transaction details, and receipts:
- Transactions report (see Moneris Go portal - Financial transactions report).
- "Transaction details" page (see Moneris Go portal - Transaction details).
- Debit/credit receipt (see Moneris Go portal - Receipt example: debit/credit).
Moneris Go portal - Installments Enabled by Visa
Moneris Go portal - Installments Enabled by Visa
Installments enabled by Visa allows eligible cardholders to pay for a qualifying Purchase or Preauthorization in fixed, equal installments made over a defined period of time without an additional line of credit, credit check, or a new account. Installments enabled by Visa is offered by participating banks and facilitated by Visa’s payment technology for Visa and non-Visa cards.
How it works during a transaction
The cardholder shops in-store or on your Website and initiates checkout as usual. At the checkout (terminal or ecommerce integration), the cardholder enters their card information. If their card is eligible for Installments enabled by Visa, and if the Purchase or Preauthorization qualifies, the available Installments enabled by Visa plans will display at the checkout. The cardholder then chooses a plan and reviews the plan terms (set by their issuing bank). Once the cardholder accepts the terms, they can complete their order. The cardholder's card-issuing bank will bill them in fixed equal installment payments over a defined period of time per the terms of the plan they selected and per their cardholder agreement (see Installment enabled by Visa line items in Moneris Go portal - Receipt example: debit/credit).
If the cardholder's card or Purchase/Preauthorization is not eligible for an Installments enabled by Visa plan, then no Installments enabled by Visa plan will be displayed at the checkout.
Note: If the cardholder wants more information, they must contact their card-issuing bank or review their cardholder agreement. Depending on the installment plan(s) that you configure, installment plan funding fees will be paid to the card issuer by the cardholder (consumer-funded installment plan) or you (merchant-funded installment plan).
Enabling/disabling Installments enabled by Visa plans on your synched terminals
To enable/disable one or more Installments enabled by Visa plans on all terminals that are synched to your store, see Moneris Go portal - Terminal settings: Installments by Visa.
Enabling/disabling Installments enabled by Visa plans in your Moneris Checkout integration
To enable/disable Installments enabled by Visa plans in your Moneris Checkout integration, see Moneris Go portal - Moneris Checkout - Configuring the "Visa Installments" settings .