Live Mode

Overview

Live Mode is the production operating state in which API requests, transactions, callbacks, and account changes affect real users, real assets, or enforceable business records. Monitoring for Live Mode should distinguish transport success, processing success, and the final external or financial result.

The main risks include test credentials used in production, accidental real transactions, unvalidated configuration, missing alerts, and unsafe manual testing. It is different from test mode not only by endpoint or key but also by financial consequence, compliance controls, operational ownership, and recovery requirements.

In production, teams should define ownership and apply separate production credentials, least privilege, change approval, monitoring, incident response, reconciliation, and environment banners. Credentials, endpoints, limits, and available capabilities may differ from test environments. Changes to Live Mode should be tested against normal, failed, delayed, duplicate, and recovery paths that apply to the operation.

Useful measures include live transaction success rate, production error rate, unauthorized test activity, and configuration drift count. Live Mode is closely connected to Test Mode, Sandbox Account, and Client Certificate. Evidence for Live Mode should preserve the input, configuration version, actor or service, decision, downstream reference, and final outcome.

The Live Mode runbook should define who can retry, cancel, replay, reconcile, communicate, and approve an exception. Testing Live Mode should cover boundary values, dependency failure, restart recovery, and incompatible versions where they affect the workflow.

Operational metrics for Live Mode should use stable denominators and separate technical activity from successful business completion. The production boundary for Live Mode should identify the authoritative system, responsible owner, accepted states, and recovery path.