> ## Documentation Index
> Fetch the complete documentation index at: https://developer.kalixo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Go live

> What to switch, register and check before you take real payments.

Going live is mostly switching keys and registering your production details, plus a last
check of the things that must be right before real money moves.

## Switch to live

**1. Get live keys**

Ask [integrations@kalixo.io](mailto:integrations@kalixo.io) for live keys
(`kc_sk_live_...` and `kc_pk_live_...`). The live API accepts only live keys
(`api_key_mode_mismatch` otherwise). Keep the secret key on your server.

**2. Register your live domains**

Send Kalixo every domain that shows the checkout or receives the shopper back. Publishable
keys work only from registered domains (`origin_not_allowed` otherwise), and a
`return_url` must be on one of them (`return_url_not_allowed` otherwise).

**3. Create a live webhook endpoint**

Register your production URL with the live secret key, store the returned `secret` (shown
once) and subscribe to the events you handle.

**4. Use the live API**

With a live key, `@kalixo/checkout-node` and Kalixo.js call `https://checkout.kalixo.io`
automatically. If you call the API directly, switch from
`https://sandbox.checkout.kalixo.io` to `https://checkout.kalixo.io`.

## Check before launch

* [ ] **Fulfil on your server only.** You read the payment with `GET /v1/payments/{id}`
  before you deliver, never from `payment.completed`, a `return_url` redirect or
  `checkout_session.status`. See [Fulfilment](https://developer.kalixo.io/checkout/guides/fulfilment.md).
* [ ] **Amount mismatches are handled.** You never fulfil when `amount_mismatch` is `true`.
* [ ] **Webhooks are robust.** You verify the signature against the raw body, answer `2xx`
  within 10 seconds, deduplicate on the event `id`, ignore lower `version`s and process
  asynchronously.
* [ ] **Every `POST` has an `Idempotency-Key`** derived from your own records and reused on
  retries. See [Idempotency](https://developer.kalixo.io/checkout/concepts/idempotency.md).
* [ ] **Every outcome is covered**: declines and retries, pending payments, 3D Secure, full and
  partial refunds, and disputes. See [What to test before going live](https://developer.kalixo.io/checkout/concepts/testing.md#what-to-test-before-going-live).
* [ ] **`429` is handled.** You wait for `Retry-After`. See [Rate limits](https://developer.kalixo.io/checkout/concepts/rate-limits.md).
* [ ] **Secrets are safe.** No secret key in client code, no `client_secret` in logs or
  analytics, and the webhook secret stored securely. See [Security](https://developer.kalixo.io/checkout/concepts/security.md).
* [ ] **Your pages are protected** with HTTPS, `Strict-Transport-Security` and a Content
  Security Policy that allows Kalixo.js. See [Kalixo.js](https://developer.kalixo.io/checkout/guides/kalixo-js.md).
* [ ] **You can reconcile.** You can download the `financial_transactions`
  [report](https://developer.kalixo.io/checkout/guides/reports.md) and match it to your orders.
* [ ] **You know how to rotate secrets**: a secret key (deploy the new one, then ask Kalixo to
  revoke the old one) and a webhook secret (both secrets sign for 24 hours).

## After launch

* Watch `payment.failed` rates and decline codes. A sudden rise can mean card testing.
* Watch your webhook endpoint. If it was down, catch up with `GET /v1/events`.
* Follow the [changelog](https://developer.kalixo.io/checkout/changelog.md). Kalixo adds fields and event types without a
  new API version, so ignore the ones you do not know.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.