openreceive-server 0.4.4 → 0.4.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: '08bf7311603d77400f63f99b2ac15650105a25fdeb21ac3f38f8cf2df243f394'
-  data.tar.gz: 07ff30f8eab72b50544bc4022135dcf9a4d1e80e28e5062ccb22793bf01222fc
+  metadata.gz: e2a6f6628a84d20dca3757b9017ba6e40c0fac41e016257e988173533be5d650
+  data.tar.gz: 5d9fd1babd45564b31274141c2af4875a339cb21d7fef33997442e6b39b1ee44
 SHA512:
-  metadata.gz: 1f3aa5d0622a47af6f2b0d1f40866f2763359564875cbfa7299781e840ee6a503e0e8bae78ce8d8825545f49d19c7c1a8a047b35780368410df65818ec8da3af
-  data.tar.gz: b7012062378dcbc8da84cd8ed9488c1e9efff9a0e54abd9580e5093cb38617b35760073d0748b1737807364299a3217ed86ad715f8cb8a70cc78ce678bddc501
+  metadata.gz: da0988ee975768e373de725c7417c821df8c46d159186e0993ee3b3273f658c54622e21410c7b46baf6b65892155d9c8b29e7343145b83bffc6580a7e453cd42
+  data.tar.gz: fb1518e4924dfb4dab17b32178f056ac78a80d849ca6d4e97502da653189e2411e3115167dd14669c7c1800195c31f2d1ffa04f4abb9d2982773d7c662bc31f8

data/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 0.4.6 - 2026-09-11
+
+Refresh installation and quickstart documentation and package metadata.
+Release in lockstep with openreceive 0.4.6, including the live-price request fix
+that removes obsolete VEF. No server adapter API change.
+
+## 0.4.5 - 2026-09-07
+
+Release in lockstep with the Python/PHP publishing workflow fixes and complete
+WooCommerce integration documentation. Shared HTTP golden fixtures now use
+the canonical placeholder definitions. No Ruby public API change.
+
 ## 0.4.4 - 2026-09-07
 
 Version lockstep with the 0.4.4 npm release (every checkout image now ships

data/README.md

@@ -1,6 +1,41 @@
 # openreceive-server
 
-Storage-free Ruby service and Rack handler. Configure a receive-only NWC client. The host
+**Accept Bitcoin Lightning payments in Ruby and Rack. Your app, your wallet.**
+
+[OpenReceive](https://openreceive.org) brings Lightning checkout to your existing
+Ruby application. Receive payments directly into a wallet you control, while
+keeping your orders, prices, and fulfillment in your own code.
+
+OpenReceive supports optional swaps from **USDT, USDC, SOL, and ETH** through
+a configured swap provider. The provider converts the payment to **BTC over
+Lightning**, which settles into the merchant's connected wallet. Available
+assets and networks depend on the provider; swaps are optional.
+
+- Create invoices and check payments through a receive-only Nostr Wallet
+  Connect (NWC) client.
+- Use the payment service directly or mount the framework-agnostic Rack handler.
+- Reconcile pending payments with shared settlement rules and exact money math.
+- Keep your existing persistence stack, with no separate OpenReceive service
+  or database to deploy.
+
+**Building with Rails?** Start with
+[`openreceive-rails`](https://github.com/OpenReceive/openreceive/blob/master/packages/ruby/openreceive-rails/README.md): it adds payment storage,
+reconciliation, and an install generator on top of this gem.
+
+## Install
+
+Requires Ruby 3.2 or later. Add to your Gemfile and run `bundle install`:
+
+```ruby
+gem "openreceive-server"
+```
+
+For a custom integration, provide your NWC client, payment repository, and
+application hooks. The service itself has no persistence dependency.
+
+## Connect your application
+
+Configure a receive-only NWC client. The host
 authorizes requests, resolves order amounts, commits payment hashes before responding, and
 consumes at-least-once verified payment events by hash. The service refuses to start when the
 NWC connection advertises spend methods (`pay_invoice`, `multi_pay_invoice`,
@@ -46,3 +81,12 @@ they store to `service.reconcile_payments({ attempts:, max_pages:, deadline: })`
 and apply the per-hash results through `on_paid` — `RackApp` deliberately has
 no built-in hook, and the durable-gate convenience (`OpenReceive.maybe_reconcile!`)
 ships only with the Rails engine.
+
+## Links
+
+- API reference: [Ruby and Rails APIs](https://github.com/OpenReceive/openreceive/blob/master/docs/guides/api-reference.md)
+- Rails quickstart: [Use the engine with built-in persistence](https://github.com/OpenReceive/openreceive/blob/master/docs/guides/quickstart-rails.md)
+- Source and issues: <https://github.com/openreceive/openreceive>
+- Changelog: [CHANGELOG.md](CHANGELOG.md)
+
+MIT license.

data/lib/openreceive/server/version.rb

@@ -2,6 +2,6 @@
 
 module OpenReceive
   module Server
-    VERSION = "0.4.4"
+    VERSION = "0.4.6"
   end
 end

data/skills/integrate-openreceive/SKILL.md

@@ -30,6 +30,7 @@ code** (`NWC_URI`).
    - Rails: [references/rails.md](references/rails.md)
    - Django: [references/django.md](references/django.md)
    - Laravel: [references/laravel.md](references/laravel.md)
+   - WordPress + WooCommerce: [references/woocommerce.md](references/woocommerce.md) — the packaged gateway and merchant settings.
    - BTCPay Server: [references/btcpay.md](references/btcpay.md) — a plugin,
      configured in BTCPay's store UI or Greenfield API; no application code,
      no npm packages, no gem. The rest of this file is about the library.

data/skills/integrate-openreceive/references/btcpay.md

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (BTCPay Server)
 
-These directions describe OpenReceive 0.4.4.
+These directions describe OpenReceive 0.4.6.
 
 Connect a BTCPay Server store to a receive-only NWC wallet with the OpenReceive
 plugin, and optionally let payers pay BTCPay invoices with USDT, USDC, ETH or

data/skills/integrate-openreceive/references/django.md

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (Django)
 
-These directions describe OpenReceive 0.4.4.
+These directions describe OpenReceive 0.4.6.
 
 Add OpenReceive to a Django project — the app you are already working in. You
 do not need a copy of the OpenReceive source: the Python package is on PyPI

data/skills/integrate-openreceive/references/fastapi.md

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (FastAPI)
 
-These directions describe OpenReceive 0.4.4.
+These directions describe OpenReceive 0.4.6.
 
 Add OpenReceive to a FastAPI application — the app you are already working in.
 You do not need a copy of the OpenReceive source: the engine is on PyPI

data/skills/integrate-openreceive/references/fastify.md

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (Fastify)
 
-These directions describe OpenReceive 0.4.4.
+These directions describe OpenReceive 0.4.6.
 
 Add OpenReceive to a Fastify application — the app you are already working in.
 You do not need a copy of the OpenReceive source: the packages are on npm, and

data/skills/integrate-openreceive/references/laravel.md

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (Laravel)
 
-These directions describe OpenReceive 0.4.4.
+These directions describe OpenReceive 0.4.6.
 
 Add OpenReceive to a Laravel application — the app you are already working in.
 You do not need a copy of the OpenReceive source: the package is on Packagist

data/skills/integrate-openreceive/references/next.md

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (Next.js)
 
-These directions describe OpenReceive 0.4.4.
+These directions describe OpenReceive 0.4.6.
 
 Add OpenReceive to a Next.js App Router application — the app you are already
 working in. You do not need a copy of the OpenReceive source: the packages are

data/skills/integrate-openreceive/references/node.md

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (Node.js)
 
-These directions describe OpenReceive 0.4.4.
+These directions describe OpenReceive 0.4.6.
 
 Add OpenReceive to a Node application — the app you are already working in. You
 do not need a copy of the OpenReceive source: the packages are on npm, and the

data/skills/integrate-openreceive/references/php.md

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (PHP)
 
-These directions describe OpenReceive 0.4.4.
+These directions describe OpenReceive 0.4.6.
 
 Add OpenReceive to a PHP application — the app you are already working in. You
 do not need a copy of the OpenReceive source: the engine is on Packagist

data/skills/integrate-openreceive/references/rails.md

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (Rails)
 
-These directions describe OpenReceive 0.4.4.
+These directions describe OpenReceive 0.4.6.
 
 Add OpenReceive to a Rails application — the app you are already working in. You
 do not need a copy of the OpenReceive source: the gem is on RubyGems, the

data/skills/integrate-openreceive/references/woocommerce.md

@@ -0,0 +1,176 @@
+# OpenReceive agent directions (WordPress + WooCommerce)
+
+These directions describe OpenReceive 0.4.6.
+
+Install and configure the OpenReceive gateway in the existing WooCommerce
+store. Preserve its theme, checkout, customer accounts, order model and prices.
+The plugin bundles the PHP engine and checkout assets; the merchant does not
+install npm or Composer packages on the WordPress server.
+
+## Step 0 — inspect configuration
+
+Check WordPress, WooCommerce and PHP versions, GMP and sodium availability,
+whether the plugin is installed, and whether the Doctor panel reports the
+receive-only NWC credential as set. Never display its value. For a real store,
+ask the merchant to configure a receive-only wallet if none is available.
+For repository development, use the Docker demo's explicit testkit override.
+
+Upload a built plugin archive, not a zip of the source directory. The plugin
+has not yet been accepted into the WordPress.org directory. Configuration and
+the complete quickstart follow below.
+
+The plugin owns only its payment-attempt tables in the WordPress database.
+WooCommerce owns orders, totals, stock and email. Do not add an external
+idempotency store, payment database, browser wallet credentials or custom
+fulfillment implementation. Guest return links use WooCommerce's order key;
+the plugin verifies it before issuing an expiring order-bound cookie.
+
+Run `wp openreceive doctor` after configuration. Use the documented scheduled
+reconciliation or optional notifications command for offline settlement.
+Manual merchant refunds and provider-managed payer swap refunds are separate
+flows; a receive-only NWC wallet cannot send payments.
+
+## Further reading
+
+- [Express Quickstart (Node)](https://openreceive.org/guides/quickstart-node.md)
+- [Fastify Quickstart](https://openreceive.org/guides/quickstart-fastify.md)
+- [FastAPI Quickstart](https://openreceive.org/guides/quickstart-fastapi.md)
+- [Django Quickstart](https://openreceive.org/guides/quickstart-django.md)
+- [Next.js Quickstart](https://openreceive.org/guides/quickstart-next.md)
+- [Rails Quickstart](https://openreceive.org/guides/quickstart-rails.md)
+- [PHP Quickstart (plain PHP)](https://openreceive.org/guides/quickstart-php.md)
+- [Laravel Quickstart](https://openreceive.org/guides/quickstart-laravel.md)
+- [BTCPay Server Quickstart](https://openreceive.org/guides/quickstart-btcpay.md)
+- [BTCPay Plugin Reference](https://openreceive.org/guides/btcpay-reference.md)
+- [Node ORM Recipes](https://openreceive.org/guides/node-orms.md)
+- [Authorization](https://openreceive.org/guides/authorization.md)
+- [Rate Limiting](https://openreceive.org/guides/rate-limiting.md)
+- [Frontend Checkout](https://openreceive.org/guides/frontend-checkout.md)
+- [Checkout UX](https://openreceive.org/guides/checkout-ux.md)
+- [Headless Checkout](https://openreceive.org/guides/headless-checkout.md)
+- [Automated Swaps](https://openreceive.org/guides/automated-swaps.md)
+- [Swap Refunds](https://openreceive.org/guides/swap-refunds.md)
+- [Lightning Swap Connect URI](https://openreceive.org/guides/lightning-swap-connect.md)
+- [Environment Variables](https://openreceive.org/guides/environment-variables.md)
+- [Payment Storage](https://openreceive.org/guides/storage.md)
+- [Deploying OpenReceive](https://openreceive.org/guides/deploying.md)
+- [Testing Your OpenReceive Integration](https://openreceive.org/guides/host-testing.md)
+- [API Reference](https://openreceive.org/guides/api-reference.md)
+- [Security](https://openreceive.org/guides/security.md)
+- [Provider Registry](https://openreceive.org/guides/provider-registry.md)
+- [Price Feeds](https://openreceive.org/guides/price-feeds.md)
+- [React Material UI Recipe](https://openreceive.org/guides/react-material-ui-recipe.md)
+- [Flask Recipe](https://openreceive.org/guides/flask-recipe.md)
+- [Writing Your Own Checkout Route](https://openreceive.org/guides/custom-checkout-route.md)
+- [Agent Directions: Node.js](https://openreceive.org/guides/agent-directions-node.md)
+- [Agent Directions: Fastify](https://openreceive.org/guides/agent-directions-fastify.md)
+- [Agent Directions: FastAPI](https://openreceive.org/guides/agent-directions-fastapi.md)
+- [Agent Directions: Django](https://openreceive.org/guides/agent-directions-django.md)
+- [Agent Directions: Next.js](https://openreceive.org/guides/agent-directions-next.md)
+- [Agent Directions: Rails](https://openreceive.org/guides/agent-directions-rails.md)
+- [Agent Directions: PHP](https://openreceive.org/guides/agent-directions-php.md)
+- [Agent Directions: Laravel](https://openreceive.org/guides/agent-directions-laravel.md)
+- [Agent Directions: BTCPay Server](https://openreceive.org/guides/agent-directions-btcpay.md)
+- [WordPress + WooCommerce Quickstart](https://openreceive.org/guides/quickstart-woocommerce.md)
+
+---
+
+## The quickstart, in full
+
+Inlined verbatim so this file needs no network access — follow it once Step 0
+passes. The page it comes from is https://openreceive.org/guides/quickstart-woocommerce.
+
+## WordPress + WooCommerce quickstart
+
+Install the built OpenReceive plugin zip through **Plugins → Add New → Upload
+Plugin**, with WooCommerce already active. The source directory needs a build;
+it cannot be uploaded as-is. WordPress.org submission is still pending.
+
+Requirements: WordPress 6.6+, WooCommerce 9+, 64-bit PHP 8.2+ with GMP and sodium,
+and MySQL 8 or MariaDB 10.5+. Activation creates payment-attempt tables in the
+existing WordPress database. No separate database or application is required.
+
+### Get the installable archive
+
+Use `openreceive-wordpress-<version>.zip` from the selected
+[OpenReceive GitHub release](https://github.com/OpenReceive/openreceive/releases)
+when that asset is listed. A GitHub source-code zip is not the plugin archive.
+If the release does not yet provide a built zip, build it on a development
+machine with Node 22+, PHP 8.2+, Composer and WP-CLI:
+
+```sh
+git clone https://github.com/OpenReceive/openreceive.git
+cd openreceive
+git checkout <release-tag>
+npm ci
+npm run build:packages
+composer install --working-dir=packages/php/wordpress
+npm run release:wordpress:build
+```
+
+Upload the resulting `dist/openreceive-wordpress-<version>.zip`. WP-CLI must be
+on `PATH`, or set `OPENRECEIVE_WP_CLI` to the absolute path of its phar. The
+WordPress server needs neither Node nor Composer: dependencies and checkout
+assets are bundled inside the built plugin.
+
+### Configure the wallet
+
+Open **WooCommerce → Settings → Payments → OpenReceive**. Enter a receive-only
+NWC code, save, then enable the gateway. Saving verifies receive permissions
+and fails closed on a spend-capable wallet unless the explicit override is set.
+The password fields never show saved credentials. Values are encrypted using
+keys derived from WordPress's authentication keys; re-enter them after rotating
+those keys.
+
+For managed deployments, configure `OPENRECEIVE_NWC_URI` in `wp-config.php` from
+your server's secret environment. It takes precedence over the settings field.
+Optional `OPENRECEIVE_LSC_URI_PRIMARY` and `OPENRECEIVE_LSC_URI_BACKUP` constants
+configure swap providers. Never put these values in browser code or logs.
+
+### Checkout and settlement
+
+Both WooCommerce checkout blocks and classic checkout redirect to the order-pay
+page. The plugin reads the amount from `WC_Order`, serves the bundled checkout,
+and authorizes the customer through their account, checkout session or an
+expiring signed cookie issued after verifying the order-pay key. Keep that
+order-pay URL available to customers returning to a pending payment or swap
+refund. The plugin verifies that each requested payment hash belongs to the order.
+
+Payment attempts persist before invoice instructions appear. Settlement commits
+once in the payment transaction. WooCommerce's `payment_complete` then handles
+status, stock and emails. A durable order marker lets subsequent requests and
+scheduled passes repair an interruption between settlement and order completion.
+
+The checkout polling drives opportunistic reconciliation through the PHP
+engine's shared database gate. Action Scheduler adds a recurring one-minute
+safety net. Configure a system cron to run WordPress scheduled work on stores
+with little traffic; no page visits means WP-Cron alone cannot guarantee prompt
+settlement. Optional process-manager commands:
+
+```sh
+wp openreceive doctor
+wp openreceive reconcile
+wp openreceive notifications
+```
+
+The notifications command runs as a separate process. The Doctor panel in the
+gateway settings reports schema, credential presence, scheduling and attention
+orders. A currency without a usable price feed makes the gateway unavailable.
+
+### Refunds and removal
+
+The receive-only wallet cannot send merchant refunds. Make those manually from
+your wallet. Payer swap refunds use the configured provider through the same
+authorized order-pay page; enabling LSC payments commits the shop to keeping
+that recovery path available. See [swap refunds](https://openreceive.org/guides/swap-refunds.md).
+
+Deactivation preserves payment records. Deleting the plugin drops its two
+tables only if **Remove data on uninstall** was enabled. WooCommerce orders are
+retained.
+
+### Local example
+
+The repository's `examples/wordpress` Docker stack builds the plugin and seeds
+WooCommerce from the shared button catalog. Run `npm run demo wordpress` for
+the real-wallet mode, or use its documented `compose.testkit.yml` override for
+a disposable fake-wallet shop. No testkit routes are registered by default.

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: openreceive-server
 version: !ruby/object:Gem::Version
-  version: 0.4.4
+  version: 0.4.6
 platform: ruby
 authors:
 - OpenReceive
@@ -15,18 +15,27 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 0.4.4
+        version: 0.4.6
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 0.4.4
-description: 'Server building blocks for OpenReceive: a storage-free Service that
-  mirrors the Node engine and a framework-agnostic Rack app implementing the shipped
-  HTTP routes while the host owns order and payment persistence. Receive-only: it
-  never exposes a spend path and the NWC secret never leaves the server.'
+        version: 0.4.6
+description: |
+  Accept Bitcoin Lightning payments directly into a wallet you control, from your
+  Ruby or Rack application. OpenReceive provides invoice creation, payment checks,
+  and settlement reconciliation through a receive-only Nostr Wallet Connect
+  (NWC) client. Optional swaps let customers pay with USDT, USDC, SOL, and ETH
+  through a configured provider; you receive BTC over Lightning in your wallet.
+  Available assets and networks depend on the provider.
+
+  Bring your own wallet client, authorization, and payment persistence. The service
+  and Rack handler fit into your existing application, with no separate OpenReceive
+  service or database to deploy. Your app keeps control of orders, prices, and
+  fulfillment; wallet credentials stay on the server. Rails developers can use
+  openreceive-rails for built-in payment storage and reconciliation.
 email:
 - info@openreceive.org
 executables: []
@@ -64,6 +73,7 @@ files:
 - skills/integrate-openreceive/references/node.md
 - skills/integrate-openreceive/references/php.md
 - skills/integrate-openreceive/references/rails.md
+- skills/integrate-openreceive/references/woocommerce.md
 homepage: https://openreceive.org
 licenses:
 - MIT
@@ -72,7 +82,7 @@ metadata:
   source_code_uri: https://github.com/openreceive/openreceive
   changelog_uri: https://github.com/openreceive/openreceive/blob/master/packages/ruby/openreceive-server/CHANGELOG.md
   bug_tracker_uri: https://github.com/openreceive/openreceive/issues
-  documentation_uri: https://rubydoc.info/gems/openreceive-server
+  documentation_uri: https://github.com/openreceive/openreceive/blob/master/packages/ruby/openreceive-server/README.md
   rubygems_mfa_required: 'true'
 rdoc_options: []
 require_paths:
@@ -90,5 +100,5 @@ required_rubygems_version: !ruby/object:Gem::Requirement
 requirements: []
 rubygems_version: 3.6.9
 specification_version: 4
-summary: Storage-free OpenReceive receive-only service and HTTP routes for Ruby.
+summary: Accept Bitcoin Lightning payments in Ruby and Rack. Your app, your wallet.
 test_files: []