Upcoming CLI workflows

Select staging and authenticate

revkeen config set base-url https://staging-api.revkeen.com
revkeen login --help
revkeen auth status

The candidate adds browser PKCE/device authentication and keyring/refresh handling. Follow the installed command's supported login flags. Confirm the browser's merchant and granted access. A stale key in REVKEEN_API_KEY can override your intended session; inspect the credential source before changing data. Logout removes local state; revoke retired grants or keys through their management flow.

Forward webhooks locally

Start your receiver on port 4242 using the signature-verifying example, then:

revkeen listen --forward-to http://127.0.0.1:4242/webhooks --events invoice.paid,payment.succeeded

The listener prints a session signing secret. Supply that secret to your local receiver without committing it or copying the terminal output into a ticket. In another terminal using the same staging merchant:

revkeen trigger invoice.paid

trigger sends a fixture to active CLI listeners. It does not create a real invoice or move money. Check the forwarded HTTP status and your receiver's durable inbox. On reconnection, use the current session secret; do not assume an earlier secret remains valid. Stop with Ctrl+C. Do not disable signature verification to troubleshoot a mismatch.

Cart onboarding

Start with reads and a local scaffold preview:

revkeen cart status
revkeen cart origins list
revkeen doctor --project-path .
revkeen init --cms sanity --framework nextjs --deploy-target vercel --dry-run

Readiness reports activation, keys, origins, webhooks, and products. Review diagnostics before applying changes. init --dry-run previews the plan; running without it can change local files and remote setup.

The following commands change merchant configuration. An authorised administrator should run them for the intended staging merchant:

revkeen cart keys issue
revkeen cart origins add https://storefront-staging.example.com
revkeen cart webhooks setup --url https://storefront-staging.example.com/webhooks/revkeen

Replace example origins with your own. Key issuance can print credentials once: capture them in your secret store, not CI logs. The publishable key belongs on approved browser origins; the secret key stays on the server. Re-run status, then test an allowed and a denied origin as described in storefront setup.

Interactive dashboard

revkeen dashboard

The terminal UI uses the same configured merchant authority. A visual menu does not grant additional permissions. Keep production mutations out of unattended scripts; use bounded reads and inspect errors.

Release acceptance

Before treating this guide as generally available, verify matching GitHub/npm/installer/Homebrew versions and checksums, execute each help command from the installed binary, forward and verify a fixture, and complete Cart setup for a staging merchant. A source build alone does not establish those release-channel checks.