SubsCrypto
A Bitcoin DCA web app found early revenue, then hit the harder validation problem: payment processors and fraud controls had to support the core workflow.
View sourceProduct snapshot
What it was
Let users set up recurring Bitcoin exposure through a subscription-like payment flow.
Who it was for
Problem / value
Reduce the friction of manual recurring crypto buys for non-crypto users.
What happened
Summary
SubsCrypto reported early revenue, then ran into payment-processor and fraud-risk problems that directly affected the core workflow.
Outcome
Current operating status is unclear from public sources.
Demand signal
This was not a pure no-demand case. The risk was that early revenue did not prove a durable buyer path when processors could block the transaction loop.
Distribution issue
Google Ads, Stripe, and Square became gatekeepers. Without compliant acquisition and payment rails, the product could not reliably deliver subscription-like Bitcoin buys.
Timeline
- Founder reported first revenue and a Stripe balance in April 2023.
- Founder later described Google Ads and Stripe dependency problems.
- Stripe turned down the project after fraud issues.
- The founder relaunched with Square, then reported Square suspension after the first payment.
Before you build
Why it matters
Sensitive categories can fail at the rails layer even when users pay. If the processor will not support the workflow, the business model is not validated.
Primary check
Validate processor policy, fraud exposure, and fallback rails before treating first payments in a regulated workflow as proof of product-market fit.
If you build this today
Start with policy validation: processor pre-approval, chargeback controls, reserves, a crypto-native fallback, and a small controlled beta before public checkout.