TouchNet (uPay) Hosted Payments
The TouchNet uPay Hosted Payment integration allows institutions to securely process parking and violation transactions through their existing TouchNet merchant account. Its primary purpose is to ensure successful communication and financial data transfer between the OPS-COM environment and the TouchNet payment gateway. This article is intended for OPS-COM administrators and IT staff responsible for configuring financial integrations.
Setup and Configuration
Setting up this integration requires a coordinated exchange of information between your organization, your TouchNet Account Manager, and your OPS-COM Account Manager.
Gathering Required Credentials
You must obtain the following configuration details from your TouchNet Account Manager for both your Sandbox (Test) and Production (Live) environments:
-
uPay Site ID: A unique identifier, usually a 3-digit number (e.g., 013).
-
uPay URL: A secure URL that uniquely identifies your account.
-
T-Link Web Service URL: Another secure URL that uniquely identifies your account for backend communication.
Providing Details to OPS-COM: Once you have gathered these credentials, you must provide them to your OPS-COM Account Manager to complete the backend configuration. Please note that additional charges for setup may apply.
Configuring the T-Link Web Service
OperationsCommander's parent company, Tomahawk Technologies, is a certified TouchNet Ready Partner.
-
When configuring the T-Link in your TouchNet account, look for a partner selection drop-down menu.
-
Select Tomahawk Technologies from the list.
If you do not have the ability to configure a T-Link web service URL and your TouchNet Account Manager has not supplied one, you must request that TouchNet set up a uPay site for you that explicitly supports T-Link web services.
General Ledger Codes
OperationsCommander's TouchNet integration currently supports multiple General Ledger (GL) codes. This allows you to route funds to different accounts based on the item type.
-
You can specify one GL code for parking permits and a separate GL code for all other payments (such as violations or lockers).
-
Alternatively, you can use the exact same GL code for all purchases.
-
If you are using GL codes, you must provide the exact GL code names configured in your TouchNet account to your OPS-COM Account Manager.
Using this Feature
Because this is a backend payment gateway configuration, administrators do not manually interact with this feature on a daily basis. Once fully configured and tested by the OPS-COM support team, the TouchNet payment gateway will automatically handle electronic routing when users process transactions on the user portal or when administrators process credit card payments via the administrative portal.
Best Practices and Considerations
Sandbox Testing: Always provide both your Sandbox and Production credentials to your OPS-COM Account Manager. This ensures the integration can be thoroughly tested in a safe, simulated environment before live financial transactions are actively processed.
-
GL Code Accuracy: Verify that the GL codes you provide to OPS-COM match exactly with what is configured in your TouchNet system. Incorrect routing codes can cause payments to fail or cause funds to be deposited into the wrong institutional accounts.