Skip to main content
Every SDK follows semantic versioning and is published on npm under @tagadapay. This page says which payments API each one talks to: V2 (the Commerce API, https://api.tagada.io/api/public/v1) or V3 (the Payments API, https://api.tagada.io/v1).

​
Current versions

​
Package by package

​
@tagadapay/node-sdk

The server SDK for the Commerce API: stores, orders, customers, subscriptions, and V2 payments (tagada.payments.process(), refund(), void()). Default base URL https://api.tagada.io/api/public/v1.
  • Payments API (V3): no methods yet. A tagada.payments namespace for V3 is coming soon. Until then, call https://api.tagada.io/v1 over HTTP.
  • On a store switched to V3, payments.process() keeps working. See compatibility.

​
@tagadapay/headless-sdk

Builds a custom checkout on your domain when TagadaPay manages the cart. Pays a checkout session with payment.processPayment() (checkout/pay-v2) and handles 3DS and redirects itself.
  • Payments API (V3): since 1.21.0, a store switched to V3 pays with the same calls: cards, Apple Pay and Google Pay go through the server, and local methods and redirects run the V3 next_action loop inside the SDK (npm build, with @tagadapay/core-js ^3.7.0). The CDN build does not run that loop yet. Nothing changes in your calls.
  • Replaces @tagadapay/plugin-sdk over time.

​
@tagadapay/core-js

Low-level browser building blocks.
  • Root export (V2): card and wallet tokenization (tagadaToken), 3DS helpers, Radar. Pair it with node-sdk payments.process().
  • @tagadapay/core-js/payments-v3 (V3, Preview), since 3.7.0: the browser client of the Payments API: loadPayments, card fields, wallets, confirmPayment and the next_action loop. See Browser client.

​
@tagadapay/plugin-sdk

React SDK for plugins that run inside TagadaPay’s plugin and funnel runtime.
  • Legacy, frozen: fixes only. It will not get Payments API features.
  • On a store switched to V3, it keeps working through the compatibility layer.
  • For new custom checkouts, use @tagadapay/headless-sdk.

​
Minimum versions

Older versions keep working. Upgrade so support can tell which SDK and version sent a request.

​
The X-Tagada-SDK header

Every SDK names itself on its requests:
The header is informational. Do not set it yourself in direct HTTP calls.

​
SDKs and API versions

V2 has no dated versions: any supported SDK version talks to it. The Payments API is dated: @tagadapay/core-js/payments-v3 sends the Payments-Version it was built against (2026-11-01 in 3.7.0), so upgrading the package is how you move to a newer API version. See Versioning.