Get started · FlowPay

How FlowPayworksacross every payment flow.

FlowPay brings stream, invoice, and paywall logic into one on-chain payment system built around native USDC. Built on Arc.

What you need

Wallet
EVM-compatible
Network
Arc
Token
Native USDC

Stream

Send USDC every second

Start a continuous payment flow to any address. Balance accrues every second automatically, and the recipient can withdraw whenever they want.

Use cases

Salary payments that feel continuous instead of monthly
Freelancer retainers during a project
Subscription-style service payments

Sender (payer)

  1. 1Enter recipient wallet address and monthly USDC amount
  2. 2Set an initial deposit to define how long the stream runs
  3. 3Create the stream — funds begin accruing per second immediately
  4. 4Cancel anytime via the active streams panel; unspent deposit is returned to your wallet

Recipient

  1. 1Receive the stream ID from the sender
  2. 2Enter the ID in the Stream lookup to see your live balance
  3. 3Watch USDC accrue in real time every second
  4. 4Withdraw your earned balance whenever you want — no waiting

Invoice

Create and settle USDC invoices

Create an invoice for a product or service and share the ID. The other party pays on-chain and funds arrive directly to your wallet.

Use cases

Freelance design, development, or consulting work
Supplier or vendor payment requests
Deadline-based project payments

Invoice creator

  1. 1Set the USDC amount, description, and optional deadline
  2. 2Create the invoice — a unique numeric ID is generated on-chain
  3. 3Share the invoice ID with your client
  4. 4Funds arrive directly in your wallet once the client pays

Payer (client)

  1. 1Receive the invoice ID from the creator
  2. 2Enter the ID and the amount in the Pay invoice form
  3. 3Confirm the transaction — payment settles on-chain instantly
  4. 4Both parties can verify the transaction on Arc Explorer

Paywall

An onchain marketplace for pay-per-request APIs and AI-powered services

FlowPay's Paywall connects two sides: clients who pay per request and service providers who earn per call. Service ownership and pricing live onchain, while payments settle in batches with provider earnings claimable from the contract.

Use cases

AI-powered APIs monetized per call
Data feeds billed by actual usage
Any service that shouldn't need a subscription

Service providers

  1. 1Register your API or AI-powered service endpoint
  2. 2Your backend URL stays private — clients get a proxy URL
  3. 3Public metadata appears in the marketplace automatically
  4. 4Earn USDC per request, then claim settled revenue onchain

Clients

  1. 1Browse available services in the marketplace
  2. 2Deposit USDC credits once
  3. 3Sign each request off-chain — zero gas
  4. 4Credits deduct per call; withdraw unused balance anytime

Ready to try it?

Start with stream, invoice, or paywall and test the flow on Arc.

Stream Invoice Paywall