Urgent.News

What's breaking now, across thousands of outlets.

Tech

The Price of a Percentage

Run the arithmetic a percentage-of-recovery tool hopes you will not. Say a store fails $40,000 of payments in a year — unremarkable for a mid-size subscription business — and a competent tool recovers a third of it. At a typical percentage take, the invoice for that recovery lands in the thousands, every year, growing in lockstep with the business it protects. The tool has quietly become one of…

A recovery tool that calculates a percentage of recovered payments may seem advantageous at first glance. However, upon closer examination, it becomes clear that this pricing model can be detrimental to merchants in the long run. Consider a mid-size subscription business facing $40,000 in uncollected payments - a figure that is not unusual in this industry.

A proficient tool might recover one-third of this amount, resulting in a significant invoice for the merchant every year, growing in tandem with the business's success. This tool has become a dominant force in the industry, often contracted like a utility and paid like a partner.

Comparing this to a flat fee pricing model, the disparity becomes apparent. While a flat fee remains constant, regardless of the recovery amount, the percentage-based tool's revenue is limited. Consequently, the vendor's profits are maximized when the merchant's losses are at their peak. This asymmetry is the driving force behind Swipe Again's decision to charge a flat fee of $179, which is openly explained on its flat-fee page.

By adopting a percentage model, vendors stand to gain the most when merchants suffer the most substantial losses, creating an incentive for the vendor to be less concerned about the merchant's issues. This pricing structure ultimately undermines the merchant's interests, as vendors prefer percentages to mitigate their own risks, inadvertently placing merchants in an increasingly precarious position.

In a world where pricing strategies lean heavily in one direction, the flat fee does not represent a discount; it signifies a distinct commitment to the vendor's interests over the merchant's. This should be evident in the pricing, as it is a choice that must be made clear.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Webhooks Lie by Omission

A webhook is a promise a platform makes in the moment, and like most promises made in a hurry, it occasionally does not arrive.

  • Webhooks often omit crucial information
  • Systems must account for missing data
  • Reconciliation sweeps verify accuracy

Ghost in the Machine: Necromancing Dead Codebases Locally with Gemma 3 & Ollama

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 4: Ghost in the Machine Disclosure: this project was built with AI assistance — a local Gemma 3 model performed the code…

  • "Legacy Code Necromancer" tool resurrects abandoned codebases locally
  • Gemma 3 via Ollama analyzes code, removes sensitive info, suggests improvements
  • Tool identifies 15 issues in sample, 8 confirmed critical flaws, rejects unreliable suggestions

Onboarding Is a Funnel, Not a Form

Most SaaS onboarding is designed as paperwork: collect the fields, show the dashboard, send the welcome email, wonder about activation later.

  • Onboarding should be viewed as a multi-step funnel, not just form-filling.
  • Deliberate design decisions dictate the signup, card details, and connect steps.
  • Share of trials connected within 24 hours is the key metric to monitor.

Node.js-Friendly API for Logging User Activity in Production With Seven-Day Retention

A production notification log is useful only if it can reconstruct a failed delivery without turning every player action into permanent storage.

  • Node.js-friendly API for logging user activity in production with seven-day retention
  • Key fields: eventid, userid, notificationid, attempt, status, occurredat, provider, traceid
  • Minimal ingestion request with Authorization, Content-Type, Idempotency-Key headers

More from Thursday 29 October →