Receive Stripe Webhook
The one write path for Stripe-moved dollars, both directions. Every dollar that lands — manual Checkout or the auto-top-up charge — arrives as a succeeded payment intent, keyed by the event id; every dollar Stripe pulls back — a refund, or a dispute we lost — arrives as a clawback, keyed by the refund or dispute id so partial refunds land separately. A $0 card check arrives as a succeeded setup intent and unlocks the welcome credit, and a manual top-up unlocks it too (the card is proven either way; an auto charge reuses a card already checked). A fraud signal — the card network's early fraud warning, or a dispute lost on a card payment — forfeits the welcome credit of the charged org and of the org that card unlocked, and blocks the card. Redeliveries are clean no-ops on every key; RPC trouble on the resume start or Stripe trouble on the card read propagates as a 5xx so Stripe redelivers and retries it.
Request
- Base URLhttps://api.teaflask.com (the document declares no server; this is the origin it was published from)
- URLhttps://api.teaflask.com/api/v1/webhooks/stripe
- Authnone declared
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.