AvoPay Bitcoin for WooCommerce
| 开发者 | avopaydev |
|---|---|
| 更新时间 | 2026年7月9日 00:41 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
AvoPay lets your WooCommerce store accept Bitcoin Lightning payments with zero chargebacks, no KYC, and no code changes required. Payments settle directly to your self-custodial AQUA wallet — no middleman, no custodian.
AvoPay never holds your money. There is no AvoPay balance, no withdrawal step, and no custodial account — every payment settles wallet-to-wallet. Bitcoin appears as one more payment method at checkout, working alongside your existing gateways (Stripe, PayPal, cards) rather than replacing them.
Learn more at avopay.dev/woocommerce.
Features
- Zero node setup — no Bitcoin or Lightning node required
- Non-custodial — funds go directly to your AQUA wallet
- Two payment options — Lightning invoice or direct Liquid Bitcoin (L-BTC) payment
- Automatic sats conversion — for stores priced in EUR, USD, GBP, CAD, AUD, JPY, CHF, DKK, or BRL
- No chargebacks — Bitcoin payments are irreversible by design
- Built-in retry flow — up to 3 automatic retries per order
- Full audit log — every payment event stored per order
- Customer selects Bitcoin Lightning at checkout
- AvoPay creates a non-custodial Boltz reverse swap routing the payment to your Liquid address
- Funds arrive in your AQUA wallet automatically — no manual steps required
- WooCommerce 8.0+
- Store currency set to EUR, USD, GBP, CAD, AUD, JPY, CHF, DKK, or BRL (additional currencies will be added over time)
- An AvoPay account — register at avopay.dev
- AQUA wallet by JAN3 (free, iOS and Android — aqua.net)
安装:
- In your WordPress admin, go to Plugins > Add New Plugin
- Search for "AvoPay Bitcoin for WooCommerce"
- Click Install Now, then Activate
- Go to WooCommerce > Settings > Payments > AvoPay and enable the payment method
- Navigate to WooCommerce > AvoPay to complete the 3-step setup:
- Create a free account at avopay.dev and copy your API key
- Paste your API key into the plugin to connect your account
- Scan the QR code with your AQUA wallet to link your Bitcoin address
- Send a test payment to verify everything works end-to-end
屏幕截图:
常见问题:
Do I need to run a Bitcoin node?
No. AvoPay uses Boltz Exchange for non-custodial Lightning to Liquid swaps. No node required.
Where do funds go?
Directly to your AQUA wallet. AvoPay never holds your funds.
What wallet do I need?
The AQUA wallet by JAN3 — free on iOS and Android at aqua.net.
Are there chargebacks?
No. Bitcoin payments are irreversible by design.
Can I accept both cards and Bitcoin?
Yes. AvoPay adds Bitcoin as one more payment method at checkout — it works alongside Stripe, PayPal, and any other WooCommerce gateway you already use. Customers who want to pay by card still can; nothing about your existing checkout changes.
Which currencies are supported?
Stores priced in EUR, USD, GBP, CAD, AUD, JPY, CHF, DKK, or BRL. The order total is converted to satoshis at the live BTC rate at checkout. Additional currencies will be added over time.
What are the fees?
AvoPay charges a flat subscription with no percentage transaction fee. A Boltz swap fee of roughly 0.25% plus a small network fee applies at settlement — charged by Boltz, not AvoPay. Your first 5 payments are free.
What happens if the AvoPay service is unreachable?
New Bitcoin payments fail gracefully — the customer sees a standard payment error and can complete the order with any other payment method you offer. Orders that have already been paid are never lost: Boltz retries settlement webhooks, and the plugin's own cron re-checks every pending order once a minute until settlement is verified. Because funds settle wallet-to-wallet, your money is never held by AvoPay at any point.
What happens to my data if I uninstall the plugin?
Plugin configuration (API key, logs, wallet connection) is deleted automatically. WooCommerce order payment data is preserved by default as a financial audit record. You can enable full deletion under WooCommerce > Settings > Payments > AvoPay before uninstalling.
更新日志:
1.0.20
- Fix: checkout could show a fatal PHP error ("Call to a member function get_total() on false") when WooCommerce was unable to load the order while starting a Bitcoin payment. The gateway now fails gracefully with a clear "please refresh and try again" notice instead of a white screen.
- Improvement: when an order can't be loaded at payment start, the cause is now logged with context (WooCommerce version, HPOS on/off, plugin version) to speed up diagnosis.
- Feature: L-BTC (Liquid) payments now settle via instant server push — orders are marked paid moments after the first Liquid confirmation instead of waiting for the polling cron. The cron remains as an automatic fallback.
- Feature: the checkout page now shows "Payment detected — waiting for first Liquid confirmation" as soon as an L-BTC payment is seen on the network.
- Improvement: wallet reconnects that would strand in-flight L-BTC payments are now blocked by the AvoPay server; the dashboard shows the reason instead of failing silently.
- Improvement: the L-BTC status poll settles faster (every minute instead of up to five).
- Security: cron endpoints now accept the authentication header only — the legacy ?secret= URL fallback was removed.
- Security: L-BTC (Liquid) payments now settle through the shared cryptographic verifier — the confidential amount and asset are verified and one Liquid confirmation is required before an order is marked paid.
- Security: removed the plugin's independent on-chain detection path, which was blind to confidential amounts; WooCommerce now delegates to the same settlement implementation used by the AvoPay API (one verifier, no duplicate logic).
- Feature: optional Bitcoin on-chain payment tab via Boltz chain swaps (BTC→L-BTC atomic swap); enabled per-merchant in the AvoPay dashboard; minimum order 25,000 sats
- UX: payment tab order changed to Lightning → Bitcoin Onchain → Liquid across the checkout page
- UX: tab labels renamed — "L-BTC Direct" → "Liquid", "Bitcoin" → "Bitcoin Onchain"; emoji removed from all tab labels
- Maintenance: version number now correctly reflected in plugin header (was stuck at 1.0.12 since v1.0.1 due to release tooling bug)
- Maintenance: release tooling corrected; no plugin behaviour changes
- Fix: PHP fatal error on cron backstop caused by stale interface declarations (broken since v1.0.1)
- Fix: retry payment button now calls the API correctly instead of a removed local method (broken since v1.0.1)
- Fix: "Tested up to" updated to WordPress 7.0 — restores search visibility on WP.org
- Code: Plugin Check 0 errors, 0 warnings
- Fix: payment card now renders above order details and billing address on WooCommerce Blocks checkout
- UX: checkout QR card redesigned — white background for scanner compatibility, reduced size, dark theme
- UX: payment prompt text added above Lightning invoice ("Please complete the Lightning payment below to finalise your order.")
- UX: Lightning QR reduced from 380px to 220px — still fully scannable, page no longer requires scrolling to see order details
- UX: payment method icon updated to Bitcoin logo; description updated to "Pay from any Bitcoin Lightning wallet"
- UX: admin dashboard header updated with AvoPay logo and Bitcoin menu icon
- Marketplace: installation instructions updated for WordPress.org — no manual ZIP download required
- Compliance: move "External services" to a standalone top-level readme section with full data-sent descriptions and Privacy + Terms links for all five services
- Security: payment status polling endpoints now require a per-order poll token (generated at checkout, verified server-side) — prevents unauthenticated enumeration of order status
- Feature: merchant-absorbs-fees across all payment channels
- Copy: step 3 title, description, and button text updated for clarity
- Fix: admin dashboard now passes correct
licensedproperty to JS (fixes step 2 auto-QR load and step 3 test payment display)
- Compliance: remove custom update checker (WP.org guideline — updates served from WP.org)
- Compliance: rename plugin slug to avopay-bitcoin-for-woocommerce (WooCommerce trademark policy)
- Code: replace date(), parse_url(), strip_tags() with WP equivalents gmdate(), wp_parse_url(), wp_strip_all_tags()
- Code: add wp_unslash() before all sanitize_text_field() calls on superglobals
- Code: add ordered placeholders (%1$s) and translators comments in all translatable strings
- Code: remove development error_log() call
- Fix: site domain now registered with AvoPay on API key activation so client dashboard shows correct domain
- Compliance: payment creation logic moved server-side; plugin is now a thin API connector (no local trial counter or gateway disable)
- Compliance: inline script and style tags replaced with wp_add_inline_script / wp_add_inline_style
- Security: input sanitization added for CONTENT_TYPE, POST keys, and JSON payload version field
- Docs: external service Terms and Privacy links added for CoinGecko, CoinCap, and Blockstream Esplora
- WordPress.org release
- Added: optional "Delete AvoPay data on uninstall" setting (default: off, preserves order financial records)
- Improved: full uninstall cleanup of plugin options, logs table, and cron jobs
- Improved: activation table creation uses dbDelta for safe upgrades
- Fix: test payment stops at transaction.mempool with live wait counter
- UX: step 2 connected + date merged into single pill
- UX: step 3 success state split into green banner and neutral info box
- Security: rate limiting on all API routes
- Security: JWT token_version revocation — stale tokens rejected immediately
- Security: CORS locked down to avopay.dev domains
- Security: OTP log suppression in Nginx access logs
- Security: startup env validation — API exits on missing required vars
- Fix: claim fee bumping on retry (RBF — 500 to 750 to 1000 sats/vbyte)
- Feature: invoice.settled status marks order paid instantly
- Improvement: decoupled claim trigger from webhook handler
- Improvement: adaptive JS polling (1s x 15 then 3s)
- Improvement: API secondary poll via open-CORS swap status endpoint
- Fix: double payment email on fast settlements
- Feature: relay architecture — API-side callback delivery with retry queue
- Feature: swap_registry table tracks full lifecycle per swap
- Feature: server-side callback delivery via AvoPay API
- Fix: WP cron backstop age guard skips orders younger than 2 minutes
- Feature: slow payment watchdog — 30 min delay email and 120 min manual review flag
- Feature: Hetzner cron backstop every 5 min for stuck pending orders
- Feature: L-BTC direct payment tab — customer can pay from any Liquid wallet
- Fix: test payment 500 error — removed stale descriptor method calls
- Fix: step 2 QR and step 3 test payment now show error feedback on AJAX failure
- Fix: claim broadcaster now works on any hosting environment
- Fix: empty PHP files replaced to prevent security scanner false positives
- Feature: server-side SLIP-0077 address derivation via AvoPay API
- Change: vendor directory removed — zero PHP dependencies
- Feature: L-BTC direct payment support
- Feature: retry flow (max 3 attempts)
- Feature: PM2 graceful shutdown
- Feature: claim retry queue with backoff
- Initial public release