When we designed the ReactivVibeAI tipping economy, the obvious choice was a Stripe-powered direct-tipping flow — type in a number, hit pay, money goes to the creator. We didn't do that. Here's why we built Sparks instead.
The friction problem
Every direct credit-card tip is a one-card-form transaction. Even with Apple Pay it's three taps. On a live show where the moment lasts ten seconds, three taps is the difference between tipping and not. Sparks are pre-loaded, so a tip is one tap.
The decision-fatigue problem
"How much should I tip?" is a question that makes people freeze. Sparks bundle the decision: you bought $20 worth of Sparks once; now you're just choosing how many to send to a specific track. The math is friendlier.
The fee problem
Direct card tips of $1 lose 30% to processor fees. Sparks bundle the processor fee into a single purchase, so a $1-equivalent tip actually delivers $0.90 to the creator instead of $0.70.
The subscription problem
We considered a subscription model and rejected it. Subscriptions extract money from fans regardless of whether they showed up for a show. Sparks only convert to creator income when you actually use them. That feels right.
What we won't do
We will never auto-charge a card on a recurring basis. Sparks are one-time purchases, full stop. Learn about how Sparks work.