Skip to content
Stashtab Docs
Esc
↑↓navigate↵open⌘Jpreview
On this page

Environments and proof

Use the host and authorized test identity supplied for your integration; synthetic QA does not establish provider capability.

Use the Vault base URL and registered identity supplied by Stashtab for your integration. Local and isolated QA runs use separate test identities and data. The historical custody API’s sk_test_* / sk_live_* keys and sandbox /advance operation are not Warehouse credentials or routes.

A contract test proves a request shape and a QA response proves the exercised test path. A synthetic adapter cannot prove that a carrier, billing provider, or external partner account has accepted a live effect. When a required source or setup is missing, an operation returns warehouse_not_ready (409). When a required source is temporarily unreachable, it returns provider_unavailable (503). Do not infer availability from an OpenAPI page.

For customer go-live, use the separately verified account and provider capabilities supplied through the rollout process.

For a TEST integration, Stashtab supplies the verified HTTPS origin, console link, and authorized test identity. Its data and authorization boundary are separate from disposable local engineering QA. A simulated response or persisted test decision does not establish a live external effect.

Shared Test order workflows

When shared Test is configured and released for an integration, it uses the same Vault application, customer organization, HTTP base, and MCP endpoint as the released Vault service. The Test page URL and the immutable mode of an organization API key select Test activity. Stashtab then supplies the released origin, organization setup, and appropriate key through the secure channel; never use a Preview URL, local QA branch, browser session, or infrastructure credential as an integration endpoint.

Released shared Test workflows use synthetic Test facts. They do not prove a carrier label purchase, physical dispatch, billing charge, or recipient delivery. Configured Test inventory supports redemptions with explicit lines. Published pack lookup and pack-based creation require Live mode. Observe an unknown provider outcome through its operation or order read and keep the original submission key.

Deferred graded-card capabilities

Professional grading, graded-card certificate lookup and exact-slab redemption are deferred from the current integration rollout. TEST does not provide a certificate registry or a substitute workflow for them. Retained historical schema fields are compatibility details, not an instruction that the capability is available. Use the deposit and redemption walkthrough and capability matrix for the supported raw-card, sealed-goods and ordinary-redemption flow.

Was this page helpful?