PolyPay - Turn your wallet into a payment gateway for humans and AI

by•
Most crypto gateways hold your money first. PolyPay doesn't. Paste your own wallet address and you're live — we watch the chain, match payments to orders, and fire Ed25519-signed webhooks. No custody, no private keys, no wallet approval. 10 chains (BTC, ETH, Tron, Solana, Base, BSC, Polygon, Arbitrum, Optimism, TON), USDT/USDC + native assets. Hosted checkout, JS/PHP SDKs, WHMCS, WooCommerce, Shopify. Plus x402 + MCP: AI agents pay per API call in USDC, no account needed.

Add a comment

Replies

Best
Maker
šŸ“Œ
Hey Product Hunt šŸ‘‹ I built this after watching a hosting client lose a week to a crypto payment integration. Every gateway wanted the same thing first: send us the money, we'll forward it later. Custody, KYC queues, T+1 settlement, and a support ticket when a transfer got stuck on-chain. The thing he actually wanted was absurdly simple — money from his customers landing in his own wallet. So PolyPay starts from the opposite end. You paste your own wallet address, and that's the setup. We watch the chain, match each payment to an order, wait for confirmations, and fire an Ed25519-signed webhook. We never hold your funds and never ask you to approve a wallet. There is no private key here for us to lose. The part I didn't plan for: merchants weren't the only ones showing up. Agents were. People wanted to charge software, not just people. That reshaped the roadmap, so we shipped x402 — wrap any API, data feed or MCP resource behind an HTTP 402 challenge, and an AI agent pays in USDC on Base and retries automatically. No account, no signup form, no human in the loop. Same dashboard, same wallet, same reporting as your human checkout. Live today: • 10 chains — Bitcoin, Ethereum, Tron, Solana, Polygon, BSC, Base, Arbitrum, Optimism, TON. USDT/USDC plus native assets. • Hosted checkout, JS SDK, PHP SDK, plain REST. WHMCS, WooCommerce, Shopify. • x402 for agent payments, plus an MCP server so your coding agent can create orders and resources directly. • Signed webhooks, sandbox environment, notification center (Telegram, Email, Discord, Slack, WhatsApp, webhooks). • 10 languages across checkout and dashboard. Three things I'd genuinely like your take on: 1. If you run an API or MCP server — would you charge agents per call, or would you rather sell them prepaid credits? 2. What's the one integration that would have to exist before you'd switch off your current gateway? 3. Is "funds go straight to your wallet" actually an advantage for you, or does it just mean more accounting work? I'll be here all day. Roast the docs, the checkout flow, the pricing — especially the pricing. — StonyGround, building PolyPay