Split payment POC: environment variables reference

The same four Commerce OAuth credentials are used in every component. In Commerce Admin, create one Integration, then reuse the four values in every .env file below. (See Split payment POC: prerequisites and environment setup for the activation steps.)

The four OAuth credentials (used everywhere)

App Builder orchestrator

split-payment-orchestrator/.env

Copy from .env.example in the orchestrator directory. Do not commit this file.

# Commerce REST base URL — no trailing slash
COMMERCE_BASE_URL=https://your-store.example.com

# OAuth 1.0a integration credentials
COMMERCE_CONSUMER_KEY=
COMMERCE_CONSUMER_SECRET=
COMMERCE_ACCESS_TOKEN=
COMMERCE_ACCESS_TOKEN_SECRET=

# Must match split_payment/general/threshold in Commerce config (default: 100)
# Both Commerce and App Builder fall back to 100 if this is missing, non-numeric, or ≤ 0
PAYMENT_THRESHOLD=100

LOG_LEVEL=info

# Demo dashboard: if set, requires ?secret=<value> in URL or x-demo-secret header
# Leave empty for private staging only (anyone with the URL can list/accept orders)
DEMO_UI_SECRET=

# Optional: override the base URL used in dashboard action links (useful behind proxies)
DEMO_UI_BASE_URL=

Experience Cloud UI extension (commerce-checkout-starter-kit)

commerce-checkout-starter-kit/.env

This component uses two credential sets: IMS for order listing with the Admin UI SDK, and OAuth 1.0a for accept and decline actions.

# IMS — used by CustomMenu/commerce-rest-api to list orders
# The Admin UI SDK provides the IMS token context; these set the Commerce base URL
COMMERCE_BASE_URL=https://your-store.example.com
OAUTH_CLIENT_ID=
OAUTH_CLIENT_SECRETS=
OAUTH_TECHNICAL_ACCOUNT_ID=
OAUTH_TECHNICAL_ACCOUNT_EMAIL=
OAUTH_SCOPES=
OAUTH_IMS_ORG_ID=
AIO_CLI_ENV=stage

# OAuth 1.0a — same four credentials, COMMERCE_INTEGRATION_ prefix
COMMERCE_INTEGRATION_BASE_URL=https://your-store.example.com
COMMERCE_INTEGRATION_CONSUMER_KEY=
COMMERCE_INTEGRATION_CONSUMER_SECRET=
COMMERCE_INTEGRATION_ACCESS_TOKEN=
COMMERCE_INTEGRATION_ACCESS_TOKEN_SECRET=

Simulation script

commerce-backend-ui-1/.env.simulation

Copy from .env.simulation.example in the same directory.

COMMERCE_BASE_URL=https://your-store.example.com
COMMERCE_CONSUMER_KEY=
COMMERCE_CONSUMER_SECRET=
COMMERCE_ACCESS_TOKEN=
COMMERCE_ACCESS_TOKEN_SECRET=

Notes

PAYMENT_THRESHOLD — Must match split_payment/general/threshold in Commerce system configuration. Both sides default to 100 if the value is missing, not numeric, or less than or equal to 0. If you change the threshold in Commerce, update the App Builder .env to match.

DEMO_UI_SECRET — Optional but recommended for any deployment that is not localhost. Anyone with the dashboard URL can list orders and run accept and decline if this is empty. For a real staging environment, set a shared secret.

COMMERCE_BASE_URL — Never include a trailing slash. The Commerce REST client appends /rest/V1/ automatically.

AIO_CLI_ENV — Set to stage for the Stage workspace. Change to prod when you deploy to Production.

All resources in this series

Reference resources