Payflow

Start by moving money to people you know by name, not by copying addresses. Connect your wallet, link your Farcaster, Lens, or ENS identity, and you can pay or request from any handle you follow. Type a username, choose a token, add a note, and send. Create a payment link or QR code for tips or one-off sales; drop it in a bio, a post, or a DM. Set transactions to public or private, and keep a verifiable on-chain receipt for every transfer. If you need predictable cash flow, turn on recurring payments and let the system handle renewals and reminders.

For teams and communities, organize payouts without juggling spreadsheets. Import a list of handles, assign amounts or percentages, and dispatch everything in a single batch. Configure automatic splits for collaborators, affiliates, or royalty partners so revenue is shared the moment it lands. Gate releases behind milestones and unlock funds when conditions are met. Monitor activity with dashboards, export reports for accounting, and subscribe to notifications so contributors know when they’ve been paid—no matter which app they use to interact with their social identity.

Creators and merchants can turn their audience into customers in a few clicks. Offer membership tiers with recurring support, sell digital goods, or run sponsored drops with measurable outcomes. Post a pay link in your content stream and accept payments where fans already engage with you. For events, publish a checkout link, verify attendees by handle at the door, and route proceeds to co-hosts automatically. Issue refunds or partial credits from the same interface, and keep your community in the loop with transparent, on-chain receipts.

Developers can embed payments anywhere with a lightweight widget or SDK. Resolve a handle to a wallet, initialize a transfer, listen for confirmations, and render receipts—all through simple methods. Use webhooks to power unlocks, role assignments, and CRM updates after a successful payment. Build handle-first experiences without managing complex address books, and rely on the shared social graph to keep mapping accurate across apps. Test in a sandbox, move to production with minimal changes, and let users pay by the identities they already trust.