diff --git a/architecture.md b/architecture.md index 40ae4c6..d941b91 100644 --- a/architecture.md +++ b/architecture.md @@ -106,7 +106,7 @@ Major documentation reorganization completed: - ✅ Charge Credits (`docs/integrate/patterns/charge-credits.mdx`) - ✅ Subscription Access (`docs/integrate/patterns/subscription-access.mdx`) - ✅ Dynamic Pricing (`docs/integrate/patterns/dynamic-pricing.mdx`) -- ✅ Orders: Goods & Services Checkout (`docs/integrate/patterns/orders.mdx`) — Phase 1 contract, marked not yet GA +- ✅ Orders: Goods & Services Checkout (`docs/integrate/patterns/orders.mdx`) — Phase 1 contract #### Platform Integrations (Symlinks to existing content) - ✅ x402 Protocol (`docs/integrate/platforms/x402-protocol.mdx`) diff --git a/integrate/patterns/orders.mdx b/integrate/patterns/orders.mdx index de3722c..a4d92d7 100644 --- a/integrate/patterns/orders.mdx +++ b/integrate/patterns/orders.mdx @@ -4,10 +4,6 @@ description: "Charge a buyer an arbitrary cart total by card in the browser with icon: "cart-shopping" --- - -**Not yet generally available.** Orders are being rolled out to organization accounts and are not enabled in production yet. This guide documents the Phase 1 contract so you can plan your integration. Watch this page for availability. - - An **Order** is a first-class, off-plan charge for an arbitrary amount: the price is whatever your cart adds up to on this request. You call one endpoint from your server, state the amount, and get back a `clientSecret` the buyer's browser confirms with their card. Nothing needs to exist in advance: no plan, no buyer Nevermined account, no delegation. Orders live alongside plans; they don't replace them. Use a plan for a reusable, catalog-listed service. Use an Order when you need to charge one buyer one specific total and move on. @@ -64,11 +60,11 @@ Your server sets the price. The buyer's browser confirms the payment. A Stripe w -The hosted checkout is the buyer-facing half of Orders and ships with the same rollout as the API, together with SDK helpers for `POST /api/v1/orders`. You don't need your own Stripe Elements integration: the hosted checkout confirms the `clientSecret` for you. Your side is the server-to-server REST contract on this page. +The hosted checkout is the buyer-facing half of Orders. You don't need your own Stripe Elements integration: the hosted checkout confirms the `clientSecret` for you. Your side is the server-to-server REST contract on this page. -Prefer to read working code? The [Fiat Checkout Chat tutorial](https://github.com/nevermined-io/tutorials/tree/main/fiat-checkout-chat) is a minimal Next.js chat UI plus a thin merchant backend that implements this exact flow — create an order, hand off the `orderId`, confirm by card in the hosted checkout, and read the paid status. While Orders is pre-GA it runs against a local Nevermined stack; see the tutorial's prerequisites. +Prefer to read working code? The [Fiat Checkout Chat tutorial](https://github.com/nevermined-io/tutorials/tree/main/fiat-checkout-chat) is a minimal Next.js chat UI plus a thin merchant backend that implements this exact flow — create an order, hand off the `orderId`, confirm by card in the hosted checkout, and read the paid status. It runs against a local Nevermined stack — see the tutorial's prerequisites. ## Create an Order @@ -281,7 +277,7 @@ Server-side checkout by agents, a refund API, and dispute handling through Never - A worked Next.js + merchant-backend example of the Orders flow. Runs on a local stack while Orders is pre-GA. + A worked Next.js + merchant-backend example of the Orders flow. Runs against a local Nevermined stack; see its prerequisites. Card plans, delegations, revenue routing, and fees for the rest of the fiat rails.