OperationsCommander - https://opscom.wiki

Payments and Transaction Flow

The OPS-COM system utilizes a standardized three-step transaction flow to manage the lifecycle of user purchases, such as parking permits. Understanding this workflow helps administrators accurately track financial commitments and manage inventory status from the initial reservation to final payment. This guide is intended for OPS-COM administrators responsible for financial processing and user account management.

Setup and Configuration

The payment transaction flow is an inherent system process within OPS-COM and does not require specific module configuration to function. However, administrators should ensure their payment methods and gateways are correctly configured before users attempt to make purchases.

Using this Feature

The lifecycle of an item purchase consists of three primary stages: linking the item, making a payment promise, and processing the payment.

Step 1: Linking the Item to a User

A user or an administrator links an item, such as a permit, to a user's account.

The system utilizes an automated midnight clearing list. If a user reserves an item but does not proceed to the next step to establish a promise of payment, the system will automatically release the permit back into the available inventory at midnight.

Step 2: Making a Promise of Payment

The user or administrator selects a specific payment type (e.g., cash, cheque, or payroll deduction) to finalize the reservation.

Step 3: Processing the Payment

Once the physical payment (cash, cheque, etc.) is received by the office, the administrator must finalize the transaction in the system.


Best Practices and Considerations


Take Command of Your Parking and Security - https://OperationsCommander.com

Revision #2
Created 14 May 2024 07:18:01
Updated 8 July 2026 11:09:36