Per-transaction Pricing Fits Candex

A transaction fee works here because Candex is not selling a seat based software tool, it is taking over a messy payment event that only exists when a buyer needs to use a small or irregular supplier. In tail spend, the pain shows up one purchase at a time, like paying a local event venue or niche consultant. Charging per transaction lets cost rise only when the buyer actually uses that shortcut, which matches both the customer budget logic and Candex's own operating workload.

• The product does real work on every transaction. Candex becomes the approved vendor, collects supplier tax and bank details, runs sanctions checks, manages invoice states, and pays the supplier after the buyer pays Candex. That is closer to a payments operation than a pure software login, so usage pricing fits the cost structure better than a flat subscription.
  1 sacra 2 candex 4 candex
• The buyer problem is highly uneven. A company may have thousands of low dollar vendors that appear once, then disappear. Charging a recurring platform fee for that feels mismatched, while a roughly 3% fee tied to each routed purchase scales automatically as more departments, geographies, and categories adopt the workflow.
  1 sacra 2 candex 3 candex 5 prnewswire
• This pricing also lowers adoption friction against procurement suites. Candex plugs into tools like Ariba, Coupa, SAP, Oracle, and Workday through punchout, so an enterprise can start with one slice of unmanaged spend instead of approving a large transformation budget. That makes the commercial decision look like paying for solved exceptions, not buying another major software system.
  1 sacra 4 candex 5 prnewswire

Going forward, the model gets stronger as more spend flows through the master vendor rail. If Candex keeps expanding inside existing accounts, the business compounds through higher transaction volume, while deeper compliance and global payments work make the platform harder for generic procurement software to copy.