Switch to live
1
Get live keys
Ask [email protected] 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 frompayment.completed, areturn_urlredirect orcheckout_session.status. See Fulfilment. - Amount mismatches are handled. You never fulfil when
amount_mismatchistrue. - Webhooks are robust. You verify the signature against the raw body, answer
2xxwithin 10 seconds, deduplicate on the eventid, ignore lowerversions and process asynchronously. - Every
POSThas anIdempotency-Keyderived from your own records and reused on retries. See Idempotency. - Every outcome is covered: declines and retries, pending payments, 3D Secure, full and partial refunds, and disputes. See What to test before going live.
-
429is handled. You wait forRetry-After. See Rate limits. - Secrets are safe. No secret key in client code, no
client_secretin logs or analytics, and the webhook secret stored securely. See Security. - Your pages are protected with HTTPS,
Strict-Transport-Securityand a Content Security Policy that allows Kalixo.js. See Kalixo.js. - You can reconcile. You can download the
financial_transactionsreport 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.failedrates 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. Kalixo adds fields and event types without a new API version, so ignore the ones you do not know.