@openreceive/http 0.4.12 → 0.4.14

package/dist/adapter-surface.js

@@ -7,7 +7,7 @@ import {
   isServiceErrorShape,
   mapHostRouteError,
   startNotificationWorker
-} from "./chunk-PGZAFYN6.js";
+} from "./chunk-67MZJBIF.js";
 export {
   HostError,
   HttpError,

package/dist/{chunk-PGZAFYN6.js → chunk-67MZJBIF.js}

@@ -229,7 +229,10 @@ function isUnderPrefix(pathname, prefix) {
 import { compact, unixSeconds as unixSeconds7 } from "@openreceive/core";
 
 // src/reconcile-gate.ts
-import { createPaymentScanWindow, unixSeconds as unixSeconds5 } from "@openreceive/core";
+import {
+  createPaymentScanWindow,
+  unixSeconds as unixSeconds5
+} from "@openreceive/core";
 
 // src/host-payments.ts
 import { unixSeconds as unixSeconds3 } from "@openreceive/core";
@@ -1307,10 +1310,11 @@ function abortableDelay(milliseconds, signal) {
 }
 
 // src/reconcile-gate.ts
-var OPENRECEIVE_MIN_RECONCILE_INTERVAL_SECONDS = 2;
+var OPENRECEIVE_MIN_RECONCILE_INTERVAL_SECONDS = 3;
 var OPENRECEIVE_RECONCILE_SCAN_TIMEOUT_MS = 9e3;
+var SCAN_BACKSTOP_GRACE_MS = 500;
 var OPENRECEIVE_RECONCILE_SCAN_MAX_PAGES = 50;
-var EARLY_INVOICE_INTERVAL_SECONDS = 2;
+var EARLY_INVOICE_INTERVAL_SECONDS = 3;
 var MID_INVOICE_INTERVAL_SECONDS = 6;
 var LATE_INVOICE_INTERVAL_SECONDS = 12;
 var EARLY_INVOICE_WINDOW_SECONDS = 2 * 60;
@@ -1345,7 +1349,10 @@ async function maybeReconcilePayments(input) {
   try {
     const clock = input.clock ?? unixSeconds5;
     const now = clock();
-    const minInterval = Math.max(2, input.minIntervalSeconds ?? 2);
+    const minInterval = Math.max(
+      OPENRECEIVE_MIN_RECONCILE_INTERVAL_SECONDS,
+      input.minIntervalSeconds ?? OPENRECEIVE_MIN_RECONCILE_INTERVAL_SECONDS
+    );
     const timeout = Math.min(
       OPENRECEIVE_RECONCILE_SCAN_TIMEOUT_MS,
       input.scanTimeoutMs ?? OPENRECEIVE_RECONCILE_SCAN_TIMEOUT_MS
@@ -1368,22 +1375,33 @@ async function maybeReconcilePayments(input) {
       let candidates = await input.host.payments.listReconcilableAttempts(scheduler.cursor);
       if (candidates.length === 0 && scheduler.cursor !== null)
         candidates = await input.host.payments.listReconcilableAttempts(null);
-      const last = candidates.at(-1);
-      scheduler.cursor = last === void 0 || candidates.length < OPENRECEIVE_RECONCILE_BATCH_SIZE ? null : { created_at: last.createdAt, payment_hash: last.paymentHash };
-      const fresh = candidates.filter((attempt) => !queued.has(attempt.paymentHash));
-      if (fresh.length > 0)
-        scheduler.windows.push(
-          createPaymentScanWindow(
-            fresh.map((attempt) => ({
-              payment_hash: attempt.paymentHash,
-              created_at: attempt.createdAt,
-              expires_at: attempt.expiresAt,
-              created_at_source: attempt.createdAtSource ?? "host"
-            })),
-            now,
-            input.overlapSeconds
-          )
-        );
+      const cohorts = /* @__PURE__ */ new Map();
+      let taken = 0;
+      for (const attempt of candidates) {
+        if (!queued.has(attempt.paymentHash)) {
+          const wallet = attempt.createdAtSource === "wallet";
+          let cohort = cohorts.get(wallet);
+          if (cohort === void 0) {
+            if (scheduler.windows.length + cohorts.size >= 2) break;
+            cohort = [];
+            cohorts.set(wallet, cohort);
+          }
+          cohort.push({
+            payment_hash: attempt.paymentHash,
+            created_at: attempt.createdAt,
+            expires_at: attempt.expiresAt,
+            created_at_source: attempt.createdAtSource ?? "host"
+          });
+        }
+        taken += 1;
+      }
+      const last = candidates[taken - 1];
+      scheduler.cursor = last === void 0 || taken === candidates.length && candidates.length < OPENRECEIVE_RECONCILE_BATCH_SIZE ? null : { created_at: last.createdAt, payment_hash: last.paymentHash };
+      for (const wallet of [true, false]) {
+        const cohort = cohorts.get(wallet);
+        if (cohort !== void 0)
+          scheduler.windows.push(createPaymentScanWindow(cohort, now, input.overlapSeconds));
+      }
     }
     const window = scheduler.windows.shift();
     if (window === void 0) {
@@ -1445,7 +1463,7 @@ async function maybeReconcilePayments(input) {
           }
         }
       }),
-      timeout,
+      timeout + SCAN_BACKSTOP_GRACE_MS,
       controller
     );
     if (slice.outcome === "continued") {

package/dist/index.d.ts

@@ -282,15 +282,16 @@ declare function startReconciler(input: {
 
 /**
  * Floor for the durable reconcile-gate interval: at most one real wallet scan
- * per two seconds across EVERY worker sharing the host database. This gate is
+ * per three seconds across EVERY worker sharing the host database. This gate is
  * the NWC rate limit for settlement scans — open tabs polling `payments/check`
  * (~3s) all share the one global pass instead of fanning out wallet walks.
  */
-declare const OPENRECEIVE_MIN_RECONCILE_INTERVAL_SECONDS: 2;
+declare const OPENRECEIVE_MIN_RECONCILE_INTERVAL_SECONDS: 3;
 /**
  * Wall-clock bound on an awaited request-path pass: a slow wallet must not
- * hang user-facing requests. A timed-out pass counts as a failed scan; the
- * gate stays claimed so the next interval retries without a stampede.
+ * hang user-facing requests. A page still in flight at the deadline is cut;
+ * the pass keeps the progress of its completed pages, and the next interval
+ * resumes there.
  */
 declare const OPENRECEIVE_RECONCILE_SCAN_TIMEOUT_MS: 9000;
 /** Page cap per wallet-history walk on the awaited request path. */
@@ -304,7 +305,7 @@ type OpportunisticReconcileResult = {
 interface MaybeReconcilePaymentsOptions {
     readonly service: OpenReceive;
     readonly host: Host;
-    /** Gate interval floor. Default (and minimum) 2 seconds. */
+    /** Gate interval floor. Default (and minimum) 3 seconds. */
     readonly minIntervalSeconds?: number;
     readonly overlapSeconds?: number;
     readonly scanTimeoutMs?: number;
@@ -315,7 +316,7 @@ interface MaybeReconcilePaymentsOptions {
 }
 /**
  * The gate interval for the current pending set: the configured floor,
- * stretched by invoice age (2s while any pending invoice is under 2 minutes
+ * stretched by invoice age (3s while any pending invoice is under 2 minutes
  * old, 6s under 5 minutes, else 12s).
  */
 declare function reconcileIntervalSeconds(attempts: readonly ReconcilableAttempt[], now: number, minIntervalSeconds?: number): number;

package/dist/index.js

@@ -34,7 +34,7 @@ import {
   startReconciler,
   typeOrmDb,
   webRequest
-} from "./chunk-PGZAFYN6.js";
+} from "./chunk-67MZJBIF.js";
 export {
   HostError,
   HttpError,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openreceive/http",
-  "version": "0.4.12",
+  "version": "0.4.14",
   "description": "Node.js HTTP routes and payment storage for Bitcoin Lightning checkout, with optional USDT, USDC, SOL and ETH swaps.",
   "keywords": [
     "bitcoin",
@@ -17,8 +17,8 @@
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
   "dependencies": {
-    "@openreceive/core": "0.4.12",
-    "@openreceive/node": "0.4.12"
+    "@openreceive/core": "0.4.14",
+    "@openreceive/node": "0.4.14"
   },
   "exports": {
     ".": {

package/skills/debug-openreceive-payment/SKILL.md

@@ -49,7 +49,7 @@ same diagnostics redacted, always exit 0 — safe to share.
 ## 4. Paid but never settles
 
 - Settlement is opportunistic: any OpenReceive request runs one reconcile pass
-  through a durable gate (min 2s between wallet scans, stretched by invoice
+  through a durable gate (min 3s between wallet scans, stretched by invoice
   age). A quiet server settles on the next request — or run the optional
   notification worker. No timer is missing; that is the design.
 - An unpaid attempt closes only after a successful wallet scan at/after expiry

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

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (BTCPay Server)
 
-These directions describe OpenReceive 0.4.12.
+These directions describe OpenReceive 0.4.14.
 
 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

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

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (Django)
 
-These directions describe OpenReceive 0.4.12.
+These directions describe OpenReceive 0.4.14.
 
 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
@@ -167,15 +167,19 @@ itself, and they hold for every integration.
   late becomes `refund_required`, and the payer claims it on a SECOND VISIT,
   after leaving your page to fetch an address from another wallet. Three things
   must exist or that money is unreachable through your UI: a per-order URL your
-  server serves (`/checkout/:reference` — `syncUrl` on the drop-ins), your own
-  order-summary route to restore the order from, and the ATTEMPT.
+  server serves (`/checkout/:reference` — `syncUrl` on `<Checkout>`, `sync-url`
+  or `resumable` on `<openreceive-checkout>`), your own order-summary route to
+  restore the order from, and the ATTEMPT.
   `/checkouts/prepare` returns no attempts, so a checkout rebuilt from the
   reference alone opens on the method grid. Re-picking the same coin
   (`POST /swaps`) re-serves the committed attempt — but only while it is live,
   and the shadow invoice behind a swap lasts about half an hour, after which the
   same click mints a NEW deposit address and the refund is off-screen. Keep the
   `payment_hash` and reopen the attempt with `POST /swaps/status`, which has no
-  such window. https://openreceive.org/guides/swap-refunds.md
+  such window. On the drop-ins: `resumePaymentHash`, fed from `onState`, on
+  `<Checkout>`; the `resume-payment-hash` attribute, fed from the
+  `openreceive-state` event (`event.detail.state.payment_hash`), on
+  `<openreceive-checkout>`. https://openreceive.org/guides/swap-refunds.md
 - Show the payer WHAT THEY ARE BUYING. Return an optional `description` beside
   the price from `amount_for` and both drop-ins render it above the
   amount. Without it the checkout is a QR and "$1.00" with no sign of what the

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

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (FastAPI)
 
-These directions describe OpenReceive 0.4.12.
+These directions describe OpenReceive 0.4.14.
 
 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
@@ -157,15 +157,19 @@ itself, and they hold for every integration.
   late becomes `refund_required`, and the payer claims it on a SECOND VISIT,
   after leaving your page to fetch an address from another wallet. Three things
   must exist or that money is unreachable through your UI: a per-order URL your
-  server serves (`/checkout/:reference` — `syncUrl` on the drop-ins), your own
-  order-summary route to restore the order from, and the ATTEMPT.
+  server serves (`/checkout/:reference` — `syncUrl` on `<Checkout>`, `sync-url`
+  or `resumable` on `<openreceive-checkout>`), your own order-summary route to
+  restore the order from, and the ATTEMPT.
   `/checkouts/prepare` returns no attempts, so a checkout rebuilt from the
   reference alone opens on the method grid. Re-picking the same coin
   (`POST /swaps`) re-serves the committed attempt — but only while it is live,
   and the shadow invoice behind a swap lasts about half an hour, after which the
   same click mints a NEW deposit address and the refund is off-screen. Keep the
   `payment_hash` and reopen the attempt with `POST /swaps/status`, which has no
-  such window. https://openreceive.org/guides/swap-refunds.md
+  such window. On the drop-ins: `resumePaymentHash`, fed from `onState`, on
+  `<Checkout>`; the `resume-payment-hash` attribute, fed from the
+  `openreceive-state` event (`event.detail.state.payment_hash`), on
+  `<openreceive-checkout>`. https://openreceive.org/guides/swap-refunds.md
 - Show the payer WHAT THEY ARE BUYING. Return an optional `description` beside
   the price from `amount_for` and both drop-ins render it above the amount.
   Without it the checkout is a QR and "$1.00" with no sign of what the dollar

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

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (Fastify)
 
-These directions describe OpenReceive 0.4.12.
+These directions describe OpenReceive 0.4.14.
 
 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
@@ -149,15 +149,19 @@ itself, and they hold for every integration.
   late becomes `refund_required`, and the payer claims it on a SECOND VISIT,
   after leaving your page to fetch an address from another wallet. Three things
   must exist or that money is unreachable through your UI: a per-order URL your
-  server serves (`/checkout/:reference` — `syncUrl` on the drop-ins), your own
-  order-summary route to restore the order from, and the ATTEMPT.
+  server serves (`/checkout/:reference` — `syncUrl` on `<Checkout>`, `sync-url`
+  or `resumable` on `<openreceive-checkout>`), your own order-summary route to
+  restore the order from, and the ATTEMPT.
   `/checkouts/prepare` returns no attempts, so a checkout rebuilt from the
   reference alone opens on the method grid. Re-picking the same coin
   (`POST /swaps`) re-serves the committed attempt — but only while it is live,
   and the shadow invoice behind a swap lasts about half an hour, after which the
   same click mints a NEW deposit address and the refund is off-screen. Keep the
   `payment_hash` and reopen the attempt with `POST /swaps/status`, which has no
-  such window. https://openreceive.org/guides/swap-refunds.md
+  such window. On the drop-ins: `resumePaymentHash`, fed from `onState`, on
+  `<Checkout>`; the `resume-payment-hash` attribute, fed from the
+  `openreceive-state` event (`event.detail.state.payment_hash`), on
+  `<openreceive-checkout>`. https://openreceive.org/guides/swap-refunds.md
 - Show the payer WHAT THEY ARE BUYING. Return an optional `description` beside
   the price from `amountFor` and both drop-ins render it above the amount.
   Without it the checkout is a QR and "$1.00" with no sign of what the dollar
@@ -375,7 +379,9 @@ there is nothing else to generate. Details:
 No ORM? You can pass a bare driver handle (`pg`, `node:sqlite`,
 `better-sqlite3`) as the `db` in step 4. The scaffold has no flavor for it.
 Instead of scaffolding, run the same DDL once yourself, using
-`paymentsSchemaSql(dialect)` from `@openreceive/http`.
+`paymentsSchemaSql(dialect)` from `@openreceive/http`. Your adapter already
+pulls that package in, but this import is yours, so install it too:
+`npm install @openreceive/http`.
 
 ### 3. Add wallet credentials
 

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

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (Laravel)
 
-These directions describe OpenReceive 0.4.12.
+These directions describe OpenReceive 0.4.14.
 
 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
@@ -158,15 +158,19 @@ itself, and they hold for every integration.
   late becomes `refund_required`, and the payer claims it on a SECOND VISIT,
   after leaving your page to fetch an address from another wallet. Three things
   must exist or that money is unreachable through your UI: a per-order URL your
-  server serves (`/checkout/:reference` — `syncUrl` on the drop-ins), your own
-  order-summary route to restore the order from, and the ATTEMPT.
+  server serves (`/checkout/:reference` — `syncUrl` on `<Checkout>`, `sync-url`
+  or `resumable` on `<openreceive-checkout>`), your own order-summary route to
+  restore the order from, and the ATTEMPT.
   `/checkouts/prepare` returns no attempts, so a checkout rebuilt from the
   reference alone opens on the method grid. Re-picking the same coin
   (`POST /swaps`) re-serves the committed attempt — but only while it is live,
   and the shadow invoice behind a swap lasts about half an hour, after which the
   same click mints a NEW deposit address and the refund is off-screen. Keep the
   `payment_hash` and reopen the attempt with `POST /swaps/status`, which has no
-  such window. https://openreceive.org/guides/swap-refunds.md
+  such window. On the drop-ins: `resumePaymentHash`, fed from `onState`, on
+  `<Checkout>`; the `resume-payment-hash` attribute, fed from the
+  `openreceive-state` event (`event.detail.state.payment_hash`), on
+  `<openreceive-checkout>`. https://openreceive.org/guides/swap-refunds.md
 - Show the payer WHAT THEY ARE BUYING. Return an optional `description` beside
   the price from `amountFor` and both drop-ins render it above the
   amount. Without it the checkout is a QR and "$1.00" with no sign of what the

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

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (Next.js)
 
-These directions describe OpenReceive 0.4.12.
+These directions describe OpenReceive 0.4.14.
 
 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
@@ -149,15 +149,19 @@ itself, and they hold for every integration.
   late becomes `refund_required`, and the payer claims it on a SECOND VISIT,
   after leaving your page to fetch an address from another wallet. Three things
   must exist or that money is unreachable through your UI: a per-order URL your
-  server serves (`/checkout/:reference` — `syncUrl` on the drop-ins), your own
-  order-summary route to restore the order from, and the ATTEMPT.
+  server serves (`/checkout/:reference` — `syncUrl` on `<Checkout>`, `sync-url`
+  or `resumable` on `<openreceive-checkout>`), your own order-summary route to
+  restore the order from, and the ATTEMPT.
   `/checkouts/prepare` returns no attempts, so a checkout rebuilt from the
   reference alone opens on the method grid. Re-picking the same coin
   (`POST /swaps`) re-serves the committed attempt — but only while it is live,
   and the shadow invoice behind a swap lasts about half an hour, after which the
   same click mints a NEW deposit address and the refund is off-screen. Keep the
   `payment_hash` and reopen the attempt with `POST /swaps/status`, which has no
-  such window. https://openreceive.org/guides/swap-refunds.md
+  such window. On the drop-ins: `resumePaymentHash`, fed from `onState`, on
+  `<Checkout>`; the `resume-payment-hash` attribute, fed from the
+  `openreceive-state` event (`event.detail.state.payment_hash`), on
+  `<openreceive-checkout>`. https://openreceive.org/guides/swap-refunds.md
 - Show the payer WHAT THEY ARE BUYING. Return an optional `description` beside
   the price from `amountFor` and both drop-ins render it above the amount.
   Without it the checkout is a QR and "$1.00" with no sign of what the dollar
@@ -381,7 +385,9 @@ there is nothing else to generate. Details:
 No ORM? You can pass a bare driver handle (`pg`, `node:sqlite`,
 `better-sqlite3`) as the `db` in step 4. The scaffold has no flavor for it.
 Instead of scaffolding, run the same DDL once yourself, using
-`paymentsSchemaSql(dialect)` from `@openreceive/http`.
+`paymentsSchemaSql(dialect)` from `@openreceive/http`. Your adapter already
+pulls that package in, but this import is yours, so install it too:
+`npm install @openreceive/http`.
 
 ### 3. Add wallet credentials
 

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

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (Node.js)
 
-These directions describe OpenReceive 0.4.12.
+These directions describe OpenReceive 0.4.14.
 
 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
@@ -146,15 +146,19 @@ itself, and they hold for every integration.
   late becomes `refund_required`, and the payer claims it on a SECOND VISIT,
   after leaving your page to fetch an address from another wallet. Three things
   must exist or that money is unreachable through your UI: a per-order URL your
-  server serves (`/checkout/:reference` — `syncUrl` on the drop-ins), your own
-  order-summary route to restore the order from, and the ATTEMPT.
+  server serves (`/checkout/:reference` — `syncUrl` on `<Checkout>`, `sync-url`
+  or `resumable` on `<openreceive-checkout>`), your own order-summary route to
+  restore the order from, and the ATTEMPT.
   `/checkouts/prepare` returns no attempts, so a checkout rebuilt from the
   reference alone opens on the method grid. Re-picking the same coin
   (`POST /swaps`) re-serves the committed attempt — but only while it is live,
   and the shadow invoice behind a swap lasts about half an hour, after which the
   same click mints a NEW deposit address and the refund is off-screen. Keep the
   `payment_hash` and reopen the attempt with `POST /swaps/status`, which has no
-  such window. https://openreceive.org/guides/swap-refunds.md
+  such window. On the drop-ins: `resumePaymentHash`, fed from `onState`, on
+  `<Checkout>`; the `resume-payment-hash` attribute, fed from the
+  `openreceive-state` event (`event.detail.state.payment_hash`), on
+  `<openreceive-checkout>`. https://openreceive.org/guides/swap-refunds.md
 - Show the payer WHAT THEY ARE BUYING. Return an optional `description` beside
   the price from `amountFor` and both drop-ins render it above the amount.
   Without it the checkout is a QR and "$1.00" with no sign of what the dollar
@@ -366,7 +370,9 @@ there is nothing else to generate. Details:
 No ORM? You can pass a bare driver handle (`pg`, `node:sqlite`,
 `better-sqlite3`) as the `db` in step 4. The scaffold has no flavor for it.
 Instead of scaffolding, run the same DDL once yourself, using
-`paymentsSchemaSql(dialect)` from `@openreceive/http`.
+`paymentsSchemaSql(dialect)` from `@openreceive/http`. Your adapter already
+pulls that package in, but this import is yours, so install it too:
+`npm install @openreceive/http`.
 
 ### 3. Add wallet credentials
 

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

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (PHP)
 
-These directions describe OpenReceive 0.4.12.
+These directions describe OpenReceive 0.4.14.
 
 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
@@ -171,7 +171,9 @@ itself, and they hold for every integration.
   and the shadow invoice behind a swap lasts about half an hour, after which the
   same click mints a NEW deposit address and the refund is off-screen. Keep the
   `payment_hash` and reopen the attempt with `POST /swaps/status`, which has no
-  such window. https://openreceive.org/guides/swap-refunds.md
+  such window. On the element: the `resume-payment-hash` attribute, fed from
+  the `openreceive-state` event (`event.detail.state.payment_hash`).
+  https://openreceive.org/guides/swap-refunds.md
 - Show the payer WHAT THEY ARE BUYING. Return an optional `description` beside
   the price from `amountFor` and the drop-in renders it above the amount.
   Without it the checkout is a QR and "$1.00" with no sign of what the dollar
@@ -651,7 +653,7 @@ use registry `icon_path` / tutorial `path` keys as browser URLs.
 
 Settlement runs on the request path. Every payment route first runs one bounded
 reconcile pass through the durable `openreceive_meta` gate. The gate allows at
-most one real wallet scan every 2 seconds, shared by every PHP process. You do
+most one real wallet scan every 3 seconds, shared by every PHP process. You do
 not need a cron job. Tune or disable it with `Engine`'s
 `opportunisticReconcile` (`false`, or `['min_interval_seconds' => …]`).
 

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

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (Rails)
 
-These directions describe OpenReceive 0.4.12.
+These directions describe OpenReceive 0.4.14.
 
 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
@@ -153,15 +153,19 @@ itself, and they hold for every integration.
   late becomes `refund_required`, and the payer claims it on a SECOND VISIT,
   after leaving your page to fetch an address from another wallet. Three things
   must exist or that money is unreachable through your UI: a per-order URL your
-  server serves (`/checkout/:reference` — `syncUrl` on the drop-ins), your own
-  order-summary route to restore the order from, and the ATTEMPT.
+  server serves (`/checkout/:reference` — `syncUrl` on `<Checkout>`, `sync-url`
+  or `resumable` on `<openreceive-checkout>`), your own order-summary route to
+  restore the order from, and the ATTEMPT.
   `/checkouts/prepare` returns no attempts, so a checkout rebuilt from the
   reference alone opens on the method grid. Re-picking the same coin
   (`POST /swaps`) re-serves the committed attempt — but only while it is live,
   and the shadow invoice behind a swap lasts about half an hour, after which the
   same click mints a NEW deposit address and the refund is off-screen. Keep the
   `payment_hash` and reopen the attempt with `POST /swaps/status`, which has no
-  such window. https://openreceive.org/guides/swap-refunds.md
+  such window. On the drop-ins: `resumePaymentHash`, fed from `onState`, on
+  `<Checkout>`; the `resume-payment-hash` attribute, fed from the
+  `openreceive-state` event (`event.detail.state.payment_hash`), on
+  `<openreceive-checkout>`. https://openreceive.org/guides/swap-refunds.md
 - Show the payer WHAT THEY ARE BUYING. Return an optional `description` beside
   the price from `config.amount_for` and both drop-ins render it above the
   amount. Without it the checkout is a QR and "$1.00" with no sign of what the

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

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (WordPress + WooCommerce)
 
-These directions describe OpenReceive 0.4.12.
+These directions describe OpenReceive 0.4.14.
 
 Install and configure the OpenReceive gateway in the existing WooCommerce
 store. Preserve its theme, checkout, customer accounts, order model and prices.