Guide · Stripe → Microsoft Teams · Verified November 1, 2026
Stripe to Microsoft Teams webhook guide
Short answer: One Stripe endpoint verifies each delivery, a destination filter keeps the events in this guide, and every match is delivered to Microsoft Teams with its own retry schedule and delivery log.
Some payments need the customer to finish 3-D Secure, and finance wants those in Teams rather than in an inbox. This pairing posts one card per action-required invoice with the hosted invoice link, so someone can chase it before the subscription lapses.
At a glance
id when it starts with evt_, stable across Stripe retries.Target: Microsoft TeamsA Hooks Microsoft Teams destination POSTs a MessageCard to an incoming webhook URL from an Office 365 Connector, Power Automate, or Workflows; the URL is a project secret. Connectors answer 200 with the body 1, and Workflows answer 202.1. Configure the Stripe webhook
- In the Stripe Dashboard, open Developers → Webhooks → Add endpoint.
- Paste the endpoint's ingestion URL and select the events you need (invoice, checkout, subscription).
- Copy the endpoint's Signing secret (`whsec_...`) into the Hooks endpoint secret.
- Send a test event from the Stripe Dashboard and confirm it in the delivery log.
HMAC-SHA256 over <t>.<raw body>; any matching v1 signature passes. Five minutes between t and the current time.
2. Filter to the events that matter
Filters run per destination before rendering, so a non-matching event is stored with no delivery and no agent call. The rules below are the difference between a useful pairing and a noisy one.
Filter: payments that need action
{
"allow": [
{ "field": "event.type", "op": "equals", "value": "invoice.payment_action_required" }
]
}3. Configure the Microsoft Teams destination
A Hooks Microsoft Teams destination POSTs a MessageCard to an incoming webhook URL from an Office 365 Connector, Power Automate, or Workflows; the URL is a project secret. Connectors answer 200 with the body 1, and Workflows answer 202.
Destination: Microsoft Teams incoming webhook
{
"webhookUrl": "{{secret.TEAMS_WEBHOOK_URL}}",
"title": "Payment needs action: {{event.subject.title}}",
"text": "[Open invoice]({{event.subject.url}})",
"themeColor": "D93F0B"
}Secrets enter configs only as {{secret.NAME}} references; literal credentials are rejected. Full Microsoft Teams target guide
4. Verify the delivery and its retries
Send one real event from the source, then open Deliveries. A 2xx from the target means accepted, not finished. 408, 425, 429 and 5xx retry with backoff honoring Retry-After; other 4xx fail permanently with a named code. The rendered request is stored per attempt, so a bad field path is visible without re-sending.

The pitfall this pairing hits
An expired connector answers 401, not 404. A Teams connector that was removed or expired returns 401 with a body like Webhook has expired. Hooks treats it as a permanent failure and records the reason on the attempt, so the fix is a new webhook URL in the channel — retrying the delivery will not help.
Frequently asked questions
Do I need one endpoint per source or one per destination?
One endpoint per source. Each destination under that endpoint carries its own filter, template, retry schedule, and delivery log, so the same event can feed several targets without duplicate ingress URLs.
What happens while the target is down?
Retryable failures back off and retry within the destination's window; permanent 4xx failures stop immediately. Either way, the original event stays stored, so after fixing the target you replay the event instead of asking the source to send it again.
An expired connector answers 401, not 404
A Teams connector that was removed or expired returns 401 with a body like Webhook has expired. Hooks treats it as a permanent failure and records the reason on the attempt, so the fix is a new webhook URL in the channel — retrying the delivery will not help.