Developer SDK
Published release: SDK 0.1.3 is publicly available on npm. Package installation does not activate new backend features.
The Kordiva SDK connects your own website to Kordiva’s existing catalog and checkout APIs. Your backend holds the store key; the browser receives a checkout URL. Card details remain in the existing Kordiva/Stripe hosted flow.
0.1.3 is publicly available on npm. Anyone can install published packages without a download token; using protected Kordiva APIs still requires a store-specific TEST or LIVE key and the relevant account approval.
| Package | Runs where | Purpose |
|---|---|---|
@kordiva/sdk | Server, Node 20+ | Catalog, hosted/recurring checkout, LIVE confirmation, Business subscription reads and signed merchant event verification |
@kordiva/checkout | Browser or server | Validate an exact allowed origin and hand off to checkout |
@kordiva/react | React 18.2/19, Next client components | Accessible checkout button calling your own backend |
Which integration should you choose?
Section titled “Which integration should you choose?”| Your website | Recommended integration | Store API key? |
|---|---|---|
| Kordiva CMS themes | Use the built-in storefront | No separate key |
| WordPress / HTML / static link | Existing Kordiva Checkout Link | No |
| Custom Node.js backend | @kordiva/sdk package guide | Yes, server only |
| React / Next.js | @kordiva/react guide + checkout helper; SDK on backend | Yes, server only |
| Plain JavaScript | @kordiva/checkout guide plus protected backend | Only for protected Store API |
The SDK is optional. It does not replace Kordiva CMS stores, Checkout Links, the existing direct HTTP API, Booking or Rent-a-Car modules. You may use a Kordiva storefront and an SDK integration in parallel. The three packages do not create a new payment processor or change Business Stripe Connect or Individual Full Merchant of Record responsibilities.
Payment confirmation: Kordiva handles Stripe notifications on its servers. Your backend checks LIVE payments.confirm() before showing success; a browser return URL alone is not proof. No separate merchant Stripe webhook is needed for standard Kordiva hosted checkout, and 0.1.3 adds signed Business lifecycle webhooks through the separate merchant-webhooks export. How to confirm payments.
Package-specific documentation
Section titled “Package-specific documentation”Start with the package you found on npm: @kordiva/sdk for Node.js, @kordiva/checkout for URL validation, or @kordiva/react for React/Next.js. Each guide explains install, exported API, runnable integration shape, TEST/LIVE limits and payment-success boundaries.
Public npm install
Section titled “Public npm install”pnpm add @kordiva/sdk@0.1.3pnpm add @kordiva/react@0.1.3 @kordiva/checkout@0.1.3Use @kordiva/sdk only in Node.js server code. React and checkout helpers never receive Store API keys. See the step-by-step installation, React example and WordPress/HTML example.
- Choose Business or Individual and complete the applicable application/verification.
- Read installation and run the TEST quickstart.
- Add your own authenticated backend endpoint; review security.
- Enable LIVE only after Kordiva confirms the account, product and buyer market.
All active paid Business/Sole Trader plans—Basic, Professional and Enterprise—include API and SDK integration. Individual Creator (free), Pro and approved Scale configurations include API for their own websites and applications, subject to their separate approval and environment rules. Preview does not automatically grant LIVE API access. Individual sales remain approved digital products only, with Kordiva as Full Merchant of Record and its hosted checkout, tax, refund, dispute, reserve and payout controls.
Applications cover MK, AL, RS and BA in both models; this does not prove identical LIVE capabilities. Individual remains approved one-time digital only, with Kordiva-controlled refunds, reserves and payouts. Booking and Rent-a-Car are separate.
Related guides
Section titled “Related guides”SDK · Checkout · Security · API
Business integration
Section titled “Business integration”Recurring checkout and subscription reads → Signed Business events → Raw-body verification → Business refunds → API reference. Individual MoR follows its separate refund process.