Loops HousePayminto

NEAR HACKATHON
Links
Team
1 member- SAOwner
Sagar Jethi
Overview
Proof first: on 14 Nov 2026 a buyer paid a Payminto link with 0.000854 ETH on Base from MetaMask. NEAR Intents delivered exactly 1.50 USDC to the merchant's own NEAR mainnet account 36 seconds later, and the node marked it paid only after reading that transfer on NEAR itself. Both transactions and the captured quote are in the README.
The problem: taking crypto still means custody, a chain the buyer may not hold, a refund address to type, and no safe way to let an AI agent spend.
Payminto is a self-hosted, non-custodial payment gateway on NEAR, MIT licensed. People: one checkout screen. Pick USDC, USDT or ETH on Base, Ethereum, Arbitrum, Solana or Polygon, scan one QR or press "Pay with your wallet". No refund address, no custody; the merchant gets the exact invoice in USDC on NEAR. Agents: an owner opens a Budget on a NEAR contract with a cap, allowed payees, an expiry and escrowed USDC. The agent pays per API call with signed vouchers over x402 (milliseconds, no transaction per call), and pays invoices from any chain through MCP tools (invoice_pay_options, invoice_deposit, invoice_status) or the SDK. Security: the wallet, the node and the contract each enforce the Budget, and every refusal names the rule it hit. A payee check holds lookalike or new accounts until the owner approves. Swarms: owners who owe each other are netted into one NEAR transaction; the contract verifies every voucher and stores a Merkle root, so anyone can prove a single call with no node and no keys.
Run it: pnpm local starts the whole product (local NEAR node, node, dashboard) with test accounts, no keys, no real money, and a guided 11-step tour.
Limits, plainly: the any-chain checkout rail is live on NEAR mainnet. The agent hub contract is unaudited and runs on a local NEAR node, not mainnet.