Why icpay?
Instant settlement to your wallet with no intermediaries or withdrawal delays. Customers pay, you receive – that simple.
0.5% transaction fees. Free to use. Start earning crypto in minutes.
Multi-chain support including Base, x402, and Internet Computer means your customers can pay using their preferred network and token.
Perfect for:
Key Features:
Built for developers, loved by merchants.
Get started in minutes at icpay.org
This plugin:
Requires an icpay account and API keys.
Frontend widgets use the publishable key; server tasks use the secret key.
To obtain keys, create an account on https://icpay.org and generate them in your dashboard.
This plugin includes a minified frontend script for the widget: assets/js/icpay-embed.min.js.
Widget source (primary): https://github.com/icpay/icpay-widget
SDK source (dependency): https://github.com/icpay/icpay-sdk
Build notes (recommended): The minified icpay-embed.min.js is built from the open-source icpay-widget repository.
To reproduce:
1. Clone icpay-widget and install deps (pnpm/yarn/npm supported): pnpm install
2. Build: pnpm build
3. Copy the generated minified widget bundle to this plugin at assets/js/icpay-embed.min.js.
This plugin connects to the ICPay service operated by icpay, Inc. to process payments:
– What: Payment creation and status updates.
– When: When rendering the widget (publishable key) and when receiving webhooks; when syncing payments from your dashboard.
– Data sent: Payment amounts, selected crypto asset, and optional metadata you configure (e.g., order ID). Webhook payloads contain payment status updates.
Privacy Policy: https://icpay.org/privacy
Terms of Service: https://icpay.org/terms
https://identity.ic0.app — opened only when a user chooses Internet Identity. No static assets are offloaded; it is an external login service.https://global.transak.com (or https://global-stg.transak.com in non-production) — used only when the on-ramp modal is triggered. No static assets are offloaded; it is a payment service.No JS/CSS/images are loaded from remote CDNs by this plugin. All static assets (scripts, styles, and images) used by the plugin UI are bundled and served locally within the plugin. The build script enforces this by rejecting known disallowed remote asset references.