Maintenance release; no functional changes since 0.7.1.
0.7.1
Remove the bundled GitHub self-updater; the plugin now updates through the WordPress.org directory.
Refresh the plugin description and short description.
Update the bundled Spanish (es_AR, es_ES) translations.
0.7.0
Expired checkout invoices now verify payment first, then re-issue a fresh invoice in place instead of dead-ending on “Invoice expired”.
NWC Proxy payouts are now a pooled wallet sweep to your Lightning Address (keeping the greater of 1% or 10 sats as a routing reserve), replacing per-order forwarding so small orders accumulate and ship together.
Settlement notifications are no longer missed: a wallet/Nostr signal that arrives while a check is already running is re-checked instead of dropped.
WebLN and the other payment buttons now disable when the invoice expires.
Added a “Why do I need an NWC proxy?” help dialog on the Receiver tab explaining LUD-21 / NIP-57 / NWC, with reference links.
The proxy transactions list and sweep payouts are now one real-time table with an Origin column (#order or Sweep) and a Routing fee column.
The terminal NWC wallet balance now updates live on the Receiver tab.
Removed the “Manual sats per currency unit” setting; added a help tip to “Price buffer percent”.
0.6.15
Documented the lncurl disposable-wallet service with links to its terms and privacy policy.
0.6.14
The Connection status section now appears only on the NWC Proxy tab instead of below every tab.
0.6.13
Redesigned the Receiver mode selector as a segmented toggle button group (keyboard-accessible) instead of a dropdown.
0.6.12
Renamed the “NWC Wallet” tab to “NWC Proxy”.
In NWC Proxy receiver mode, a note below the Lightning Address points to the NWC Proxy tab with a “Save & open NWC Proxy” button that saves first, then opens it.
0.6.11
Added an explainer in the NWC Proxy tab (disposable mode) describing how lncurl wallets work: free for the first hour, ~1 sat/hour after, and a 1%/10-sat routing reserve.
0.6.10
The NWC Wallet “Withdraw” flow now confirms the send and refreshes the balance as soon as the wallet’s NIP-47 payment_sent notification arrives, falling back to the pay response — so a slow or lost response is still reflected.
0.6.9
Pressing Enter in an NWC Wallet amount or destination field now runs that action (Generate invoice / Send payment) instead of saving the settings tab.
0.6.8
The disposable wallet lifetime countdown now zero-pads its units (e.g. “02h 09m 05s”) for a steady clock-style readout.
0.6.7
Moved the “Create disposable wallet” button to sit directly below the “Disposable wallet service (lncurl)” field.
0.6.6
Reset the NWC Wallet Receive/Withdraw section whenever you toggle it, so reopening always starts fresh (no stale invoice or half-filled form).
0.6.5
The NWC Wallet “Receive” flow now detects the incoming payment (via wallet notifications, with a polling fallback), shows a “Payment received” message, refreshes the balance, and closes the invoice section automatically.
0.6.4
Moved “Show connection string” to a smaller button in the top-right of the NWC wallet panel; the secret warning now appears with the revealed string.
0.6.3
Add a “Create disposable wallet” button to the NWC Proxy tab to provision a fresh proxy wallet on demand (archiving the current one).
Show a live countdown of when a disposable proxy wallet will run dry, based on its balance and the ~1 sat/hour lncurl upkeep.
0.6.2
Removed the “Auto-replace dead wallet” setting. Disposable proxy wallets are now always replaced automatically when they die — that is the point of disposable mode.
0.6.1
Maintenance release: internal release packaging and documentation only. No functional changes to the plugin.
0.6.0
New Receiver section with a single mode selector: Lightning Address, Lightning Address via NWC Proxy, or NWC. The page adapts to the chosen mode.
NWC mode lets you receive into your own NWC wallet by pasting a connection string, with a live balance shown in the Receiver section.
Lightning Address via NWC Proxy keeps the managed proxy wallet (Disposable or Permanent) on its own NWC Wallet tab, and forwards each payment to your Lightning Address.
When a Lightning Address can confirm neither LUD-21 nor NIP-57, an alert prompts you to switch to NWC Proxy mode.
Existing installs migrate automatically (the old proxy becomes NWC Proxy mode).
0.5.0
Choose your settlement method explicitly: Lightning Address (paid directly, confirmed via LUD-21 or NIP-57) or NWC wallet (paid into a Nostr Wallet Connect wallet you control).
NWC wallet payments now stay in the wallet by default. The previous “proxy” behaviour is kept as an optional Forward to Lightning Address toggle (with the same routing reserve and idempotent forwarding).
Removed the implicit, automatic LA→NWC fallback and the duplicate “Use NWC Proxy” checkbox — the method is now a single, clear choice.
Existing installs are migrated automatically: the old NWC proxy maps to NWC mode with forwarding enabled; everything else maps to Lightning Address mode.
0.4.13
Add a “Show connection string” button to the proxy wallet panel to reveal the current NWC connection string (disposable or permanent) for importing the wallet into another app. The string is fetched on demand for the administrator only, never rendered into the page, and carries a “keep it private” warning.
0.4.12
Fix proxy forwards that settled but were left stuck on “pending” (and could be sent a second time on retry) when the wallet’s pay response was lost in transit. The forward invoice is now stored before paying and reconciled via lookup_invoice, making forwarding idempotent.
Show the routing fee paid alongside the reserve kept in the forward order note.
0.4.11
Add a “Show” button to each proxy transaction that opens a detail view with the received (proxy) and sent (forward) invoice details: amounts, payment hash, preimages, and invoices.
0.4.10
Attach a “Proxied from Woocommerce #” comment (LUD-12) to forwarded NWC proxy payments, when the destination Lightning Address accepts comments.
0.4.9
When the NWC proxy wallet is enabled, route every payment through it — even when the Lightning Address supports LUD-21 or NIP-57. Turn it off to settle directly through the address again.
0.4.8
Add a proxy transactions list on the NWC tab: the latest 5 payments received through the proxy with their forwarding status to your Lightning Address and a payment proof (preimage), plus a “Show all” button that opens a paginated modal.
0.4.7
Add a “Regenerate NWC connection” button on the NWC proxy wallet tab that appears when you change the disposable wallet service (lncurl) URL, provisioning a fresh wallet from the new service.
0.4.6
Move the NIP-57 relay URLs setting to the Advanced tab.
Add a “Use NWC Proxy” toggle on the Lightning Address tab that controls the same setting as the NWC proxy wallet tab.
0.4.5
Fix the LUD-21 status check beside the Lightning Address field: it now confirms the generated invoice actually returns a verify URL, instead of reporting LUD-21 as supported for any address that can create an invoice.
0.4.4
Show the compatible-wallets list directly on the Lightning Address tab (above the connection status) instead of behind a button and modal.
0.4.3
Link each wallet in the compatible-wallets picker to its website, and add a link to lightningaddress.com for the full list of Lightning Address wallets and services.
0.4.2
Add a “compatible wallets” picker on the Lightning Address tab: a modal listing popular wallets that give customers a Lightning Address, with logos.
Add a proxy wallet panel on the NWC tab: a live balance (updated from NWC notifications), a Receive control that generates an invoice, and a Withdraw control that pays a Lightning Address or BOLT11 invoice. All wallet operations run server-side; the connection secret is never exposed to the browser.
0.4.1
Reorganise the payment gateway settings into tabs (Checkout, Lightning Address, NWC proxy wallet, Pricing & rates, Advanced) for a clearer setup, with the NWC fields revealing based on the selected mode.
0.4.0
NWC proxy wallets can now be managed automatically. In the new Disposable mode the plugin creates a throwaway NWC wallet on demand from an lncurl service (default https://lncurl.lol), reuses it across orders, and provisions a replacement when it dies (optional, behind a toggle).
Permanent mode keeps the previous behaviour: a fixed connection string you provide that is never auto-replaced. Existing setups upgrade to Permanent mode automatically.
Show the proxy wallet balance and mode on the payment gateway settings page.
Per-order settlement and forwarding always target the exact wallet an order was invoiced on, even after the active disposable wallet has rotated.
Connection secrets are kept server-side in dedicated storage and are never written to the settings form, order data, or the browser.
Update the bundled Spanish (es_AR, es_ES) translations for the new strings.
0.3.0
Add an optional NWC (Nostr Wallet Connect, NIP-47) proxy wallet as a third settlement method for Lightning Addresses that support neither LUD-21 verification nor NIP-57 zap receipts.
When enabled, the plugin invoices a disposable NWC wallet, confirms the payment over the wallet connection (and via the cron re-check), marks the order paid, then forwards the funds to your merchant Lightning Address keeping a routing reserve of 1% or 10 sats, whichever is larger.
The browser subscribes to NIP-47 wallet notifications to detect payment faster; the connection secret is kept on the server and never exposed to customers.
Forwarding is idempotent and retried by cron, with an attempt cap and an admin note when manual intervention is needed, so a settled order is never left un-paid.
Hide the payment gateway when a configured Lightning Address has no usable settlement method (no LUD-21, no NIP-57, and no NWC proxy).
Update the bundled Spanish (es_AR, es_ES) translations for the new strings.
0.2.2
Update the bundled Spanish (es_AR, es_ES) translations to cover the new gateway, discovery, and NIP-57 strings.
0.2.1
Document the Yadio exchange-rate service with links to its Terms of Service and Privacy Policy.
0.2.0
Add live LUD-16, LUD-21 and NIP-57 checks beside the merchant Lightning Address field, each with a status icon.
Accept Lightning Addresses that do not support LUD-21: settlement is confirmed from signed NIP-57 zap receipts (at checkout and via the cron re-check), with BIP-340 signature verification so only genuine receipts can settle an order.
Show the connected gateway name and domain on the discovery settings page, and warn when the gateway domain does not match your site.
Refresh the discovery settings copy and rename the Settings menu entry to “Lightning by LaWallet”.
0.1.7
Refresh the plugin directory icon (new lightning mark with a subtle Bitcoin watermark).
0.1.6
Rename the plugin to “Accept Bitcoin with your Lightning Address” and update the short description.
0.1.5
Set the Contributors field to the plugin owner’s WordPress.org account (magollo).
Expand the Yadio external-service disclosure: clarify the optional, currency-code-only request, the manual-rate opt-out, and the available Yadio documentation.
0.1.4
Add a GitHub-based self-updater so installs distributed outside the WordPress.org directory can update from the project’s GitHub Releases. Self-disables when the plugin is hosted on WordPress.org.
0.1.3
Point the Plugin URI to the project site (wordpress.lawallet.io).
0.1.2
Enqueue the settings-page CSS and JavaScript instead of printing them inline.
Expand the Yadio external service documentation and load translations on the init hook.
Set the plugin Contributors to agustinkassis.
0.1.1
Improve Lightning payment page rate display with locked Yadio conversion snapshots and BTC/SAT display options.
Polish checkout/payment controls, including WebLN loading states, paid-state disabling, and fallback wallet visibility.
Add a Bitcoin icon to the WooCommerce LaWallet payment method option.
0.1.0
Initial release: WooCommerce Lightning gateway (LNURL-pay + LUD-21 verification, WebLN and
NIP-57 zap receipt detection, Yadio fiat conversion) and Lightning Address / NIP-05 discovery
redirects to a LaWallet gateway.
