رفتن به محتواTest mode
Test and Live are separate API-key environments with separate Payment Intent, webhook, delivery, and sandbox data boundaries.
Environment selection
The environment is selected by the API key. A Test credential uses the sandbox merchant routes and Test webhook resources; a Live credential uses Live resources. A request cannot promote Test data or credentials to Live.
Sandbox flow
POST /api/v1/sandbox/merchants/{merchant}/payment-intents creates a Test Payment Intent. POST /.../{payment_intent}/simulate accepts one implemented outcome: confirmed, expired, cancelled, underpaid, overpaid, or late. Simulation creates server-generated synthetic event evidence and does not submit a blockchain transaction or create Live authority.
What Test proves
Test validates request handling, merchant ownership, idempotency, webhook delivery, and receiver behavior. It is not evidence that a Live blockchain payment occurred and must not be joined with Live records.
Test limitations
Test webhook.test and simulated payment events are synthetic. Live payment state still requires the Live observer and its verified blockchain evidence.