Stripe
Receive Stripe webhooks in Tessel as typed, signature-checked events. Use them to chase failed invoices, reconcile payouts and issue refunds once a named person approves.
Payments
Category
Events
Sync mode
p95 420 ms
Latency
5 min
Setup time
What it can do
- Invoice paidWebhook
- Invoice payment failedWebhook
- Payout paidWebhook
- Dispute createdWebhook
- Charge refundedWebhook
- Subscription canceledWebhook
- Retrieve a customerRead
- Search chargesQuery
- Create a refundApproval
- Update a subscriptionWrite
- Create an invoice itemWrite
Overview
The Stripe connector registers a webhook endpoint on your account and turns each delivery into a typed event. Tessel verifies the Stripe-Signature header before anything runs, and the raw payload is kept in the trace of the run it started.
Finance teams use it to open a ticket in Zendesk when an invoice payment fails, to match payouts against bank lines in NetSuite and to post new disputes to a Slack channel with the evidence deadline attached.
Event coverage
Invoices, charges, refunds, payouts, disputes and subscriptions
Test mode and live mode on the same connection, kept apart in traces
Stripe Connect accounts, with the account ID on every event
How webhooks work
Tessel creates one endpoint per workspace region and subscribes only to the events your workflows use. Each event is checked against the API version pinned on the endpoint, so a field rename on Stripe's side never breaks a running workflow.
Idempotency
Every write sends an Idempotency-Key derived from the run and step, so a retried refund never refunds twice. Stripe can deliver an event more than once, and Tessel drops duplicates by event ID.
Permissions needed
Use a restricted key rather than your secret key. It needs read access to the objects your triggers watch. Write access is only required for refunds, subscription updates and invoice items.
Webhook Endpoints: Writeso Tessel can register its endpointCharges,CustomersandInvoicesset toReadRefunds: WriteandSubscriptions: Writeonly if you use those actions
Five steps. About five minutes.
Most of the time goes into creating the restricted key. Tessel checks each scope before you move on.
- Create a restricted key with the scopes belowStripe2 min
- Paste the key and choose test or live modeTessel1 min
- Choose the events Tessel should subscribe toTessel1 min
- Name an approver and a backup for refundsTessel1 min
- Send a test event with the Stripe CLI and watch it arriveVerify420 ms
Your payments, in a workflow today.
Connect Stripe on the free plan. Up to three builders and 10,000 runs a month, no card required.