Skip to main content

Convenience Fees

Difference between Transaction fees and Convenience fees:

Transaction fees are independent of OPS-COM, which are managed & enforced by your payment provider. Depending on how it’s setup end users and OPS-COM itself may not know of any such Transaction fees since it's all managed on the payment providers end.

Convenience fees on the other hand are managed through OPS-COM. For example, our system can add a $5 Convenience fee onto a payment. This is managed and enforced by OPS-COM and not the payment provider.

This page primarily related to Convenience fees, but may reference Transaction fees. It is possible a system may use both Convenience fees and Transaction fees,, but it is important to know the difference.

How to get to the Fees page:

2024-10-30_11-55-47.png

 

To access the Convenience Fees page in OPS-COM select System Configuration → Payments -> Fees.

 

Fees Page Explained:

3791d194-e0da-433d-bf84-b470d263c958.png

Fee Limitations:

  • Fees are applied once per fee type per order. This means if a fee is for permits, that if it is one permit or five permits, a single fee is applied to the order.
  • Fees are flat rate. There is no percentage based fee at this time.
  • Fees are not sent to the payment provider as a secondary item. Only the grand total is sent.

Fee Examples:

Admin collected fees:

In these scenarios, the admin charges a fee and keeps the full amount. The fee is to cover their own cost. OPS-COM does not collect on any of these fees as the client receives the full amount charged including the fee.3997c6e4-a297-461f-924d-47808e25ab43.png


Admin collected fee for collecting cash and cheques:

The admin wants users to use online payment providers to collect payment. When a user pays for an item with cash or cheque, this puts an increased burden on the admin and this fee is set up as a deterrent. The setup would apply to all item types but only apply to payment types of cash. The following is how you would set this up:

1b90fe34-8404-4bb2-ab44-8b9c427b96e6.png


Admin collected fee for permits

In this scenario, we will assume that permits are sent to a thirdparty for enforcement, but the third party charges $0.50 per permit they have to enforce. The client wishes to pass this cost onto the user. The fee will apply to all payment types, but only on permits and temp permits. The setup will look as follows:

fa0387e9-9d0e-4a42-9806-ad1b02eeccd5.png


OPS-COM collected transaction fees

In these scenarios, there is a transaction fee that is set up on the payment provider that will deduct a specific amount from every transaction. At the time of this writing, it is a flat rate per account. Different fee rates based on items will require different accounts to be used per item type.


Admin charges a convenience fee to cover the transaction fee

The agreement that all permits will incur a $2.95 transaction fee to be paid to OPS-COM is set up with the payment provider and the client. The client still wants to receive the full $150 for the permit that is purchased so they set up a convenience fee will be a charged when selecting this payment type. Since in phase 1, there can only be one account per payment type, the fee is to be applied to all item types.
13e8e2e6-56ca-490c-8251-b4531cc25e15.png

Setup as follows:

d0afabcb-2147-40b7-905d-175b85b48f91.png


Admin includes the transaction fee in the price of the item

The agreement that all permits will incur a $2.95 transaction fee to be paid to OPS-COM is set up with the payment provider and the client. The difference here is that the client will include the fee in the cost of the item. If a permit costs $150, then $2.95 of that will be sent to OPS-COM leaving the client with $147.05. There is no setup for fees in this scenario. If the client wishes to still inform the user that there is a transaction fee and that it is included, they will update a footer stating that the final amount includes the transaction fee.

f52068eb-5fe0-4935-8f66-a1f77d1d7464.png