Description
The AnyCoin Payment Gateway plugin enables WooCommerce stores to accept cryptocurrency payments directly, without requiring a third-party payment processor. This non-custodial solution gives merchants full control over their funds.
Key Features
- Non-custodial: You maintain full control of your funds
- Multi-asset support: Accept ZANO and fUSD cryptocurrencies
- Real-time monitoring: Automatic blockchain transaction verification
- QR code payments: Easy mobile wallet integration
- Integrated addresses: Unique payment IDs for each transaction
- Admin dashboard: Transaction oversight and management
- Automated processing: Background monitoring and status updates
Supported Assets
- ZANO
- fUSD
How It Works
- Customer selects AnyCoin payment at checkout
- System generates unique integrated address with payment ID
- Customer scans QR code or copies payment details
- Customer sends payment from their cryptocurrency wallet
- Plugin monitors blockchain for payment confirmation
- Order status updates automatically when confirmed
Privacy Policy
This plugin sends the configured wallet address and private view key to the configured blockchain node, and to the legacy verification service when needed. These are sensitive wallet privacy credentials. View keys are placed in JSON bodies. HTTPS certificates are verified; explicitly enabled HTTP node connections are unencrypted and can expose the view key and payment responses to interception. External verification services require HTTPS. The plugin does not send customer names, email addresses, or billing addresses to these APIs. Provider request logs and WordPress database/backups must be protected. QR codes are generated locally.
Videos
External Services
This plugin connects to the following third-party/external services:
-
AnyCoin Verification API
- Purpose: Verify Payment ID details for transactions and assist with asset metadata.
- Endpoint base: https://api.acceptanycoin.com
- Data sent: Transaction hash, wallet address, and private view key. Uses POST JSON at /api/decode-transaction/{hash}; the service must support this contract. Hosted-service compatibility is not yet verified.
- When: During payment verification and monitoring.
- Terms/Privacy: See provider policies on
https://www.acceptanycoin.com/terms-of-service.
-
Zano Explorer API
- Purpose: Retrieve transaction block/confirmation details for verification.
- Endpoint: https://explorer.zano.org/api/get_tx_details/{tx_hash}
- Data sent: Transaction hash only; no customer PII.
- When: During payment monitoring to compute confirmations.
- Privacy: Public blockchain explorer (no account data stored by this plugin).
-
MEXC Price API
- Purpose: Fetch ZANO/USD price to estimate conversion amounts.
- Endpoint: https://api.mexc.com/api/v3/ticker/price?symbol=ZANOUSDT
- Data sent: None (GET request only); no customer PII.
- When: On admin screens and at checkout to compute displayed amounts.
- Terms/Privacy:
https://www.mexc.com/terms
-
Configured Zano node
- Purpose: Generate integrated addresses and decode incoming payment outputs.
- Data sent: Wallet address, payment IDs, and private view key in JSON request bodies.
- Endpoint: Merchant-configured trusted URL ending in /json_rpc. HTTPS is recommended; HTTP requires Allow HTTP node and a protected network connection.
Notes:
– You may self-host the verification service and node. QR generation is local.
– Network endpoints can be configured within plugin settings where applicable.
Support
For support, please visit https://acceptanycoin.com/anycoin-payment-processor
Installation
- Upload plugin ZIP through Plugins → Add New → Upload Plugin
- Activate the plugin
- Go to WooCommerce → Settings → Payments → AnyCoin Payment
- Enter your wallet address, private view key, and trusted node endpoint; for HTTP-only nodes enable Allow HTTP node
- Save settings
FAQ
Is this plugin custodial?
No, this is a non-custodial solution. Payments go directly to your cryptocurrency wallet address.
What cryptocurrencies are supported?
Currently supports ZANO and fUSD assets on the Zano blockchain network.
Do I need to run a blockchain node?
Configure a trusted node URL ending in /json_rpc, including its port. HTTPS is recommended. For an HTTP-only node, enable Allow HTTP node in gateway settings; this also supports a node on the WordPress server or private network. HTTP sends the private view key and payment responses without encryption, so protect that connection with a private link or VPN. Orders must be priced in USD.
How are payments verified?
Payments are detected by securely scanning the blockchain using your wallet’s private view key. This allows the plugin to identify incoming transactions to your address without exposing your funds or private spend key.
Is there a transaction fee?
The plugin itself doesn’t charge fees. You only pay standard network transaction fees.
Changelog
1.1.1
- Security: authorize payment pages and AJAX requests by customer, store manager, or secret order key.
- Security: verify HTTPS certificates, disable redirects, remove private view keys from URLs and debug payload logs.
- Support HTTP-only Zano nodes through the explicit Allow HTTP node setting, including configured custom ports and private IPv4 hosts. External services still require HTTPS.
- Connection tests now require a valid node height response rather than accepting HTTP 200 alone.
- Security: prevent asset changes after detection and races between asset updates, claims, and expiration.
- Security: require real received amounts and actual blockchain inclusion before confirming payments.
- HF6: scope grouped fallback claims to transaction/payment ID and verify each ID’s incoming asset amount separately, including FUSD.
- HF6: reject rounded/overflowing daemon payment IDs and ambiguous wallet ID conversions; validate grouped response fields.
- HF6: keep the old duplicate-payment index unless its unique transaction/payment-ID replacement is verified.
- Reject unavailable exchange rates and non-USD orders instead of guessing amounts.
- Bound QR inputs, throttle status polling, and prevent caching/referrer leakage on payment pages.
- Upgrade requirements: configure a trusted node running Zano v2.2.1.501 or newer; existing HTTP nodes need Allow HTTP node enabled. Verify that the HTTPS legacy verification backend supports POST JSON. FUSD decoder responses must identify their asset. GET-only verification is rejected. Test checkout on staging before deployment.
1.1.0
- Zano Hard Fork 6 (HF6) support: payments are now matched using intrinsic per-output payment IDs decoded directly from the Zano node
- A single transaction can now pay multiple orders with different payment IDs and assets, as allowed after HF6
- Safe handling of 64-bit payment IDs in node responses
- Database migration: transaction uniqueness is now enforced per transaction + payment ID instead of per transaction
- Security: payment amounts are now always computed server-side and FUSD payments are amount-verified like ZANO
- Fixed: transactions are only matched against the asset the order expects
- Fixed: intrinsically verified payments are no longer re-verified through the external API, preventing paid orders from being marked failed
- Fixed: the status update task now honors the configured confirmation threshold
- Note: the configured Zano node must run version 2.2.1.501 or newer
1.0.5
- Minor Fixes
1.0.4
- Minor Fixes
1.0.3
- Minor Fixes
1.0.2
- Image Fixes
1.0.1
- Initial release
- Non-custodial cryptocurrency payment processing
- ZANO and fUSD asset support
- Real-time blockchain monitoring
- QR code payment integration
- Admin dashboard and automated verification
