Sepia
What Sepia stores when you connect Stripe — and what it does not.
What Sepia stores
- Your webhook signing secret (
whsec_…) so Sepia can verify events you send from your own Stripe account. - Optionally, a restricted key (
rk_…) you choose to paste — only if you want Sepia to call Stripe APIs later. Webhook verify does not require it. - Commerce Event facts from those webhooks (sale, refund, cancel, dispute): Buyer email, product id, and related order identifiers needed for Entitlement and Kit Projection.
What Sepia does not store
- No card numbers — Sepia never sees PAN, CVC, or full payment method details.
- No payouts — Sepia is not a Merchant of Record and does not move money or hold balances.
- No Stripe Connect platform OAuth; you keep the webhook on your own account.
Why the webhook signing secret
Stripe signs each delivery. The secret lets Sepia confirm the payload came from your endpoint configuration — not a forged POST. Without it, anyone who guessed your webhook URL could append fake Commerce Events.
Connect in four steps
- Create a webhook endpoint aimed at the URL on your Sepia connect page.
- Listen for purchase and refund events (
checkout.session.completed,charge.refunded). - Paste that endpoint’s
whsec_…into Sepia. Other apps (Zapier, etc.) need their own endpoints and secrets. - Put
metadata.product_idon Checkout/Charge and map the same string to a Kit tag on the connect page.
Retention intent
Credentials stay only while Stripe is connected for that Creator. Commerce Events remain in the Ledger so you can Replay Entitlement and audit Kit Projection; they are order facts, not payment instruments.
This is a Design Partner trust page, not a SOC 2 report.
Revoke path
On your connect page, use Disconnect Stripe. That clears stored Stripe credentials and stops ingest for that Rail until you connect again. You can also delete the webhook endpoint in your Stripe Dashboard.