Payflow

Created By
chainbounda year ago
A toolkit for building micropayment-gated MCP servers
Overview

what is Payflow?

Payflow is a demonstration of a micropayment server using the MCP (Micropayment Protocol) that allows for seamless transactions in a decentralized environment.

how to use Payflow?

To use Payflow, set up the local MCP server by configuring it with the necessary parameters and integrating it with the Cryo MCP server for remote transactions. Follow the quickstart guide provided in the documentation.

key features of Payflow?

  • Local MCP server for generating micropayments
  • TypeScript SDK for easy integration of micropayments
  • Example server setup for demonstration purposes

use cases of Payflow?

  1. Enabling micropayments for digital content
  2. Facilitating small transactions in decentralized applications
  3. Integrating payment solutions in various platforms using the SDK

FAQ from Payflow?

  • What is MCP?

MCP stands for Micropayment Protocol, which is designed for handling small transactions efficiently.

  • Is Payflow open source?

Yes! Payflow is open source and available on GitHub.

  • Can I use Payflow for real transactions?

Payflow is primarily a demo and should be tested in a controlled environment before any real transactions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
chainbound
Star
1
Language
TypeScript
License
MIT license
Category
finance

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago