SDKs - Ionic Docs

Ionic ships three packages. Which one you install depends on where the code runs: your server can hold a secret key; the browser must never see one.

Package	Runs	Holds	Use it for
`@ionicfi/sdk`	Your server	Secret key (`sk_…`)	Every API call: sessions, payments, customers, webhooks verification
`@ionicfi/js`	The browser	Session credentials only	Mounting embedded checkout on your page
`@ionicfi/react`	The browser (React)	Nothing extra	`<CheckoutEmbed>`: embedded checkout as a component

The server SDK’s methods and types match the API reference exactly. The browser packages load their runtime from Ionic’s CDN at mount time, so security updates reach your integration without a redeploy.

Typical setups

Backend + hosted checkout: @ionicfi/sdk only. Create sessions server-side, redirect the buyer, fulfill from webhooks.
Backend + embedded checkout (React app): @ionicfi/sdk on the server, @ionicfi/react in the frontend.
Backend + embedded checkout (any other frontend): @ionicfi/sdk on the server, @ionicfi/js (or a plain script tag) in the frontend.
Not on Node? Every SDK call has a raw HTTP equivalent in the API reference; the guides show both side by side.

​Typical setups

Typical setups