**Deposit Types** allow administrators to define and manage various categories of deposits (e.g., for permits, equipment, or specific services). This feature is essential for accurately tracking refundable amounts, providing clear financial oversight, and ensuring proper accounting for deposited funds within the system.
### Using this Feature The **Manage Deposits** page provides a straightforward interface to add, edit, and view the usage of various deposit types. 1. Hover over **System Configuration,** then **Payments,** and click **Manage Deposit Types**. ##### Adding a Deposit Type 1. Click **Add Deposit Type**. 2. Fill out the information as needed: - **Label**: This is the name that will be used to identify the deposit type (e.g., "Permit Deposit," "Key Fob Deposit"). - **Placeholder Text**: This field is optional. It provides a prompt or sample information that will appear in the deposit information text field when creating a deposit record. - **Flags**: This toggle controls the ability to edit the **Assignable Text** field in the resulting active deposit record. This text will appear in the user's profile associated with the deposit. - **Amount**: The amount that the deposit will cost. - **Active checkbox:** This determines if the deposit is currently available to be assigned. 3. Click **Save Changes**. ##### Editing a Deposit Type 1. Locate the deposit type and click the **Edit** button next to it. 2. Make any necessary changes to the fields. 3. Click **Save Changes**. ##### Deleting a Deposit Type 1\. If no records are associated with this deposit you can click the **Delete** button. --- ### Best Practices & Considerations - **Clear Labeling**: Use descriptive labels for your deposit types (e.g., "Annual Permit Deposit," "Visitor Pass Deposit") to ensure clarity for both administrators and users. - **Placeholder Text Utility**: Utilize the **Placeholder Text** to provide clear instructions or examples for administrators when entering deposit information. - **Understanding "Flags"**: The "Flags" setting for `Assignable Text` can be useful for adding specific, customizable notes to individual deposit records on user profiles, allowing for unique details per transaction. - **Financial Reconciliation**: Accurately tracking deposit types is crucial for financial reconciliation and managing refundable amounts. # New PagePreview Spaces in OPSCOM provide clients and support staff with a secure, isolated testing environment that mirrors your live production system's data. These spaces are invaluable for testing new features, staging changes, or conducting training without impacting your operational system, ensuring a safe sandbox for development and learning.
### Setup & Configuration Preview spaces are typically created on demand. Your production/live OPSCOM system is used to either create a new preview space or refresh an existing one with current or historical data. ##### Creating or Refreshing a Preview Space 1. Click **Tools,** then **Database to Preview**. From this page, you have two options for refreshing your preview database: - **For Up-to-Date Information**: 1. Select **Backup Production Database**. 2. Wait for the backup process to complete. 3. Click the **Refresh Preview Database** button. - **For an Older Backup**: 1. Select the specific date of the backup you wish to restore the preview database to. 2. Click the **Refresh Preview Database** button.It may take a few minutes to refresh the database. Generally, a database is refreshed in 1-2 minutes, but it can take up to 15 minutes depending on the size of your database. A message will be displayed along the top of the screen notifying you when the database refresh is complete.
Once the preview database has been refreshed, your preview system will automatically be created or updated. You can access the preview system by adding ".preview" before "OPSCOM.com" in your browser's address bar. For example, if your production space is `https://tomahawku.OPSCOM.com`, your preview space will be `https://tomahawku.preview.OPSCOM.com`. --- ### Using this Feature ##### Accessing Your Preview Space As an OPSCOM client, you can access your preview space directly by simply adding the ".preview." suffix to your subdomain name. For instance, if your production site is located at `https://yourorganization.OPSCOM.com`, your preview space can be found at `https://yourorganization.preview.OPSCOM.com`. ##### Preview Space Banner To clearly distinguish a preview space from a live production system, all preview spaces are denoted with an **amber warning banner** displayed prominently at the top of the page. ##### Locking and Unlocking Database Reset Option You can now lock and unlock preview and development OPSCOM databases to prevent them from being reset or refreshed accidentally. 1. On your preview site, click **Tools**, then **Reset Database**. 2. Toggle the lock/unlock setting as needed. - You will be prompted to provide a **reason** for locking or unlocking the database. - A history of the previous 10 lock/unlock actions will be displayed below for your reference. This feature allows you to ensure that if you are actively working on a preview/development system and do **NOT** wish for your changes to be reset or lost, you can place a lock. This lock notifies others attempting to refresh the database that a reset is not desired. --- ### Best Practices & Considerations - **Testing and Training Benefits**: Preview spaces are extremely useful for testing and training purposes. They allow you to work with a copy of your live database, providing real data for exercises without any risk of affecting your production system. The database can be manually reset at any time, allowing you to "erase" training data and start testing scenarios from scratch. - **Daily Data Backups**: Production/live data is backed up daily at **2 AM EST** and is available to push to the testing environment at any time. This means if you perform a refresh of your preview site, it will pull data captured the night before. This operation is specifically for providing relevant data for testing and preview during training or similar efforts and is separate from normal system backup procedures. - **Automatic Deletion of Inactive Spaces**: Preview sites are automatically deleted after **7 days of no login activity**. - If you require a preview site for an extended period, please contact OPSCOM support staff, and an expiry date can be set. - **Email Notifications are Suppressed**: No Emails Sent from Preview/Testing - All email notifications that would normally be sent from the server are captured and suppressed in preview/testing environments. Therefore, any email notifications generated within your preview space will **not** reach clients or external recipients. This is a deliberate security measure to prevent accidental communication from a non-production environment. # Managing Payment Types**Managing Payment Types** allows administrators to control which payment methods are available throughout the system. This comprehensive control enables you to define new payment options, assign them to specific user types (e.g., Staff, Students, Public), and configure their usage for subscriptions or guest payments, thereby streamlining transactions and ensuring alignment with your organization's financial policies.
### Using this Feature The **Payment Types** screen gives you a comprehensive interface to create, edit, and view details about different payment methods available in OPSCOM. 1. Go to **System Configuration,** then **Payments,** and click **$ Setup Payment Types**. ##### Adding Payment Types**Use Case -** For this example, we will setup a Payment type that will use the provider Always Successful. This will allow payments to immediately be flagged as fully processed with no intervention of any admin. This is often used for things like Payroll deduction. For example, you want your users to be able to purchase a permit through Payroll deduction that will immediately be valid upon checkout. The actual payments will take place through payroll and have nothing to do with OPSCOM.
1. Click the **Add Type** button. 2. The list of **Providers** is hard coded and controlled by Tomahawk. You will not be able to change this picklist. The tooltip below the provider will tell you what each provider means. 3. Pick **Always Successful** for this example. 4. Click **Next Step.** 5. Provide a **Type Name.** 6. Choose the **User Types** this will be available to. 7. On the **Settings** tab, Enable the checkboxes as you required. 8. In the section **Allowed Payment Types**, you will see any payment types that are currently active first, then a list of inactive payment types after. 9. Click **Update Payment Type**. ##### Hosted Payment Providers The following links will detail the process of setting up a Hosted Payment provider, of which currently support. Click the link matching the payment provider you are adding below and follow the steps outlined on those articles. - [OpenEdge](https://opscom.wiki/books/the-opscom-admin-portal/page/openedge-hosted-payments): - We need the following credentials to work with OpenEdge; - **Auth Key**: a multi-digit string key - **Terminal ID**: a 8 digit numeric key - **X-Web ID**: a 12 digit numeric key - [Moneris Checkout](https://opscom.wiki/books/the-opscom-admin-portal/page/moneris-checkout): - We need the following credentials to work with Moneris Checkout; - **store\_id: ***store#*** ** - **api\_token:** *xxxxxxx* - **checkout\_id:** *xxxxxxxxStore#* - [Bambora Checkout](https://opscom.wiki/books/the-opscom-admin-portal/page/bambora-checkout): - We need the following credentials to work with Bambora Checkout (JSBambora): - **Payment Authorization Header:** An alphanumeric passcode - **Profile Authorization Header:** An alphanumeric passcode Once you retrieve the required values from your hosted payment provider of choice, save the credentials securely and contact OPSCOM Support for further instructions.The information you obtain in the above documentation are **credentials that secure the information exchanged between OPSCOM and the provider.** Please save these in a secure manner, it is important they are stored properly to ensure operational security.
##### Extended Payment Information For each payment type, you can view extended information on the Payment Types screen. - A **general description** of the payment type. - An **indication of what the user will be prompted for** when selecting that payment type. For example, in a hosted payment scenario like EdgeExpress, the user might be prompted to enter an email address before being redirected to the payment provider to enter credit card information. - The number of users associated to this payment type. There are also three columns on the far right that use an **X** or **checkmark** to indicate specific uses of the payment type: - **Column 1**: Indicates if this payment type can be used for **guest payments**. - **Column 2**: Indicates if this payment type can be used for **permit and invoice renewal payments**. - **Column 3**: Indicates if this payment type can be used for **Text2ParkMe subscriptions**. ##### Configuring Payment Types for Subscriptions and Guest Payments You can fine-tune how specific payment types are used for subscriptions and guest payments. 1. Find the payment type you wish to configure and click the **Pencil icon**. 2. Click the **Settings** tab. 3. Select the items you wish to allow the payment type to be used for (e.g., enable **Text2ParkMe**, **subscriptions to permit renewals**, as well as **guest payments**). 4. Prompt Information can be changed as well. You can enable only an **email address** or **full address information**. Full address info is required when the provider is doing Address Verification using AVS, 3DS or other similar service. This controls what shows up on the **QR Code reservations** screen after the **Payment Type** is selected. 5. Click **Update Payment Type**. ##### Processing as an Admin When processing payments as an administrator, the payment types presented will be split into two categories: - What the user would be allowed to use for their specific User Type. - What an administrator can choose (which may include additional options not visible to the user). --- ### Best Practices & Considerations - **Granular Control**: Leverage User Types to restrict payment methods, ensuring users only see relevant options. For example, you might only allow "Payroll Deduction" for Staff users. - **Clear User Experience**: By limiting available payment types based on context or user, you simplify the checkout process and reduce confusion for users. - **Refund Alignment**: Ensure that appropriate refund types are linked to their corresponding payment types to facilitate smooth and accurate refund processing. - **Subscription Compatibility**: When enabling payment types for subscriptions (recurring billing), verify that the chosen payment gateway provider fully supports recurring transactions. - **Regular Review**: Periodically review your payment type configurations and their associated settings to ensure they remain aligned with your organization's financial policies and evolving needs. # Managing Convenience Fees**Convenience Fees** in OPSCOM allow administrators to add an additional flat-rate charge directly to user payments, managed entirely within the OPSCOM system. This feature provides flexibility to offset processing costs, incentivize certain payment methods, or cover administrative burdens, distinct from any transaction fees imposed by external payment providers.
### Difference Between Transaction Fees and Convenience Fees It's crucial to understand the distinction between these two types of fees: - **Transaction Fees**: These are charges applied by your **payment provider** (e.g., credit card processor) for processing a payment. They are independent of OPSCOM's internal settings. Depending on your setup, OPSCOM and end-users may not be directly aware of these fees as they are managed solely by the payment provider. - **Convenience Fees**: These are additional charges that are **managed and applied directly through OPSCOM**. For example, your OPSCOM system can add a $5 convenience fee onto a payment. This fee amount is visible within OPSCOM and is added to the grand total before being sent to the payment provider. It is possible for a system to utilize both Convenience Fees (managed by OPSCOM) and Transaction Fees (managed by the payment provider), but recognizing their distinct origins and management is important. --- ### Using this Feature The **Fees Page** allows you to set up various convenience fees.You can only use Convenience fees if you have Bambora/Worldline as your payment provider.
##### Fee Limitations Before configuring, understand these limitations:The **Taxes** configuration page in OPSCOM allows administrators to define and manage the tax percentages applied to payments made within the system. This feature is crucial for ensuring accurate tax calculation during checkout, maintaining compliance with local tax regulations, and providing transparency to users regarding applicable taxes.
### Setup & Configuration You must be a Primary Admin with the permission to **Manage System Configuration** to be able to edit the system settings.If you do not see the settings mentioned in this article, please contact
This article describes the Flex Dollar and Payroll Deduction feature, a specialized payment method for handling partial payments with credits. This feature allows your users to apply a pre-defined amount of **flex dollars** towards a permit purchase, with the system automatically notifying administrators of the remaining balance to be processed via payroll.
#### OPSCOM Support Configuration The **Flex Dollar Payment** feature is a *custom development,* tailored specifically for one client, Trent University. It is not intended to be useful to, or available to all clients. Its availability is controlled by specific configurations set up by an OPSCOM Support team member. This feature requires configuration by an administration of your system, and must also be enabled by an OPSCOM support team member before it can be used. The setup involves defining the selectable flex dollar amounts, setting the notification email, and assigning the payment type to the appropriate users. #### This feature is enabled by a system-level setting that is typically configured by OPSCOM support upon request. Once enabled, you may proceed with the steps below. #### Configuration and Functionality 1. To enable flex dollars, hover over **System Configuration**, and click **System Settings**. 2. Click **Permits**. 3. Enable the checkbox beside **Enable Flex Dollars**. ##### Configure Email Notifications An email address must be configured to receive a notification internally and each time this payment method is used (and the details of the transaction for accounting). 1. Hover over **System Configuration, Payments** and click **Manage** **Flex Dollars** 2. In the **Flex Dollars Alert Email** text box, enter an email address you will be monitoring. This email address must be monitored for any changes to be made to student flex dollar balances. ##### Define Flex Dollar Amount Create the specific flex dollar values that users can select during checkout. 1. Hover over **System Configuration, Payments,** and click **Manage** **Flex Dollars.** 2. Click the **Add New** button. 3. Enter a **Label**. This is the text the user will see in the drop-down menu (e.g., "Apply $100 of Flex Credit"). 4. Enter the corresponding numeric **Value** (e.g., `100.00`). 5. Click **Save**. 6. Repeat this process for all the pre-determined flex dollar amounts your organization offers. ##### Assign Payment Method to User Types Finally, this payment method must be enabled for the specific user types who are permitted to use it. 1. Hover over **System Configuration**, **Users**, and and click **User Types**. 2. Select the user type you wish to grant access to (e.g., Staff). 3. In the user type settings, assign the **Flex Dollars/Payroll Deduction** payment option. 4. For detailed instructions, please refer to the [User Types Administration wiki article](https://opscom.wiki/books/setup-configuration-for-admins/page/user-types "https://opscom.wiki/books/adminstrators-setup-configuration/page/user-types"). ### Using this Feature Once configured, the feature provides a streamlined workflow for users and a clear notification process for administrators. ##### User Purchase Workflow 1. An eligible user adds a standard term permit to their shopping cart. 2. On the checkout page, they select **Flex Dollars/Payroll Deduction** as the payment method. 3. A new drop-down menu appears, populated with the flex dollar **Labels** you configured. 4. The user selects an amount and completes the transaction. Their permit is considered valid and is issued immediately. ##### Administrator Workflow (Post-Purchase) 1. Upon successful purchase, an email is automatically sent to the address configured in ***"Flex Dollar Alert Email"*** field. 2. This notification contains the key information needed for manual processing: - User's Name and Contact Information - Permit Details - Flex Dollar Amount Applied - Remaining Balance Due 3. Your administrative team (e.g., Payroll or Parking department) uses this information to confirm users flex dollar balances the remaining balance via your organization's internal payroll system. 4. For auditing purposes, a note detailing the flex dollar amount is also automatically added to the users transaction payment record.The payroll deduction component is **not an automated process** and **neither is the updating of Flex Dollar balance**. The system's function is to calculate and report the remaining payroll deduction balance to administrators.
# Best Practices & Considerations - This payment option will **only appear to eligible users when their cart contains only standard permits**. It will not be available if other items, such as violation payments or locker rentals, are also in the cart. - **Use clear and descriptive labels** for the flex dollar amounts (e.g., "Use $75 Payroll Credit"). This transparency is key to reducing user confusion and support requests during the checkout process. - **Ensure the staff who manage payroll are aware of this workflow** and understand how to act on the email notifications. Clear internal communication is critical to the success of this feature. - **External Verification & Reconciliation:** It is critical to understand that OPSCOM does not verify real-time flex dollar balances with any external system. Administrators are solely responsible for independently verifying the spent flex dollar amounts with their HR/payroll department and managing any discrepancies or adjustments outside of the OPSCOM system. **Note: **this type of payment is treated as a full, successful payment. The system does not have split-payment logic or backend validation of flex balances beyond recording the user's chosen amount. # Stripe Payment Provider SetupThis feature shows how to integrate with Stripe to process credit card payments directly within the system. Its primary purpose is to provide a secure and seamless checkout experience for users while simplifying financial reconciliation for operations. This article is intended for **OPSCOM administrators** responsible for financial setup.
--- ## Setup and Configuration ### Admin Portal To begin the integration, an administrator must setup a payment type in OPSCOM, with will be linked to their Stripe account. This is handled through the central administration portal where you will input your unique credentials. - Hover over **System Configuration > Payments**, then click **Setup Payment Types**. - Click **Add Type**. - Click the **Payment Provider** drop-down menu and choose **Stripe.js** from the available options. Once the provider is selected, you can **name the payment type**, **select applicable user types**, and then **go to the settings tab*.*** Now, you have to get the API keys for your Stripe account, and setup webhooks, which can be found on the stripe dashboard, which you should be logged into, from a previous step. Your **Publishable Key**, and **Secret Key**, can be found and copied here. You can click on these values to copy them, and paste them into the payment type settings in OPSCOM. [](https://opscom.wiki/uploads/images/gallery/2026-04/VOiimage.png)You must provide your unique identification keys. Enter your Stripe public key into the **Publishable Key** field and your Stripe secret key into the **Secret Key** field. **Only enter the Testing Credentials until you are ready for your users to have access to this.**
Take this time to ensure that the ***Currency*** setting is correct, in the payment type settings (the default is US dollars). The next steps will be about populating the **Webhook ID** and **Webhook Secret** fields, in OPSCOM, with the correct information from your Stripe dashboard. [](https://opscom.wiki/uploads/images/gallery/2026-04/gCTimage.png) --- ### Third-Party Webhook Configuration Webhooks are essential for Stripe to notify OPSCOM regarding payment successes or refund completions.Without these Webhooks, the system **WILL NOT** communicate any transaction information to OPSCOM.
| Sub-section | What it covers |
|---|---|
| **Register Your Endpoint** | Step-by-step Stripe Dashboard instructions to create an event destination, select event types, and enter the OPSCOM webhook URL |
| **Retrieve Your Signing Secret** | How to reveal and copy the `whsec_` secret, and destination ID into OPSCOM |
| **Test Your Endpoint** | Stripe CLI commands to forward live test events locally before going live |
| **Secure Your Endpoint** | Signature verification explanation and IP allowlisting recommendation |
| **Manage Event Delivery** | Delivered/Pending/Failed status descriptions and how to manually resend events |
Ensure that your **Webhook Secret** is correctly matched between Stripe and OPSCOM to prevent "Pending" status errors on completed payments.
[](https://opscom.wiki/uploads/images/gallery/2026-04/E3jimage.png) --- ## User Experience and Handheld Use ### Web Portal Transactions Users will interact with the Stripe interface during their standard checkout process. When they reach the final stage of a transaction, they simply click the **Pay with Credit Card** button to open the secure payment form. After they enter the credit card details into the form, they click the **Submit Payment** button to complete the purchase. ### Handheld App — *OPSCOM Parking Enforcement* For administrators or staff using handheld units in the field, the process is optimized for touch interaction. Tap **Checkout** to open the payment summary within the app. From there, tap **Select Payment Method** and choose **Stripe**. To prevent accidental charges, the final step requires you to tap and hold the **Process Payment** button to finalize the transaction. ## Managing Transactions and Reports Administrators can review all processed payments and manage financial returns through the standard reporting interfaces. Hover over **Financial Management** and click **Transaction Reports** then **Recent Payments** to view a live list of activity. Within this report, the **Status** column displays the current state of each payment, while the **Payment Date** indicates exactly when the transaction occurred. If you need more detail, click the **View Details** icon next to a specific transaction to see the full Stripe receipt. If a correction is needed, click the **Refund Payment** button to initiate a return of funds. You will then click the **Confirm Refund** drop-down menu and choose **Full Refund** to finalize the reversal.You can quickly find a specific transaction by using the search bar to enter a user's name or a specific receipt order ID/Confirm Code.
--- ## Best Practices and Considerations - **Deployment Testing** Organizations should always keep **Live Mode** disabled during the initial deployment until all testing is verified with test credit card information. It is highly recommended to process a single, small test transaction in **Live Mode** using a real card before making the payment option available to the general public. - **Security Requirements** Maintaining the security of your financial environment is critical. You should never share your **Stripe Secret Key** or **Webhook Secret** with anyone or store it in plain text outside of the secure administration configuration screens. - **Change the signing secret periodically**, and only subscribe to required event types.