Reloop

We're building Reloop, a Web3-native subscription platform that lets users manage and pay for all their recurring services using crypto FXRP. At the same time, it gives creators and companies a simple way to list their subscription-based offerings and get paid automatically without relying on banks or traditional payment systems.

Here’s how it works: users lock a small amount of crypto into a smart contract, and our system handles recurring payments on their behalf. We use real-time price feeds to calculate the equivalent in crypto for services priced in dollars, and we allow users to approve monthly payments through off-chain signatures—saving them gas and giving a smooth experience. If a payment fails, we introduce a short, randomized grace period before cancellation, giving users time to fix it.

For creators and businesses, Reloop offers a dashboard to create and manage plans, track subscribers, and receive automated payments directly into their wallets. Everything is permissionless, secure, and transparent.

Over time, we want to become the go-to system for recurring payments in Web3—the Stripe of subscriptions for a decentralized economy.

We built Reloop on the Flare Network and Nitrolite’s ERC-7824 protocol for state channels. Our stack is optimized to handle recurring payments in a way that’s secure, low-cost, and seamless for both users and creators.

Flare powers three core features:

FAssets: We use it to bring non-EVM assets like XRP into the smart contract system (e.g., as FXRP). FTSO (Flare Time Series Oracle): We fetch real-time USD prices for FXRP/BTC to calculate how much crypto a user needs to lock per subscription. Secure Random Number Generator: If a user’s payment fails, we trigger a randomized grace period (0–6 hours) before cancellation.

We integrated Nitrolite to handle the actual subscription payments via off-chain state channels (ERC-7824). This lets users sign monthly payment approvals off-chain, so they don’t pay gas fees each time. We only settle on-chain once per billing cycle or if there’s a dispute, keeping costs low.

One hacky but effective thing we did was mock out the RNG responses to simulate various grace period behaviors in testing. We also built a fallback script to convert dollar amounts into FXRP even if the FTSO fails — using cached oracles as backup.