ICPay

ICPay is a multi-chain crypto payment infrastructure project launched in late 2025 and headquartered in the United Kingdom. Its stated mission is to do for crypto what Stripe did for card payments: reduce integration complexity to a few lines of code while eliminating chargebacks, geographic restrictions, and the high fees charged by traditional processors. The project is built around three supported blockchain environments — the Internet Computer Protocol (ICP), Solana, and Base (EVM) — and is designed from the ground up to support both human-facing commerce and autonomous AI agent payments.

Core Mechanism

At the center of ICPay is a REST API hosted at api.icpay.org. Developers authenticate with a publishable key on the frontend or a secret key on the server side and create payment intents that specify an amount in USD or a token quantity. The API returns a transaction for the payer's wallet to sign, abstracting away chain-specific differences in how Solana, EVM, and Internet Computer transactions are constructed and broadcast.

For Solana, developers pass a solanaProvider when initializing the SDK. The SDK then attaches the payer's public key and either signs the transaction client-side or relays a pre-built transaction returned by the API, matching the same contract used by the embeddable widget. Supported Solana wallets include Phantom and Backpack.

For EVM chains, MetaMask, Coinbase Wallet, and WalletConnect are supported. For Internet Computer, the SDK integrates with Plug, Internet Identity, Oisy, and NFID.

Developer Tools

ICPay ships two main developer packages:

icpay-sdk is the core TypeScript library. It exposes methods for creating payment intents in USD or token amounts, fetching verified ledger lists, resolving canister IDs, and querying real-time prices and balances. Tokens are referenced using human-readable shortcodes such as sol_usdc, base_usdc, and ic_icp. The SDK was published under the @ic-pay npm scope and its GitHub repository was last updated in May 2026.

icpay-widget is a set of framework-agnostic Web Components with optional React bindings (@ic-pay/icpay-widget/react). Eight ready-made UI components are available:

• icpay-pay-button: fixed or configurable-amount payment trigger
• icpay-amount-input: custom USD amount entry
• icpay-tip-jar: preset tip denomination selector
• icpay-premium-content: gates content behind a one-time payment
• icpay-article-paywall: previews article content with a crypto unlock
• icpay-coffee-shop: preset inventory store for simple storefronts
• icpay-donation-thermometer: fundraising progress tracker
• icpay-progress-bar: transaction status display

All components accept a publishable API key attribute, optional per-chain recipient addresses for relay payments, and CSS variable theming. A Payload CMS plugin (icpay-payload-plugin) is also available for content-platform integrations.

Fees and Settlement

ICPay charges a flat 0.5% transaction fee on processed volume, compared to Stripe's standard 2.9% plus a fixed per-transaction charge. Settlement is on-chain and described as completing in under two seconds, reflecting the fast finality properties of both Solana and the Internet Computer. There are no chargebacks and no geographic restrictions, unlike card processors that operate only in certain countries.

Supported Assets

The platform accepts payments in the following assets across supported chains:

• Solana: SOL and SPL tokens (including USDC via the sol_usdc shortcode)
• Base / EVM: ETH and ERC-20 tokens (including USDC via base_usdc)
• Internet Computer: ICP and ICRC-compatible tokens

ICPay does not issue a native token. Revenue is derived from the 0.5% processing fee. Token lists are retrieved dynamically from the API, so new assets can be supported without SDK version bumps.

AI Agent Payment Protocols

The "Stripe for AI agents" positioning reflects ICPay's support for two emerging agentic payment standards:

X402 is a payment protocol built on HTTP's 402 "Payment Required" status code. When an AI agent or automated client hits an API endpoint protected by X402, the server returns a 402 response with payment instructions. The client pays on-chain, then retries with a payment proof header to receive the resource. ICPay supports X402 sign-and-settle across Internet Computer, EVM, and Solana, allowing any ICPay-integrated endpoint to become a payable API resource accessible to autonomous agents.

ATXP (Agent Transaction Protocol) follows a quote/pay/execute model designed for multi-step agentic workflows. ICPay's SDK surfaces ATXP as an advanced flow option alongside X402. ATXP has shown early traction in the broader Solana ecosystem, having moved to X402 and MPP (Machine Payments Protocol) on Solana and surpassing one million transactions.

These integrations position ICPay as infrastructure for the machine-economy use case: AI agents that need to autonomously pay for APIs, unlock paywalled content, or purchase digital goods without human approval in the loop.

Solana Ecosystem Fit

Solana's fast finality and low transaction costs make it a natural fit for the sub-second, micro-value payment flows that agentic commerce requires. ICPay's Solana integration covers native SOL, USDC as an SPL token, wallet compatibility with Phantom and Backpack, and support for X402 — a protocol for which Solana has become a leading execution chain, accounting for roughly 25% of all X402 transactions as of mid-2026. ICPay sits at the intersection of the Solana payment ecosystem and the Internet Computer's compute layer, offering a cross-chain payment surface that Solana developers can access through a single SDK.

Team and Community

ICPay is a small team based in the United Kingdom. The project was announced on the DFINITY developer forum in late 2025, where the core team participated in developer feedback discussions. The GitHub organization shows four repositories under active maintenance, with the SDK and widget repos last updated in May 2026. Community channels include a Discord server and a contact email at [email protected]. The project remains early-stage by GitHub star count, but its technical scope — spanning three major blockchain ecosystems and two emerging agentic payment standards — reflects an ambitious infrastructure bet on the convergence of crypto payments and AI agent commerce.

Audits and Security

No public security audit has been disclosed as of mid-2026. The platform authenticates developer integrations through API keys (publishable for frontend, secret for server-side) and relies on on-chain transaction finality for settlement security. Developers should apply standard key hygiene practices when integrating the private SDK server-side.