openreceive 0.4.28 → 0.4.30

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 8c198777522ede161b4aa74adfbc59ba1602b12f4796da961a525c1712cc39a9
-  data.tar.gz: d0a7f92203bda702712fa5168defa22771837c3d25b367e11918baacf564abbe
+  metadata.gz: c10eb99c4f0e844372ad4d7118fd0bf31709ff8057ab866fadd620709d5cf473
+  data.tar.gz: '0665926238910589002659373b4d87d9f246d65347aa26dbdbb46e03851a920e'
 SHA512:
-  metadata.gz: 30e0688e93e66f04e1c01950f889a9f1506de5d687a6596664da8d657932d35179594ef961933794b4ecb4923922ae7a6f5a00a4fc14ef4b0530ffb95c71462a
-  data.tar.gz: c59517260edb75d6b4289d10317a9105971bfb731a46e7e3b7c682efa80a2b54629c7166d0c9890b1993c5e60e85f0e33ac7270cef2f242e84ab6210184b0fe4
+  metadata.gz: 690edbd738078a7e70f542b55b62d1df8580407ea565ff1a01a77d697a0c9e4a71a87136546618758339ba33921377f3bddc48895b21fd37b4d2ec4679e19f27
+  data.tar.gz: e73bfa44e4ece6112a97221fccae50703abce4b1549ca3326c3ad6f4ff1e2962902e1d1485d3b4982cfbaba89a59e59935a54eb2f906ab0b9870b6e9f916a695

data/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 0.4.30 - 2026-10-19
+
+Release with the complete 0.4.30 package family. The bundled agent skill adds the
+PrestaShop, Odoo and Vendure references and the guide corrections from a review of
+openreceive.org. No Ruby runtime changes from 0.4.29.
+
+## 0.4.29 - 2026-10-19
+
+Release with the complete 0.4.29 package family. The bundled agent skill's
+FOSSBilling reference covers the extension directory install. No Ruby runtime
+changes from 0.4.28.
+
 ## 0.4.28 - 2026-10-18
 
 Release with the complete 0.4.28 package family. The bundled agent skill adds

data/lib/openreceive/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module OpenReceive
-  VERSION = "0.4.28"
+  VERSION = "0.4.30"
 end

data/skills/integrate-openreceive/SKILL.md

@@ -6,7 +6,7 @@ description: >
   SvelteKit, Nuxt, Astro, React Router, TanStack Start, Rails,
   Python, Django, FastAPI, Flask, Laravel, plain PHP, WordPress/WooCommerce,
   Easy Digital Downloads,
-  Paymenter, FOSSBilling, Medusa, Lovable, Bolt, Supabase, React, Vue, Svelte, Angular, or plain HTML applications,
+  Paymenter, FOSSBilling, PrestaShop, Odoo, Medusa, Vendure, Lovable, Bolt, Supabase, React, Vue, Svelte, Angular, or plain HTML applications,
   mobile apps (React Native, Expo, Flutter, Swift, Kotlin) through their
   server, or connecting BTCPay Server to a receive-only NWC wallet. A configured swap provider
   converts these payments to BTC over Lightning in the merchant's connected
@@ -59,9 +59,18 @@ connected wallet; asset and network availability depends on the provider.
    - FOSSBilling: [references/fossbilling.md](references/fossbilling.md) — a
      module and payment gateway from the GitHub release, configured with
      console commands; no Composer or npm packages.
+   - PrestaShop: [references/prestashop.md](references/prestashop.md) — a
+     payment module from the GitHub release, configured with bin/console
+     commands; no Composer or npm packages.
+   - Odoo: [references/odoo.md](references/odoo.md) — a payment provider module
+     from the GitHub release and the `openreceive` package from PyPI,
+     configured with `odoo openreceive` commands.
    - Medusa: [references/medusa.md](references/medusa.md) — the
      `@openreceive/medusa` plugin and payment provider in the Medusa server,
      and the React checkout in the storefront; no hooks to write.
+   - Vendure: [references/vendure.md](references/vendure.md) — the
+     `@openreceive/vendure` plugin and payment method handler in the Vendure
+     server, and the React checkout in the storefront; no hooks to write.
    - Lovable (TanStack Start on Cloudflare Workers, with Supabase):
      [references/lovable.md](references/lovable.md) — no terminal; codes are
      Lovable secrets and payments go through Supabase's HTTPS API.

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

@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/astro/full.md
 - Do not suggest rotating or revoking a code because it was pasted here.
 - Start the quickstart only once the NWC code is saved, and the LSC code is saved or the user said "Bitcoin only".
 
-These directions describe OpenReceive 0.4.28.
+These directions describe OpenReceive 0.4.30.
 
 Add OpenReceive to an Astro site — the one you are already working in, on
 `@astrojs/node`. OpenReceive ships no Astro package: the integration is one
@@ -434,13 +434,12 @@ enough; drop the `.md` for the same page a person would read.
 - https://openreceive.org/guides/custom-checkout-route.md — advanced: replacing the shipped adapter's routes with your own
 - https://openreceive.org/guides/react-material-ui-recipe.md — a worked custom UI on a component library
 - https://openreceive.org/guides/quickstart-next.md — each hook explained step by step, on Next.js; they are the same here
+- https://openreceive.org/guides/payment-safety-upgrade.md — coordinated upgrades and reviewed repair of existing attempts
 - https://openreceive.org/guides.md — the index, if what you need is not above
 
 Questions, or a problem with the library itself:
 https://openreceive.org/contact
 
-- https://openreceive.org/guides/payment-safety-upgrade.md — coordinated upgrades and reviewed repair of existing attempts
-
 ---
 
 ## The quickstart, in full
@@ -481,7 +480,7 @@ On Node, with `@astrojs/node`. The payment route and the checkout page render
 on demand (`prerender = false`); the rest of the site can stay static. The
 wallet connection and your database driver need Node, so the route cannot run
 on an edge runtime. The Vercel and Netlify adapters deploy Node functions:
-read Bitcoin checkout on serverless hosts first.
+read [Bitcoin checkout on serverless hosts](https://openreceive.org/guides/serverless.md) first.
 For Cloudflare Workers, the [TanStack Start recipe](https://openreceive.org/guides/tanstack-start-recipe.md#where-it-runs)
 explains what a Worker needs. This recipe was not run on those hosts.
 
@@ -572,25 +571,25 @@ export const POST: APIRoute = (context) => handleOpenReceive(context);
 
 `native` is the endpoint's `APIContext`, so `authorize` can check the
 session your app already has: its cookies, or the user your middleware puts
-in `context.locals`. The Next.js quickstart
+in `context.locals`. The [Next.js quickstart](https://openreceive.org/guides/quickstart-next.md)
 explains each hook. They are the same here.
 
 One stack serves the whole server process. Astro's origin check refuses
 cross-site form posts. The checkout sends JSON, which it lets through.
 `clientAddress` is the socket address. Behind your own reverse proxy, list
 your domain in `security.allowedDomains`: Astro then takes the payer's
-address from `x-forwarded-for` (Rate limiting).
+address from `x-forwarded-for` ([Rate limiting](https://openreceive.org/guides/rate-limiting.md)).
 
 ### Your database
 
 `db` is a `pg` Pool, `node:sqlite` or `better-sqlite3`, or one of the
-adapters in Node ORM recipes. With Drizzle, pass
+adapters in [Node ORM recipes](https://openreceive.org/guides/node-orms.md). With Drizzle, pass
 the `pg` Pool underneath it.
 
 Create OpenReceive's two tables with your migrations
 (`npx openreceive scaffold payments --orm <your orm>`), or run
 `paymentsSchemaSql("postgres")` from `@openreceive/http` once. It is
-idempotent. See Payment storage.
+idempotent. See [Payment storage](https://openreceive.org/guides/storage.md).
 
 ### The checkout page
 
@@ -630,7 +629,7 @@ if (!order || order.visitor !== Astro.cookies.get("visitor")?.value) {
 
 The element starts the checkout in the browser. The payer picks Bitcoin and
 gets the invoice. Keep it at the order's own URL: a payer with a swap deposit
-in flight comes back to it (Swap refunds).
+in flight comes back to it ([Swap refunds](https://openreceive.org/guides/swap-refunds.md)).
 
 ### Settings
 

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

@@ -17,7 +17,7 @@ If your fetch tool gave you a summary, fetch that URL again for the full text.
 - Do not suggest rotating or revoking a code because it was pasted here.
 - Start Step 1 only once NWC_URI is saved, and LSC_URI_PRIMARY is saved or the user said "Bitcoin only".
 
-These directions describe OpenReceive 0.4.28.
+These directions describe OpenReceive 0.4.30.
 
 Add OpenReceive to this Bolt app: a Vite React app on Bolt Cloud, with Bolt
 Database or a connected Supabase project as its database, and Supabase Edge
@@ -123,9 +123,11 @@ explicitly declined.
 
 ## Step 1 — the packages
 
-Add `@openreceive/react` at 0.4.28 or newer to the app's
-`package.json`. The function imports `npm:@openreceive/http@^0.4.28`
-and `npm:@supabase/supabase-js@2` directly; add nothing else. No `pg`, no
+Add `@openreceive/react` at 0.4.30 or newer to the app's
+`package.json`. The function imports `npm:@openreceive/http@^0.4.30`
+and `npm:@supabase/supabase-js@2` directly; add nothing else. (The recipe
+below writes `^0.4.27`, the oldest release with the `cors` option; both
+resolve to the newest 0.4.x.) No `pg`, no
 Postgres driver, no OpenReceive scaffold.
 
 ## Step 2 — the migration
@@ -353,7 +355,7 @@ Use `@openreceive/*` 0.4.27 or newer: the function needs the `cors` option.
 
 ### 1. The migration
 
-Save the SQL from Supabase migration,
+Save the SQL from [Supabase migration](https://openreceive.org/guides/supabase-migration.md),
 unchanged, as a new migration (`supabase/migrations/<timestamp>_openreceive.sql`)
 and apply it. It creates OpenReceive's tables with row level security on and
 every grant revoked from `anon` and `authenticated`, and the functions the
@@ -502,7 +504,7 @@ is. OpenReceive never allows credentials across sites, so no cookie reaches
 the function, and a page on any listed origin can only send the tokens it
 holds. `authorize` decides with the token, on every request. Never answer
 these routes with CORS headers of your own, and never remove the token check.
-More: Cross-site requests.
+More: [Cross-site requests](https://openreceive.org/guides/authorization.md#cross-site-requests).
 
 ### 6. The secrets
 
@@ -573,7 +575,7 @@ page, as the payer's receipt.
 OpenReceive's CI runs both storage routes in Supabase's edge-runtime under
 the hosted limits, including a cross-site page with a bearer token. The trial
 harness runs coding agents through a Bolt-shaped shop on a local Supabase
-stack (see How we test platforms). We
+stack (see [How we test platforms](https://openreceive.org/guides/how-we-test-platforms.md)). We
 have not deployed to Supabase's hosted platform: its own API gateway, its
 `verify_jwt` check and its handling of preflights are untested. If something
 there does not work as this recipe says,

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

@@ -13,11 +13,11 @@ curl -fsSL https://openreceive.org/agent-directions/btcpay/full.md
 - Check first: BTCPay Server 2.4.4 or later, and the plugin installed from Plugins → Plugin Directory.
 - Unless the store already uses OpenReceive, stop and ask the user for a receive-only NWC code.
 - Save it via Store → OpenReceive or the Greenfield API, never BTCPay's Lightning node screen. Never echo it.
-- If the user wants USDT, USDC, ETH or SOL, ask for an LSC code too, but do not wait for it.
+- Next ask for the LSC code. If the user wants stablecoins, USDT, USDC, ETH, SOL or crypto, do not ask yes/no first.
 - Never tick the spend-capable override to make a save succeed.
 - Do not suggest rotating or revoking a code because it was pasted here.
 
-These directions describe OpenReceive 0.4.28.
+These directions describe OpenReceive 0.4.30.
 
 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
@@ -196,13 +196,12 @@ enough; drop the `.md` for the same page a person would read.
 - https://openreceive.org/guides/lightning-swap-connect.md — what an LSC code actually is
 - https://openreceive.org/guides/automated-swaps.md — provider states, and what turning swaps on commits a merchant to
 - https://openreceive.org/guides/swap-refunds.md — the refund states; the route back is BTCPay's own invoice checkout page here
+- https://openreceive.org/guides/payment-safety-upgrade.md — coordinated upgrades and reviewed repair of existing attempts
 - https://openreceive.org/guides.md — the index, if what you need is not above
 
 Questions, or a problem with the plugin itself:
 https://openreceive.org/contact
 
-- https://openreceive.org/guides/payment-safety-upgrade.md — coordinated upgrades and reviewed repair of existing attempts
-
 ---
 
 ## The quickstart, in full

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

@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/django/full.md
 - Do not suggest rotating or revoking a code because it was pasted here.
 - Start the quickstart only once the NWC code is saved, and the LSC code is saved or the user said "Bitcoin only".
 
-These directions describe OpenReceive 0.4.28.
+These directions describe OpenReceive 0.4.30.
 
 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
@@ -442,13 +442,12 @@ enough; drop the `.md` for the same page a person would read.
 - https://openreceive.org/guides/custom-checkout-route.md — advanced: replacing the mounted engine's routes with your own
 - https://openreceive.org/guides/react-material-ui-recipe.md — a worked custom UI on a component library
 - https://openreceive.org/agent-directions/flask.md — the same engine as a Flask Blueprint: follow those directions instead if this app is Flask after all
+- https://openreceive.org/guides/payment-safety-upgrade.md — coordinated upgrades and reviewed repair of existing attempts
 - https://openreceive.org/guides.md — the index, if what you need is not above
 
 Questions, or a problem with the library itself:
 https://openreceive.org/contact
 
-- https://openreceive.org/guides/payment-safety-upgrade.md — coordinated upgrades and reviewed repair of existing attempts
-
 ---
 
 ## The quickstart, in full

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

@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/edd/full.md
 - Do not suggest rotating or revoking a code because it was pasted here.
 - Setup is done only when the NWC code is saved, and the LSC code is saved or the user said "Bitcoin only".
 
-These directions describe OpenReceive 0.4.28.
+These directions describe OpenReceive 0.4.30.
 
 Install and configure the OpenReceive payment gateway in the Easy Digital
 Downloads (EDD) store you are working in. Preserve its theme, checkout,
@@ -96,7 +96,7 @@ is saved or the user said "Bitcoin only". Never invent a placeholder code.
 Install this release from the WordPress.org plugin directory:
 
 ```sh
-wp plugin install openreceive --version=0.4.28 --activate
+wp plugin install openreceive --version=0.4.30 --activate
 ```
 
 If that fails because WordPress.org does not have this version yet, install
@@ -104,7 +104,7 @@ the ZIP attached to the same GitHub release. Never install the GitHub
 source-code ZIP or a ZIP from an older release:
 
 ```sh
-wp plugin install https://github.com/OpenReceive/openreceive/releases/download/v0.4.28/openreceive-wordpress-0.4.28.zip --activate
+wp plugin install https://github.com/OpenReceive/openreceive/releases/download/v0.4.30/openreceive-wordpress-0.4.30.zip --activate
 ```
 
 It needs Easy Digital Downloads active, and PHP 8.2+ with GMP and sodium in
@@ -222,7 +222,6 @@ question.
 - [Lightning Swap Connect URI](https://openreceive.org/guides/lightning-swap-connect.md)
 - [Security](https://openreceive.org/guides/security.md)
 - [Price Feeds](https://openreceive.org/guides/price-feeds.md)
-- [Payment Safety Upgrade](https://openreceive.org/guides/payment-safety-upgrade.md)
 
 ---
 
@@ -258,7 +257,7 @@ activate it. With WP-CLI, run `wp plugin install openreceive --activate`.
 
 Each GitHub release also attaches the plugin as a ZIP, for a site that cannot
 reach WordPress.org:
-[openreceive-wordpress-0.4.28.zip](https://github.com/OpenReceive/openreceive/releases/download/v0.4.28/openreceive-wordpress-0.4.28.zip).
+[openreceive-wordpress-0.4.30.zip](https://github.com/OpenReceive/openreceive/releases/download/v0.4.30/openreceive-wordpress-0.4.30.zip).
 Install it through **Plugins → Add New → Upload Plugin**. The GitHub
 source-code ZIP is not an installable plugin.
 

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

@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/fastapi/full.md
 - Do not suggest rotating or revoking a code because it was pasted here.
 - Start the quickstart only once the NWC code is saved, and the LSC code is saved or the user said "Bitcoin only".
 
-These directions describe OpenReceive 0.4.28.
+These directions describe OpenReceive 0.4.30.
 
 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
@@ -444,13 +444,12 @@ enough; drop the `.md` for the same page a person would read.
 - https://openreceive.org/guides/custom-checkout-route.md — advanced: replacing the shipped adapter's routes with your own
 - https://openreceive.org/guides/react-material-ui-recipe.md — a worked custom UI on a component library
 - https://openreceive.org/agent-directions/flask.md — the same engine as a Flask Blueprint: follow those directions instead if this app is Flask after all
+- https://openreceive.org/guides/payment-safety-upgrade.md — coordinated upgrades and reviewed repair of existing attempts
 - https://openreceive.org/guides.md — the index, if what you need is not above
 
 Questions, or a problem with the library itself:
 https://openreceive.org/contact
 
-- https://openreceive.org/guides/payment-safety-upgrade.md — coordinated upgrades and reviewed repair of existing attempts
-
 ---
 
 ## The quickstart, in full
@@ -625,14 +624,14 @@ checks the wallet, and requests get `503 WALLET_UNAVAILABLE` until the check
 passes.
 → [openreceive_router](https://openreceive.org/guides/api-reference.md#openreceive_router) ·
 [openreceive_lifespan](https://openreceive.org/guides/api-reference.md#openreceive_lifespan) ·
-[the authorize context](https://openreceive.org/guides/api-reference.md#the-authorize-context)
+[the authorize context](https://openreceive.org/guides/api-reference.md#host-python)
 
 `rate_limiting=True` is for public web shops. Leave it off for point-of-sale,
 where many payers share one IP. → [Rate limiting](https://openreceive.org/guides/rate-limiting.md)
 
 An optional worker, `openreceive notifications --app main:app`, listens for
 wallet payment notifications so settlement does not wait for the next page
-load. → [openreceive notifications](https://openreceive.org/guides/api-reference.md#openreceive-notifications)
+load. → [openreceive notifications](https://openreceive.org/guides/api-reference.md#openreceive-reconcile--openreceive-notifications)
 
 Your app also needs an ordinary order-creation route that validates the cart,
 prices with exact decimal math, and returns the order id the page will pass as

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

@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/fastify/full.md
 - Do not suggest rotating or revoking a code because it was pasted here.
 - Start the quickstart only once the NWC code is saved, and the LSC code is saved or the user said "Bitcoin only".
 
-These directions describe OpenReceive 0.4.28.
+These directions describe OpenReceive 0.4.30.
 
 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
@@ -429,13 +429,12 @@ enough; drop the `.md` for the same page a person would read.
 - https://openreceive.org/guides/api-reference.md — every route, option and error code
 - https://openreceive.org/guides/custom-checkout-route.md — advanced: replacing the shipped adapter's routes with your own
 - https://openreceive.org/guides/react-material-ui-recipe.md — a worked custom UI on a component library
+- https://openreceive.org/guides/payment-safety-upgrade.md — coordinated upgrades and reviewed repair of existing attempts
 - https://openreceive.org/guides.md — the index, if what you need is not above
 
 Questions, or a problem with the library itself:
 https://openreceive.org/contact
 
-- https://openreceive.org/guides/payment-safety-upgrade.md — coordinated upgrades and reviewed repair of existing attempts
-
 ---
 
 ## The quickstart, in full
@@ -464,8 +463,8 @@ stays the same.
 | Server   | `@openreceive/fastify`, `@openreceive/express`, `@openreceive/next`                                                           |
 | Frontend | `@openreceive/react`, `@openreceive/vue`, `@openreceive/svelte`, `@openreceive/angular`, `@openreceive/elements` (plain HTML) |
 
-Express: [quickstart-node.md](https://openreceive.org/guides/quickstart-node.md) · Next.js:
-[quickstart-next.md](https://openreceive.org/guides/quickstart-next.md). This page is the Fastify one.
+Express: [Express quickstart](https://openreceive.org/guides/quickstart-node.md) · Next.js:
+[Next.js quickstart](https://openreceive.org/guides/quickstart-next.md). This page is the Fastify one.
 
 On a fresh project, also install what this guide assumes you already have: the
 framework, a static-file plugin for the checkout page, and an env loader

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

@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/flask/full.md
 - Do not suggest rotating or revoking a code because it was pasted here.
 - Start the quickstart only once the NWC code is saved, and the LSC code is saved or the user said "Bitcoin only".
 
-These directions describe OpenReceive 0.4.28.
+These directions describe OpenReceive 0.4.30.
 
 Add OpenReceive to a Flask application — the app you are already working in.
 You do not need a copy of the OpenReceive source: the engine is on PyPI
@@ -449,13 +449,12 @@ enough; drop the `.md` for the same page a person would read.
 - https://openreceive.org/guides/api-reference.md — every route, option and error code
 - https://openreceive.org/guides/custom-checkout-route.md — advanced: replacing the shipped adapter's routes with your own
 - https://openreceive.org/guides/react-material-ui-recipe.md — a worked custom UI on a component library
+- https://openreceive.org/guides/payment-safety-upgrade.md — coordinated upgrades and reviewed repair of existing attempts
 - https://openreceive.org/guides.md — the index, if what you need is not above
 
 Questions, or a problem with the library itself:
 https://openreceive.org/contact
 
-- https://openreceive.org/guides/payment-safety-upgrade.md — coordinated upgrades and reviewed repair of existing attempts
-
 ---
 
 ## The quickstart, in full

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

@@ -3,7 +3,7 @@ This is the full file; follow it from Step 0.
 # OpenReceive agent directions (FOSSBilling)
 
 ```sh
-# READ THIS FIRST: this file is 23 KB and a summary drops required steps. Download it whole:
+# READ THIS FIRST: this file is 24 KB and a summary drops required steps. Download it whole:
 curl -fsSL https://openreceive.org/agent-directions/fossbilling/full.md
 # Skip the download only if you already have all of it: pasted, read from disk or fetched raw.
 ```
@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/fossbilling/full.md
 - Do not suggest rotating or revoking a code because it was pasted here.
 - Setup is done only when the NWC code is saved, and the LSC code is saved or the user said "Bitcoin only".
 
-These directions describe OpenReceive 0.4.28.
+These directions describe OpenReceive 0.4.30.
 
 Install and configure the OpenReceive payment method in the FOSSBilling
 billing panel you are working in. Preserve its theme, clients, products,
@@ -121,16 +121,18 @@ Docker image, download and unpack it inside the container, as the web user,
 then activate the module:
 
 ```sh
-docker compose exec -T -u www-data fossbilling sh -c 'curl -fsSLO https://github.com/OpenReceive/openreceive/releases/download/v0.4.28/openreceive-fossbilling-0.4.28.zip && unzip -oq openreceive-fossbilling-0.4.28.zip && rm openreceive-fossbilling-0.4.28.zip'
+docker compose exec -T -u www-data fossbilling sh -c 'curl -fsSLO https://github.com/OpenReceive/openreceive/releases/download/v0.4.30/openreceive-fossbilling-0.4.30.zip && unzip -oq openreceive-fossbilling-0.4.30.zip && rm openreceive-fossbilling-0.4.30.zip'
 docker compose exec -T -u www-data fossbilling php modules/Openreceive/activate.php
 ```
 
 On a server, unpack it in FOSSBilling's folder the same way, make the two
-folders the web user's, and run the same `activate.php`. Activation creates
-the extension's two tables in FOSSBilling's database and its payment gateway,
-"Bitcoin Lightning", hooks its reconcile pass into FOSSBilling's cron, and
-makes the `openreceive:*` console commands appear. The gateway stays off until
-a wallet code is saved.
+folders the web user's, and run the same `activate.php`. Activation writes the
+payment gateway's files into `library/Payment/Adapter/OpenReceive` from the
+module's own copy, creates the extension's two tables in FOSSBilling's
+database and its payment gateway, "Bitcoin Lightning", hooks its reconcile
+pass into FOSSBilling's cron, and makes the `openreceive:*` console commands
+appear. The gateway stays off until a wallet code is saved. If `activate.php`
+says that folder holds another gateway, report that and stop.
 
 ## Step 2 — store the codes
 
@@ -233,7 +235,6 @@ FOSSBilling's cron has never run, say so in one line of that message.
 - [Lightning Swap Connect URI](https://openreceive.org/guides/lightning-swap-connect.md)
 - [Security](https://openreceive.org/guides/security.md)
 - [Price Feeds](https://openreceive.org/guides/price-feeds.md)
-- [Payment Safety Upgrade](https://openreceive.org/guides/payment-safety-upgrade.md)
 
 ---
 
@@ -275,9 +276,9 @@ routes, console commands and cron hook), and
 
 ```sh
 cd /var/www/fossbilling
-curl -fsSLO https://github.com/OpenReceive/openreceive/releases/download/v0.4.28/openreceive-fossbilling-0.4.28.zip
-unzip -oq openreceive-fossbilling-0.4.28.zip
-rm openreceive-fossbilling-0.4.28.zip
+curl -fsSLO https://github.com/OpenReceive/openreceive/releases/download/v0.4.30/openreceive-fossbilling-0.4.30.zip
+unzip -oq openreceive-fossbilling-0.4.30.zip
+rm openreceive-fossbilling-0.4.30.zip
 chown -R www-data:www-data modules/Openreceive library/Payment/Adapter/OpenReceive
 sudo -u www-data php modules/Openreceive/activate.php
 ```
@@ -288,11 +289,26 @@ either. Activation creates the extension's two tables and its payment
 gateway, "Bitcoin Lightning", and hooks its reconcile pass into FOSSBilling's
 cron. The gateway stays off until a wallet code is saved.
 
+The module carries its own copy of the payment gateway and writes it into
+`library/Payment/Adapter/OpenReceive` each time it is activated, so running
+`activate.php` again after an update brings the gateway up to date with the
+module. It replaces only OpenReceive's own gateway files: if that folder holds
+anything else, activation stops and says so.
+
 The ZIP already bundles the extension's dependencies and the checkout's
 script, under their own prefixed names, so Composer never runs and nothing in
 FOSSBilling's own `vendor/` changes. The GitHub source-code ZIP is not an
 installable extension.
 
+#### The module-only ZIP
+
+Each release also attaches `openreceive-fossbilling-module-<version>.zip`:
+the module alone, with its files at the top of the ZIP rather than inside
+`modules/Openreceive`. That is the package FOSSBilling's extension directory
+installs. Its **Install** button unpacks the ZIP into `modules/Openreceive`,
+and activating OpenReceive under **Extensions** then writes the payment
+gateway, as above. Both ZIPs hold the same module.
+
 #### FOSSBilling in Docker
 
 FOSSBilling's official image has sodium but not GMP. Build your own image on
@@ -314,7 +330,7 @@ Run every command inside the container, in `/var/www/html`, as its web user
 `www-data`. Unpack the release there too:
 
 ```sh
-docker compose exec -T -u www-data fossbilling sh -c 'curl -fsSLO https://github.com/OpenReceive/openreceive/releases/download/v0.4.28/openreceive-fossbilling-0.4.28.zip && unzip -oq openreceive-fossbilling-0.4.28.zip && rm openreceive-fossbilling-0.4.28.zip'
+docker compose exec -T -u www-data fossbilling sh -c 'curl -fsSLO https://github.com/OpenReceive/openreceive/releases/download/v0.4.30/openreceive-fossbilling-0.4.30.zip && unzip -oq openreceive-fossbilling-0.4.30.zip && rm openreceive-fossbilling-0.4.30.zip'
 docker compose exec -T -u www-data fossbilling php modules/Openreceive/activate.php
 ```
 
@@ -349,7 +365,8 @@ Lightning" to "Bitcoin & stablecoins"; the settings page's name field, or
 `--name="…"`, sets your own. Skip the swap code for Bitcoin-only checkout.
 
 `doctor` checks the module, GMP and sodium, each code as set or unset (never
-its value), the payment gateway, the tables, the checkout's files, the wallet,
+its value), the payment gateway's files and row, the tables, the checkout's
+files, the wallet,
 the price feed for every FOSSBilling currency, each swap provider and the cron
 hook with FOSSBilling's last cron run. It exits nonzero when a check fails.
 
@@ -413,8 +430,14 @@ converted reclaims it from the same invoice's payment page, while the invoice
 is still unpaid. If you turn on swaps, you commit to keeping that path
 available. See [swap refunds](https://openreceive.org/guides/swap-refunds.md).
 
-Deactivating or uninstalling the module keeps the two tables: they are a
-record of payments received.
+Deactivating the module turns its payment gateway off, because a deactivated
+module serves no checkout. Activating it again turns the gateway back on when
+a wallet code is saved.
+
+Uninstalling the module keeps the two tables, which are a record of payments
+received, and leaves the gateway off. Its row and its files in
+`library/Payment/Adapter/OpenReceive` stay too, since FOSSBilling's invoices
+and transactions refer to the gateway.
 
 ### Tested, and not tested
 
@@ -427,6 +450,15 @@ service is active. A payment whose page was closed was recorded by
 FOSSBilling's cron. Another client, a visitor and a request without the page's
 security token were refused.
 
+Tested on 2026-10-18 in the same setup: the module-only ZIP installed through
+FOSSBilling's own **Install** and **Activate** buttons in the admin area, with
+the extension directory's answer for OpenReceive supplied locally, then the
+same checks. Deactivating, activating again, uninstalling, reinstalling and
+updating a 0.4.28 install with `activate.php` were checked too. On
+FOSSBilling 0.8.0, the oldest release the module accepts: the same install
+and activation, `configure`, the doctor, `test-invoice --new`, deactivating
+and activating again.
+
 Not tested: FOSSBilling behind nginx rather than its image's Apache, shared
 hosting without a shell, and FOSSBilling's subscription payments. Lightning
 cannot pull a payment, so OpenReceive offers no subscriptions: the client

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

@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/laravel/full.md
 - Do not suggest rotating or revoking a code because it was pasted here.
 - Start the quickstart only once the NWC code is saved, and the LSC code is saved or the user said "Bitcoin only".
 
-These directions describe OpenReceive 0.4.28.
+These directions describe OpenReceive 0.4.30.
 
 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
@@ -405,13 +405,12 @@ enough; drop the `.md` for the same page a person would read.
 - https://openreceive.org/guides/api-reference.md — every route, option and error code
 - https://openreceive.org/guides/custom-checkout-route.md — advanced: replacing the mounted engine's routes with your own
 - https://openreceive.org/guides/react-material-ui-recipe.md — a worked custom UI on a component library
+- https://openreceive.org/guides/payment-safety-upgrade.md — coordinated upgrades and reviewed repair of existing attempts
 - https://openreceive.org/guides.md — the index, if what you need is not above
 
 Questions, or a problem with the library itself:
 https://openreceive.org/contact
 
-- https://openreceive.org/guides/payment-safety-upgrade.md — coordinated upgrades and reviewed repair of existing attempts
-
 ---
 
 ## The quickstart, in full
@@ -421,7 +420,7 @@ passes. The page it comes from is https://openreceive.org/guides/quickstart-lara
 
 ## Laravel quickstart
 
-Requires PHP ≥ 8.2 (64-bit) and Laravel ≥ 11 (12 current). You also need these
+Requires PHP ≥ 8.2 (64-bit) and Laravel 11, 12 or 13. You also need these
 PHP extensions:
 
 - `ext-gmp`, which is REQUIRED. The NWC transport's elliptic-curve math depends