Split payment POC: App Builder orchestrator AI prompt

Use this page to copy the full prompt that generates the split-payment-orchestrator project: the payment-orchestrator I/O Event consumer, payment-accept and payment-decline web actions, the demo-dashboard, and the Commerce REST client.

How to use this prompt

Copy everything from PROMPT START to End of prompt into Cursor (with Claude) or directly into Claude. Run the prompt from the split-payment-orchestrator/ directory (the App Builder project root).

Before you run

The prompt

PROMPT START

You are generating a complete Adobe App Builder application for orchestrating split payments in Adobe Commerce. This application receives I/O Events from Commerce, processes split payment decisions, and calls back into Commerce via REST.

Project: split-payment-orchestrator
Runtime: Node.js 18
Key dependencies: @adobe/aio-sdk ^6.0.0, got ^11.8.6, oauth-1.0a ^2.2.6

Generate all files listed below. The application must work with Adobe I/O Runtime (aio app deploy).

File Structure to Generate

split-payment-orchestrator/
├── package.json
├── app.config.yaml
├── .env.example
└── actions/
    ├── payment-orchestrator/
    │   ├── index.js         ← I/O Event entry point
    │   ├── commerce-client.js
    │   ├── threshold.js
    │   ├── cash-payment.js
    │   ├── order-update.js
    │   └── store-credit.js  ← Deprecated stub; kept for reference
    ├── payment-accept/
    │   └── index.js
    ├── payment-decline/
    │   └── index.js
    └── demo-dashboard/
        └── index.js

package.json

{
  "name": "split-payment-orchestrator",
  "version": "1.0.0",
  "private": true,
  "description": "Adobe App Builder action — split payment PoC orchestrator",
  "engines": { "node": ">=18" },
  "scripts": {
    "deploy": "NODE_OPTIONS=--disable-warning=DEP0040 aio app deploy",
    "aio": "NODE_OPTIONS=--disable-warning=DEP0040 aio"
  },
  "dependencies": {
    "@adobe/aio-sdk": "^6.0.0",
    "@adobe/exc-app": "^1.5.9",
    "got": "^11.8.6",
    "oauth-1.0a": "^2.2.6"
  }
}

app.config.yaml

Define four actions in the split_payment_orchestrator package:

payment-orchestrator

payment-accept

payment-decline

demo-dashboard

事件注册 （在events.registrations下）：

Split payment — sales order place before:
  description: Invokes payment-orchestrator when an order is about to be placed
  events_of_interest:
    - provider_metadata: dx_commerce_events
      event_codes:
        - com.adobe.commerce.observer.sales_order_place_before
  runtime_action: split_payment_orchestrator/payment-orchestrator

actions/payment-orchestrator/commerce-client.js

为Adobe Commerce共享了OAuth 1.0a REST客户端。 实施：

createCommerceClient(params, logger) — 返回{ request, baseUrl }

actions/payment-orchestrator/threshold.js

evaluateThreshold({ orderTotal, storeCreditAmount, cashAmount, params, logger }) — 返回{ pass: boolean, reason: string }

逻辑：

actions/payment-orchestrator/cash-payment.js

recordCashPending({ commerce, orderId, cashAmount, logger }) — 返回{ ok: boolean, error? }

actions/payment-orchestrator/order-update.js

updateOrderAfterOrchestration({ commerce, orderId, success, detail, logger }) — 返回{ ok: boolean, error? }

actions/payment-orchestrator/store-credit.js

applyStoreCredit({ commerce, cartId, amount, logger }) — 已弃用的无操作实施

将此文件与JSDoc @deprecated通知一起包含在内，说明：

orchestrator不再通过REST应用商店点数。 使用BalanceManagementInterface::apply()在Commerce PHP模块(PlaceOrderPlugin)中结帐时应用商店点数，这需要有效的购物车。 到App Builder收到I/O事件时，购物车处于不活动状态。 此文件将保留以供参考或用于自定义流程，其中存储点数在订购后应用。

保持工作实施（与其他模块形状相同），以便开发人员可以研究该模式，但请将其明确标记为未在当前流程中使用。

actions/payment-orchestrator/index.js

I/O事件入口点。 实现async function main(params)。

有效负载提取：

Adobe Commerce I/O事件可能会以多种形式交付有效负载。 通过按顺序检查这些路径来提取order值对象：

字段提取自值：

流量：

Important: Always return statusCode: 200 — I/O Runtime will retry non-200 responses, which would cause duplicate order processing. Errors are reported in the body.

PUBLIC_ERRORconstant: "Payment could not be processed. Please try again or contact support." — used for all external-facing error messages.

actions/payment-accept/index.js

HTTP web action. Calls POST /V1/split-payment/orders/:orderId/cash-received.

Order ID resolution: Check params.orderId, then params.payload.orderId, then params.__ow_body (parsed JSON). Return 400 if missing.

流量：

actions/payment-decline/index.js

HTTP web action. Same pattern as payment-accept but calls POST /V1/split-payment/orders/:orderId/cash-decline.

Return { ok: true, orderId, message: 'declined' } on success.

actions/demo-dashboard/index.js

Self-contained demo operator dashboard. Serves an HTML dashboard for listing pending cash orders and triggering accept/decline actions. This is a single web action that serves both the HTML UI and a JSON API.

Security:

Routing (based on HTTP method + path/body):

The action receives all requests. Determine intent from:

Fetching pending orders:

HTML Dashboard:
The dashboard is an HTML string returned with Content-Type: text/html. It should:

Error surfacing in the UI:
When a Commerce REST call fails, include the HTTP status and a short description of the Commerce error body (sanitize — strip HTML tags, truncate to 500 chars). Do not expose credentials.

响应帮助程序：

function jsonResponse(statusCode, obj, extraHeaders = {}) { ... }
function htmlResponse(html) { ... }

.env.example

# Commerce REST base URL — no trailing slash
COMMERCE_BASE_URL=

# OAuth 1.0a integration credentials (Admin → System → Integrations)
COMMERCE_CONSUMER_KEY=
COMMERCE_CONSUMER_SECRET=
COMMERCE_ACCESS_TOKEN=
COMMERCE_ACCESS_TOKEN_SECRET=

# PoC threshold — must match split_payment/general/threshold in Commerce (default: 100)
PAYMENT_THRESHOLD=100

LOG_LEVEL=info

# Demo dashboard optional shared secret
DEMO_UI_SECRET=
DEMO_UI_BASE_URL=

部署命令

生成所有文件后，从split-payment-orchestrator/目录：

npm install
cp .env.example .env
# Edit .env with your credentials
aio app deploy

部署后，请记下aio app deploy打印的操作URL。 demo-dashboard URL是您访问操作员仪表板的位置。

提示结束

Related split payment POC resources