Membership payments with transaction-based pricing.
Selected niche: payment, renewal and access automation for merchants with existing paid content or tools. The category has established paid offerings; BBBFi acquisition and retention remain unvalidated.
Why paid manual reports were dropped
A one-off quote and runway calculation are easy to replace with free tools. Treasury needs do not establish willingness to pay 199 USDC/month for reports. The earlier price lacked customer evidence and required human delivery. That paid direction is discontinued; the calculator remains free.
Comparison and tradeoffs across six products
| Product | Primary-source observation |
|---|---|
| InviteMember ↗ | Paid membership automation; monthly entry plan $19, with volume-based tiers. |
| MoonPay Commerce ↗ | Self-serve checkout; standard fee 2%, HelioX 1%; optional services cost extra. |
| Stripe ↗ | Stablecoin and recurring payments; listed USDC networks do not include X Layer. |
| Unlock ↗ | Onchain membership and subscription NFTs already exist; this is an established category. |
| Revert ↗ | Auto-compounding charges 2% of compounded fees; a clone still needs capital and security trust. |
| OKX DEX ↗ | Limit orders already support X Layer; basic orders alone do not differentiate the product. |
These are provider-published capabilities and prices, not independently audited sales or BBBFi orders. This is not an exhaustive competitor census. Prices, networks and features were checked on the research date and may change.
Who pays, and why a direct transfer is insufficient
Initial customer criteria: an existing product, existing paying users already holding USDC on X Layer, and manual transfer checking before website or API access is enabled. Moving non-crypto customers onto X Layer can cost more than it saves; they are not the initial target. With no established acquisition channel, demand is still unvalidated.
- A payment grants a timed entitlement. A wallet signature proves ownership; the merchant server verifies its pinned plan and expiry before delivery. Expired requests are denied; successful renewals extend access.
- A plain transfer lacks a plan ID, paid-through date, bounded renewal mandate and verifiable entitlement. Replacing that integration work is the value. Merchants needing only occasional transfers have no strong reason to pay BBBFi.
- Fees follow successful sales rather than reports or prepaid monthly packages. Public integration components and checkout links make installation and sharing self-serve.
Implemented payment and delivery rules
- Price, period, merchant and origin binding are immutable. Each successful payment sends 99% directly to the merchant. The protocol receives 1% on initial payment; renewals split 0.8% to the protocol and 0.2% to the executor. There is no platform deposit balance.
- One period is the default. Auto-renewal requires explicit buyer selection, is capped at 12 charges including today, and can be cancelled while retaining paid access. Insufficient funds or allowance stops renewal; missed periods are not back-billed.
- TapeOut combines four onchain predicates inside the payment contract, rejecting unauthorized, early, paused or unfunded renewals. Access depends on paid onchain state and a wallet signature, not a browser claim of payment.
- Merchants must install a server verifier pinned to their own plan ID. Hiding frontend UI is not access control. A merchant can refund a full period and simultaneously close the subscription, covering processing fees already settled.
Acquisition costs and break-even must be explicit
All figures are scenarios, not actual revenue. Conservatively assume every payment is a renewal, yielding 0.8% protocol revenue. Default monthly cost: 1,235 USDC = 60 infrastructure + 3 support hours × 25 + 4 acquisition hours × 25 + a hypothetical 12,000 development/security budget amortized over 12 months. This is not an audit quote or a claim of audit. Tax, refund disputes and extra risk costs are excluded. Merchants host their own content/API and server RPC.
Protocol revenue (0.8%): 480.00 USDC
Balance after listed costs:-755.00 USDCMonthly GMV to cover costs: 154,375 USDC
The default scenario loses money: 20 merchants each settling 3,000 per month do not cover the full assumed budget. A deployed contract is not evidence of a profitable business.
Validation sequence and stop criteria without a channel
- Find merchants already receiving recurring payments and meeting the wallet criteria, rather than advertising to a broad non-crypto audience. Use public integration documentation, runnable examples and partnerships for initial trials; no such outreach is claimed completed.
- First gate: three independent merchant integrations, each with at least 20 genuine non-team orders, without subsidies, self-purchases or contest prizes. Do not expand Telegram, cross-chain or token support before this gate.
- Across two billing cycles, check real second payments, retained merchant use and support below 15 minutes per merchant per month. Acquisition cost should be recovered within three months of gross contribution.
- If three qualifying merchants cannot be found within 30–45 days, or wallet/integration friction prevents conversion, stop the direction rather than relabel it as validated. No existing paid customers, renewal rate or profitability is claimed.
Competitive limits
This is not an uncontested invention. MoonPay, Stripe, InviteMember and Unlock are more mature. The initial scope is native X Layer USDC, direct settlement, bounded mandates and a small server integration. A merchant already served well by another product has no reason to migrate. Until acquisition and repeat payments are demonstrated, this is an automatable paid product under validation, not a proven profitable company.