# Connecting Stripe

> The native Stripe integration — what it announces (payments, subscription invoices and refunds), why Konverda only reads and never moves money, how it recognises the person (phone, then email), what payments without a contact are, and how to build the rule that thanks somebody after a payment.

Fuente / source: https://soporte.konverda.com/en/docs/developers/stripe
Idioma / language: en
Actualizado / updated: 2026-09-09

---
Stripe is a **native integration**: you authorise Konverda once on Stripe's own page and, from then on, every payment and every refund on your account reaches Konverda instantly. No Zapier in between, no URL to paste.

The card is in the app, under **«Ajustes → Integraciones → Stripe»** (settings → integrations → Stripe).

## Konverda only reads your Stripe {#read-only}

This is the first thing worth knowing, because it decides everything else.

Konverda asks Stripe for **read-only** access. With that authorisation Konverda can **see** your payments, your subscription invoices and your refunds, and it **cannot**:

- charge anybody or create a charge;
- refund money or cancel a subscription;
- change your products, your prices or your settings;
- touch anything on the marketplace or payouts side.

This is not a promise of good behaviour: it is the permission Stripe granted. Even if somebody tried from inside Konverda, Stripe itself would refuse. **Konverda never moves money.**

## Connecting {#connect}

:::pasos
1. On the Stripe card, press **«Conectar»** (connect) and authorise with the business's Stripe account. Only an owner can: the connection belongs to the **account**, not to a workspace.
2. On return, the workspace you connected from is linked. Another workspace of the same account links itself from its own card with **«Vincular»** (link).
3. The card turns to **«Conectada»** (connected) with your Stripe account's name, and shows when the last payment arrived.
:::

It works with any Stripe account — no particular plan is required.

## What each notification carries {#events}

| What happens in Stripe | What Konverda sees |
|---|---|
| A Checkout or Payment Link charge | **«Pedido pagado»** (order paid) |
| A charge made from your own integration | **«Pedido pagado»** |
| A subscription invoice charged | **«Pedido pagado»**, marked as a subscription |
| A refund, full or partial | **«Pedido reembolsado»** (order refunded) |

Each notification carries the amount and currency (Konverda does the cents arithmetic for you), the person's email and name and — when Stripe has it — their phone, the line items when the payment carries them, and the link to the receipt or invoice.

**A payment is recorded exactly once.** Stripe sends several notifications for one charge (the payment intent, the Checkout session, the subscription invoice); Konverda recognises them as the same payment and records **one sale**, with the richest description among those that arrived.

## The rules: payments and refunds {#rules}

A Stripe payment is **not a new notification to learn**: it is the very «Pedido pagado» Konverda already used for shops. That is why the rules you already had keep working the day you connect Stripe.

:::pasos
1. In **«Automatizaciones»**, create a rule with the **«Pedido pagado»** trigger.
2. Choose what to do: a flow that says thank you, that delivers an access, or that tags the contact.
3. For returns, another rule on **«Pedido reembolsado»** — for instance a flow that asks what went wrong.
:::

If you want to narrow it down by product, the order trigger accepts a list of products: Konverda creates the record for each Stripe product the first time it sells, with nothing for you to set up.

Rules and flows fired by a payment follow the same laws as the rest of the platform: they only reach **marketing contacts** (see [The marketing opt-in](/en/docs/contactos-y-consentimiento/el-opt-in-de-marketing)), and no message leaves outside the 24-hour window without an approved template.

## How Konverda finds the contact {#matching}

The order is fixed: **phone first; then email.**

- **By phone**, if Stripe carries one. Stripe only asks for a phone when you enable it in Checkout, so most of the time it is the email that decides.
- **By email**, which is the field Stripe always has. It must already exist on the contact.
- **A payment never creates a contact.** Paying is not WhatsApp consent: if nothing matches, the payment is still recorded as a sale (it counts towards your revenue) and shows up under **«Pagos sin contacto»** (payments without a contact) for you to say who it was.
- Matching is per workspace. If the account has several linked workspaces, somebody known in two of them is found in both.
- One email on two contacts of the same workspace is not a match: Konverda would rather not guess than half-guess.

A payment does not change a contact's tier either: it enrols nobody into marketing and lifts no opt-out. It records the fact and nothing else.

## Payments without a contact {#unmatched}

The Stripe card lists the payments that arrived without Konverda being able to recognise the person: the name, the email they paid with, and when. **Konverda never links on a similar name — you decide**, because linking the wrong person fires a rule at the wrong human.

:::pasos
1. Press **«¿Quién es?»** (who is this?) on the payment. The contact picker opens already filtered by the name on the payment; you can search by phone or by part of the name if it does not show up.
2. Leave **«Guardar el email … en este contacto»** ticked if you want the next payment to be recognised by itself. If that contact already had a different email, Konverda keeps it and tells you.
3. Press the contact. The sale is attributed to that person and your «Pedido pagado» rule **fires right then**, exactly as if it had matched on arrival.
:::

If the payment belongs to nobody on your list, **«No es un contacto»** hides it: the sale still counts towards your revenue, and no contact is created or changed.

## Disconnecting and reconnecting {#disconnect}

**«Desconectar»** revokes the authorisation at Stripe and **unlinks every workspace** of the account. The rules stay where they were, with nothing to fire them, until an owner connects again. Sales already recorded are untouched.

If Stripe stops accepting the authorisation (somebody revokes it from Stripe, the application is removed), the card turns to **«Desconectada»** and the owners get a notification in the app and by email. **Reconnecting** takes a minute and touches no rule.