Connect Cakto

Connecting Cakto sends every approved sale, renewal, refund and chargeback to Clakta as it happens. It takes one webhook: Clakta gives you a URL and a secret, and you paste both into a new webhook in Cakto.

Connect

1. Go to Project settings → Sales platforms.
2. Choose Cakto, name the connection, and click Create connection. Clakta generates a webhook URL and a secret — copy both.
3. In Cakto, create a new webhook. Paste the URL into its URL field and the secret into its Secret field.
4. Select every product you sell, and enable the six events below.
5. Save the webhook in Cakto, then click Finish in Clakta.

The connection is usable the moment it is created — the card reads Added straight away — and sales start arriving once the webhook is saved on Cakto's side.

Events to select

Extra events are harmless — anything Clakta does not handle is acknowledged and ignored. But leave Assinatura renovada out and you only ever see the first payment of a subscription, because a renewal never fires Compra aprovada.

Attribute sales to visitors

A Cakto checkout link has one free field, sck, and Clakta reads the visitor's session from it. Build the link with the session id of the page the visitor is already on:

const url = `https://pay.cakto.com.br/abc123?sck=${clakta.getSessionId()}`

That needs the tracking script on the page — and with it in place, a visitor clicking a Cakto link on your site gets sck appended automatically. You only need to build the URL yourself for a checkout the script can't see, such as a server-side redirect, where clakta.decorateCaktoUrl(url) does the same job.

Sales still arrive without it; they are just recorded as unattributed, so you see the revenue but not the traffic behind it. Projects in privacy-friendly mode have no session id to send, and record no buyer name or email either.

What gets recorded

Revenue in reais (Cakto settles only in BRL), the buyer's name and email, the product and its offer, the payment method, the approval date, and the attribution from sck and any UTMs on the link. Pix, boleto and cards are recorded by name; PicPay and Open Finance read Other.

Cakto delivers a whole checkout as a single event, so a purchase sold with order bumps arrives as the main product plus each bump beside it. Clakta records each one as its own order, which is how Cakto treats them too — a bump can be refunded on its own without touching the rest of the purchase. They share a buyer and a session, so attribution credits the same visit for all of them, and each counts towards your plan's monthly orders.

Refunds and chargebacks

Both mark the order refunded and record the date the money moved. A refund for a sale that predates the connection is ignored rather than invented — Clakta never saw the original order, and creating one on the refund date would report revenue on a day it never happened.

Disconnect

Remove the connection from Project settings → Sales platforms. Deliveries stop being accepted immediately, and orders already recorded stay where they are. Delete the webhook in Cakto too, so it stops retrying against an endpoint that no longer exists.

Troubleshooting