@buildonbase I am building solo based in Switzerland, with a finished product https://t.co/qkgjemyKzJ. Need help to launch. Anyone with experience please DM. Can't go to NY. And yes, it is all @base.
https://t.co/lAhoRHxrwd fixes the pain of manually approving recurring crypto bills and trusting middlemen with your funds — subscription payments pull directly from your wallet to the merchant's, automatically.
For USDC and EURC: one signature authorizes it, and pulls happen gas-free for you on @base — AuthOnce never holds your money.
If your #SaaS already takes USDC/EURC subscriptions (or you want to try it), DM me to get your merchant wallet approved. Free to test — we're on Testnet right now.
Full demo of AuthOnce — non-custodial subscription billing on @base
One signature to subscribe.
Funds never leave your wallet.
0.5% flat fee.
Fully on-chain & verifiable.
Built for SaaS + Web3 teams already getting paid in stablecoins.
@jessepollak@brian_armstrong
Great to see x402 momentum — worth noting the recurring side of this is a different problem than per-call payments. We've been building non-custodial recurring billing on Base (subscriptions, not one-off calls) — EIP-2612 gasless signup, ERC-1271 support for smart-wallet/agent signers already tested end-to-end on-chain. Complementary rails, not competing ones.
Just executed AuthOnce's first real ERC-1271 pull — on @base Sepolia testnet — a @safe smart wallet authorized a recurring subscription payment, settled on-chain, fully non-custodial.
This is the mechanism behind smart-wallet & AI-agent billing: signature-based authorization, no custody, no human clicking "approve" each cycle.
Tx: https://t.co/JVmT9do405
Next: wiring this into the production keeper. 🧱
Great breakdown of the merchant opportunity. One gap worth adding: recurring payments.
One-time crypto payments are solved. But subscriptions — SaaS, memberships, data feeds — still require manual transfers or custodial platforms every cycle.
AuthOnce fixes this. Non-custodial recurring USDC billing on @base . Subscribers authorise once, keeper pulls automatically every cycle. 0.5% flat. No churn from failed payments.
Built for exactly the merchants this article is describing.
https://t.co/MR9EuTRkCo
One protocol. Three types of subscribers. Each gets the right message when a payment fails.
💳 Card payment failed? Clear, simple instructions.
👤 Wallet low on USDC? Top up and we retry.
🤖 AI agent vault empty? Fund it on-chain.
Built-in dunning. 0.5% flat. Base Network.
https://t.co/MR9EuTRkCo
cc @base@jessepollak@circle@WalletConnect
Today the keeper bot pulled 9 live subscriptions on-chain, automatically, without touching a single wallet. Protocol working as designed.
Audit next. Mainnet September.
@AuthOnce
Something I didn't expect when building AuthOnce:
The subscriber experience in Web3 payments is basically an afterthought.
Every protocol I studied was built for the merchant. The subscriber just had to trust nobody would drain their wallet.
That's not good enough.
#DeFi #Base #Web3
Subvisual call Monday.
First real conversation with people who've built and scaled Web3 products.
Solo founder preparing for his first investor meeting. No pressure.
Building in public means sharing this too.
#BuildInPublic#Web3#Fundraising
The hardest part of building a payment protocol isn't the payments.
It's the failure layer.
What happens when a payment fails at 3am? Who gets notified? How many retries? When do you give up?
Grace periods, keeper bots, webhook fallbacks — that's the real product.
#BuildInPublic #DeFi #Base