Skip to main content
You integrate once, with Kalixo.js or the hosted checkout, and Kalixo shows the shopper the payment methods that fit the checkout session. You never add a method-specific SDK, and new methods need no change on your side. Kalixo chooses the methods from the session’s country and currency and from what is enabled for your account. A method that does not fit the session is not shown.
Kalixo configures which payment methods your account offers. Ask [email protected] which methods are available for your markets, or to enable one.

How methods behave

For every kind, wait for payment.captured and read the payment on your server before you deliver. The shopper may close the tab before returning from a redirect. See Fulfilment.

Create sessions that fit

  • Set country to the shopper’s country and currency to the currency you sell in. Local methods appear only for their home market and currency.
  • The shopper always pays the session amount. If a provider reports a different amount, Kalixo sets amount_mismatch: true and reverses the payment. See Amount integrity.
  • The payment’s payment_method.type tells you which method the shopper used.

Capture and refunds

Many redirect and bank methods capture at authorisation: they do not support manual or partial capture. Use capture_method: "manual" only when the methods on your account support it, typically cards. See Captures, cancellations and refunds.

Testing

The sandbox test cards are on the Testing page. If Kalixo routes your sandbox account to a payment provider’s test environment, the checkout shows that provider’s test form, and Kalixo integrations sends you the test data for each method.