3 min read

The $500 second yes: big tips without big accidents

Big cheese is real and welcome, and it is exactly where speed turns dangerous. One rule handles it: a single tip over $500 asks the supporter twice.

Most tips are $5. Some are $25. And every so often, someone means it: a $600 thank-you after the post that changed something for them, a whale closing out a great season. Big cheese is real and welcome. It is also exactly where tipping systems break trust, because the same speed that makes $5 delightful makes $2,500 dangerous. Our answer is one rule, called the second yes.

The rule

A single cheese over $500 does not run immediately. It parks, and the supporter is asked to confirm it a second time, in the saycheese app. Approve, and the tip proceeds like any other, captured within seconds, final on capture, and the creator is alerted the moment it lands. Ignore it, and it expires within a day: nothing charged, nothing sent, and the creator never hears about it.

Below the line, nothing changes. No caps, no daily budgets, no velocity meters. $5 and $25 and $400 all move at the speed of a comment, because that speed is the product.

The parked tip is visible in the supporter’s own history while it waits, with what happens next spelled out in one line, so nothing about the state is mysterious on their side either.

Friction should scale with consequence

Good systems spend friction where mistakes are expensive. A mistyped 🧀$25 is annoying, and a refund, when granted, absorbs it. A mistyped 🧀$2500 is a genuinely bad day: a rent payment, a panicked support thread, a dispute that hurts everyone. And beyond typos there are hot moments. The auction of enthusiasm during a live show. The late-night surge someone regrets by morning. The compromised account spending a card that is not theirs.

One deliberate confirmation, in a second place, in a calmer second moment, filters nearly all of it. What survives the second yes is the thing the supporter actually meant, twice.

Why the creator hears nothing until yes

Notice the sequencing: the creator is not told about a parked cheese. This is the alert-honesty rule doing its job at the high end. A heads-up about a $900 maybe would be a promise the supporter has not made yet. If it then expired, we would have handed you an income and taken it back. So you learn about big cheese the way you learn about all cheese, once it is real. No phantom windfalls, no awkward evaporations.

The guest ceiling

Guest cheese from your page caps at $500 flat, with one line at checkout: cheese over $500 needs an account. The second yes lives in the app, and an anonymous card at a checkout has no second place to say it. Anyone moved to give more than $500 is someone with a real relationship to your work, and the account they create to do it is where that relationship gets a name.

What this replaces

The industry default for big-payment safety is a pile of invisible tripwires: daily limits, rolling budgets, risk scores that decline without explanation. Each one occasionally saves someone, and each one occasionally humiliates a genuine supporter at their most generous moment. We took the pile out and left one visible, predictable rule. Generosity should not have to gamble on a risk model’s mood.

Every cheese is final when it sends. A single cheese over $500 needs your yes in our app. That is the whole rulebook.

For supporters, the second yes means your biggest gestures are safe to make: nothing life-sized leaves your card on one keystroke. For creators, it means every large number you are ever told about is money that was meant, confirmed, and captured. The $500 line is where we slow the cheese down just enough to be sure, so that everything below it never has to slow down at all.