Stripe integration

Connect Stripe to Kirora to record supported successful payments as purchase events on the customer who paid. Use it to thank customers, find your best buyers and see payments attributed to campaigns and journeys.

Before you start

Maintained by: Kirora. Kirora sets up and looks after the webhook endpoint in your Stripe account.
Availability: built in to Kirora, with nothing to install.
Direction: into Kirora, from Stripe. Kirora writes nothing to Stripe except creating and removing its own webhook endpoint.
You need: a Stripe account and its secret key, or a restricted key, from Stripe’s Developers › API keys, and the admin or owner role in Kirora. For plans, see Which plans include it?

What it does

Each successful charge (Stripe’s charge.succeeded) becomes an Order Completed event on the customer who paid, with order_id (the payment intent), total in the currency’s main unit, such as 12.50, and currency.
Each payment is recorded once, even if Stripe reports it again.

Matching: by the charge’s email address: the billing email, or the receipt email when there’s no billing email.
New payers: a payer who isn’t a contact yet is added without marketing consent. Transactional email can reach them; your marketing email waits until they agree to it.

Connect Stripe

In Stripe, go to Developers › API keys and copy your secret key (it starts sk_), or create a restricted key with Webhook Endpoints: Write, the only permission Kirora uses.
In Kirora, go to Integrations › Stripe.
Paste it into Secret key and choose Connect Stripe.

Kirora checks the key and sets up the connection in your Stripe account for you, so there’s nothing to paste back into Stripe.

Test it

Connect with a key from Stripe’s test mode (it starts sk_test_ or rk_test_).
In Stripe’s test mode, take a test payment with an email address of your own.
In Kirora, Integrations › Stripe shows the time under Last payment received, and that contact’s Timeline shows the Order Completed event.
When you’re ready, choose Replace key and paste your live key. Kirora removes the test connection from your Stripe account.

Use it for

A thank-you or review request after an order: start a journey on Order Completed. See Build a journey.
Your best and lapsed buyers: build a segment of customers who ordered recently, or haven’t ordered in 60 days. See Segments.
Payments attributed to campaigns and journeys: a conversion goal attributes the orders that follow a message within its window to that campaign or journey. See Understand your reports.
Revenue goals: measure revenue or average purchase value against a target, from the payments Stripe sends. See Goals.

Limitations

Only successful charges are recorded. Refunds, disputes and failed payments don’t appear.
A charge with no email address is skipped, since there’s no one to match it to.
Payments made before you connect aren’t imported.
A workspace connects one Stripe account.

Get help

If payments stop arriving, Integrations › Stripe shows the last error, and Kirora tells admins and the owner that Stripe data isn’t coming through. Stripe retries delivery of a webhook that Kirora could not accept, so it’s recorded once the problem is fixed; a new key clears a key error. For anything else, contact us.

Questions

Which plans include it?

Available on Starter and above. On the Free plan, connecting Stripe asks you to upgrade first.

How do I change the key or disconnect?

On Integrations › Stripe, choose Replace key or Disconnect. Disconnecting also removes Kirora’s connection from your Stripe account. Events already recorded stay.

Next steps

Connect an integration: the step-by-step guide in the docs.
Reports and revenue: see payments attributed to campaigns and journeys.
Goals: track revenue targets against the pace to reach them.