# Connecting Stripe and other integrations

> What the Stripe connection imports, how the key is protected, how to sync, and how to disconnect and erase everything.

- Canonical: https://help.enisa.ai/en/cuenta-y-facturacion/integraciones
- Updated: 2026-08-26
- Language: en-US
- Versión en español: https://help.enisa.ai/cuenta-y-facturacion/integraciones.md

Under **Settings → Integrations**, you can connect a Stripe restricted key to propose historical company data without uploading a ledger. The connection is optional, read-only and requires explicit consent.

## What the connection reads

- Customers, charges, refunds and invoices needed to calculate monthly aggregates.
- No more than the previous 24 months.
- Aggregate amounts and counts: no general ledger or full card data is imported.

The screen shows the exact permissions before you connect. Full secret keys and keys with write access are rejected.

## Connecting and syncing

1. In Stripe, create a **restricted key** with the listed read permissions.
2. Paste it into enisa.ai, tick the consent box and press **Connect**.
3. Press **Sync** whenever you want to refresh the aggregates. The date and result of the latest attempt are shown.
4. Review proposed data in your knowledge base. A sync never turns a proposal into an accepted fact.

The key is encrypted before storage and is never shown again or written to logs.

## Disconnecting and erasing

Press **Disconnect** to revoke the connection and atomically purge the credential and imported data. You can then connect a different key from scratch.

## What about Holded?

Holded is shown as unavailable. We do not ask for or store a key until the approved accounting adapter exists; the integration fails closed and never pretends that a sync succeeded.