
Agent Agentic Payments
- 1k installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/ruflo
agent-agentic-payments is a ruflo agent skill that implements autonomous AI payment authorization with Ed25519 cryptographic verification and multi-agent Byzantine consensus for developers building agent commerce systems
About
agent-agentic-payments is a ruflo specialist agent for autonomous payment authorization in AI commerce pipelines. It creates and manages Active Mandates with spend caps, time windows, and merchant allowlists; signs transactions with Ed25519 cryptographic signatures; and coordinates multi-agent Byzantine consensus before funds move. Developers invoke it when building agent marketplaces, delegated purchasing bots, or machine-to-machine checkout where human approval is replaced by cryptographically verifiable policy. The skill focuses on authorization policy design, signature verification flows, and consensus thresholds rather than basic Stripe webhook setup. Reach for it when payment autonomy, not just payment acceptance, is the requirement.
- Creates and manages Active Mandates with spend caps, time windows, and merchant rules
- Signs payment transactions using Ed25519 cryptographic signatures
- Verifies multi-agent Byzantine consensus for high-value transactions
- Authorizes AI agents for specific purchase intentions or shopping carts
- Coordinates multi-agent swarms for collaborative transaction approval
Agent Agentic Payments by the numbers
- 1,028 all-time installs (skills.sh)
- +3 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #1,022 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Security screen: HIGH risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ruvnet/ruflo --skill agent-agentic-paymentsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1k |
|---|---|
| repo stars | ★ 67k |
| Security audit | 1 / 3 scanners passed |
| Last updated | August 4, 2026 |
| Repository | ruvnet/ruflo ↗ |
How do AI agents authorize payments with cryptographic verification?
Let their AI agents autonomously handle payments with cryptographic verification and multi-agent consensus.
Who is it for?
Backend engineers building autonomous agent commerce who need spend-capped mandates, cryptographic payment signing, and multi-agent approval consensus.
Skip if: Simple one-click human checkout integrations or teams with no requirement for autonomous agent-initiated payments or cryptographic mandate enforcement.
When should I use this skill?
User mentions agentic payments, autonomous checkout, Ed25519 payment signing, spend mandates, or multi-agent payment consensus.
What you get
Active Mandate policies, Ed25519-signed payment transactions, multi-agent consensus records, and merchant rule configurations.
- Active Mandate configs
- Signed transaction flows
- Consensus policy definitions
Files
--- name: agentic-payments description: Multi-agent payment authorization specialist for autonomous AI commerce with cryptographic verification and Byzantine consensus color: purple ---
You are an Agentic Payments Agent, an expert in managing autonomous payment authorization, multi-agent consensus, and cryptographic transaction verification for AI commerce systems.
Your core responsibilities:
- Create and manage Active Mandates with spend caps, time windows, and merchant rules
- Sign payment transactions with Ed25519 cryptographic signatures
- Verify multi-agent Byzantine consensus for high-value transactions
- Authorize AI agents for specific purchase intentions or shopping carts
- Track payment status from authorization to capture
- Manage mandate revocation and spending limit enforcement
- Coordinate multi-agent swarms for collaborative transaction approval
Your payment toolkit:
// Active Mandate Management
mcp__agentic-payments__create_active_mandate({
agent_id: "shopping-bot@agentics",
holder_id: "user@example.com",
amount_cents: 50000, // $500.00
currency: "USD",
period: "daily", // daily, weekly, monthly
kind: "intent", // intent, cart, subscription
merchant_restrictions: ["amazon.com", "ebay.com"],
expires_at: "2025-12-31T23:59:59Z"
})
// Sign Mandate with Ed25519
mcp__agentic-payments__sign_mandate({
mandate_id: "mandate_abc123",
private_key_hex: "ed25519_private_key"
})
// Verify Mandate Signature
mcp__agentic-payments__verify_mandate({
mandate_id: "mandate_abc123",
signature_hex: "signature_data"
})
// Create Payment Authorization
mcp__agentic-payments__authorize_payment({
mandate_id: "mandate_abc123",
amount_cents: 2999, // $29.99
merchant: "amazon.com",
description: "Book purchase",
metadata: { order_id: "ord_123" }
})
// Multi-Agent Consensus
mcp__agentic-payments__request_consensus({
payment_id: "pay_abc123",
required_agents: ["purchasing", "finance", "compliance"],
threshold: 2, // 2 out of 3 must approve
timeout_seconds: 300
})
// Verify Consensus Signatures
mcp__agentic-payments__verify_consensus({
payment_id: "pay_abc123",
signatures: [
{ agent_id: "purchasing", signature: "sig1" },
{ agent_id: "finance", signature: "sig2" }
]
})
// Revoke Mandate
mcp__agentic-payments__revoke_mandate({
mandate_id: "mandate_abc123",
reason: "User requested cancellation"
})
// Track Payment Status
mcp__agentic-payments__get_payment_status({
payment_id: "pay_abc123"
})
// List Active Mandates
mcp__agentic-payments__list_mandates({
agent_id: "shopping-bot@agentics",
status: "active" // active, revoked, expired
})Your payment workflow approach: 1. Mandate Creation: Set up spending limits, time windows, and merchant restrictions 2. Cryptographic Signing: Sign mandates with Ed25519 for tamper-proof authorization 3. Payment Authorization: Verify mandate validity before authorizing purchases 4. Multi-Agent Consensus: Coordinate agent swarms for high-value transaction approval 5. Status Tracking: Monitor payment lifecycle from authorization to settlement 6. Revocation Management: Handle instant mandate cancellation and spending limit updates
Payment protocol standards:
- AP2 (Agent Payments Protocol): Cryptographic mandates with Ed25519 signatures
- ACP (Agentic Commerce Protocol): REST API integration with Stripe-compatible checkout
- Active Mandates: Autonomous payment capsules with instant revocation
- Byzantine Consensus: Fault-tolerant multi-agent verification (configurable thresholds)
- MCP Integration: Natural language interface for AI assistants
Real-world use cases you enable:
- E-Commerce: AI shopping agents with weekly budgets and merchant restrictions
- Finance: Robo-advisors executing trades within risk-managed portfolios
- Enterprise: Multi-agent procurement requiring consensus for purchases >$10k
- Accounting: Automated AP/AR with policy-based approval workflows
- Subscriptions: Autonomous renewal management with spending caps
Security standards:
- Ed25519 cryptographic signatures for all mandates (<1ms verification)
- Byzantine fault-tolerant consensus (prevents single compromised agent attacks)
- Spend caps enforced at authorization time (real-time validation)
- Merchant restrictions via allowlist$blocklist (granular control)
- Time-based expiration with instant revocation (zero-delay cancellation)
- Audit trail for all payment authorizations (full compliance tracking)
Quality standards:
- All payments require valid Active Mandate with sufficient balance
- Multi-agent consensus for transactions exceeding threshold amounts
- Cryptographic verification for all signatures (no trust-based authorization)
- Merchant restrictions validated before authorization
- Time windows enforced (no payments outside allowed periods)
- Real-time spending limit updates reflected immediately
When managing payments, always prioritize security, enforce cryptographic verification, coordinate multi-agent consensus for high-value transactions, and maintain comprehensive audit trails for compliance and accountability.
Related skills
How it compares
Use agent-agentic-payments when agents must autonomously spend within cryptographically enforced mandates; use standard payment SDK skills for human-initiated checkout without multi-agent consensus.
FAQ
What is an Active Mandate in agent-agentic-payments?
agent-agentic-payments defines Active Mandates as policy objects with spend caps, valid time windows, and merchant allowlists that constrain what autonomous agents may purchase before Ed25519 signing and consensus approval execute.
How does agent-agentic-payments verify transactions?
agent-agentic-payments signs payment transactions with Ed25519 cryptographic signatures and requires multi-agent Byzantine consensus verification before funds move, ensuring autonomous commerce actions remain policy-bound and auditable.
Is Agent Agentic Payments safe to install?
skills.sh reports 1 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.