Yes. Krokul CRM integrates with Stripe. The manager sends a payment link straight from the deal, the completed Checkout Session comes back as a payment fact that closes the payment plan, and a refund in Stripe shows up on the same deal. The link between the two runs through the Krokul app in Zapier, Make, n8n or Albato, or through the Krokul API and webhooks.
Automation platformsZapierMaken8nAlbato
The manager opens the payment plan of a deal and chooses Stripe as the provider. Krokul creates a Stripe Checkout Session for that line, with the amount, the currency and the deal reference in its metadata, and shows the link with its expiry. The link goes to the client in the next email or message.
When the client pays, Stripe sends checkout.session.completed to the Krokul connector. Krokul checks the Stripe signature, finds the plan line by the metadata and records a payment fact against it. The client company debt drops, payment.received fires, and invoice.paid follows once the invoice is covered.
A refund issued in the Stripe Dashboard arrives as a refund of the Charge. Krokul finds the payment it recorded earlier by the Stripe ID and books a refund linked to it. The deal shows the net amount, and the invoice reopens if the refund leaves it short.
For clients billed through Stripe Invoices, invoice.payment_failed creates a task for the account manager on the deal. The task names the Invoice and the amount, so the client hears about the problem from a person before the next reminder.
The first payment link for a client company creates the Stripe Customer with the company name and billing email, and Krokul stores the Customer ID as an external key. Later links reuse the same Customer, so Stripe keeps one payment history per client.
| Stripe | Direction | Krokul | When |
|---|---|---|---|
| Checkout Session (payment link) | Krokul → Stripe | Payment plan line on the deal | The manager sends a payment link from the deal |
| Customer | Krokul → Stripe | Client company | The first link for a client company |
| Checkout Session completed | Stripe → Krokul | Payment fact closing the plan line | Stripe event checkout.session.completed |
| Invoice paid | Stripe → Krokul | Payment fact on the invoice | Stripe event invoice.paid |
| Refund of a Charge | Stripe → Krokul | Refund linked to the recorded payment | A refund is issued in Stripe |
| Invoice payment failed | Stripe → Krokul | Task on the deal | Stripe event invoice.payment_failed |
Yes. Krokul integrates with Stripe through the Krokul app in Zapier, Make, n8n and Albato, and through its API and webhooks.
Yes. Krokul creates a Stripe Checkout Session for the chosen payment plan line and shows the link on the deal. The paid session closes that line by itself.
Stripe sends amounts in the smallest unit of the currency, such as cents. Krokul stores main units, so the connector divides by the currency factor before it writes the payment.
Krokul books a refund linked to the original payment. If the invoice is no longer covered, it becomes unpaid again, and invoice.paid can fire after the next full payment.
Subscriptions, disputes and payouts to your bank stay in Stripe. Stripe reports amounts in the smallest currency unit, and Krokul converts them to main units on the deal.
Tell us which service you use and what should move between it and Krokul. We reply with the way to do it and when it will be ready.
Request received. We reply to your email.
Stripe is a trademark of Stripe, Inc. Krokul is not affiliated with Stripe.