The Cost of Revenue Sharing

The Model Most Operators Have Never Questioned

Cash advance on the gaming floor has operated on a revenue-share model for decades. The vendor supplies the hardware, processes the transactions, and takes a percentage of every dollar advanced. The operator gets a service. The vendor gets a cut.

For many operators, this arrangement was inherited, not chosen. It was the default when the property opened. The contract auto-renewed. The fees became a line item no one looked at too closely.

That is worth looking at more closely.

How the Math Compounds

Revenue-share rates vary by contract. Consider a straightforward example: a mid-size gaming property processing $1 million in cash advances per month, with a vendor earning 1.5% of gross transaction volume, pays approximately $15,000 per month (roughly $180,000 per year) to the vendor.

If patron volume increases, as operators work to ensure it does, so does the vendor's take. Automatically. Without any change in the service delivered.

What the Contract Actually Says

Long-term contracts are standard in the revenue-share space, and that is not coincidental. A multi-year term with auto-renewal provisions and meaningful switching costs creates a structure where the operator has limited leverage at renewal.

Feature requests are common. Feature delivery is less common. Price increases are absorbed because evaluating alternatives requires operational disruption most properties prefer to avoid.

The result is a vendor relationship that is more durable than it is competitive.

The Compliance Layer

Gaming operators in the US and Canada are subject to AML reporting obligations — FINTRAC in Canada, BSA/AML in the United States — along with state and provincial regulatory requirements and increasing scrutiny on AML controls at the cage. Most legacy cash advance systems were not built with these requirements as a primary design concern. They were retrofitted over time.

When a regulator asks for transaction data, reconciliation records, or reporting documentation, the operator should be able to produce it without waiting for a vendor to generate a report on their schedule. That dependency is a compliance exposure that most operators have not formally assessed.

The Operator-Owned Alternative

A software licence model works differently. The operator pays a flat monthly fee for the platform, transactions process through the operator's own merchant account, and settlement goes directly to the casino's bank account.

This is not a new concept in enterprise software. It is the standard model for virtually every other operational system a casino runs: property management, surveillance, loyalty, food and beverage. Cash advance has been the exception. There is no structural reason it needs to remain one.

What to Evaluate Before a Transition

• 1
  True cost of the current arrangement

  Calculate gross transaction volume multiplied by the vendor's effective rate. Include waived fees, promotional periods, and any volume-based escalators in the contract. The number is often larger than the accounts payable line suggests.

• 2
  Contract terms and exit provisions

  Understand the remaining term, any early termination clauses, and the notice period for non-renewal. Many auto-renewal windows are short and easy to miss.

• 3
  Integration requirements

  A replacement platform needs to connect to the existing gateway, acquirer relationship, EMV PIN pad hardware, ID scanners, and receipt printers. Confirm compatibility before committing to a transition timeline.

• 4
  Compliance continuity

  AML reporting (FINTRAC in Canada, BSA in the United States), patron transaction records, and jurisdiction-specific compliance controls need to carry over without a gap. The platform should support these natively, not through manual workarounds.

• 5
  Operational disruption

  Staff training, kiosk changeover, and cage workflow adjustments are manageable with the right implementation support. The transition period is finite. The savings from a flat-fee model are ongoing.

A Final Note

This paper is not an argument that every operator should switch vendors immediately. It is an argument that every operator should run the numbers.

The revenue-share model was built at a time when the vendor was providing capital, taking on transaction risk, and operating in a less competitive market. Those conditions have changed. The contracts have not always changed with them.

The calculation is straightforward. What you do with it is an operational decision.