Test mode to going live

Everything in Kling works in the test environment from the moment you sign up. Real payments need a verified account and, for cards, an approved agreement with a card acquirer. Kling handles the application for you; this page explains the steps.

Works the moment you sign up

• The whole dashboard: payment links, subscriptions, products, customers, Kling POS, online bank claims.
• A test API key (sk_test_...) and the full API, SDKs, CLI and MCP server.
• Test card payments. Use 4111 1111 1111 1111 for a successful payment and 4000 0000 0000 0002 for a declined one. Any other 16-digit number also succeeds.

No verification, no card and no contract is needed for any of this.

Apply to go live

Open the dashboard and choose Go live. The application asks for:

• whether you sell as a company or as an individual, and the kennitala (company details are filled in from the kennitala),
• name, address and phone number, and your website if you sell from one,
• the bank account payouts go to (you keep your own bank),
• who signs on the company's behalf,
• what you sell, described precisely,
• expected card volume and average payment size.

Card payments: the acquirer's approval

The acquirer is the company that processes the card payment itself. Kling applies to the acquirer on your behalf and handles the correspondence. You complete a due diligence form and sign the agreement. The live environment opens once the acquirer approves the application.

That last part is not fully in Kling's hands, and the time it takes depends mostly on how quickly the paperwork comes in. You speed it up most by:

• completing the due diligence form right away, and having everyone else with signing authority do the same,
• signing the agreement as soon as it arrives,
• describing what your business does precisely, not in one word,
• if you sell online, having the required information on your website (below),
• answering email from the acquirer, and checking your spam folder.

You can ask where things stand at any time at hallo@kling.is.

What your website must show

The acquirer requires all of this on your site before approval:

• a description of what you sell,
• terms covering delivery, refunds and cancellation,
• company name, kennitala, address, phone number and email,
• a privacy policy,
• the currency prices are shown in,
• the Visa and Mastercard marks in colour wherever payment methods are listed.

Online bank claims

Online bank claims don't go through a card acquirer. You sign the claims agreement as part of the application, so claims can be approved first and you can start sending them while you wait for card payments. After approval, set up bank claims and add a payment card for Kling's per-claim fee; the dashboard walks you through both. See Online bank claims.

Switching your integration to live

1. Once a payment method is approved, create a live key (sk_live_...) on the API Keys & Docs page.
2. Replace the test key in your server's environment. Nothing else in the code changes.
3. Set up your webhook endpoint again for the live environment. Test and live webhooks are separate, with separate signing secrets.
4. Take one small real payment and refund it, to see the whole flow end to end.

Pricing

No setup fee and no fixed monthly cost; you pay per payment. See pricing.