Sweep Console
It's a Stripe-like subscription payments platform, but instead of card networks and bank rails, every payment settles in USDC.
Videos




Pila tecnológica
Descripción
SweepConsole — Stripe-like for stablecoin subscriptions
It's a Stripe-like subscription payments platform, but instead of card networks and bank rails, every payment settles in USDC on Arc (Circle's L1 EVM chain). Merchants create plans, share checkout/payment links, and get paid in stablecoins on a recurring basis — without ever having to touch crypto plumbing or sign a transaction themselves.
Who it's for and the problem it solves
Recurring crypto payments are genuinely hard: someone has to pull funds every month, gas has to get paid, money often lives on the wrong chain, and you don't want to become a custodian holding everyone's money. SweepConsole hides all of that behind a Stripe-shaped developer experience — plans, subscriptions, webhooks, a checkout page, an API.
Progreso del hackathon
Week 1 — Foundation & the core product (June 7 → 13):
This week was about standing up a working Stripe-shaped product end to end.
Stage 1 — Scaffold (Jun 7). pnpm monorepo laid down: packages/contracts (Foundry), apps/web, apps/api. First skeletons committed.
Stage 2 — The contract (Jun 7 → 13). SubscriptionManager.sol written and hardened: subscribe / settle / renew-from-allowance / refund / cancel. Test suite grown to 60 passing tests (finalized Jun 13). This is the settlement core everything else sits on.
Stage 3 — API + portal + checkout (Jun 8 → 9). The June 9 push was the single biggest day of the week (200+ files) — the Express API routes (passport, plans, subscriptions, checkout, webhooks), the merchant portal, and the customer checkout UI all came together. Note: this is also when the stack was restructured off the original Next.js app onto Vite SPA + Express + Foundry.
Stage 4 — Spec-addendum compliance (Jun 10 → 13). Brought the build in line with the June addendum decisions: hybrid billing (escrow + allowance renewals), push settlement (merchants never sign), two merchant payout paths (Circle W3S wallet or external address verified by signed nonce), escrow-only refunds, gasless checkout, email capture bound to webhooks, and payment links. Also stood up the Gateway cross-chain checkout (subscribeViaGateway) and deployed SubscriptionManager to Arc Testnet.
By end of Week 1: a working, deployed, Stripe-like stablecoin subscription product
Week 2 — Autonomous cross-chain renewals (June 14 → 16, in progress):
This week is one hard problem: how do you autonomously renew a subscription when the subscriber's money lives on a different chain — without custody, without a monthly signature, without the merchant ever touching crypto?
Stage 5 — The decision (Jun 14). Chose to solve renewal authorization with MetaMask delegation (ERC-7710/7715) rather than per-chain collector contracts. Built a single-chain spike, feature-flagged OFF.
Stage 6 — The R&D gauntlet (Jun 15 — the 240-file day). This was the heavy one. Settled on single-chain selection (Arc-first, else one chain that covers the full period), enforced "Arc never touches CCTP," then ran straight into a wall: MetaMask won't let a dApp sign raw ERC-7710 delegations for user wallets, and 7715 periodic permissions only allow a single capped transfer per period — no arbitrary contract calls. So I worked the trilemma through options A → B → and landed on C1: a relayer-bridge model — the relayer redeems each periodic mandate as one transfer, then does its own CCTP v2 burn→Arc mint to the creator. Then validated the full burn → Iris attestation → Arc mint end-to-end on testnet, wired Payment rows + renewal webhooks, and made the source-chain flow crash-resumable (BridgeTransfer pulled→burned→minted). An integration harness caught two real bugs (a consumed-allowance orphan window, an amount-drift seed bug) — both fixed.
Stage 7 — Polish (Jun 16, today). Cleanup of the checkout sweep UI and loose ends from the renewal rework.
Where it stands now: cross-chain renewal is fully built and proven on testnet, still behind the TIER2_DELEGATION flag — remaining work is operational (relayer gas funding per chain), a later trust-minimized BurnHelper, and a contract audit before mainnet.
Estado de recaudación de fondos
Still on early stage. No funds raised at the moment