SDK TEST & LIVE
Published release: SDK 0.1.3 is publicly available on npm. Package installation does not activate new backend features.
| Operation | TEST | LIVE |
|---|---|---|
| Catalog reads | Supported with matching key | Supported with matching key |
checkout.createTest | Dedicated isolated TEST link | Rejected |
checkout.createHosted | Rejected | Approved hosted session path |
payments.confirm | Rejected | Supported payment projection |
| Real bank payout | Never created by these SDK TEST calls | Existing controlled Kordiva workflow; no SDK payout method |
The same configured API origin can serve both modes; using a second hostname does not establish isolation. The key’s server record is authoritative. The SDK rejects obvious prefix/environment mismatches and never falls back between modes.
HTTPS is required. Local HTTP is allowed only with TEST and explicit allowInsecureLocalhost: true for localhost/loopback. This is a development transport exception, not a production bypass.
Successful TEST does not approve LIVE countries, taxes, Stripe capabilities, reserves or agreements. Individual seller countries MK/AL/RS/BA and buyer markets are separate. Check current market status.
Local TEST handoff
Section titled “Local TEST handoff”API transport and browser navigation have separate opt-ins. On the server, allowInsecureLocalhost: true is accepted only with a TEST key/environment and an exact loopback API origin. For browser helpers, pass { environment: 'TEST', allowLocalTest: true } to checkoutHref or as the fourth argument to redirectToCheckout. For React, pass that object as checkoutOptions.
The returned local URL must have an exact allowed origin on localhost, loopback or a .localhost subdomain, path /api/test-commerce/link, and a nonempty token. HTTP /q/... LIVE handoffs, remote HTTP and an absent/incorrect environment are rejected. HTTPS remains the default. These options permit local navigation only; they cannot prove Stripe mode or override server credential identity.
Individual TEST example (16 October 2026)
Section titled “Individual TEST example (16 October 2026)”Using the public @kordiva/[email protected] in an approved Individual TEST store, the owner read the catalog, created a TEST checkout link and completed a Stripe Sandbox card payment. The matching Kordiva TEST order became PAID with verified TEST tax evidence. This demonstrates SDK → TEST checkout → Stripe Sandbox → Kordiva TEST order, not LIVE eligibility, actual Stripe processing fees or a bank payout. The webhook endpoint’s HTTP delivery response was not independently inspected in this walkthrough.
The earlier screenshot below records a different historical TEST onboarding state requiring payment activation. It does not describe the approved account used for the later successful test. TEST catalog and design may be shared with the public store, so do not change them just to test checkout.
