@capxul/cli 4.20.0-beta.21 → 4.20.0-beta.22

package/README.md

@@ -209,8 +209,10 @@ Issue accepts a basic payment request or an Invoice request JSON object from
 `amount`. A basic request requires an explicit `reference` and accepts an
 optional private `memo`. An Invoice request also supplies `invoice`.
 Issue saves available document PDFs in the common directory by default.
-Human and JSON output include `checkoutUrl` for an Invoice instruction with a link token.
-Memo requests do not receive an Invoice checkout URL.
+Human and JSON output include `checkoutUrl` for an Invoice or Memo request
+instruction with a link token. Invoice requests keep `/checkout/invoices/`.
+Basic requests use `/checkout/requests/`. Movement documents do not create
+request links.
 The PDF includes the checkout link from the authorized backend render context.
 For a custom deployment, set `CAPXUL_CHECKOUT_FRONTEND_ORIGIN` in both the CLI
 and backend environments. Use the same frontend origin for both.
@@ -1061,9 +1063,9 @@ revision, quantity, price, asset, network, and recipient for that purchase.
 Changing the URL cannot change a saved purchase. Refresh retains its checkout
 reference. Separate purchasers receive separate checkout and settlement IDs.
 
-## Invoice and document flow
+## Request and document flow
 
-Alice issues an Invoice to Bob with `request issue`. For an Organization issuer,
+Alice issues a basic request or an Invoice to Bob with `request issue`. For an Organization issuer,
 Alice uses `org request issue --org ORGANIZATION_ID`. Issuance saves Alice's PDF
 by default and returns the request ID, document references, and checkout URL.
 Bob runs `inbox list`, then `inbox get --request-id REQUEST_ID`. An Organization