Hosted Payments

The Hosted Payments functionality allows organizations to integrate secure, third-party payment gateways with the OPS-COM platform. Its primary purpose is to facilitate online transactions for user purchases—such as permits, lockers, and violations—while maintaining strict PCI compliance by redirecting sensitive credit card data to the provider's secure servers. This article is intended for OPS-COM administrators.

Setup and Configuration

Because OPS-COM supports a wide variety of hosted payment providers, the specific configuration steps depend heavily on your chosen merchant gateway. However, all hosted payment integrations are managed from the same centralized administrative menu.

1. Hover over System Configuration and click Payments then Setup Payment Types.

2. Click the Add Type button.

3. Select your specific merchant gateway from the provider drop-down menu.

For detailed, step-by-step instructions on generating the required API credentials and configuring the backend settings for your specific gateway, please refer to the appropriate integrated wiki article below:

Maintain Credential Security: Never share your payment gateway API keys, passwords, or token IDs openly. If your gateway credentials expire or are reset within your merchant portal, you must immediately update them within your OPS-COM payment settings to prevent site-wide checkout failures.

Supported Hosted Payment Providers

• OpenEdge Hosted Payments
  
• Bambora/Worldline Checkout 
• Moneris Hosted Payments
• Paypal Hosted Payments
• SchoolPay 
• TouchNet uPay
• Transact Campus/CashNet

Limited Support Providers

• Authorize.Net - Limited Support
• Chase Exact - Limited Support

Testing Integrations: Always perform a small test transaction before going live with a newly configured hosted payment provider. Most providers offer a sandbox or development environment that allows you to verify the checkout flow and ensure payments are routing correctly back to OPS-COM without affecting real financial records.

Using this Feature

Because hosted payments rely on backend API connections and secure redirects, administrators do not manually interact with the web payment feature on a daily basis once the initial configuration is complete.

The standard user checkout flow for a hosted payment proceeds as follows:

1. Select the designated hosted payment type during the OPS-COM checkout process.

2. Click the confirmation button to be securely redirected to the external provider's hosted payment form.

3. Enter the required credit card details on the secure webpage.

4. Confirm the payment details to process the funds.

Visual Cues and Status Indicators

• Automated Redirection: Once the payment successfully processes on the provider's end, transaction results are posted back to the OPS-COM system. The user is then automatically redirected back to the OPS-COM portal, where a final payment confirmation screen and receipt are generated for their records.

Best Practices and Considerations

• User-Friendly Naming: The text you enter into the payment configuration name field is exactly what your users will see when selecting a payment method during checkout. Choose a clear, recognizable name like "Credit Card" or "Online Payment" to avoid confusion.