Stripe

Stripe is Shingo's primary revenue data source. It provides the billing events that power revenue attribution, connecting user behavior to actual dollar outcomes.

What Shingo reads

Charges

Payment amounts, status, and failure reasons

Subscriptions

Plan changes, upgrades, downgrades, cancellations

Customers

Account metadata for cohort segmentation

Invoices

Billing cycles, amounts, and payment status

Checkout Sessions

Conversion funnel data for checkout flows

Payment Intents

Payment flow outcomes and failure codes

Setup

1

Create a restricted key

In your Stripe Dashboard, go to Developers → API Keys → Create restricted key. Name it 'Shingo (read-only)'.

2

Set permissions to Read

Grant Read access to: Charges, Customers, Subscriptions, Invoices, Checkout Sessions, and Payment Intents. Do not enable Write on any resource.

3

Copy the key

The key will look like rk_live_... — copy it immediately, as Stripe only shows it once.

4

Paste in Shingo

In the Shingo onboarding flow, paste the key in the Stripe connector field. Shingo will verify the connection and begin ingesting data.

Shingo only needs read-only access. We never create charges, modify subscriptions, or write to your Stripe account in any way. The restricted key format (rk_live_) enforces this at the Stripe API level.

Key format

# Stripe restricted key (read-only)

rk_live_xxxxxxxxxxxxxxxxxxxxxxxx