| 开发者 | 1nodes |
|---|---|
| 更新时间 | 2026年9月21日 12:57 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
1nodes-crypto-payments-for-edd folder to the /wp-content/plugins/ directory, or install the plugin ZIP file through Plugins → Add New Plugin → Upload Plugin.Plugins menu in WordPress.Downloads → Settings → Payments.Yes. Easy Digital Downloads is required to use this plugin.
The plugin is designed for Easy Digital Downloads 3.7.0 and later compatible versions.
PHP 8.1 or later is required.
Create a 1nodes account and obtain your Merchant Key and Secret Key from your account dashboard.
After the customer completes the payment on 1nodes, 1nodes sends a signed webhook request to the store. The plugin verifies the webhook signature and marks the corresponding EDD payment as complete. When the customer returns to the store, the plugin also checks the local EDD payment status using AJAX while waiting for webhook confirmation.
Yes. The plugin allows customers to complete payments through the 1nodes hosted cryptocurrency checkout.
The non-custodial option allows merchants to receive cryptocurrency payments directly to their own wallet using an XPUB-based setup. Payment addresses can be derived without giving 1nodes access to the merchant's private keys or recovery phrase.
With the non-custodial payment option, customer payments are sent directly to addresses derived for the merchant's wallet rather than being held by 1nodes.
No. Private keys and wallet recovery phrases are not required by this plugin and should never be provided to 1nodes.
The standard gateway uses percentage-based transaction fees. The non-custodial option uses a monthly subscription and allows supported cryptocurrency payments to be sent directly to the merchant's wallet using an XPUB-based setup.
No. The plugin automatically generates the webhook callback URL when a payment is created.
The Merchant Key is stored in the WordPress database as an EDD gateway setting and is used for authenticated requests to the 1nodes API.
Yes. The Secret Key is used to verify the HMAC SHA-256 signature included with webhook requests from 1nodes.