Authentication - Ionic Docs

Customer-facing API requests use secret API keys from trusted server environments.

import { Ionic } from "@ionicfi/sdk";

const ionic = new Ionic({ token: process.env.IONIC_SECRET_KEY });

const sessions = await ionic.checkout.sessions.list();

curl https://api.ionicfi.com/v1/checkout/sessions \
  -H "Authorization: Bearer sk_v1_test_..."

Keep secret keys on your server. Do not place them in browsers, mobile apps, hosted checkout pages, or logs.

Hosted checkout

Your backend creates checkout sessions and payment links. Ionic-hosted checkout handles buyer payment collection and confirmation without requiring you to send raw card data to the API. Create checkout resources on your server, redirect the buyer, and retrieve the completed session from your server before fulfilling the order.

Retry behavior

Authentication identifies the caller. Idempotency identifies a retryable operation. For create and refund calls, send the same Idempotency-Key when retrying the same operation. See Idempotency for the retry model.