Connect AWS Lambda and Stripe to unlock the power of automation
- No credit card required
- Free forever for core features
- 14-day trial for premium features and apps
Set up your first integration
Quickly connect AWS Lambda to Stripe with a Zapier template.
Our most popular template
How Zapier works
Zapier makes it easy to integrate AWS Lambda with Stripe - no code necessary. See how you can get setup in minutes.
Choose a trigger
A trigger is the event that starts your Zap—like a "New Function" from AWS Lambda.
Add your action
An action happens after the trigger—such as "Cancel Subscription" in Stripe.
You’re connected!
Zapier seamlessly connects AWS Lambda and Stripe, automating your workflow.
Supported triggers and actions
Zapier helps you create workflows that connect your apps to automate repetitive tasks. A trigger is an event that starts a workflow, and an action is an event a Zap performs.
- Region
Try ItTriggerPolling- Region
- FunctionRequired
- ArgumentsRequired
ActionWrite- Canceled Subscription
Triggers when a subscription is canceled (by a subscriber or due to end of billing period).
Try ItTriggerInstant - Failed Payment
Triggers when a payment attempt fails.
Try ItTriggerInstant
- Region
- FunctionRequired
- ArgumentsRequired
ActionWrite- Region
- ArgumentsRequired
- CodeRequired
ActionWrite- Checkout Session Completed
Triggers when a checkout session is completed.
Try ItTriggerInstant - Invoice Payment Failed
Triggers when an invoice payment fails.
Try ItTriggerInstant
Zapier is the automation platform of choice for 87% of Forbes Cloud 100 companies in 2023




93%
Customers who say using Zapier has made them better at their job
25m
Customers have created over 25 million Zaps on the platform
6 mins
The average user takes less than 6 minutes to set up a Zap
Learn how to automate Stripe on the Zapier blog
Frequently Asked Questions about AWS Lambda + Stripe integrations
New to automation with Zapier? You're not alone. Here are some answers to common questions about how Zapier works with AWS Lambda and Stripe
What is AWS Lambda and how does it integrate with Stripe?
AWS Lambda is a serverless compute service that runs your code in response to events and automatically manages the underlying compute resources. When integrated with Stripe, you can utilize AWS Lambda to automate tasks such as processing payments or handling webhooks by executing code in response to Stripe events.
How can I trigger an AWS Lambda function from a Stripe event?
You can trigger an AWS Lambda function from a Stripe event using Amazon API Gateway, which acts as the endpoint for Stripe webhooks. When a specific event occurs, like a successful payment or subscription created, Stripe sends an HTTP POST request to the API Gateway URL, which then invokes the appropriate Lambda function.
What permissions are needed to allow AWS Lambda to access Stripe?
To allow AWS Lambda to successfully interact with Stripe, you'll need to ensure that any API keys used by your Lambda functions have sufficient permissions. These are often managed through either IAM roles within AWS for executing functions or directly within your Stripe account settings.
Can I handle failed payment events from Stripe with AWS Lambda?
Yes, you can configure a webhook in Stripe for 'invoice.payment_failed' events and set it up through API Gateway to trigger an AWS Lambda function. The function could then execute your custom logic for handling such failures, such as retrying the payment or notifying customers via email.
How do we manage secrets or API keys for safe transactions between AWS Lambda and Stripe?
We manage secrets like Stripe API keys in a secure way by using AWS Secrets Manager or AWS Systems Manager Parameter Store. This ensures that sensitive information is encrypted at rest and accessible only during runtime by the authorized resources and functions.
Is it possible to perform batch processing of payments using AWS Lambda with Stripe?
Although AWS Lambda is excellent at handling individual events triggered by real-time actions, it isn't ideal for batch processing due to its timeout limitations. For batch processing payments on Stripe, we recommend considering other services or breaking down the task into smaller processes operated by multiple invocations of Lambdas.
Are there any limitations when using AWS Lambda with Stripe webhooks?
One limitation when setting up integrations involving Lambdas triggered by webhooks is cold start latency. Each time a new instance of your code runs due to inactivity, there might be an initial delay. Also, ensure that your function execution time does not exceed timeout limits set either side: on API Gateway integrations or inside your round trip processing logic.