---
title: "Growing your Stripe integration With Event Destinations"
description: "Stripe Event Destinations, now in general availability and rolling out to all accounts, lets companies extend payment workflows without changing existing integrations. The post explains how Stripe events can be sent either to an AWS account through Amazon EventBridge or to a webhook endpoint, with EventBridge routing selected events to services such as AWS Lambda, Step Functions, and SQS. Event filtering, logging, transformation, and built-in security reduce the need to operate webhook servers and verify signatures in application code. Serverless Lambda functions can add custom logic and connect to DynamoDB, S3, or SNS, supporting examples including date-limited memberships, partial student payments, and real-time tipping broadcasts through AWS IoT Core and WebSockets. The resulting architecture is presented as flexible and scalable for variable or growing event volumes while preserving the underlying Stripe integration."
---

# Growing your Stripe integration With Event Destinations

[Stripe](https://yomu.fyi/company/stripe) · Ben Smith · Oct 31, 2024

**Type:** Explainer

## Summary

Stripe Event Destinations, now in general availability and rolling out to all accounts, lets companies extend payment workflows without changing existing integrations. The post explains how Stripe events can be sent either to an AWS account through Amazon EventBridge or to a webhook endpoint, with EventBridge routing selected events to services such as AWS Lambda, Step Functions, and SQS. Event filtering, logging, transformation, and built-in security reduce the need to operate webhook servers and verify signatures in application code. Serverless Lambda functions can add custom logic and connect to DynamoDB, S3, or SNS, supporting examples including date-limited memberships, partial student payments, and real-time tipping broadcasts through AWS IoT Core and WebSockets. The resulting architecture is presented as flexible and scalable for variable or growing event volumes while preserving the underlying Stripe integration.

## Context

Stripe’s pre-built payment features may not cover every company-specific workflow, while modifying an existing Stripe integration can be disruptive. The post addresses the need to add custom payment behavior, reduce webhook infrastructure overhead, and support variable or growing event volumes.

## Approach / What changed

Use Stripe Event Destinations to send events to Amazon EventBridge, then filter, route, and transform them for AWS services such as Lambda, Step Functions, SQS, DynamoDB, S3, SNS, and AWS IoT Core. Serverless functions implement custom logic for subscription dates, partial payment schedules, and real-time tipping broadcasts without changing the underlying Stripe integration.

## Takeaways

- EventBridge can route Stripe events directly to AWS Lambda, Step Functions, or SQS, avoiding the need to manage webhook server-side code and endpoint scalability.
- Lambda functions can respond to Stripe events with custom logic, including calculating subscription end dates or creating subscription schedules and invoice metadata.
- AWS IoT Core and WebSockets can distribute successful payment or tipping events to connected viewers in real time, with EventBridge and IoT Core supporting increasing event volumes.

**Tags:** [Architecture](https://yomu.fyi/topic/architecture), [AWS](https://yomu.fyi/topic/aws), [Scalability](https://yomu.fyi/topic/scalability), [Serverless](https://yomu.fyi/topic/serverless)

- Source: [Stripe](https://stripe.dev/blog/growing-your-stripe-integration-with-event-destinations)
- Source URL: https://stripe.dev/blog/growing-your-stripe-integration-with-event-destinations
- Ingested by Yomu: 2026-08-28T08:56:52.975Z

[Read original post](https://stripe.dev/blog/growing-your-stripe-integration-with-event-destinations)