內容簡介
總結：ICPay payments 外掛允許您使用下拉式小工具在 Internet Computer (ICP) 上接受付款。此外掛由 ICPay, Ltd. (位於美國德拉瓦州) 提供。有任何問題請聯繫：[email protected]。
問題：ICPay payments 外掛提供了哪些功能以及相關範圍？
答案：ICPay payments 外掛提供 Gutenberg 區塊和短代码用於所有 ICPay 付款小工具（如付款按鈕、金額輸入、小費罐、高級內容、文章付費牆、捐款溫度計、咖啡店）；在本地排隊 ICPay 付款小工具腳本；添加管理員設定以供公開和密鑰使用；接收 ICPay 付款 Webhooks 以更新本地數據；同步來自 ICPay 付款的支付（手動和計時任務）；在本地表中存儲具有豐富數據（amountUsd、amountUnits、ledgerSymbol、pluginSource、wp user）的支付；顯示具有篩選器、分頁和詳細視圖的管理員列表。
問題：ICPay payments 外掛連接的 ICPay 服務用於處理哪些付款相關操作？這些數據是在何時發送的？
答案：ICPay payments 外掛連接到由 ICPay, Ltd. 運營的 ICPay 服務來處理支付的創建和狀態更新操作；這些數據在渲染小工具時（公開密鑰）以及接收 Webhooks、同步支付時從您的儀表板發送；已配置第三方服務的選定数字资产，以及選定的加密资产、您配置的可选元数据（例如，訂單 ID）。 Webhook 載荷包含付款狀態更新。
問題：ICPay payments 外掛是否會從遠端CDN 加載 JS/CSS/images 資源？
答案：不，這個外掛不會從遠端CDN加載JS/CSS/images。外掛的所有靜態資產（腳本、樣式和圖像）均已在外掛內部捆綁並在本地提供。构建腳本通過拒絕已知不允许的遠端資產引用來強制執行此操作。
外掛標籤
開發者團隊
原文外掛簡介
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:
E-commerce stores wanting to tap into crypto-native customers
Digital products and services
SaaS businesses
International payments without currency conversion fees
Key Features:
Seamless WooCommerce integration
Support for 50+ cryptocurrencies and tokens
Real-time payment confirmations
Developer-friendly with extensive documentation
Secure, non-custodial – funds go directly to your wallet
Optional X402 (Coinbase) payment support enabled
Built for developers, loved by merchants.
Get started in minutes at icpay.org
This plugin:
Provides a Gutenberg block and shortcodes for all icpay payment widgets (Pay Button, Amount Input, Tip Jar, Premium Content, Article Paywall, Donation Thermometer, Coffee Shop)
Enqueues the ICPay payments widget script locally
Adds admin settings for publishable and secret keys
Receives icpay payments webhooks to update local data
Syncs payments from icpay payments (manual and cron)
Stores payments in a local table with enriched data (amountUsd, amountUnits, ledgerSymbol (token), pluginSource, wp user)
Shows an admin list with filters, pagination, and detail view
Adds Tools action to clear local ICPay payment history (with confirmation)
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.
Source code and build
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.
External service disclosure
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
Additional third-party services used by the widget (optional)
Identity (authentication): https://identity.ic0.app — opened only when a user chooses Internet Identity. No static assets are offloaded; it is an external login service.
On-ramp provider: 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.
