Skip to main content

Transact Campus/CashNet Hosted Payment Setup

The Transact Campus and CashNet Hosted Payment integration allows institutions to securely process parking and violation transactions through their existing CashNet merchant account. The primary purpose of this configuration is to ensure successful communication and data transfer between the OPSCOM environment and the external CashNet payment gateway. This article is intended for OPSCOM 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 and the OPSCOM support team, followed by specific URL configurations within your CashNet portal.

Information to Provide to OPSCOM Support

To begin the setup process, you must supply specific configuration details from your CashNet system to the OPSCOM support team.

  • Merchant Code: Provide the specific merchant code your institution will be submitting items against from your client system.

  • Item Code: Create a specific item in CashNet for these transactions and provide the exact code to OPSCOM. This item must be configured to allow its value to change dynamically based on the transaction amount.

Exact Matches Required: The item codes provided to OPSCOM must match exactly what is configured in your CashNet system. Any discrepancy between the systems will cause the transactions to fail.

Configuring CashNet Store Settings

Once OPSCOM support has your details, they will provide you with specific URLs containing your unique hosted ID. You must enter these into your CashNet Store Settings.

  1. Navigate to your CashNet Store Settings page.

  2. Enter the provided complete payment URL into the Sign-out & Complete payment field.

  3. Enter the provided incomplete payment URL into the Sign-out & Incomplete field.

  4. Select Append Data using GET from the Pass information to calling system drop-down menu.

URL Format Example: The URLs provided by OPSCOM will look similar to [https://hostedpayments.parkadmin.com/hook/cashnet/CLIENTS-UNIQUE-HOSTED-ID/?a=r](https://hostedpayments.parkadmin.com/hook/cashnet/CLIENTS-UNIQUE-HOSTED-ID/?a=r). You must ensure the placeholder text is replaced with your actual unique identifier.

Configuring CashNet HTTP Notifications

You must also configure CashNet to send transaction notification data back to OPSCOM so the system knows when a payment has cleared.

  1. Navigate to the HTTP Notifications configuration section within CashNet.

  2. Enter the provided callback URL into the Successful & Failed Transactions field.

  3. Select Name Value Format (POST) from the Select format for HTTP content drop-down menu.

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, the CashNet 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

  • Firewall Allowlisting: New outbound connections from CashNet will not work until they are explicitly allowed through their security firewall. Contact CASHNet Client Support to enable the new connection before attempting to process live transactions through OPSCOM.

  • Verify Placeholder IDs: Always ensure you replace the sample CLIENTS-UNIQUE-HOSTED-ID in the URLs provided by OPSCOM with the actual unique identifier assigned to you by CashNet before saving your settings.

  • Variable Pricing Configuration: Ensure the specific item code created in CashNet is properly set to accept variable values. Because parking permits and violation fines fluctuate in cost based on user selections, the gateway must be able to accept the dynamic total pushed from the OPSCOM shopping cart.

Back to top