Dev.to
7/13/2026

My payment processor rejected my product for calling it a "service"
Short summary
A solo developer's Chrome extension was rejected by Lemon Squeezy because the store description used subscription vocabulary for a one-time license. The fix was reframing the description to emphasize verifiable delivery at checkout. The author also built a provider-agnostic licensing backend to avoid single-processor dependency.
- •Payment processor rejected a one-time software product because it was described using subscription/service vocabulary
- •Fix: reframe as 'one-time software license, delivered instantly as a license key' — approved immediately
- •Lesson: make licensing backend provider-agnostic so switching processors takes one line, not a rebuild
Generated with AI, which can make mistakes.
Is this a good recommendation for you?



