Importing sales data from Stripe into AWS

Hidetaka OkamotoMar 4, 2025

Source: Stripe
Published: Mar 4, 2025
Added to Yomu: Aug 28, 2026

Summary

The article presents a low-code method for analyzing Stripe business and customer data and moving scheduled report results into AWS. Stripe Sigma lets users query payment, subscription, and plan-related data with SQL, while Sigma Assistant can generate and execute queries from natural-language prompts such as cancellation analysis. For delivery, the article uses the sigma.scheduled_query_run.created event and Stripe's Event Destination to Amazon EventBridge, where a partner event bus and event rule trigger AWS services without a separate public webhook API. Its Lambda example downloads the report CSV with the Stripe API key, parses it into JavaScript objects, and publishes the result through Amazon SNS; the same event-driven pattern can support Lambda, Step Functions, or Glue workflows.

Context

The article addresses the need for more detailed Stripe payment, subscription, sales, and customer analysis than dashboard reports provide, along with the security complexity of exposing a public webhook endpoint for SaaS event delivery. It also describes the need to combine Stripe data with other business data in AWS for analysis and planning.

Approach / What changed

Use Stripe Sigma and Sigma Assistant to query data with SQL or natural-language prompts, schedule analyses, and emit sigma.scheduled_query_run.created events. Configure Stripe Event Destinations to send those events to an Amazon EventBridge partner event bus, associate the event source, and create a matching rule. An AWS Lambda function then downloads the report CSV, parses it into JavaScript objects, and publishes the processed data to Amazon SNS.

Takeaways

Sigma Assistant can generate and execute SQL from prompts such as identifying subscription-cancellation reasons by product over the past year.
Stripe Event Destinations and Amazon EventBridge send Sigma report events into an AWS account, avoiding the need to expose and secure a separate public webhook API.
The example Lambda workflow retrieves the report CSV, parses it into JSON-like JavaScript objects, and publishes the result to an Amazon SNS topic.

AWS Data Pipelines LLMs Serverless

Read original post

Importing sales data from Stripe into AWS

Hidetaka OkamotoMar 4, 2025

Source: Stripe
Published: Mar 4, 2025
Added to Yomu: Aug 28, 2026

Summary

Context

Approach / What changed

Takeaways

Sigma Assistant can generate and execute SQL from prompts such as identifying subscription-cancellation reasons by product over the past year.
Stripe Event Destinations and Amazon EventBridge send Sigma report events into an AWS account, avoiding the need to expose and secure a separate public webhook API.
The example Lambda workflow retrieves the report CSV, parses it into JSON-like JavaScript objects, and publishes the result to an Amazon SNS topic.

AWS Data Pipelines LLMs Serverless

Read original post

Related reading

Stripe · Feb 27, 2025
Building serverless usage notification with AWS
Pay-as-you-go services need a way to warn customers when consumption reaches a configured limit, but building usage aggregation, monitoring, and notification workflows adds operational complexity. This tutorial uses Stripe Billing Alerts to define a customer-specific usage threshold with a customer_id, meter_id, gte value, and recurrence, then sends billing.alert.triggered events through Stripe Event Destinations to an Amazon EventBridge partner event source. It tests the flow with Stripe Meter Events and shows AWS CLI rules routing the event to Amazon SNS, as well as a Lambda example that retrieves the customer's email from Stripe and sends mail with Amazon SES. The result is a minimal-code notification path using AWS services, with sandbox setup required because some APIs and features may not be available in conventional test mode.
Hidetaka Okamoto
Stripe · Dec 9, 2024
Enhance your monitoring by integrating Stripe events with AWS CloudWatch Log Groups
Stripe events notify account owners about changes such as successful charges, failed invoice payments, and available reconciliation reports. Because Stripe retains events for 13 months but exposes older events than 30 days only as summaries, Amazon EventBridge can route them into an AWS account and Amazon CloudWatch Log Groups can provide longer-term monitoring and analysis. The setup uses CloudWatch metric filters to match event types such as invoice.payment_failed, convert matches into custom metrics, and support alarms, Amazon SNS notifications, dashboards, and Logs Insights queries. For example, a failed-invoice alarm can use a five-minute observation period, Sum statistics, and a threshold based on expected failure volume or anomaly detection. The resulting setup supports near-real-time visibility into successful charges and failed payments, historical trend analysis, troubleshooting, and responses to unusual activity.
Andrew Robinson
Stripe · Oct 31, 2024
Growing your Stripe integration With Event Destinations
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.
Ben Smith
Stripe · Aug 29, 2024
Bringing your Stripe objects to life with Workbench
The post demonstrates how Stripe Workbench’s Inspector can be used to examine a PaymentIntent throughout its lifecycle and diagnose payment workflow issues. It maps states including requires_payment_method, processing, requires_action, succeeded, and canceled, showing how the status property changes as inputs and decisions move the object through a state machine. The walkthrough creates and confirms test PaymentIntents with Stripe Shell commands, including a 3DS-required card that produces a requires_action state and a use_stripe_sdk next_action. It also describes reacting to state changes through webhook endpoints or Amazon EventBridge, using the Inspector to identify friction such as PaymentIntents stalled at requires_action and to debug abandoned payments.
Ben Smith