Server-less Stripe push notifications with

November 17, 2012

If you haven't heard of []( yet, it's an interesting new service that lets you write [Lua]( scripts that respond web requests, and gives you a URL endpoint to execute the script."

If you haven’t heard of yet, it’s an interesting new service that lets you write Lua scripts that respond web requests, and you gives you a URL endpoint to execute the script.

I recently launched iOS push notifications for Pay Pad for Stripe. To do that, I had to spin up a new rails on app Heroku that processes Stripe Webhooks. Not that big of a deal because Heroku deployment is really simple. However, running a full-blown rails app on Heroku feels like over-kill when all I’m really doing is acting as proxy between Stripe and UrbanAirship. Sure you could make a sinatra app, or whatever thin app you favor, but still, you are going to git push heroku master every time you want to make a change.

After watching the intro video on I realized a webscript could do everything I needed to push notifications from Stripe webhooks. So lets build it shall we?

(This assumes that you already have a Stripe account and an UrbanAirship account, and that you know how to setup iOS APN’s (Apple Push Notifications) in Objective-C)

The Push Notification Script

I think you’ll be blown away by how simple this script is.

Ok so here’s what this code does. First, it parses the incoming Stripe webhook. It then takes the event id from the webhook and calls back to the Stripe events API to get the full event details. This is a best practice for processing Stripe webhooks. Next, we parse the response from Stripe and specifically look for the charge.succeeded event in the response body. Next we build a Lua table called payload that represents the parameters we are going to POST to UrbanSirship iOS Push API. For the alert, we are going to push a friendly message with the amount of the charge. Finally we convert our payload table to a JSON-encoded string and POST it to UrbanAirship.

Once you have the script ready, you can point your Stripe app to your url endpoint which look like this: http://demo-{code}{script-name}. When you are ready, create some charge.succedded transactions on your Stripe test account and poof, you’ve got push notifications!


One of the things that I struggled with was setting the header Content-Type to application/json, which is required by UrbanAirship. It took me a while to realize that the format needed to be passed into the headers table as ['Content-Type']. I tried Content-Type, content_type, and "Content-Type" before I figured it out. The Content-Type is set to application/x-www-form-urlencoded by default.

Is this production ready?

Surprisingly, I’d say yes, though with a guarded tone. I’ve done zero due diligence regarding security or scalibility for, but I trust Steve Marx, so there you go!

Update Please note that in this above Stripe example, it is assumed that the Stripe event is coming from your account. This was done for brevity. If your users connect to your app via Stripe connect, and you want to process their webhooks, you either need to skip the call back to Stripe to get the event data (I do not recommend you do this), or you’ll need to use that users api key, not yours.