---
title: "Stripe Connector | Tajo"
description: "Tajo's Stripe connector reads customers, invoices, products, prices, subscriptions and events, and updates customer identity fields. It does not read charges."
url: https://tajo.io/docs/connectors/ecommerce/stripe/
markdown: https://tajo.io/docs/connectors/ecommerce/stripe.md
lang: en-US
author: "Set Noa"
author_url: https://tajo.io/set-noa/
robots: noindex
---

# Stripe Connector

[Set Noa](https://tajo.io/set-noa/)

Connector status: Live Verified. Tajo runs this connector today.

| Source field | Destination field | Sample value |
| --- | --- | --- |
| `record.id` | `source_id` | `record_1042` |
| `record.updated_at` | `updated_at` | `2026-10-18T08:00:00Z` |
| `record.value` | `value` | `sample_value` |

This connector has passed a live run. It reads Stripe customers, invoices, products, prices, subscriptions and events, and it writes one thing: a customer’s identity fields.

## What the connector does

- Reads customers: email, name, phone, billing address, currency and metadata.
- Reads invoices, which Tajo treats as the orders, with status, totals and the customer’s email and name.
- Reads products, prices and subscriptions.
- Reads the events log of the last 30 days. That is how a change to an existing customer or invoice reaches a sync.
- Updates a customer’s email, name, phone, description, billing address and metadata. This is the connector’s only write, and it changes data in your Stripe account.
- Authenticates with a Stripe secret key or a restricted key, and pins every request to one Stripe API version.
- Never treats a Stripe customer as a marketing contact on its own: Stripe stores no marketing consent on a customer, so consent has to come from another source.

## What the live run checked

On 15 October 2026, a run in a Stripe test-mode sandbox created test customers, products, prices, an invoice and a subscription. The connector read each of them back, updated one customer and found that change in the events log. No charge, payment or refund endpoint was called.

## Not in the connector

- Charges and payment intents. The connector does not read them.
- Real-time webhooks. Changes arrive when a sync reads them.
- Creating or changing payments, invoices or subscriptions