# OperationsCommander Payments and Transaction Flow
**OperationsCommander works hard to maintain an up to date product wiki! If you have any questions or if you feel something is missing,** [**post about it in the community.**](https://community.ops-com.com/c/product-support/6)
# Payroll Deduction Settings
## Enable / Disable paying a Violation / Permit using Payroll Deduction.
First go to System Configuration [](https://opscom.wiki/uploads/images/gallery/2025-03/image.png) then select the Payments option [](https://opscom.wiki/uploads/images/gallery/2025-03/mPWimage.png) You will now see the options "Disable Payroll Deduction for Violations" & "Disable Payroll Deduction for Temp Permits", you can use the check boxes on these options to toggle on / off the ability for users to use "Payroll Deduction" for paying Violations and/or Permits when they check out.
[](https://opscom.wiki/uploads/images/gallery/2025-03/VB7image.png)
# Setting up Quick Pay/Guest Payments
This article describes the Guest Payments feature. Guest Payments allows guest users to look up and pay for violations directly from the user portal without needing to create or log in to an account. This functionality streamlines the payment process for end-users and reduces administrative inquiries.
### Setup and Configuration
For Guest Payments to function, it must first be enabled for specific payment types and then activated in the system's global settings.
**Keep in mind:** compatible third-party payment provider that supports guest transactions must be configured in your OPSCOM system.
See this article on [setting up a third-party payment provider](https://opscom.wiki/books/setup-configuration-for-admins/page/managing-payment-types#bkmrk-the-following-links-).
##### Enable Specific Payment Types
First, you must designate which electronic payment types are available for guest transactions.
- Go to **System Configuration**, **Payments**, and click **Setup Payment Types**.
- Create a new payment type or click the **Edit** icon next to an existing one that you wish to enable for guests.
- Select the **Settings** tab.
- Click the **Enable for Guest Payments** checkbox.
- Click **Save** to confirm the change.
Repeat these steps for all payment types you want to make available for guest payments.
##### Activate Global Setting
After enabling the desired payment types, you must activate the feature for the entire system.
- Go to **System Configuration**, and click **System Settings**.
- Select the **Violations** tab.
- Enable the **Enable Anonymous Violation Payments** checkbox.
- Click **Save Settings**.
### Using this Feature
Once Guest Payments are fully configured, a button will appear on the public portal's main login page, allowing users to pay for a violation without logging in.
See this article for the [User Experience of guest payments](https://opscom.wiki/books/setup-configuration-for-admins/page/managing-payment-types#bkmrk-the-following-links-).
---
### Best Practices and Considerations
- **Select which payment types to enable for Guest Payments.** Only enable electronic payment methods (e.g., Credit Card) that can be processed automatically through your payment provider.
- **Confirm your payment provider supports this functionality.** Guest Payments will not work without a compatible payment gateway configured in OPSCOM. Consult your payment provider's documentation or support if you are unsure.
- **Communicate the availability of this feature to the public.** Consider adding a note on your organization's parking information page to direct users to this convenient payment option.
####
# Payment Reconciliation: Submitted / Processed
The Payment Reconciliation page allows users to effectively track and manage the status of payments within a defined time period. This report is specifically designed to reconcile the dollar value of received payments with your bank or credit card merchant by comparing the amounts charged between the two. Users can filter results to view either submitted or processed payments.
## Setup & Configuration
To access the Payment Reconciliation page you must have the permission to **View Payments** turned on. This can be added to your role by your Primary Admin.
---
### Creating a Payment Reconciliation Group
1. Navigate to **System Configuration**, then **Admin Management**, and click on **Manage Groups**.
2. This brings you to the **Manage Administrator Groups** page.
3. To create a Payment Reconciliation group click on the **Payment Reconciliation** module and then click **Add New** in the top right corner under. [](https://opscom.wiki/uploads/images/gallery/2026-04/iKqimage.png)
The **Adding New Group** window will appear with the following options:
**Options**
Info
**1. Group Name**
The Group Name is how you set the name of a group.
**2. Module**
The Module is where you can set the purpose of the group.
**3. Admin Members**
The Admin Members is the area in which you can add admin members to the group
4. When you are finished click the **Save Group** button. You will see your group added to the bottom of the Administrator Groups.
##### Adding Members to a Group
1. Navigate to **System Configuration**, then **Admin Management**, and click on **Manage Groups**.
2. Click the Edit button next to the Administrator Group you wish to edit.
3. Click on the **Admin Members** bar to add more members to the group.
4. When finished, click the **Save Group** button found at the bottom of the Editing Group.
## Using this Feature
1. Go to **Payments**, and click **Payment Reconciliation**.
2. On this page, you can apply filters to refine the payment data displayed:
- **Filter by Date Range:** Define the start and end dates for the payments you wish to view.
- **Filter by Payment Type:** Select the specific payment method(s) you want to include in the results.
- **Filter by Admin Group:** Filter reconciliation data based on specific admin groups designated for payment reconciliation.
3. Click Search. The results are displayed below the search criteria.
4. Click on any column header to reorder the data.
### System Task (Export Options)
The page offers various export options, shown in green, that allow users to generate files for external use:
- **Copy:** Copies the row data to your clipboard, allowing you to paste it into any program, such as Excel.
- **CSV:** Creates and prompts you to download a CSV (Comma-separated values, `.csv`) file for use in your program of choice.
- **Excel:** Creates and prompts you to download an Excel (Microsoft Excel, `.xls`) file for use in your program of choice.
- **Print:** Prompts your browser to print the current page view.
---
## Best Practices & Considerations
- **Reconciliation Focus:** The Payment Reconciliation report is the correct tool for comparing system payments with bank/merchant payments.
- **Avoid Daily Payments Itemized for Reconciliation Tasks:** The **Daily Payments Itemized** report shows received payments, but it is **not recommended for reconciliation** because it may display tax differently and can lead to rounding errors, making dollar-value comparison inaccurate.
# Accepting a Student Account Payment from the Admin Portal
## Accepting a Student Account Payment
To Begin lets select a permit to purchase. In this case the admin is assigning a permit to a student and taking payment via Student Account.
[](https://opscom.wiki/uploads/images/gallery/2024-06/gWVimage.png)
In this example we are purchasing a permit in the General Monthly Lot for Patricia Birch.
[](https://opscom.wiki/uploads/images/gallery/2024-06/r7Yimage.png)
Once the lot has been selected, the admin can then choose a permit to assign to the user. Click on **Purchase this Permit** to continue.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Xjyimage.png)
The payment due page will appear. Click on **Proceed to Payment** to continue.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Z8Yimage.png)
The screen will refresh and the admin will be presented with the **Payment Selection** section of the process.
[](https://opscom.wiki/uploads/images/gallery/2024-06/1DZimage.png)
In this case we have selected a **Student Account** payment. Click **Submit Payment** to continue.
[](https://opscom.wiki/uploads/images/gallery/2024-06/iCnimage.png)
The screen will refresh and the admin will be presented with the Payment Selection section of the process. In this case we have selected a cash payment. Click **Submit Payment** to continue.
[](https://opscom.wiki/uploads/images/gallery/2024-06/atYimage.png)
The **Transaction Details** screen will appear. There are three choices available.
- Process Manually which will complete the transaction
- Cancel and Keep which will terminate the transaction but return the locker to awaiting payment status
- Cancel and Release which will also terminate the transaction and release the locker back into the pool of available lockers to rent.
IN our example we will select Process Manually to complete the transaction.
[](https://opscom.wiki/uploads/images/gallery/2024-06/tpbimage.png)
The payment will be processed and the **Transaction Details** screen will display a receipt. Because the payment method is **Student Account** the item will be marked as paid by student account.
A report can be run of daily payments filtered by Student Account. This report can be provided to the financial department to allow finance to retrieve the funds from the student account.
[](https://opscom.wiki/uploads/images/gallery/2024-06/fcnimage.png)
# Payment for a locker from the Admin Portal
## Paying for a locker.
To begin click on the **Lockers** menu item in the user's profile on the admin portal.
[](https://opscom.wiki/uploads/images/gallery/2024-06/0imimage.png)
The locker registration page appears with a list of buildings with lockers available.
[](https://opscom.wiki/uploads/images/gallery/2024-06/XQ8image.png)
The locker selection page will open allowing the admin to chose the locker area within the building chosen. In this case we are looking for a locker in the women's locker room.
[](https://opscom.wiki/uploads/images/gallery/2024-06/1jHimage.png)
The admin may then select the specific locker number they wish to assign to the user. Click on **Reserve Locker** to continue.
[](https://opscom.wiki/uploads/images/gallery/2024-06/upJimage.png)
The confirm **Locker Registration** page will open where the admin can verify the information about the locker being assigned. Click on **Confirm Info** to continue.
[](https://opscom.wiki/uploads/images/gallery/2024-06/4q2image.png)
The payment due page will appear. Click on **Proceed to Payment** to continue.
[](https://opscom.wiki/uploads/images/gallery/2024-06/cL2image.png)
The screen will refresh and the admin will be presented with the Payment Selection section of the process.
[](https://opscom.wiki/uploads/images/gallery/2024-06/0Phimage.png)
In this case we have selected a **Cash** payment. Click **Submit Payment** to continue.
[](https://opscom.wiki/uploads/images/gallery/2024-06/lSfimage.png)
The transaction Details screen will appear. There are three choices available.
- Process Manually which will complete the transaction
- Cancel and Keep which will terminate the transaction but return the locker to awaiting payment status
- Cancel and Release which will also terminate the transaction and release the locker back into the pool of available lockers to rent.
IN our example we will select Process Manually to complete the transaction.
[](https://opscom.wiki/uploads/images/gallery/2024-06/2UGimage.png)
The payment will be processed and the Transaction Details screen will display a receipt.
[](https://opscom.wiki/uploads/images/gallery/2024-06/xUrimage.png)
# Admin Portal Permit Purchase with Credit Card
## The Permit
We begin by going to a user's dashboard on the admin portal and proceeding to the Parking tab.
In our example we are issuing and paying for a permit on behalf of user over the phone.
[](https://opscom.wiki/uploads/images/gallery/2024-06/hkyimage.png)
We then get taken to the Confirm Parking Permit Registration page where the admin can choose either the next permit available or select a specific permit number.
Click on Purchase this Permit to Continue.
[](https://opscom.wiki/uploads/images/gallery/2024-06/HEZimage.png)
The Payments Due screen will open listing items that require payment.
[](https://opscom.wiki/uploads/images/gallery/2024-06/YX4image.png)
## The Payment Type
From the payment Due screen the admin can choose a payment method to be used for this purchase. In our example we choose a payment provider.
Click on Submit Payment Information to continue.
[](https://opscom.wiki/uploads/images/gallery/2024-06/LuYimage.png)
A confirmation Screen will appear listing the payment type. Click on Submit Payment Information button to proceed to the payment gateway.
[](https://opscom.wiki/uploads/images/gallery/2024-06/7Zjimage.png)
You will be directed to the payment provider's input form. Fill out the form and click Make Payment to complete the purchase.
[](https://opscom.wiki/uploads/images/gallery/2024-06/fLZimage.png)
A transaction record will appear. This information is stored and can be accessed form the user's payment history or you can search for the Confirmation Number in various search tools.
[](https://opscom.wiki/uploads/images/gallery/2024-06/UMJimage.png)
# Daily Payments - Itemized
The Daily Payments - Itemized page can be found under Payments -> Daily Payments - Itemized.
[](https://opscom.wiki/uploads/images/gallery/2024-08/2024-08-08-15-15-19.png)
On this page your can filter for submitted or processed payments based on a date range and payment type:
[](https://opscom.wiki/uploads/images/gallery/2024-08/2024-08-08-15-18-09.png)
Two options for excel export exist:
[](https://opscom.wiki/uploads/images/gallery/2024-08/yZximage.png)
- **Export to Excel (Group)**: payment items such as permits, deposits, violations, lockers, etc that are part of the same payment are grouped together.
Example:
[](https://opscom.wiki/uploads/images/gallery/2024-08/lJIimage.png)
- **Export to Excel (Line)**: payment items such as permits, deposits, violations, lockers, etc that are part of the same payment are listed on separate lines/rows.
Example:
[](https://opscom.wiki/uploads/images/gallery/2024-08/MPeimage.png)
After clicking "List Payments" results will then be displayed below the search criteria, grouped by day:
[](https://opscom.wiki/uploads/images/gallery/2024-08/nYrimage.png)
Additionally along the bottom of the page a table breakdown of daily processed orders is shown:[](https://opscom.wiki/uploads/images/gallery/2024-08/Nucimage.png)
# Admin Portal Cash, Cheque or Debit Payment
## Purchasing a Permit
To begin let's have a look at purchasing a permit for the admin portal. Select the **Parking Tab** and the click the **Standard Permit** button to access the permit purchase screen.
[](https://opscom.wiki/uploads/images/gallery/2024-06/HNqimage.png)
The **Confirm Parking Permit Registration** page appears. An admin can simply use the next permit available or select a specific permit to assign to the user.
The cost of the permit will show in this interface. Click on **Purchase this Permit** to proceed.
[](https://opscom.wiki/uploads/images/gallery/2024-06/9ekimage.png)
This will then take you to the **Confirm Parking Permit Registration** page.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Xykimage.png)
If everything looks good as far as what you expect the payment to be you may then select the payment type you wish to use.
[](https://opscom.wiki/uploads/images/gallery/2024-06/3wGimage.png)
In our example we will choose **Cash** however **Cheque, Money Order** and **Debit Card** work in the same manner.
[](https://opscom.wiki/uploads/images/gallery/2024-06/WQiimage.png)
Once the payment type is selected you will be directed to the **Payment Due** screen where you will see the important information of what you are paying for and what payment type was selected.
Click **Submit Payment** Information to proceed with the purchase.
[](https://opscom.wiki/uploads/images/gallery/2024-06/SA9image.png)
The screen will refresh with three choices that can be made at this point.
**Process Manually** - which will process the payment. It is at this point you would collect the cash, cheque, money order, or debit card to process.
**Cancel and Keep** - This will terminate this transaction but keep the permit in awaiting payment status.
**Cancel & Release** - This will terminate this transaction and release the permit back into the pool of available permits.
In our example we will select Process Manually to complete the transaction.
[](https://opscom.wiki/uploads/images/gallery/2024-06/xgiimage.png)
The screen will refresh with a confirmation screen record of the purchase.
[](https://opscom.wiki/uploads/images/gallery/2024-06/gR8image.png)
# Paying for a Violation from the Admin Portal
## Searching for a Violation
There are two methods to searching a violation. You can place the violation number in the **quick search** bar and click on the resulting drop down.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Tv2image.png)
Or... Alternately you can use the **Violation Search** from the **Violations** menu.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Fffimage.png)
Enter the **ticket number** or **plate number** in the **Search Text** box and click on **Search Using Only Text** to retrieve a list of violations.
Click on the **ticket number** to proceed.
*Note: Using the Ticket Number will list the specific ticket. Using the Plate Number will list all tickets associated with the plate.*
[](https://opscom.wiki/uploads/images/gallery/2024-06/jFoimage.png)
## Choosing an Action
The **Violation Information** window will pop up. Click on **Action** to proceed.
[](https://opscom.wiki/uploads/images/gallery/2024-06/d8ximage.png)
A list of possible actions will appear. Click on **Make Payment** to access the payment screen.
[](https://opscom.wiki/uploads/images/gallery/2024-06/iMlimage.png)
## The Payment Screen
The payment screen will display any item that is awaiting payment. This could include **Violations, Permits,** and **Deposits**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/vWAimage.png)
You may opt to pay for all items or decide to pay for the specific violation by toggling off the items you wish to pay for at another time.
*Note: If items are past due you will be required to pay for them and will not be able to toggle them off.*
[](https://opscom.wiki/uploads/images/gallery/2024-06/ZtMimage.png)
Click **Proceed to Payment** to continue.
[](https://opscom.wiki/uploads/images/gallery/2024-06/CxJimage.png)
## Choosing a Payment Type
Select the payment type you wish to use. In this case we are using **cash** as a payment type. You may also select **cheque** or **debit card** payment here.
*Note: As an admin you may choose any payment type available in your system. If the payment was being made from the user portal you can see only **Credit Card** in this case would be available as a payment type.*
[](https://opscom.wiki/uploads/images/gallery/2024-06/wj6image.png)
In our example we are choosing **cash**. Click on **Submit Payment** Information to proceed.
[](https://opscom.wiki/uploads/images/gallery/2024-06/es5image.png)
A confirmation screen will appear noting the payment method. Click on **Submit Payment Information** once again to proceed.
[](https://opscom.wiki/uploads/images/gallery/2024-06/cTqimage.png)
## Making the Payment
The **Transaction Detail** screen will appear. You may wish to update the **Comment** at this point.
*Note: You may also cancel the transaction at this point if there is reason to do so. Be aware that canceling a payment for a violation simply places the violation back into awaiting payment status.*
*For a permit you may opt to cancel the transaction yet keep the permit in awaiting payment status (**Cancel and Keep**) or you may **Cancel and Release** the permit.*
[](https://opscom.wiki/uploads/images/gallery/2024-06/scximage.png)
In our example we will **Process the payment manually** and accept the cash payment.
[](https://opscom.wiki/uploads/images/gallery/2024-06/PsUimage.png)
## The Final Transaction Detail Screen
The **Transaction Detail** page will refresh showing the details of the purchase.
[](https://opscom.wiki/uploads/images/gallery/2024-06/U9pimage.png)
# Payment Data Export via Banner SFTP
# Configuration
There are several items that must be configured in order for the right information to display in the exported CVS file.
# User Profile
In the user profile, a **unique user ID** must be configured.
This information will likely be populated by a user data import.
[](https://opscom.wiki/uploads/images/gallery/2024-06/XOEimage.png)
# Lot Administration
Each lot requires a unique **banner detail code**.
To set the banner detail code, go to **Lot Administration** and click on **Pricing & Lot Admin**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/AWoimage.png)
Select the lot you wish to add the detail code to. Click on the **lot name** to access the configuration screens.
[](https://opscom.wiki/uploads/images/gallery/2024-06/K1pimage.png)
Once you are in the lot configuration tool, select the **Additional** tab.
[](https://opscom.wiki/uploads/images/gallery/2024-06/X5Aimage.png)
Enter the **Lot Detail Code**. (These codes are established in the preliminary planning phase of the project)
[](https://opscom.wiki/uploads/images/gallery/2024-06/64Eimage.png)
# Ticket Categories
From the **Options Menu**, hover over **Violations** and select **Manage Ticket Categories**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Hb9image.png)
Click **Edit** on the **Category** you wish to configure.
[](https://opscom.wiki/uploads/images/gallery/2024-06/tgCimage.png)
Enter the detail code for the ticket category.
In this case, the Detail Code is **PRKB** for the **Boot Fee** category.
[](https://opscom.wiki/uploads/images/gallery/2024-06/h12image.png)
# Sales Window
On the sales window configuration page, we need to enter a **Term Code** used for **Permits** only.To do so go to the **Permits** Menu and select **Sales Windows**
[](https://opscom.wiki/uploads/images/gallery/2024-06/pXJimage.png)
To access the configuration screen, click on **EDIT.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/Qzwimage.png)
Here you will enter the **Term Code** for the selected **Sales Window** that you want to appear on the permit purchases export.
[](https://opscom.wiki/uploads/images/gallery/2024-06/cl1image.png)
# Activate Script to Run on a Schedule
You must now ensure the **System Task** is set to active and has an active schedule set.
In the **Options** menu, click on **View System Task Logs**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/5eEimage.png)
In this example, the Task is set to run at 2:00 am Nightly
[](https://opscom.wiki/uploads/images/gallery/2024-06/bBeimage.png)
# The User PortalYou are now set to make a payment on the user portal. In this example, we will purchase a permit.Go to the user portal and click on the **Permits** menu item.
[](https://opscom.wiki/uploads/images/gallery/2024-06/3kCimage.png)
Select the Lot you wish to purchase a permit in.
[](https://opscom.wiki/uploads/images/gallery/2024-06/BtDimage.png)
Click **Reserve Permit**
[](https://opscom.wiki/uploads/images/gallery/2024-06/9DBimage.png)
**Continue to Checkout** to view your **Cart**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/0QZimage.png)
Select **Banner Payment** as your **Payment Type.**This can be configured so that Banner Payment is your only selection available.
[](https://opscom.wiki/uploads/images/gallery/2024-06/KGCimage.png)
Click **Submit Payment.**The screen will refresh to show the **Confirm Payment** page.Click on **Confirm Payment.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/6Xgimage.png)
Once the payment is processed, you will get an online receipt.
[](https://opscom.wiki/uploads/images/gallery/2024-06/32Iimage.png)
Some additional information on how the Banner export process works:
Export to Banner will run whenever the system task is set to, and gathers any violations that can be sent to banner that haven't been exported yet. When a violation has been exported by the system task, it has a flag put on it that marks it has been exported to Banner.
It will export the violations it found into a new file, and does not affect any previously output files, meaning it doesn't create a cumulative file that gets more added each day. Rather, it creates a new file every time it runs; this isn't necessarily daily, it runs at whatever interval the client has decided for it.
This would mean if they missed a day, there would be more than one new file in the output folder for them to process in Banner.
# Search Payments
## Accessing the Report
From the Payments menu click on **Search**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/eUTimage.png)
The page will refresh with the **Payments Reporting** search form that gives you the ability to search by **Confirm Code, Transaction ID, Order ID**, as well as a number of present search items below.
[](https://opscom.wiki/uploads/images/gallery/2024-06/2O2image.png)
Here is an example of searching based on the **confirm code 7d444zbcdffe54b50bde**
[](https://opscom.wiki/uploads/images/gallery/2024-06/EGEimage.png)
Provided the confirm code exists in the system the screen will refresh with the **Transaction Details** for that purchase.
[](https://opscom.wiki/uploads/images/gallery/2024-06/wEwimage.png)
## Pre-Configured Searches
The search tool also has a number of additional pre configured searches that will help you find information quickly.
Some of the reports will have the ambility to set a date range where others do not require a specified range.
**List Cheque Refunds**
[](https://opscom.wiki/uploads/images/gallery/2024-06/vorimage.png)
**List unprocessed Cash, Cheque and Money Order payments**
[](https://opscom.wiki/uploads/images/gallery/2024-06/o5jimage.png)
**List unprocessed Credit Card payments**
[](https://opscom.wiki/uploads/images/gallery/2024-06/6RRimage.png)
**List unprocessed Payroll Deduction payments**
[](https://opscom.wiki/uploads/images/gallery/2024-06/kS7image.png)
**List unprocessed Internal payments**
[](https://opscom.wiki/uploads/images/gallery/2024-06/IMnimage.png)
**List ALL unprocessed payments**
[](https://opscom.wiki/uploads/images/gallery/2024-06/mB9image.png)
**List ALL unprocessed adjustments**
[](https://opscom.wiki/uploads/images/gallery/2024-06/wS1image.png)
**List ALL Processed Payroll Deductions**
[](https://opscom.wiki/uploads/images/gallery/2024-06/iXMimage.png)
**List All Processed Violations (by date range)**
[](https://opscom.wiki/uploads/images/gallery/2024-06/Ddfimage.png)
**List Daily Processed/Submitted Payments (by date range)**
You may search for submitted payments as well as Processed payment in this report. The search criteria screen will look like this:
[](https://opscom.wiki/uploads/images/gallery/2024-06/lKUimage.png)
The resulting report will have two sections to it. One that lists the payments in detail.
[](https://opscom.wiki/uploads/images/gallery/2024-06/KErimage.png)
...And one that lists a daily summary.
[](https://opscom.wiki/uploads/images/gallery/2024-06/XpLimage.png)
# Banner Report
## Generating the Report
To begin look for the **Banner Report** menu item under the **Payments Menu**
[](https://opscom.wiki/uploads/images/gallery/2024-06/qxFimage.png)
The screen will refresh and display the **Banner Report Search** page.
On this page you select:
**User Types:** Select the User Type you wish to report and pay for.
**Choose Item Type:** Select the item you wish to pay for. In our example we are paying for yearly permits.
**Up To and Including:** Select the end date of the period you wish to pay for.
**Banner Code:** Enter the payment or identifying code that you wish to apply to this record in Banner. (Code 100)
**Detail Code:** Enter the code that represents the item you are paying for. In our case it will be a yearly permit for 2020. (YP2020)
**Admin Code:** Enter your admin ID number to track who is making this payment report.
[](https://opscom.wiki/uploads/images/gallery/2024-06/3CXimage.png)
There are two functions you can perform here. **Mark as Paid** or **Export to Excel**.
## Exporting to Excel
The export to Excel functionality allows the admin to export a spreadsheet of names and payments that will be made.
[](https://opscom.wiki/uploads/images/gallery/2024-06/uNBimage.png)
Here is a sample of an exported spreadsheet. This report can then be imported into Banner to facilitate payment through a Student or Staff account.
[](https://opscom.wiki/uploads/images/gallery/2024-06/gwAimage.png)
## Mark Items as Paid
To mark these reported items paid in OPSCOM Select Mark as Paid.
[](https://opscom.wiki/uploads/images/gallery/2024-06/NjFimage.png)
A popup window will appear for the admin to confirm the transaction.
Click **Confirm** to continue.
[](https://opscom.wiki/uploads/images/gallery/2024-06/al4image.png)
A confirmation screen will appear displaying the **transaction code** for the payment.
[](https://opscom.wiki/uploads/images/gallery/2024-06/2ioimage.png)
If you searched the transaction code you would see this return. Note: All three items here are now paid for,
[](https://opscom.wiki/uploads/images/gallery/2024-06/ehtimage.png)
# Flex Payments
## Configuring a Lot For Flex Payments
To begin create a **Flex Payment Lot** and added 10 permits to it (FLX001...FLX010)
To do so first go to **Lot Administration** and select **Pricing & Lot Admin.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/oLKimage.png)
Name the lot **Flex Payment Lot** or something you consider appropriate.
Set the cost at **$0.00**
Set the **Usertype** to the users who will be using Flex Payments. In our example we are using **Full Time Staff**.
**Note: the lot does not have to be set to visible to users as this functionality will only be used on the Admin Portal**
[](https://opscom.wiki/uploads/images/gallery/2024-06/sGGimage.png)
Set the **Sales Window** to **Yearly**
[](https://opscom.wiki/uploads/images/gallery/2024-06/npAimage.png)
## Adding Flex Permits to the Lot
Go to **Allocate** and add your ten permits.
[](https://opscom.wiki/uploads/images/gallery/2024-06/oiJimage.png)
## Testing Flex Payments
To test find a **Full Time Staff** user with a vehicle in our example we are using **John Doe**.
Click on the **Parking** tab to begin the purchase process.
[](https://opscom.wiki/uploads/images/gallery/2024-06/rOpimage.png)
Purchase a permit from the **Flex Payment Lot**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/hZjimage.png)
Process it as if it were a **zero dollar cash purchase**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/pznimage.png)
The **Payments Due** screen will open. Select **Proceed to Payment** to continue.
[](https://opscom.wiki/uploads/images/gallery/2024-06/gy2image.png)
On the very last confirmation screen click on **Adjust** to bring up the adjustment screen.
[](https://opscom.wiki/uploads/images/gallery/2024-06/2YDimage.png)
Set a -200.00 value (credit). Added a comment (Flex Payment Adjustment) and clicked on **Add Adjustment**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/zycimage.png)
## How the credit is displayed on the user Portal
Do not process the credit yet as it will appear as a credit on the users account.
[](https://opscom.wiki/uploads/images/gallery/2024-06/JZiimage.png)
This credit can now be applied to a permit purchase.
# Payroll Deduction Workflow
## Purchasing a permit using Payroll Deduction
In this scenario Patricia Birch will purchase a permit via Payroll Deduction. We will cover the purchase process on both admin and user side.
## From the Admin Web App
Here is the payment listed in the payments screen. Click on **Proceed to Payment**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/LJuimage.png)
The screen will refresh with the payment type selection tool. Select Payroll Deduction as the payment type and click on Submit Payment Information to continue.
[](https://opscom.wiki/uploads/images/gallery/2024-06/gobimage.png)
The confirmation screen appears. Please check the information to ensure it is correct. Then click Confirm Payment Information to continue.
[](https://opscom.wiki/uploads/images/gallery/2024-06/klAimage.png)
The screen will refresh with the Transaction Detail screen. To complete the purchase click on Process Manually to continue.
[](https://opscom.wiki/uploads/images/gallery/2024-06/4pwimage.png)
The screen will refresh with the final screen in the purchase process. The system considers the permit purchased at this point.
[](https://opscom.wiki/uploads/images/gallery/2024-06/nvgimage.png)
To collect on Payroll Deduction purchases, use the Payroll Deduction Report to help track purchases.
# Admin Portal Violation Payments with Credit Card
## Paying a Violation with Visa
Log in with your admin credentials on the admin side.
[](https://opscom.wiki/uploads/images/gallery/2024-06/rvvimage.png)
Navigate under the violations tab to the search tab.
[](https://opscom.wiki/uploads/images/gallery/2024-06/oUTimage.png)
Type the ticket number into the search text box.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Vudimage.png)
In this case we looked up ticket TT-10016 and found that it belongs to user jsmith with a plate that is ABC123.
[](https://opscom.wiki/uploads/images/gallery/2024-06/DB4image.png)
Click the Ticket # and you will be brought to the Violation Information tab
[](https://opscom.wiki/uploads/images/gallery/2024-06/etyimage.png)
Afterwards click on the actions tab and click on Make Payment.
[](https://opscom.wiki/uploads/images/gallery/2024-06/5bkimage.png)
This will bring you to the user's payment page so you can process said violation.
[](https://opscom.wiki/uploads/images/gallery/2024-06/17fimage.png)
In this case you want to deselect any other objects that are not being paid for at the moment (in this case the permit) and click proceed to payment.
[](https://opscom.wiki/uploads/images/gallery/2024-06/ulhimage.png)
This brings you to the checkout page where you have three ways you can handle this detailed below.
[](https://opscom.wiki/uploads/images/gallery/2024-06/HOaimage.png)
Click on the drop down menu in order to pick Credit Card, MasterCard or Visa. In this case we're going to use Visa.
[](https://opscom.wiki/uploads/images/gallery/2024-06/BNyimage.png)
It will bring up the proper options for you to enter in credit card information and click 'Submit Payment Information'
[](https://opscom.wiki/uploads/images/gallery/2024-06/0YGimage.png)
This will bring you to a payment type confirmation page, to continue press the 'Confirm Payment Information' button
[](https://opscom.wiki/uploads/images/gallery/2024-06/1Zfimage.png)
The payment processes.
[](https://opscom.wiki/uploads/images/gallery/2024-06/6yQimage.png)
Then you get brought to a transaction details page
[](https://opscom.wiki/uploads/images/gallery/2024-06/o2Iimage.png)
## Paying with Visa (External)
This payment type is used when the customer chooses to pay by credit card at the parking office where a pin pad or cash register is used.
# Failed Payments Report
1. To access the report go to the **Payments** drop down menu and select **Search Failed Payments**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/2U9image.png)
2. The **Failed Payments Report** screen will open. Enter a date range you wish to report on and click **Search**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/ZX0image.png)
3. The screen will refresh with a list of failed payment for that date range. In our example we are looking at **October 1st, 2018** to **October 15th, 2018.**
During that time period there were **5 failed payments**. The list shows the pay Id, confirmation code, amount of the payment, the date of the failed payment and the user name associated with the payment.
[](https://opscom.wiki/uploads/images/gallery/2024-06/u6Mimage.png)
4. To drill down further click on the **Confirmation Code** button to access the transaction record.
[](https://opscom.wiki/uploads/images/gallery/2024-06/iBuimage.png)
5. The transaction record screen will open where you can see details about the failed transaction.
[](https://opscom.wiki/uploads/images/gallery/2024-06/tqYimage.png)
6. Some payment providers will return detailed information with an explanation as to why the payment failed, while other providers will simply supply an error code.
In this case note that there is a response code of **481** indicated in the information.
[](https://opscom.wiki/uploads/images/gallery/2024-06/jGAimage.png)
A **481** code indicates there is an error in the information provided. Usually an incorrect expiration date or an incorrect billing address.
The definition for these codes are easily found in a web search. In this case a search for **Credit card response code 481** provided the explanation.
[](https://opscom.wiki/uploads/images/gallery/2024-06/cbaimage.png)
# Mark Items as Paid
## Marking Items Paid Menu Option
Hover over **Payments** and click **Mark Items Paid**
[](https://opscom.wiki/uploads/images/gallery/2024-06/B0zimage.png)
Select Items to Mark Paid
The **Mark Outstanding Items Paid** screen displays. You can select different parameters such as user type, item type and time period.
[](https://opscom.wiki/uploads/images/gallery/2024-06/OI5image.png)
As an example, this setting will mark all locker rentals for **Full Time Staff**, purchased before April 1st, 2018 as paid.
[](https://opscom.wiki/uploads/images/gallery/2024-06/zCGimage.png)
## Bulk Mark Violations Paid
In cases where violations have been sent for collection, the admin would get a list back from the collection agency as to what payment have been retrieved.
The admin would then be able to mark these violations as paid.
To do so click on **Bulk by Number** beside Violations.
[](https://opscom.wiki/uploads/images/gallery/2024-06/9Ajimage.png)
Enter the violations in the tool separated by a line return.
Keep in mind that you should not include the PIN with the violation number.
eg. 2-001345-**92** (92 is the PIN in this case)
[](https://opscom.wiki/uploads/images/gallery/2024-06/u4Uimage.png)
Select **Violations Paid Through Collection** from the drop-down list.
Click on **Mark Listed Paid** to complete the process.
[](https://opscom.wiki/uploads/images/gallery/2024-06/uHcimage.png)
# Payment Adjustments
## Releasing a Permit.
1. If you know the permit number perform a permit search. If you do not know the permit number, go to the user profile for whom you wish to release a permit.
Click on the permit number on the user dashboard.
[](https://opscom.wiki/uploads/images/gallery/2024-06/zPaimage.png)
2. From the permit detail click on the permit number
[](https://opscom.wiki/uploads/images/gallery/2024-06/67zimage.png)
3. You will be taken to permit search where you can released the permit
[](https://opscom.wiki/uploads/images/gallery/2024-06/aSDimage.png)
4. It is advisable to leave a comment in order to track the reason the permit was released. Click release this permit.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Sazimage.png)
5. A pop up window will appear. Click OK to confirm the release of the permit.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Xl2image.png)
6. A confirmation message will app\[ear.
[](https://opscom.wiki/uploads/images/gallery/2024-06/BAwimage.png)
7. Now when you search the permit it will appear as available.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Btzimage.png)
## Refunding a Violation
1. Once a user has paid a violation it can be refunded and placed back in awaiting payment status.
2. Go to the user's history and search for the violation you wish to refund. Click on the work Processed to access the transaction details.
[](https://opscom.wiki/uploads/images/gallery/2024-06/lqCimage.png)
3. Click on the Refund button to begin the process of refunding the violation
[](https://opscom.wiki/uploads/images/gallery/2024-06/nzMimage.png)
4. A Refund payment Record window will open. It is advisable to enter a comment as to the reason the refund is being given.
[](https://opscom.wiki/uploads/images/gallery/2024-06/xjjimage.png)
5. Click on OK in the resulting pop up confirmation screen to complete the process.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Gaiimage.png)
6. The adjustment Information window will appear. Click on Process This Adjustment.
[](https://opscom.wiki/uploads/images/gallery/2024-06/l4Rimage.png)
7. The transaction screen will refresh indicating "The associated transaction was dropped or refunded; any refund details will appear below."Notice the refund appears as an adjustment in the transaction record.
[](https://opscom.wiki/uploads/images/gallery/2024-06/hzximage.png)
8. If you were to look at the user's history you will see the violation is back to requiring a payment.
[](https://opscom.wiki/uploads/images/gallery/2024-06/p1gimage.png)
## Refunding a Locker
1. To refund a locker, find the locker in the user's profile history. Click on the process date to access the transaction detail.
[](https://opscom.wiki/uploads/images/gallery/2024-06/z7simage.png)
2. Refund the locker by clicking the refund button.
[](https://opscom.wiki/uploads/images/gallery/2024-06/3y8image.png)
3. The refund payment record window will open. It is advisable to enter a comment as to why the locker is being refunded.
Click Refund Payment Record
[](https://opscom.wiki/uploads/images/gallery/2024-06/CUvimage.png)
4. A confirmation screen will open. Click OK to continue.
[](https://opscom.wiki/uploads/images/gallery/2024-06/gSNimage.png)
5. the adjustment Information screen will open. Click on Process This Adjustment to complete the process.
6. In the user's history the locker now shows as released.
[](https://opscom.wiki/uploads/images/gallery/2024-06/x5nimage.png)
7. In the list of lockers in the building area the locker will appear as available after this process.
[](https://opscom.wiki/uploads/images/gallery/2024-06/vMiimage.png)
## Refunding a Temp Permit
1. Buy a Temp Permit
2. Pay Temp Permit
3. Refund Temp Permit
4. Temp Permit is Released
## Refunding a Violation and a Permit
1. Buy Permit
2. Get Violation
3. Pay for Violation and Permit
4. Refund Payment
5. Violation needs to be paid, permit is now available
## Adjusting a violation to $0
1. CAN'T BE DONE
2. Well I guess it can be done but the process is rough
3. Create a Payment with a permit and a violation
4. Adjust permit to cover the violation as well as the permit
5. Release the permit
# Electronic Fund Transfer Configurations
# Setup by Tomahawk
If you will be using EFT as a payment method, you must provide Tomahawk with the client number. This is provided by the Royal Bank and will be the identifier they use to deposit to your account.
This information can be setup under the Payments section of the Manage System Settings page.
[](https://opscom.wiki/uploads/images/gallery/2024-06/wv1image.png)
# Creating EFT Files to Send to your Bank
Once the subscription is set up and you have performed a rollover, you can export the flat file that contains the EFT information. This file can be sent to your bank for processing. For details about submitting this to your bank, please contact your representative at the Royal Bank of Canada.
1. Go to the payments menu and select **EFT Export.** This will generate the file you need to send to your banking institution.
[](https://opscom.wiki/uploads/images/gallery/2024-06/oT1image.png)
# **Marking EFT Items as Paid**
1. Once the payment has been processed at the bank, a report will be made available to you by your Banking institution. This report will contain information about what payments you submitted were successful. You can update the OPSCOM system and mark these as paid or NSF. To do this go to the Payment Menu and select **EFT Process.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/U0simage.png)
2. The **Electronic Funds Transfer Process** window opens. Here you have the ability to select three states for the payments:
**- Waiting -** This is the default status of the payment. If the payment has not been processed at the bank leave the payment record in Waiting status. **- Paid -** Toggle this state by clicking on the **Paid** checkbox. **- Failed -** Select this checkbox if the payment failed for any reason. This will return the item to the user's profile as awaiting payment and archive the record.
Once you have completed this process click **Mark as Indicated** to finalize the process.
[](https://opscom.wiki/uploads/images/gallery/2024-06/fquimage.png)
# Paying a Violation Anonymously on the Administrator Interface
To begin, go to the **Violations Menu** and select **Search.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/8X1image.png)
Enter either the ***Ticket Number*** or the ***License Plate*** number in the Search Text Field and click on **Search** **using only text**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/twdimage.png)
This will return a listing of violations.
Note that the **Plate Number** has been found. (1)
By clicking on the Ticket Number (2) you will bring up the **Violation Information** pop up screen.
Click on the **Make Anonymous Payment** button to proceed to the Payment Entry process.
[](https://opscom.wiki/uploads/images/gallery/2024-06/lX1image.png)
The **Payments Due** window will open allowing you to check to select the ticket you wish to pay. (4)
Click **Proceed to Payment** (5) in order to advance to the payment due window.
[](https://opscom.wiki/uploads/images/gallery/2024-06/KL4image.png)
In the **Payment Due** window, you can select the method of payment. (6)
[](https://opscom.wiki/uploads/images/gallery/2024-06/nL4image.png)
Note the list of payment types. Click **Submit Payment** to continue to process the payment.
[](https://opscom.wiki/uploads/images/gallery/2024-06/33himage.png)
The screen will refresh, listing the transaction you are about to process. Click **Confirm Payment Information** (7)
[](https://opscom.wiki/uploads/images/gallery/2024-06/i8vimage.png)
The payment will process and the screen will refresh with the **Transaction Detail** Window. At this point the transaction is complete.
[](https://opscom.wiki/uploads/images/gallery/2024-06/B7Ximage.png)
Once the transaction is complete, you can search the violation and see that it is marked as "**PROCESSED**"
[](https://opscom.wiki/uploads/images/gallery/2024-06/Y2limage.png)
# Permit Purchase by an Admin
## Purchasing a Permit
1. To begin go to **pbirch's** user profile and click on the **Parking** menu item.
[](https://opscom.wiki/uploads/images/gallery/2024-06/XaPimage.png)
2. The screen will refresh with the following option screen. You may purchase a **Standard Permit**, a **Temporary Permit** or **Associate an Access Card with the User** from this screen.
In our case we will select a Standard Parking Permit.
[](https://opscom.wiki/uploads/images/gallery/2024-06/N3fimage.png)
3. The screen will refresh with the lot selection tool.
[](https://opscom.wiki/uploads/images/gallery/2024-06/F87image.png)
The drop down allows the admin to select various lots that are available for this user based on user type. In this scenario lots available to staff members can be selected.
[](https://opscom.wiki/uploads/images/gallery/2024-06/o9Vimage.png)
As suggested we will select the **Yearly After 4PM lot**. Notice the number of available spaces in each lot is displayed here as well.
4. The screen will refresh with a confirmation screen that displays the purchase details.
[](https://opscom.wiki/uploads/images/gallery/2024-06/vP1image.png)
The system will bring up the next available permit in sequence by default, however if there were a requirement to have a specific permit issued to the user, the admin may expand the **permit #** drop down to select a specific permit.
[](https://opscom.wiki/uploads/images/gallery/2024-06/r6Yimage.png)
Once the permit is selected Click on **Purchase this Permit** to proceed.
5. The screen will refresh with the **Payments Screen** listing the permit as well as any other payment that would be due at this time. Click **Proceed to Payment** to continue.
[](https://opscom.wiki/uploads/images/gallery/2024-06/gvgimage.png)
6. The screen will refresh with the **Payment Type** selection tool.
[](https://opscom.wiki/uploads/images/gallery/2024-06/S0Uimage.png)
The admin may select whatever payment type they wish to process this payment with from the drop down list.
In our case we will select **cash** as the payment type. Click **Submit Payment Type** to proceed.
[](https://opscom.wiki/uploads/images/gallery/2024-06/IO4image.png)
7. The screen will refresh with a confirmation screen showing the payment details with totals. Click on **Confirm Payment Information** to proceed.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Hloimage.png)
8. The screen will refresh with the **Transaction Details** screen. There are several sections on this screen that display specific information about your transaction.
1- The **Confirmation Number** for this transaction.
2- The **Submit Date** along with a **View Snapshot** link which allows you to see the payment information for this purchase, however, it does not allow you to drill into the details of each transaction from the snapshot (In the example below, Permit No. 60). It will only display the total of all items and the value of each item individually.
[](https://opscom.wiki/uploads/images/gallery/2024-06/FN7image.png)
3- The **Payment Method** which can actually be changed at this point if needed.
4- Three options are available:
**Process Manually** which will complete the purchase
**Cancel & Keep** which will cancel the transaction but keep the transaction details and reserve the permit so that you can process the payment at another time.
Click on **Process Manually** to complete the purchase.
[](https://opscom.wiki/uploads/images/gallery/2024-06/7z9image.png)
1. The screen will refresh with the final Transaction Detail screen. This information screen can be accessed in the future from the user's history in order to view this information.
The admin has the option from this screen to perform a refund if needed.
[](https://opscom.wiki/uploads/images/gallery/2024-06/U0qimage.png)
## Payment Notes
Payment Notes allow Admins to annotate refunds and other payment anomalies. These notes are private and not visible to the end user.
[](https://opscom.wiki/uploads/images/gallery/2024-06/X7bimage.png)
# Transact Campus/CashNet Hosted Payment Setup
## Setting up the Payment Page
- Details you will have to provide to OPSCOM support:
Setting
Details
merchant
The merchant code we will be submitting items against. This is the Merchant Code on the clients system.
item code
They need to set up an item and give us the code. The item will need to be allowed to change the value. See below for the screen. These codes need to match exactly what the client has configured or the transactions will fail.
## Payment Page
- Found in Store Settings.
- Details OPSCOM will give to clients:
## Store Settings
- Under Store Settings, you will need to configure the following settings based on the URLs supplied by OPSCOM:
[](https://opscom.wiki/uploads/images/gallery/2024-05/PgLimage.png)
## Configure CashNet "HTTP Notifications" Section
- Go to the "HTTP Notifications" configuration with CashNet.
##### HTTP Notifications
- If you would like HTTP notifications, enter the URL next to each category. If you leave the field blank you will not receive notifications for that category.
- New outbound connections from [CASHNet.com](http://cashnet.com/) will not work until they are allowed through the CASHNet firewall.
- Please contact CASHNet Client Support if you need to enable a new connection.
[](https://opscom.wiki/uploads/images/gallery/2024-05/wRCimage.png)
## Setting Item codes
- On the item code itself, we need this set the following:
[](https://opscom.wiki/uploads/images/gallery/2024-05/f4pimage.png)
# TouchNet (uPay) Hosted Payments
##### Credentials Required:
Your TouchNet Account Manager can provide you with the following information:
- **uPay Site ID**: Usually a 3 digit number for example 013
- **uPay**: A secure URL that uniquely identifies your account
- **T-Link web service**: Another secure URL that uniquely identifies your account
These credentials will be given to you for both a Sandbox (Test) and a Production (Live) environment.
Please provide these details to your OPSCOM Account Manager. Charges for setup may apply.
##### T-Link Web Service:
OperationsCommander's parent company Tomahawk Technologies is a [TouchNet ready partner](https://partners.touchnet.com/english/directory/partner/1512039/tomahawk-technologies). When configuring the T-Link in your TouchNet account you maybe asked to select a TouchNet ready partner from a dropdown, please select "Tomahawk Technologies".
If you don't have the ability to configure a T-Link web service URL and your TouchNet Account Manager hasn't supplied one, you may need to request TouchNet setup a "uPay" site for you which supports T-Link web services.
##### GL (General Ledger) Codes:
OperationsCommander's TouchNet integration currently supports multiple GL (General Ledger) codes. One code can be specified for parking permits, another for all other payments (violations, lockers, etc). The GL code can also be the same for all purchases. If using GL codes please let your OPSCOM Account Manage know the GL code name(s) you setup in your TouchNet account.
# SchoolPay
OPSCOM supports [SchoolPay](https://www.schoolpay.com/) hosted payment integration. This means your OPSCOM users can use SchoolPay to pay for items in OPSCOM such as permits, lockers, violations, etc.
## Add a new Payment Type:
You can create a new payment type by selecting **System Configuration** → **Payments** → **Setup Payment Types** →**Add Type.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/rldimage.png)
If you don't see "Setup Payment Type" as shown above you may need to give your [role the permission](https://wiki.OPSCOM.com/x/B4DjAQ) to do so.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Wq2image.png)
Select "**SchoolPay - Hosted**" as your provider → **Next Step**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Tb7image.png)
## Edit Payment Type User Types:
You should now be brought to the "**Edit Payment Type**" page:
[](https://opscom.wiki/uploads/images/gallery/2024-06/VPuimage.png)
**Type Name:** The type name can be whatever you want it to be, though please note this will also be the name displayed to users when using payment checkout and selecting a payment method. You can reference the specific hosted payment provider such as SchoolPay or something more generic such as "Online Credit Card Payment", "Online payment", "Credit Card", etc. Really it's up to you and what you think makes most sense to your site users when making a payment, also might depend on what payment methods your SchoolPay account supports.
**Enabled for User Types**: Select the User Types you wish this new Payment Type to be visible to so they can select it during payment checkout. You can change these user types at any time
## Edit Payment Type Settings:
There are additional required configuration fields in the **Settings** area:
[](https://opscom.wiki/uploads/images/gallery/2024-06/0ZKimage.png)
**Enable for Text2ParkMe**: This payment setting isn't currently supported using OPSCOM SchoolPay integration.**Enable for Permit Renewal Payments**: This payment setting isn't currently supported using OPSCOM SchoolPay integration.**Enable for Guest Payments**: if you aren't using this feature leave the button unchecked.**Prompt Information**: Only "Email Address" is supported with SchoolPay Hosted Payments at this time.**Credentials**:
- **Username**: Obtained from SchoolPay.
- **Password**: Obtained from SchoolPay.
- **Item ID**: Obtained from SchoolPay.
- **Production/Sandbox**: Select whether you are using your SchoolPay Production/Live credentials or Sandbox/Testing credentials. Additionally, although not required you may find your OPSCOM preview space helpful for testing Sandbox/testing credentials, this way you can keep your production/live OPSCOM data (permits, users, payments, violations, etc) clean/separate during any testing.
Don't forget to save your new payment type by clicking the "Update Payment Type" button along the bottom of the page:
[](https://opscom.wiki/uploads/images/gallery/2024-06/Cxqimage.png)
Nothing further needs to be done, however if you are curious what the user process looks like when purchasing something in OPSCOM using SchoolPay a number of screenshots are below to show this.
## User flow screenshots:
User selects SchoolPay payment type in OPSCOM and supplies an email address for identification and email receipt:
[](https://opscom.wiki/uploads/images/gallery/2024-06/RKPimage.png)
User confirms payment in OPSCOM:
[](https://opscom.wiki/uploads/images/gallery/2024-06/xeiimage.png)
User is then redirected to SchoolPay's secure system for payment details and processing:
[](https://opscom.wiki/uploads/images/gallery/2024-06/Unkimage.png)
User confirms payment details and selects "Finish" at which point their payment method is charged for the transaction:
[](https://opscom.wiki/uploads/images/gallery/2024-06/KISimage.png)
If the payment is successful users will be automatically redirected back to OPSCOM checkout with a payment confirmation:
[](https://opscom.wiki/uploads/images/gallery/2024-06/LMIimage.png)
Email receipts will also be sent from SchoolPay and OPSCOM to the user supplied email address.
# PayPal
## Step #1: Create a PayPal Account
Configure OPSCOM with your PayPal email address, selected currency and whether you are configuring for production use.
## Step #2: Add credentials to OPSCOM
[](https://opscom.wiki/uploads/images/gallery/2024-06/yGTimage.png)
Supply appropriate credentials.
[](https://opscom.wiki/uploads/images/gallery/2024-06/mEwimage.png)
# OpenEdge Hosted Payments
#### Sign up for your new OpenEdge Account Here: [OPSCOM / OpenEdge](https://lp.globalpaymentsintegrated.com/referrals/OPSCOM/).
On the sign up form you will be asked for **Representative Information.** Here is the correct information to enter:
- **Rep First Name**: Phil
- **Rep Last Name**: MacCallum
- **Rep Email**: [phil.maccallum@ops-com.comcom](mailto:phil@ops-com.comcom)
- **Rep Phone**: 855.410.4141 x 224
#### Credentials Required:
Your OpenEdge Account Manager can provide you with the following information:
- **Auth Key**: a multi-digit string key
- **Terminal ID**: a 8 digit numeric key
- **X-Web ID**: a 12 digit numeric key
This will be given to you for both a Sandbox and a Production environment.
### Create OpenEdge Payment Type:
You can create a new payment type by selecting **System Configuration** ( icon in the OPSCOM admin side menu ) → **Payments** → **Setup Payment Types** →**Add Type.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/AIIimage.png)
Select "**EdgeExpress - Hosted**" as your provider → **Next Step**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/D7Ximage.png)
You should now be brought to the "**Edit Payment Type**" page:
[](https://opscom.wiki/uploads/images/gallery/2024-06/vOmimage.png)
**Type Name:** The Type name can be whatever you want it to be, though please note this will also be the name displayed to users when using payment checkout and selecting a payment method. You can reference the specific hosted payment provider such as OpenEdge/Edge Express or something more generic such as "Online Credit Card Payment", "Online payment", "Credit Card", etc. Really it's up to you and what you think makes most sense to your site users when making a payment, also might depend on what payment methods your OpenEdge/EdgeExpress.
**Enabled for User Types**: Select the User Types you wish this new Payment Type to be visible to so they can select it during payment checkout. You can change these user types at any time
There are additional required configuration fields in the **Settings** area:
[](https://opscom.wiki/uploads/images/gallery/2024-06/CGTimage.png)
**Enable for Text2ParkMe**: if you aren't using this module leave the button unchecked.**Enable for Permit Renewal Payments**: if you aren't using this feature leave the button unchecked.**Enable for Guest Payments**: if you aren't using this feature leave the button unchecked.**Prompt Information**: Only "Email Address" is supported with OpenEdge Hosted Payments at this time.**Credentials**:
- **Production/Sandbox**: Select whether you are using your OpenEdge Production/Live credentials or Sandbox/Testing credentials. Additionally, although not required you may find your OPSCOM preview space helpful for testing Sandbox/testing credentials, this way you can keep your production/live OPSCOM data (permits, users, payments, violations, etc) clean/untouched during any testing.As referenced above, your OpenEdge Account Manager can provide you with the following credentials:
- **Auth Key**: a multi-digit string key.
- **Terminal ID**: a 8 digit numeric key.
- **X-Web ID**: a 12 digit numeric key.
Don't forget to save your new payment type by clicking the "Update Payment Type" button along the bottom of the page:
Done, the new OpenEdge/Edge Express hosted payment type has been added to your OPSCOM system and you should be ready to test the payment/checkout process using this new payment type.
To test: Using a test user, add a vehicle if none already present, then purchase a $1.00 permit or violation using the new payment type. Complete and pay for the transaction. Once complete the test user will receive an email receipt showing the successful payment. Confirm that your company has received the payment into your bank account to verify that the setup is working correctly.
For some additional reference/clarification this is what the OpenEdge hosted payment page looks like to website users during the checkout/payment process:
[](https://opscom.wiki/uploads/images/gallery/2024-06/4nkimage.png)
# Moneris Checkout
This article provides OPSCOM system admins with a comprehensive guide to setting up and configuring Moneris Checkout as a payment provider. Moneris Checkout is a full-service partner that allows you to support a wide range of payment options within OPSCOM.
---
## Setup and Configuration
Properly configuring Moneris Checkout involves two key stages: configuring the settings within your Moneris merchant account and then mirroring the appropriate settings within OPSCOM. **We recommend using the pre-auth settings in both Moneris and OPSCOM for the most reliable payment process.**
**See this gif image, which shows what setting to change on the Moneris Merchant Resource Center, in order to switch from purchase to pre-authorization. (shown in the image below, beside capture method)**
[](https://opscom.wiki/uploads/images/gallery/2026-02/2026-02-24-14-33-17.gif)
### Information Required for Setup
Before beginning the configuration, you must create a profile in your Moneris account. From there, you will need to obtain the following credentials from within the Moneris account. OPSCOM will require these details to connect to the service.
- store\_id: store#
- api\_token: xxXXXXX
- checkout\_id: xxxxxxxxStore#
- Hosted\_token\_id (Generated by you, later on in this document)
<div class="info-box"> You must also determine if your Moneris security settings, such as Address Verification Service (AVS), will require your customer's billing address to be collected. This decision affects which fields OPSCOM will prompt the user to complete.
</div>
### Moneris Portal Configuration
1. Log in to the Moneris Merchant Resource Center and navigate to the configuration area.
2. Click Admin in the main menu and select Moneris Checkout Config.
3. Locate your checkout profile (e.g., MOC-SPO) and click to edit it.
From there, you can change any of the settings:
#### Checkout Type
**Select;**
“I have my custom order form and want to use Moneris simply for payment processing.”
This ensures that Moneris provides the payment fields embedded within your existing OPSCOM order form.
#### Multi-Currency
This feature can be enabled if you need to process payments in multiple currencies.****
**Feature Limitations:** with Multi-Currency Enabling Multi-Currency will disable support for Recurring Billing, Gift Cards, 3-DSecure 1.0, and Google Pay.
#### Payment
This section defines transaction rules and security options.
- **This is where you can control whether or not you wish to use a pre-authorize or payment capture model, the benefits of which are described above.**
- **Payment Security:** It is your decision whether to enable security features like AVS and CVV. **If you enable these, you must configure OPSCOM to collect the full billing address from users**. Note that if Multi-Currency is active, 3D Secure is not supported.
- **Transaction Type:** You can set this to either preauthorize, or purchase. **THE PAYMENT TYPE IN OPSCOM MUST ALSO BE CONFIGURED THE SAME WAY.**
- **Tokenize Card:** Ensure the Tokenize Card option is ***disabled***. Card tokenization for recurring payments is handled by the **Moneris Vault**, which is configured separately.
The purchase model (current) requires a client's connection be stable. Should anything interrupt that, javascript errors, spotty connection, etc., the callback will not reach OPSCOM. With the new pre-auth model, the capturing of the funds now happens server to server meaning neither the client, the app, nor spotty connections can interfere with processing the payment. The Preauthorize Capture model provides a more reliable payment process.
#### Branding and Design
To ensure the payment form integrates smoothly with the user experience:
- Disable the Enable Fullscreen checkbox. This prevents the checkout form from taking over the entire screen.
The rest of the branding and design decisions can be configured to your liking.
#### Order Confirmation
Configure Moneris to redirect the user back to OPSCOM after a payment attempt.
- Select the option “Use Own Page” for the order confirmation. This allows OPSCOM to display the final success or failure receipt.
---
### OPSCOM System Configuration
Payment Types Setup
Please click this [hyperlink](https://opscom.wiki/books/setup-configuration-for-admins/page/managing-payment-types) to be redirected to our Payment Types Setup documentation, and then finish the remaining steps after that has been finished.
Create a new section for setting up Hosted providers. We currently have only three:
- [OpenEdge](https://opscom.wiki/books/the-opscom-admin-portal/page/openedge-hosted-payments)
- [Moneris Checkout ](https://opscom.wiki/books/the-opscom-admin-portal/page/moneris-checkout)
- [Bambora Checkout](https://opscom.wiki/books/the-opscom-admin-portal/page/bambora-checkout)
---
##### Moneris Vault for Stored Payments
Moneris Vault is a complementary service used for tokenizing and storing credit cards for future use, such as with parking rollovers or Text2ParkMe. This functionality requires one additional piece of information during setup:
- hosted\_token\_id: This ID is generated from the Hosted Tokenization page within the Moneris portal.
If you encounter an "Invalid credentials" error when attempting to tokenize a card, it is likely due to a missing hosted\_token\_id or because the token's "Source URL" authentication does not match the domain you are using. For testing, you can use a profile without Source URL authentication.
---
## Best Practices and Troubleshooting
### Common Billing and AVS/CVV ErrorsThe most common issue during setup is a mismatch between Moneris's expectations and the data OPSCOM provides. If Moneris is configured to require and validate billing details (AVS is enabled), but OPSCOM is only configured to ask for an email address (promptFor is set to anonymous), all transactions will fail. You must ensure the OPSCOM configuration matches the security requirements you set in the Moneris portal.
# Moneris Hosted Paypage
## Setting up Moneris Gateway
**\[Step 1\]** - Login to your Moneris account:
**Development**/Testing Login: [https://esqa.moneris.com/mpg/](https://esqa.moneris.com/mpg/)
**Production**/Live Login: [https://www3.moneris.com/mpg](https://www3.moneris.com/mpg)
**\[Step 2\]** - Once logged into your Moneris account select **Admin** > **Hosted Paypage Config**.
**\[Step 3\]** - Along the top of the Hosted Paypage Configuration you should see your **ps\_store\_id** and **hpp\_key**. Please copy these details and send them to your **OperationsCommander (OPSCOM) contact.
[](https://opscom.wiki/uploads/images/gallery/2024-06/PTRimage.png)
**\[Step 4\]** - On the Hosted Paypage Configuration page select the settings shown in the below screenshot.
**\*Note**: We will send you the correct **Approved URL** and **Declined URL** to use. That being said, the URLs are listed below. If you do not know what URLs to use (**Development** or **Production**) please consult your **OperationsCommander (OPSCOM) contact.
**Development**/Testing:
Approved URL: [https://hostedpayments.**preview**.parkadmin.com/hook/moneris/](https://hostedpayments-dev.parkadmin.com/hook/moneris/)
Declined URL: [https://hostedpayments.**preview**.parkadmin.com/hook/moneris/](https://hostedpayments-dev.parkadmin.com/hook/moneris/)
**Production**/Live:
Approved URL: [https://hostedpayments.parkadmin.com/hook/moneris/](https://hostedpayments.parkadmin.com/hook/moneris/)
Declined URL: [https://hostedpayments.parkadmin.com/hook/moneris/](https://hostedpayments.parkadmin.com/hook/moneris/)
[](https://opscom.wiki/uploads/images/gallery/2024-06/bWvimage.png)
**\*Note**: The following **\[Steps\]** are related to the additional configuration pages along the bottom of the main Hosted Paypage Configuration:
[](https://opscom.wiki/uploads/images/gallery/2024-06/XYQimage.png)
**\[Step 5\]** - **Paypage Appearance**
These are all optional settings related to the appearance of your Moneris Hosted Paypage. There is a preview button that allows you to view changes. This will be the page that your customers see when supplying their payment details during the checkout process through **OperationsCommander (OPSCOM).
**\[Step 6\]** - **Response/Receipt Data**
Select the settings shown in the below screenshot.
**\*Note**: We will send you the correct **Async Response URL** to use. That being said, the URLs are listed below. If you do not know what URLs to use (**Development** or **Production**) please consult your **OperationsCommander (OPSCOM) contact.
**Development**/Testing:
Async Response URL: [https://hostedpayments.**preview**.parkadmin.com/hook/moneris/](https://hostedpayments-dev.parkadmin.com/hook/moneris/)
**Production**/Live:
Async Response URL: [https://hostedpayments.parkadmin.com/hook/moneris/](https://hostedpayments.parkadmin.com/hook/moneris/)
[](https://opscom.wiki/uploads/images/gallery/2024-06/RVdimage.png)
**\[Step 7\]** - **Security Features**
Select the settings shown in the below screenshot.
**\*Note**: We will send you the correct **Response URL** to use. That being said, the URLs are listed below. If you do not know what URLs to use (**Development** or **Production**) please consult your **OperationsCommander (OPSCOM) contact.
**Development**/Testing:
Response URL: [https://hostedpayments.**preview**.parkadmin.com/hook/moneris/](https://hostedpayments-dev.parkadmin.com/hook/moneris/)
**Production**/Live:
Response URL: [https://hostedpayments.parkadmin.com/hook/moneris/](https://hostedpayments.parkadmin.com/hook/moneris/)
[](https://opscom.wiki/uploads/images/gallery/2024-06/Qyfimage.png)
**\[Step 8\]** - **Email Receipts**
These are optional settings related to sending customers email receipts. **OperationsCommander (OPSCOM) doesn't currently send email receipts so you may wish to enable this functionality. By default **OperationsCommander (OPSCOM) will display a receipt back to users after a successful or failed transaction and allow successful payments to be reviewed at a later date under the users account history.
## Moneris Test Credit Cards
Moneris provides a list of credit card numbers you may use to test against during your penny testing
## Payments Declined
If you are having payments declined issue after you have set up please make sure that you are checking your total against the penny value simulator. This chart allows you to force certain callback responses based on the amount paid by the test visa gateway: [https://developer.moneris.com/en/More/Testing/Penny%20Value%20Simulator](https://developer.moneris.com/en/More/Testing/Penny%20Value%20Simulator)
# Chase E-xact Hosted Payments
Unlike the Direct Post Method, E-xact uses Hosted Payment Page (HPP) integration with Relay Response. The customer is redirected to E-xact's secure payment form, and transaction results are posted back to our webhook endpoint.
## Setting up Chase E-xact Payments
In order to configure the client OPSCOM site to use Chase E-xact Hosted Payments the client must supply the following credentials:
- Company Name
- Their exacted
- The password used to access the account
# Bambora Checkout
To properly configure your Bambora/Wordline payment type in OPSCOM you will require two separate "Authorization Headers". These headers will be referenced below as:
**
Payment Authorization Header**
**Profile Authorization Header**The process to generate the two different encoded headers is similar in that both require your Bambora Merchant ID + API access passcode, and both are encoded at the same link, however the API access passcode is different for each and shown on different pages in Bambora (order settings vs payment profile configuration).
Login to your Bambora account, then on the left navigation select **Administration** → **Account Settings** → **Order Settings.**
#### API access passcode (**Payment Authorization Header**):
On the Order settings page scroll down to "**API access passcode**". If there is nothing in the API access passcode field click the "**Generate New Code**" button. After generating your API access passcode make sure to scroll down to the bottom of the page and click "Update" to save your changes.
#### Merchant ID (MID):
Now that you know your **API access passcode** and **Merchant ID** [go here.](https://docs.na.worldline-solutions.com/plan-your-integration/create-a-test-account/encode-api-passcode "Encode API Passcode") Copy and paste your Merchant ID (1) and API access passcode (2) into the appropriate fields, then click "**Encode**"(3).
Copy/record the **Payment Authorization Header** shown. This will be needed later when you setup the Bambora Checkout payment type in OPSCOM. It will be referenced further down this page as the **Payment Authorization Header**. You should temporarily paste this into a program such as Notepad for easy access later since you will need it later during the OPSCOM configuration.
You will want to make sure to copy only the following section returned (excluding quotation marks):
"Passcode \_\_\_\_\_\_"
For example, select/copy as shown in the highlighted example below, starting at the P on Passcode. We want to exclude/not copy "Authorization:"[](https://opscom.wiki/uploads/images/gallery/2026-01/kDXbambora-image-2.png)
---
Similar to the above process for encoding your **Payment Authorization Header**, we will be going through a similar process for encoding your **Profile Authorization Header**.
Login to your Bambora account, then on the left navigation select **Configuration** → **Payment Profile Configuration.**
#### API access passcode (**Profile Authorization Header**):
Under Security Settings make sure "API access passcode:" is selected. If there is nothing in the API access passcode field click the "**Generate New Code**" button. After generating your API access passcode make sure to scroll down to the bottom of the page and click "Update" to save your changes.
Now that you know your **API access passcode** and **Merchant ID** [go here.](https://docs.na.worldline-solutions.com/plan-your-integration/create-a-test-account/encode-api-passcode "Encode API passcode"). Copy and paste your Merchant ID (1) and API access passcode (2) into the appropriate fields, then click "**Encode**"(3).
Copy/record the Authorization Passcode returned. This will be needed later when you setup the Bambora Checkout payment type in OPSCOM. It will be referenced further down this page as the "**Profile Authorization Header**". You should temporarily paste this into a program such as Notepad for easy access later since you will need it later during the OPSCOM configuration.
You will want to make sure to copy only the following section returned (excluding quotation marks):
"Passcode \_\_\_\_\_\_"
For example, select/copy as shown in the highlighted example below, starting at the P on Passcode. We want to exclude/not copy "Authorization:"
[](https://opscom.wiki/uploads/images/gallery/2024-10/E4Cimage.png)
Login to your OPSCOM system with an administrator account that has permission to edit payment types.
In the OPSCOM menu select **System Configuration** → **Payments** → **Setup Payment Types** → **Add Type**.
Select "**Bambora - Checkout**" from the Provider list, then click "**Next Step**".
**Type Name:** The Type Name can be whatever you want it to be, though please note this will also be the name displayed to users during payment checkout when they are prompted to select a payment method.
You can reference the specific hosted payment provider or something more generic such as "Online Credit Card Payment", "Online payment", "Credit Card", etc. Really it's up to you and what you think makes most sense to your site users when making a payment.
**Enabled for User Types**: Select the User Types you wish this new Payment Type to be visible to so they can select it during payment checkout. You can change these user types at any time.
Once done make sure to click the "**Update Payment Type**" button at the bottom of this page.
**Enable for Text2ParkMe**: if you aren't using this module leave the button unchecked.**Enable for [Permit Renewal Payments](https://opscom.wiki/books/the-opscom-admin-portal/page/feature-overview-rolloverrenew-permits)**: if you aren't using this feature leave the button unchecked.**Enable for [Guest Payments](https://opscom.wiki/books/OPSCOM-user-portal/page/quick-easy-guest-payments)**: if you aren't using this feature leave the button unchecked.**Prompt Information**: This depends on whether or not you're enforcing AVS (Address Verification Service) in your Bambora account. This is set in Bambora under **Administration** → **Account Settings** → **Order Settings → Transaction Reversal Options Conditions.** If using AVS you will require the Prompt for to have "Billing Details" selected, which will prompt users to supply their billing address information during checkout so AVS can pass. Otherwise if AVS isn't required in your Bambora account you can select Email Address in which case no address information will be required from users making payments.
If using AVS Bambora recommends enabling only the “AVS Postal/Zip Code Mismatch” option as the Street Mismatch is extremely sensitive and may result in a high decline rate.
##### **Production Credentials:**
**Profile Authorization Header**: Copy and paste the **Profile Authorization Header** into this field as detailed in the steps above.
Example:
> Passcode MzAwMjZ0NDVxOkY0NRg0MkRDQkM4QTQxNTJCMTM1MUE4OAZxN0NCM4ND
**Payment Authorization Header**: Copy and paste the **Payment Authorization Header** into this field as detailed in the steps above.
Example:
> Passcode BVSTYjZ0NDVxLkY0NRg0MURDQkM5QTQxNTJCMTM1HUE3OBQxN0NBN8VC
##### Other Settings:
**Validate Card when adding subscriptions**: Optional setting related to when/if users add a subscription method in OPSCOM for this payment type and whether or not the card is validated by the payment provider when first added as a subscription method. If left unchecked the card will only be validated when/if used for a payment.
**Phone Number Field**: Usually hidden, but some payment providers may require a phone number for payments depending on your fraud detection settings. Recommend leaving hidden unless otherwise stated by your payment provider or if you check a setting in Bambora to require a phone number.
Make sure to click the "**Update Payment Type**" button at the bottom of the page.
# Authorize.Net
[](https://opscom.wiki/uploads/images/gallery/2024-06/ofiimage.png)
Development: [https://sandbox.authorize.net/](https://sandbox.authorize.net/)
This space is primarily for development against the Authorize.Net API. The sandbox area ensures no transactions are accidentally pushed through a "real" payment processor.
Production: [https://account.authorize.net/](https://account.authorize.net/)
The production space is the portal to access transactions and live account settings.
## Production (or Testing) Setup
There are several places where setup is required. The hosted payments page will need to be updated to present a consistent look for the end user. This can be done under the "Payment Form" option under the "Account" area as noted below.
As well, it should be noted that the receipt page and response details do not need to be completed. As part of the payment protocol OPSCOM supplies this information to Authorize.Net
[](https://opscom.wiki/uploads/images/gallery/2024-06/G9limage.png)
Please be aware your Authorize.net merchant account needs to have the following settings:
Product Type: **Card Not Present (CNP)**
Market Type: **eCommerce**
These settings are usually setup by your Authorize.net contact on the initial account creation. If you want to confirm the correct settings go to Account > Merchant Profile. Under the Business Information heading it will show your product and market type.
### API Credentials
API credentials are required for communication between OPSCOM and Authorize.Net. You will need 3 pieces of unique identification, one of which (API Login ID) is defined at the time of the account creation.
OPSCOM will need the following ID's
- API Login ID
- Transaction Key
- Signature Key
*Where to obtain these values is noted below.*
[](https://opscom.wiki/uploads/images/gallery/2024-06/2uYimage.png)
In the above screen shot we have chosen to generate a new Transaction Key. Upon selecting Submit, the new transaction key is presented.
[](https://opscom.wiki/uploads/images/gallery/2024-06/0ENimage.png)
NOTE
The generated **Transaction Key** and **Signature Key** together with the **API Login ID** need to be supplied to Tomahawk Technologies Inc. to complete the OPSCOM setup.
### Payment Form
You can style the payment form and add additional details to the hosted payment input page. As well, fields such as shipping address can be hidden on the payment form to remove any confusion for the end user.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Zzximage.png)
Suggested payment form options:
Note
Personal details can also be removed from the form since OPSCOM will automatically connect the payment to a user. Since users will often use credit cards that are not their own (spouse, parents, corporate) adding the additional fields is suggested.
[](https://opscom.wiki/uploads/images/gallery/2024-06/zdjimage.png)
AVS (Address Verification Service)
If AVS is enabled please make sure to set the following address fields required:
See [https://support.authorize.net/knowledgebase/Knowledgearticle/?code=000001490](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=000001490) for additional information on AVS
## Site Testing
Testing
This page includes ways to generate failure states: [http://developer.authorize.net/hello\_world/testing\_guide/](http://developer.authorize.net/hello_world/testing_guide/)
# Hosted Payments
- [OpenEdge Hosted Payments](https://opscom.wiki/books/the-opscom-admin-portal/page/openedge-hosted-payments)
- [Bambora/Worldline Hosted Payments](https://opscom.wiki/books/archive/page/bambora-hosted-payments)
- [Bambora/Worldline Checkout ](https://opscom.wiki/books/the-opscom-admin-portal/page/bambora-checkout)
- [Moneris Hosted Payments](https://opscom.wiki/books/the-opscom-admin-portal/page/moneris-hosted-paypage)
- [Paypal Hosted Payments](https://opscom.wiki/books/the-opscom-admin-portal/page/paypal)
- [SchoolPay ](https://opscom.wiki/books/the-opscom-admin-portal/page/schoolpay)
- [TouchNet uPay](https://opscom.wiki/books/the-opscom-admin-portal/page/touchnet-upay-hosted-payments)
- [Transact Campus/CashNet](https://opscom.wiki/books/the-opscom-admin-portal/page/transact-campuscashnet-hosted-payment-setup)
- [Authorize.Net - Limited Support](https://opscom.wiki/books/the-opscom-admin-portal/page/openedge-hosted-payments)
- [Chase Exact - Limited Support](https://opscom.wiki/books/the-opscom-admin-portal/page/chase-e-xact-hosted-payments)
# Technical Schematic - Step #1
Setting Up
1. Send an email to the offenders primary driver that they have a new violation. Generally you would issue the ticket on the same day as the violation.
2. Set a flag in preparation for collections. (If the violation is older than AutoNoticeDays)
1. If the violations connected user is primary driver and has an email address
1. send an email and flag appropriately (**AutoNotice** = 1)
2. set **Violation.AutoNotice** to 1
2. If the violations attached to the user are for the primary driver and they have no email
1. set flag to be added to the Letter Report (2)
2. set **Violation.AutoNotice** to 2
3. 30 days after items are tagged with either 1 or 2 **Violation.AutoNotice** and that have an associated Violation Notice will appear on the "send to collections" report
1. that report allows the administrator to select who/which items will be sent to collections
# Automatic Violation Notice
The Automatic Violation Notice Script sends New and Past Due violation notice emails to ParkAdmin users.
For a Lucid Chart Diagram See: Technical Schematic - Step #1
## OPSCOM Settings to be Confirmed:
Notice related settings are set under System Config > Notice Literature:
Violation days until due is set in Tomahawk Options > System Settings:
There are additional settings that will affect whether or not all unpaid violations will be added to the letter or if the selected violations will only be included when it comes time to create the letter report. These settings are found under **System Settings →** **Collections** → **Include All Unpaid Violations.** As mentioned this will allow you to select a single violation in the list and generate a report for all violations associated with that user. Keep in mind that means it will also remove the associated violations from the pick-list on the Printable Violation Notice Report page even if you only have one of the violations selected.
[](https://opscom.wiki/uploads/images/gallery/2024-06/TT9image.png)
## Notice/Email Summary:
In total there are 4 different types of emails that will be sent once the above is setup:
- **User overdue account notice** (lets normal users know they have a violation(s) past due in OPSCOM).
- **User new violation notice** (lets normal users know they have a new violation issued to them the day of, \*note: it seems this will NOT notify older violations once enabled, e.g. violation that is 3 days old vs 1 day old, would only notify the 1 day old user since it's "new").
- **Admin past due violation report notice** (emails the OPSCOM administrator telling them how many users were emailed past due violation emails AND also how many users couldn't be emailed because they didn't have an email address in the system. These users are added to the "letter report", more info below).
## The NIC Letter
As part of the MTO process an admin can set up a **N**otice of **I**mpending **C**onviction (NIC) letter that can be sent to users who have outstanding violations that will be collected through Ontario courts.
To configure this letter go to System Messaging and edit the Notice Letter found in the Messages tab.
You can read more about Notice Letters/NIC on this page.
Letter Report:
Users who couldn't be emailed their overdue violations are added to the letter report, which is accessible under Violations > Letter report on the OPSCOM Website. The letter report was created so that OPSCOM administrators can print and mail out overdue violations if they so choose.
[](https://opscom.wiki/uploads/images/gallery/2024-06/GYAimage.png)
Note: When arriving at this page the results can fall into two categories: Printable Violation Notices and Unprintable. The Unprintable means that there is an incomplete mailing address.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Otfimage.png)
## Resending a NIC Letter
Once a NIC letter has been sent it is stored with the associated violation. If for any reason you wish to resend or re-output the letter you can do so from the ticket detail. Search for the ticket or locate it on the user's profile then click on the ticket number to view the ticket detail. From here you will see the Overdue Letter button. By clicking on this button you will be able to view and resend the notice.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Mzdimage.png)
# Collections Module
## Accessing the Collections Module
[](https://opscom.wiki/uploads/images/gallery/2024-06/Serimage.png)
There are several steps leading up to a collection since often notification of a user is all that may be needed to collect on overdue funds.
The collections module is currently tied to the Violations menu, but may in the future work with all modules in the system. Originally the implementation worked around the idea that people parking on campus may be unknown users. By having a collection module (and the MTO lookup functionality) unknown user details can be determined from a vehicle tag (plate, province, etc.). Students and staff users can be dealt with in a different manner but can also be sent to collections. In the case of a student, they can be denied graduation if their account is not paid in full.
## Collection Module Operation
In this particular case, the items related to MTO lookup are based on a data format for the Ministry or Transportation Ontario, but could be adjusted to match requirement in any area.
- ### **Vehicle Lookup Export**
- allows an administrator to export data in a MTO friendly format. This export can be imported to the MTO terminals by MTO staff (or automation) and the result is an MTO Lookup Report.
[](https://opscom.wiki/uploads/images/gallery/2024-06/w3oimage.png)
- ### **Import from Lookup (MTO)**
- allows an administrator to import the unknown user details back into the system and populate address and contact fields.
- ### **Known Report**
- allows an administrator to query and package accounts (as an Excel export) that should be sent to a collection service provider
- Internally it sets the "SentToCollections" flag on the associated violations so that future queries will not duplicate listings
logic around this report is defined as follows:
- **If** (the user has an email and an **overdue notice** *(details below)* that was sent more than 30 days ago)
**OR** (the user does not have an email and the violation is past due date)**Then** include them on the report based on the supplied parameters (user type and days overdue)
[](https://opscom.wiki/uploads/images/gallery/2024-06/g2nimage.png)
- ### **Send to Known & Unknown Report**
- generates a report of the accounts "SentToCollections" based on the date and user type
- the report includes details related to payment where applicable
[](https://opscom.wiki/uploads/images/gallery/2024-06/R95image.png)
## Overdue Notices
See also: Technical Schematic - Step #1
*This document highlights the first steps leading to a collection.*
As part of system automation, overdue notices on violations can be sent out each night. If this is not enabled on your system, please contact Tomahawk Support to have this feature enabled.
Each night the system will create an email list and send overdue notices to any known users that have emails on the system. Essentially the system looks up overdue violations, then looks up vehicles and users associated with those vehicles. From that information it may be able to obtain an email address and formulates a message for delivery to the user.
When the message is sent, the violation field "AutoNotice" is flagged in the database.
In the event a user does not have an email address, or the users are unknown, a report is compiled containing that information and is sent to the system administrator.
An overdue sample message follows:
[](https://opscom.wiki/uploads/images/gallery/2024-06/dEbimage.png)
# What does a refund look like in the system?
##### What does a Refund do in OPSCOM?
Think of a refund as hitting the "undo" button for a completed transaction. When you process a refund:
- Money Back: The customer gets their payment reversed.
- Item Released: The item(s) they purchased become available again in our inventory, ready to be sold to someone else.
**Important Note:** When you refund an entire transaction, **all items within that transaction will be reimbursed, and all of them will be released back into inventory.** If only one item needs to be reimbursed, **do an adjustment** and release the item separately.
1\. Locate the user profile for the user you want to refund for.
Note: The top right-hand corner will always identify the name of the user that is being worked on. In our example we will refund **Permit #1** at **$395.50** but keep in mind the process is identical for and refund such as Standard Permits, Temporary Permits, Locker rentals, violations etc.
2\. From the **History Tab** select **All Records.**
#### For Standard & Temporary Permits or Lockers
3\. Find the permit you want to refund and click on the Processed **date** link.
[](https://opscom.wiki/uploads/images/gallery/2024-06/HLoimage.png)
#### **For Violations**
Click on the word **Processed** to access the transaction details.
[](https://opscom.wiki/uploads/images/gallery/2024-06/0QUimage.png)
4\. The **Transaction Details** screen appears. Click on the **Refund** button to begin the refund process.
The **Refund Payment Record** window will pop up. Enter the internal organization **Requisition Code** (optional) and the **Refund Amount** (including taxes). You are required to enter a **comment** in order to proceed.
[](https://opscom.wiki/uploads/images/gallery/2024-06/S4Ximage.png)
5. Click the **Refund Payment Record** button to continue. A confirmation pop-up will appear. Click **OK** to continue.
**IMPORTANT**: **By using refund for permits and lockers you will be releasing all items associated with this Confirmation Number. Violations however will simply go back to awaiting payment status.**
6\. The **Adjustment Information** pop-up will display showing the refund details. You have the ability to select the type of refund in this window.
7\. Click on **Process This Adjustment** to proceed. You will return to the **Transaction Detail** window showing the details of the refund. Notice the refund amount of **$-395.50** is listed as an **adjustment**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/4cNimage.png)
8\. To see how this appears in the user's profile on the admin side, go back into the history tab and select **All Records**. In the user history we see the record of the original purchase as well as; (1) **Released** date and a note indicating the permit is **"Released back to system by refund process"** and (2) **w**e can also see the refund under **Adjustment Records.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/7fsimage.png)
#### Refunding to Deal with a NSF Payment
Sometimes, a payment fails (like a cheque bouncing – known as "NSF" for Non-Sufficient Funds). When this happens, we need to "refund" that payment in the system to keep our financial records accurate.
#### Why do we refund a NSF Payment?
It's essentially a bookkeeping task. Imagine a cheque came in and was recorded as a payment. If that cheque then bounces, we need to remove that "incoming" payment from our system. By performing a refund, we create an "outgoing" record that balances out the initial "incoming" record of the failed payment. This way, our system accurately reflects that the money never actually arrived.
After you process the refund for an NSF payment, reports (like the Processed Payment Report) will show both the initial "payment" and the subsequent "refund." This is perfectly normal and correct! It records the *attempt* to pay, and then the removal of that payment due to the NSF.
**Key Tips for NSF Refunds:**
- **Payment Type:** When you process the refund for an NSF, be sure to select the **same payment type** (e.g., "Cheque") as the original failed payment. This makes sense for anyone reviewing your accounting.
- **Clear Notes:** It's super important to leave **clear and detailed notes** documenting the failed payment and the exact reason for the refund. This helps everyone understand the situation later on!
# Cancel Transaction
### Cancelling
On the **Transaction Details** screen you can see the different options available. You can choose to **Cancel & Keep** or **Cancel & Release**.
- **Cancel & Keep** will cancel the transaction but keep the transaction details and reserve the permit so that you can process the payment at another time.
- **Cancel and Release** will cancel the payment and release the permit back into the system
[](https://opscom.wiki/uploads/images/gallery/2024-06/Qtjimage.png)
A pop-up message will ask that you confirm. Click OK to confirm the cancellation of the transaction.
# Adjustments
## Making an Adjustment as an Admin
1\. Note that the top right-hand corner will always identify the name of the user file that is being worked in.
[](https://opscom.wiki/uploads/images/gallery/2024-06/ncfimage.png)
2\. For this example, when finished going through the payment process, on the **Transaction Details** screen, select the **Adjust** link.
(Note the process is the same if you select the adjustment link before a transaction is completed.)
This will bring up the **Create Adjustment Record** pop-up screen. Enter in the internal organization **Requisition Code**, change the amount sign to positive if you are charging the user more or change the amount sign to a negative if you are reimbursing the user, enter the dollar amount of the adjustment, enter any comments to be associated with the adjustment and select the **Add Adjustment** button at the bottom of the screen. This will bring you back to the **Payment Details** screen with the adjustment listed below the original transaction. Note, at this point, the adjustment is not processed.
[](https://opscom.wiki/uploads/images/gallery/2024-06/FtFimage.png)
3\. Select the **Not processed** link. This will bring up the **Adjustment Information** pop-up screen where you verify the adjustment details are correct.
[](https://opscom.wiki/uploads/images/gallery/2024-06/QgFimage.png)
4\. If the adjustment details are correct, select the **Process this Adjustment** button at the bottom of the screen. You will notice the **Payment Status** line will change from **Not Processed** to **Submitted** and the date. This completes the adjustment process, altering the dollar amount associated with the item. Note, no items are released back into the inventory system using the adjustment process. If an item needs to be released back into the inventory, this will need to be done separately.
## **Adjusting a Violation Before Payment**
# Adjusting a violation to zero dollars
## Adjusting the fine amount by editing the ticket:
1. To adjust the fine amount on the ticket go to the user's profile and locate the **violation** you wish to reduce.
[](https://opscom.wiki/uploads/images/gallery/2024-06/d1Simage.png)
2. Click on the **ticket number** to access the **Violation Information** detail screen.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Sa9image.png)
3. Click on the **Edit** button in the upper right corner to access the **Edit Violation Information** page.
Halfway down the page you will see the offence listed as well as the amount of the violation.
Edit the dollar value of the fine to **$0.00.**
Click on **Update this Violation** to save your changes.
[](https://opscom.wiki/uploads/images/gallery/2024-06/qu6image.png)
4. The violation will now appear in the user profile as a zero dollar fine.
[](https://opscom.wiki/uploads/images/gallery/2024-06/YUBimage.png)
## Cancelling a fine by changing the ticket to a warning:
An admin can change a ticket to a warning which will result in cancelling the fine amount.
1. To do so **edit** the ticket as described above.
2. Check the box next to the word **Warning** to change the state of the ticket. Click on **Update this Violation** to save your changes.
[](https://opscom.wiki/uploads/images/gallery/2024-06/C9wimage.png)
3. The ticket will appear as follows in the user history. (Captured here from the admin side.)
[](https://opscom.wiki/uploads/images/gallery/2024-06/i5Himage.png)
4. This is how it would appear on the user side:
[](https://opscom.wiki/uploads/images/gallery/2024-06/l6vimage.png)
## Adjusting the fine amount by processing an adjustment:
This scenario is slightly different as adjustments to fines are done **after** the initial fine has been paid for.
1. To begin, go to the user's history and locate the violation you wish to zero out.
In our example we are using Ticket number **TT-10011.**
Click on the **Adjust** link on the left.
[](https://opscom.wiki/uploads/images/gallery/2024-06/7HRimage.png)
2. The **Create Adjustment Record** window will open.
Enter the amount you wish to reduce the fine by. In this case the current fine is $*40.00* (the violation had a fine of $*50.00,* but was paid within the widow where the discount of *$10.00* applied)
It is advisable to enter a comment as to why the fine is being reduced.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Jw2image.png)
3. This method will place an adjustment on the user's account. This is what it will look like in the payments tab.
This adjustment can be applied to a future payment or be processed as a refund.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Uj5image.png)
## Adjusting the fine through the appeals process
A fine can be adjusted or reduced to zero through the appeals process.
# Types of Reimbursement
## Cancel Transaction
- To cancel a transaction **before** a payment is processed
**When would you cancel a transaction?**
- User decides not to follow through on a promise to pay
**Note:**
- Items in the transaction are released back to the system
- The promise to pay is removed from the user (user no longer owes money)
## Adjustments
- Alter the cost of an item **before** it has been paid for
- Alter the value of a transaction**after** it has been paid for
**When would you apply an adjustment?**
- User was charged too much or too little for an item
- User is being refunded part of a transaction (ie. not longer using item; pro-rated refund)
- Adjustments can be positive or negative
- Can also be considered refunds, but full transaction refunds are a different option
**Note:**
- Items are not released back to the system
## What does a refund look like in the system?
- Item is (or items are) returned **after** it has been paid for
- Transaction needs to be cancelled**after** it has been paid for
**When would you give a refund?**
- User has decided against the purchase
- Transaction is totally incorrect and it is easier to start over
- A refund can be used to **reverse** the transaction
**Note:**
- Transaction items are released back to the system
- If there is more than one item in the transaction, all items will be reimbursed and all items are released back to the system. If only one item needs to be refunded/reimbursed, do an adjustment and release the item separately.
# Payment Processing Models
## Using a Gateway
This is being phased out as the method for handling payments.
## Using Hosted Payments
This is the preferred method for handling payments.
[](https://opscom.wiki/uploads/images/gallery/2024-06/G8Yimage.png)
# Payments and Transaction Flow
The flow is a 3 step process, which includes:
1. User/Admin link item to user
2. User makes payment promise
3. Admin processes payment
## Step #1:
A user or an administrator links a permit to the user. At this point, there is no payment link and the item is "**Awaiting Payment**" since the user has not selected a payment method (*made a promise of payment*). As well, items (permits) are not accessible to any other system user. *There is a midnight clearing list which can automatically release permits linked to users that do not have promises for payment.*
## Step #2:
User or admin links a **payment type** (ie. cheque, cash, etc.) This puts the user on the **Unprocessed Payments** list, and that list needs to be checked regularly. This allows a user to mail in a cheque or to stop by the office to make payment. In these cases, a user has "promised" to pay. We suggest that permits be released (Drop Payment) after 2 weeks since that offers users enough time to make payment.
## Step #3:
Once payment is received (cheque is received in the mail, or the user stops by the office to make a payment) the transaction is marked as **processed** and the user is linked to the item. At this point, the item is marked processed and is actually (completely) linked to the user.